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] Secondary bus reset for VT-d device

To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-devel] Secondary bus reset for VT-d device
From: "Neo Jia" <neojia@xxxxxxxxx>
Date: Thu, 28 Aug 2008 22:15:36 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Han, Weidong" <weidong.han@xxxxxxxxx>
Delivery-date: Thu, 28 Aug 2008 22:16:00 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ry6Ng6UpcOycT9O/ig7il7OqfrJxsNsTpv9IUxISOg4=; b=hWDZWZ0a3Y5G0nw09n3rhM2w/iXUMOEObgvvS7Z5TCTvosPrYYR3l8IDGG8KIkLiXs UpvdPvkrFDzW9MUXnuZDruWOEwKurPoUxy5zfXEc2AF+TtxwgYcl2JdCj4RZd7bXzzTO jUBUauuCllITPTV5Ddgm5hlnJ/1FgFK1EBM2Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=rYGMzO23PGn8bSp/ei4E0Cc7UCXGEOo0ySj5EzlgMXPxF/LKA1FrypBO/YMYW0p2dX 5MAHqiOwsOwwYZ4+bgo2cXbCYUpCTdOFlckB2aeJKO6ZA/ENMx7fNB8aP7r6Ee4N9JI1 r/hwYu3JfWKoPOVokFk+xtTZ3bBfbmIBe2XR8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <FE7BBCFBB500984A9A7922EBC95F516E019EF3D3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <5d649bdb0808282133p2a013669w63ccb399b32a8ec1@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808282144u59f75ba6r57eb8b13621c942e@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3D3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Can I trigger it manually? What happens if I just use setpci to do a
"secondary bus reset"? Will Xen be able to check if the host BARs are
enabled for the device before putting it into the guest?

Thanks,
Neo

On Thu, Aug 28, 2008 at 10:11 PM, Cui, Dexuan <dexuan.cui@xxxxxxxxx> wrote:
> Now the FLR is done automatically when a domain is destroyed (such as "xm 
> destroy/reboot/shutdown" a domain, or the domain shutdowns normally or 
> crashes) .
>
> -- Dexuan
>
>
> -----Original Message-----
> From: Neo Jia [mailto:neojia@xxxxxxxxx]
> Sent: 2008年8月29日 12:45
> To: Cui, Dexuan
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Han, Weidong
> Subject: Re: [Xen-devel] Secondary bus reset for VT-d device
>
> Thanks! But, how to trigger it? Is there a separate command I can
> issue or it is done automatically after reboot/shutdown guest?
>
> Neo
>
> 2008/8/28 Cui, Dexuan <dexuan.cui@xxxxxxxxx>:
>> Yes. When FLR-ing device, if the device lacks proper FLR capability (PCIe 
>> FLR, PCI Advanced Capabilities or ssomething), we will try SecondaryBusReset.
>> Currently the FLR is done in xend.
>>
>> -- Dexuan
>>
>>
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Neo Jia
>> Sent: 2008年8月29日 12:34
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Cc: Han, Weidong
>> Subject: [Xen-devel] Secondary bus reset for VT-d device
>>
>> hi,
>>
>> Did the current Xen in unstable branch already support the secondary
>> bus reset for VT-d devices?
>>
>> Thanks,
>> Neo
>> --
>> I would remember that if researchers were not ambitious
>> probably today we haven't the technology we are using!
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>
>
>
> --
> I would remember that if researchers were not ambitious
> probably today we haven't the technology we are using!
>



-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel