WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] IOMMU Interrupt Remapping query

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] IOMMU Interrupt Remapping query
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Mon, 6 Jun 2011 15:32:15 +0100
Delivery-date: Mon, 06 Jun 2011 07:35:05 -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: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
I am attempting to fix the kexec interactions with x2apic and iommu
functionality.  Part of this involves ensuring that all IOMMU
functionality is disabled, as the kdump kernels are not happy at having
their interrupts remapped without their knowledge.

I have introduced iommu_disable_x2apic_IR() onto the kexec path, but it
does not seem to actually disable interrupt remapping on Intel boxes
(Specifically the two Intel Nehalem boxes I am testing on).

Specifying iommu=no-intremap on the commandline causes everything to
work correctly, but leaving it out causes the kdump kernel to hang and
eventually reboot, as can be seen on the attached serial log.

The lines starting DBG: are extra debugging I have put in which shows
that the disable_IR() function is being called and writing to the registers.

This problem occurs with the XenServer version of 4.1.0 as well as on
xen-unstable at the moment.

Is there any hardware state which is not taken down by the disable
function, any subtle interactions which I have not taken account of?  I
have looked through the source and nothing pops out, but I am out of ideas.

Thanks in advance,

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

Attachment: andrewcoop-ohno-kdump-remap
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>