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

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

Thanks,

I will apply all parts of these kexec patches into xen-unstable directly,
including the ia64 portions.

 -- Keir

On 27/2/08 19:58, "Alex Williamson" <alex.williamson@xxxxxx> wrote:

> Hi Simon,
> 
>    These look ok to me.  Ack.  Thanks,
> 
> Alex
> 
> On Wed, 2008-02-27 at 16:10 +0900, Simon Horman wrote:
>> this series makes use of the extra regions that can be
>> retrieved using the kexec hypercall, as per patches posted
>> in a separate series.
>> 
>> This allows all regions that kexec needs to avoid to be retrieved
>> from the hypervisor. The patch set also places all of these
>> regions into /proc/iomem_machine - previously some where in
>> /proc/iomem_machine and some where in /proc/iomem.
>> 
>> 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.
>> 
>> As well as the related xen patches, there are also 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.
>> 



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