Re: [Xen-devel] [PATCH 0 of 7] Fix kexec in Xen (take 4)

[Keir Fraser <keir.xen@xxxxxxxxx>]

On 16/06/2011 14:05, "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx> wrote:

> One final thing to say,  These fixes are candidates for backport to 4.1
> as the kexec path is still broken there.

Since I think you ended up with their scope limited to the kexec paths only,
that should be doable.

 -- Keir

> ~Andrew
> 
> On 13/06/11 19:15, Keir Fraser wrote:
>> On 13/06/2011 18:02, "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx> wrote:
>> 
>>> This set of patches are partly bugfixed to problems I have noticed while
>>> working on this area of the codebase, and targeted fixes to get the kexec
>>> path
>>> working again on Xen 4.x
>>> 
>>> The first three patches are small bugfixes which are not directly related to
>>> the kexec problems, but are on the codepath.
>>> 
>>> The next four patches are directly related to fixing the kexec path.
>>> 
>>> These patches cause xen to track the BSP local APIC boot state and return to
>>> it before kexec'ing to a new kernel.  This prevents the kdump kernel falling
>>> over itself when booting in x2apic mode while expecting to be in xapic mode.
>>> 
>>> It also makes sure to disable IO virtualisation, along with fixing the
>>> current
>>> codepath related to disabling Interrup Remapping on Intel VTD boxes.
>> Overall looking much better! I will take a look at the patches individually,
>> and I expect Jan will be looking too. I think we may have a largely
>> check-in-able series here. :-)
>> 
>>  -- Keir
>> 
>>> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>> 



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