This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH 0 of 6] Fix kexec in Xen (take 3)

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0 of 6] Fix kexec in Xen (take 3)
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Wed, 25 May 2011 15:32:02 +0100
Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Delivery-date: Wed, 25 May 2011 07:33:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.4.3
This set of patches is designed to get the kexec path working again on Xen 4.x

kdump kernels can't boot if x2apic mode is enabled and the ACPI tables dont 
state this fact.  They also cant boot at all with interrupt remapping enabled.

These patches cause xen to track the BSP local APIC boot state and return to it 
before kexec'ing to a new kernel.  It also makes sure to disable IO 

One area which is problematic is disabling interrupt remapping.  
lapic_suspend() calls iommu_disable_x2apic_IR() which in a previous thread was 
deemed to be Intel specific and only works by chance on AMD boxes by effectivly 
being a NOP.  As lapic_suspend() is generic code, does this mean that we 
can't/don't ever disable interrupt remapping on AMD boxes?

Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Xen-devel mailing list