From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: [PATCH 0 of 6] Fix kexec in Xen (take 3) Date: Wed, 25 May 2011 15:32:02 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: Andrew Cooper List-Id: xen-devel@lists.xenproject.org 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 virtualisation. 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