| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] VT-d: improve RMRR validity checking
|
To: |
Alex Williamson <alex.williamson@xxxxxx> |
|
Subject: |
Re: [Xen-devel] [PATCH] VT-d: improve RMRR validity checking |
|
From: |
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> |
|
Date: |
Tue, 9 Mar 2010 17:22:29 -0500 |
|
Cc: |
"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Noboru Iwamatsu <n_iwamatsu@xxxxxxxxxxxxxx>, Weidong Han <weidong.han@xxxxxxxxx>, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, "linux@xxxxxxxxxxxxxx" <linux@xxxxxxxxxxxxxx>, "keir.fraser@xxxxxxxxxxxxx" <keir.fraser@xxxxxxxxxxxxx> |
|
Delivery-date: |
Tue, 09 Mar 2010 14:40:08 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<7162ab21003091357v32b3c58qae708301fdf2764a@xxxxxxxxxxxxxx> |
|
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> |
|
References: |
<C77E162B.6FE6%keir.fraser@xxxxxxxxxxxxx> <4B59098B.6000108@xxxxxxxxx> <4B590FA4.4000008@xxxxxxxxxxxxxx> <4B59132B.40607@xxxxxxxxx> <4B59188C.50901@xxxxxxxxxxxxxx> <4B59660F.4000909@xxxxxxxxx> <7162ab21003091339i4adb8669safd5e074607386a2@xxxxxxxxxxxxxx> <20100309213026.GA12602@xxxxxxxxxxxxxxxxxxx> <7162ab21003091357v32b3c58qae708301fdf2764a@xxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.19 (2009-01-05) |
On Tue, Mar 09, 2010 at 02:57:00PM -0700, Alex Williamson wrote:
> On Tue, Mar 9, 2010 at 2:30 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@xxxxxxxxxx> wrote:
> > On Tue, Mar 09, 2010 at 02:39:10PM -0700, Alex Williamson wrote:
> >>
> >> I have a system with what I consider to be a valid DRHD that's getting
> >> tripped up on this patch. The problem is that the DRHD includes an
> >> IOAPIC scope, where the IOAPIC is not materialized on the PCI bus. I
> >> think Xen is being overzealous in it's validity checking and that this
> >> is a valid configuration. What do others think? Are IOAPICs a
> >
> > How does upstream Linux handle this?
>
> Last I checked, it works just fine, doesn't care that the IOAPIC isn't
> materialized.
This is from drivers/pci/intr_remapping.c (2.6.34-rc0):
795 if (ir_supported && ir_ioapic_num != nr_ioapics) {
796 printk(KERN_WARNING
797 "Not all IO-APIC's listed under remapping
hardware\n");
798 return -1;
799 }
800
ir_ioapic_num is figured out from the count of DRHD's.
So I think Linux would actually turn off VT-d.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home