From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@hp.com>
Subject: Re: [PATCH] VT-d: improve RMRR validity checking
Date: Wed, 10 Mar 2010 11:06:54 -0700
Message-ID: <1268244414.14039.206.camel@8530w.home>
References: <C77E162B.6FE6%keir.fraser@eu.citrix.com>
	<4B59098B.6000108@intel.com> <4B590FA4.4000008@jp.fujitsu.com>
	<4B59132B.40607@intel.com> <4B59188C.50901@jp.fujitsu.com>
	<4B59660F.4000909@intel.com>
	<7162ab21003091339i4adb8669safd5e074607386a2@mail.gmail.com>
	<4B9706B3.3050903@intel.com> <1268191101.3015.30.camel@2710p.home>
	<4B9711CF.7030908@intel.com> <1268192253.3015.37.camel@2710p.home>
	<4B971F57.9000903@intel.com> <1268196438.3015.56.camel@2710p.home>
	<4B974438.3050806@intel.com>  <1268229408.14039.151.camel@8530w.home>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1268229408.14039.151.camel@8530w.home>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Weidong Han <weidong.han@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>, "Cihula,
	Joseph" <joseph.cihula@intel.com>, "Kay, Allen M" <allen.m.kay@intel.com>, "linux@eikelenboom.it" <linux@eikelenboom.it>, "keir.fraser@eu.citrix.com" <keir.fraser@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2010-03-10 at 06:56 -0700, Alex Williamson wrote:
> On Wed, 2010-03-10 at 15:03 +0800, Weidong Han wrote:
> > Can you post your Xen boot logs?

I'm not sure what you're looking for in a boot log, I think I've pretty
well described the problem.  Here's the relevant output:

(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec08000, GSI 24-47
(XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec10000, GSI 48-71
(XEN) Enabling APIC mode:  Phys.  Using 3 I/O APICs
(XEN) [VT-D]dmar.c:421:   Non-existent device (84:13.0) is reported in this DRHD's scope!
(XEN) [VT-D]dmar.c:443:   The DRHD is invalid due to there are devices under its scope are not PCI discoverable! Pls try option iommu=force or iommu=workaround_bios_bug if you really want VT-d
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.

apic_id 10 is the one described under the non-INCLUDE_PCI_ALL DRHD,
which is not materialized on the PCI bus.  The DMAR effectively breaks
down to:

DMAR
 - INTR_REMAP set

DRHD0
 - INCLUDE_PCI_ALL set
 - scope includes IOAPIC 8 & 0

DRHD1
 - INCLUDE_PCI_ALL *NOT* set
 - scope includes various PCI sub-hierarchies *AND* IOAPIC 10

DRHD0 and DRHD1 are on the same PCI segment (0x0) and are peers of one
another, so it's not possible to set INCLUDE_PCI_ALL on both DRHDs, and
it's incorrect to list IOAPIC 10 under DRHD0.

Thanks,

Alex