[Xen-devel] Re: [patch 0/3] xen: Extend xen kexec hypercall to return additional regions

[Alex Williamson <alex.williamson@xxxxxx>]

Hi Simon,

   I'm not seeing how this doesn't break the x86 COMPAT/CONFIG_COMPAT
code paths.  Where does kexec_get_range_internal() get defined for
COMPAT in [1/3], and where is machine_kexec_get_xen() defined for
CONFIG_COMPAT in [2/3]?  I'm fine with the ia64 parts if Ian/Keir want
to check them into the main tree, but there is some mixed indenting in
[3/3].  Thanks,

        Alex

On Wed, 2008-02-27 at 16:01 +0900, Simon Horman wrote:
> Hi,
> 
> this series starts off by reworking the hypercall a bit to
> allow it to have architecture-specific code under xen/arch/
> 
> It then extends the hypercall for some extra regions that
> are needed for xen ia64.
> 
> There are generic and ia64 specific patches in this series.
> I wanted to post them together as they don't make much sense
> without each other.
> 
> There are related xen-linux patches that I will send as a separate series.
> There are related kexec-tools patches which I have posted to
> the kexec mailing list and intend to merge.
>   http://lists.infradead.org/pipermail/kexec/2008-February/001348.html
> 
> 
> The end-game here is to make sure that all the reserved regions
> show up in /proc/iomem_machine on ia64. This currently does not happen.
> And manifests as kexec only being able to be performed once as
> the boot parameter ends up being overwritten in relocate_kernel before
> purgatory is reached.
> 
>   Xen--kexec-->Xen--kexec [hang in purgatory!]
> 
> 
> The EFI-RID patches for ia64 xen kexec are also needed for kexec
> to function on ia64. However they touch different code paths and can
> be merged separately.
> 
-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel