17 messages in com.xensource.lists.xen-ia64-develRe: [Patch][RFC] fix PAL_HALT ( is Re...
FromSent OnAttachments
Akio Takebe21 Jan 2007 05:56 
Isaku Yamahata21 Jan 2007 06:27 
Akio Takebe23 Jan 2007 18:43.patch
Isaku Yamahata23 Jan 2007 23:49 
Akio Takebe24 Jan 2007 01:35 
tgin...@free.fr24 Jan 2007 02:13 
Akio Takebe24 Jan 2007 02:28 
Tristan Gingold24 Jan 2007 03:19 
Alex Williamson24 Jan 2007 08:18 
Akio Takebe24 Jan 2007 15:26 
Akio Takebe24 Jan 2007 17:02 
Alex Williamson24 Jan 2007 18:08 
Tristan Gingold24 Jan 2007 19:09 
Xu, Anthony24 Jan 2007 19:25 
Akio Takebe25 Jan 2007 18:36 
Akio Takebe25 Jan 2007 18:36.patch, .patch
Akio Takebe26 Jan 2007 03:30 
Subject:Re: [Patch][RFC] fix PAL_HALT ( is Re: [Xen-ia64-devel] [RFC] dump core is failed for PAL_HALT)
From:tgin...@free.fr (tgin@free.fr)
Date:01/24/2007 02:13:56 AM
List:com.xensource.lists.xen-ia64-devel

Selon Isaku Yamahata <yama@valinux.co.jp>:

On Wed, Jan 24, 2007 at 11:43:37AM +0900, Akio Takebe wrote: [...] According to SDM vol2 11.9, PAL_HALT places cpu in low power state.

Correct.

So the current behaviour that xen/ia64 shutdown unconditionally is wrong.

Yes, but that's the code in linux/ia64. Why linux/ia64 doesn't call the shutdown EFI runtime service ? I don't know. Maybe Alex knows the answer.

CPU hot-unplug routine also calls cpu_halt(). In that case, only the targeted cpu should be halted. We don't want domain shutdown.

If the last vcpu calls PAL_HALT, the domain can be safely shut down.

Probably modifying machine_reboot() and machine_power_off() needs modification(paravirtualization) to call shutdown hypercall.

I think all the paravirtualization can be done through EFI+PAL calls.

Tristan.