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

RE: [Xen-devel] RE: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Miroslav Rezanina <mrezanin@xxxxxxxxxx>
Subject: RE: [Xen-devel] RE: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_msg_read_remap_rte with acpi=off
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Tue, 20 Oct 2009 00:09:26 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 19 Oct 2009 09:09:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7024AEB.17E79%keir.fraser@xxxxxxxxxxxxx>
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: <EADF0A36011179459010BDF5142A457501CECA88D2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C7024AEB.17E79%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpQrfYaPJP/l2nLTzW4nI+GixWepgAA3Y3kAABH+R0AAFrlEgAENZwQAAF9fvAAAoPmkQAAZEDA
Thread-topic: [Xen-devel] RE: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_msg_read_remap_rte with acpi=off
Keir Fraser wrote:
> On 19/10/2009 15:46, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx> wrote:
> 
>>> But, can't you reproduce the crash I mentioned before?
>>> Please see the attached crash log -- I'm using c/s
>>> 20341:ea34183c5c11 and with "iommu=1 acpi=off" and I use a DQ35
>>> host. 
>>> 
>>> Actually what I care is the " if ( acpi_disabled ) iommu_enabled =
>>> 0". 
>> 
>> BTW: from my crash log, you can see the bogus info -- actually the
>> host doesn't support SC, QI and IR.
>> (XEN) Intel VT-d Snoop Control supported.
>> (XEN) Intel VT-d DMA Passthrough not supported.
>> (XEN) Intel VT-d Queued Invalidation supported.
>> (XEN) Intel VT-d Interrupt Remapping supported.
>> (XEN) I/O virtualisation enabled
> 
> Ah, hm, well maybe you need that too. Actually I checked in a slightly
> broader check as c/s 20342, which checks that
> !list_empty(acpi_drhd_units). If you have no such units then
> initialising IOMMU support is rather pointless. And if you did not do
> ACPI bootstrap then you cannot have parsed any units. So the check is
> at least as strong as checking !acpi_disabled, I think.
> 
> Hopefully everyone will be happy that this unlikely corner case,
> requiring the user to have actually shot themselves in the foot by
> manually specifying two contradictory boot parameters, is now solved
> to their satisfaction. ;-) 
Yes, I think 20342 should fix the issue. :-)

Thanks,
-- Dexuan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>