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] Bug when disabling/enabling a PT device with MSI enable

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Bug when disabling/enabling a PT device with MSI enabled
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Tue, 24 Nov 2009 22:27:38 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 24 Nov 2009 12:28:05 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UE2+Gzqyo9ju9ffWIAL8eZLUmJ6NyDBN9vkqoSe39Dw=; b=QMTqxI7C3CjBOtYOrUc8wrWPf2IcDCxgAzAMCbV2y5ICq3pIlEYeaFPtCnqU2yYGm7 qi6X0BxF/ERBsq0xH5b01ivzdBkLFbMq+YMhzvcD5Tmr2+WlTJLrIf/At2NHM/jM4Klz phuGaUCYKTU7SNk74unmHgT1sBbyNKOGz4J9M=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AmdN3YiEAW/E43RiE1pILUDG16oWJ5pBJT79DI4IdlkUCzDzMwYJm7EjM20n3UgVRe tfurSt+5g+obzssKQOJdly90oxQgB0YQT9j0qdm5M5RnAx1DMNTx96XjzTXR1KkylHMI pCwPtzqcWo1GYmnMXDBDJLvCm2KzSzzEPeXr8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091124194815.GB29566@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: <8686c3cd0911241042n1b6f84a9u3623518baa021cc2@xxxxxxxxxxxxxx> <20091124194815.GB29566@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Can u please supply more details? how can i fix this issue?
I think that when the hardware reset occured, the MSI was disabled,
and that needs to be re-enabled again... no?

On Tue, Nov 24, 2009 at 9:48 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Tue, Nov 24, 2009 at 08:42:49PM +0200, Tom Rotenberg wrote:
>> Hi,
>>
>> I am using the xen-3,4, and i am doing pass-through for a device with
>> MSI enabled (the device of-course supports MSI) to a domU with Windows
>> XP. When i disable and then re-enable the device using Windows device
>> manager, everything looks like it's working fine, but the device seems
>> to malfunction.
>> After digging a little bit, i saw that the problem is, because the bit
>> of the interrupt-status (bit 3) in the status register (offset 0x6 in
>> the PCI config space) was turned on somehow -  this proibably caused
>> the MSI to malfunction (because the IntX assertion was enabled - thus
>> disabling the MSI) - and this lead to the problem i experienced.
>>
>> Any ideas on how to solve this issue?
>
> Looks like QEMU is not doing its job. It ought to be tracking
> when an MSI devices transforms to a INTx PCI device (and vice-versa) and
> make the appropiate Xen calls. Look in ioemu-dir/hw/pass-through.c
>

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