[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Strange PCI Passthrough problem
- To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
- From: "Todd Deshane" <deshantm@xxxxxxxxx>
- Date: Fri, 10 Oct 2008 00:01:46 -0400
- Cc: xen-devel mailing list <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Thu, 09 Oct 2008 21:02:13 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=EV3AH5YEN90VH5TikdyIYGgkWGf+MrReRdqjMbf7OXcZI44SM09L/+qt2+YTVhLN8p eNNh0N78Rwmelz0AU2jI9rI+6a1uN/NogRz7l+TwRHOqyR+HOu4DHMGKQGSDht/wAsKc MB6u9KCPe9s6F3tutFZ77KoXbiBCZtqJx7Cs0=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
2008/10/9 Cui, Dexuan <dexuan.cui@xxxxxxxxx>
Hi Todd,
Can you attach the output log of 'lspci -tv' and 'lspci -xxx -vvv'?
Attached.
I'm afraid you meet with the co-assignment limit.
If a device(including multi-function device) hasn't a proper standard FLR method, we have to use the SecondaryBusReset as a FLR method, so we require the co-assignment.
You can refer to http://xenbits.xensource.com/xen-unstable.hg?rev/e61978c24d84 for details.
Thanks for the information.
Let me know if there is anything else I can do.
Cheers, Todd
Attachment:
lspci-tv
Description: Binary data
Attachment:
lspci-xxx-vvv
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
