| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] VT-d: improve RMRR validity checking
|
To: |
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [PATCH] VT-d: improve RMRR validity checking |
|
From: |
Alex Williamson <alex.williamson@xxxxxx> |
|
Date: |
Tue, 9 Mar 2010 14:57:00 -0700 |
|
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 13:57:53 -0800 |
|
Dkim-signature: |
v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=CUBzw5aC9m5uNR+VA4fb3bd7evJPzpu9osJiXI4EqfA=; b=sx2iyhxcFIrz0/C1pmQy/CVHc/cCl7BF2RNDfU1Z3Rw3+Id+EFrI1eXB0uoL9VUve8 ISiGafhjXrw0nEMCWWtGJClTejSEfKDKmjqMr1u/dGvZi5Nt1rXbHZg6+eeY1T7sCqD4 6entNTePgZknHYdA0nsQ37mfclHu7F+QSgSNo= |
|
Domainkey-signature: |
a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=cWQiQCSVwqdae3qDVkloTOA8yI6ak63/t9zx+OiDJklsOFdGNydqvaU6vJrfx3hLF/ dGJ+Yone3AQKhYCgHQ15zfZuP0ujkGBrxLUCkFyGZ7BbXWpBA5DQBcw7J/Nh6GJfCw69 l+5HdxmXuaWyez7l7/+UQtO1mPYajDgZ/oqHo= |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20100309213026.GA12602@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> |
|
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> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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.
Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home