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: follow up to a pciback "pv pci-passthrough co-assign

To: mail ignored <0.bugs.only.0@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
From: Weidong Han <weidong.han@xxxxxxxxx>
Date: Mon, 25 Jan 2010 09:44:58 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 24 Jan 2010 17:45:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c67eed301001231015v2c572d2fxb4a221157f3f1bfd@xxxxxxxxxxxxxx>
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: <c67eed301001221732s4b6a9a10p4be4182ecf831b6a@xxxxxxxxxxxxxx> <20100123123042.GG2861@xxxxxxxxxxx> <c67eed301001230840l2987a8adr81bf3dc53b2f8d58@xxxxxxxxxxxxxx> <20100123164850.GT2861@xxxxxxxxxxx> <c67eed301001230936o37dc63c2le944386cbaa02ff3@xxxxxxxxxxxxxx> <20100123174333.GW2861@xxxxxxxxxxx> <c67eed301001230945i45b8bb22q8cc3ded555cd7959@xxxxxxxxxxxxxx> <c67eed301001230954i6e9098fdwde189d429b8591fa@xxxxxxxxxxxxxx> <20100123175705.GY2861@xxxxxxxxxxx> <c67eed301001230958x2b22a5cs45df42cb956f75ed@xxxxxxxxxxxxxx> <c67eed301001231015v2c572d2fxb4a221157f3f1bfd@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
mail ignored wrote:
On Sat, Jan 23, 2010 at 9:58 AM, mail ignored <0.bugs.only.0@xxxxxxxxx> wrote:
thanks.  i suppose i'll file a bug @ opensuse abt this, and see if
they'll put something into code so these changes will 'survive'
xen(-tools) updates ...

cref -> https://bugzilla.novell.com/show_bug.cgi?id=573311

I think this is not a bug. pls note that the devices behind PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge can only be collectively assigned to a single domain, because the source-id in DMA requests is not device's bdf. Pls refer to section 3.6.1 in VT-d spec. What's more, FLR is required to make sure the device in a correct status before assignment, and some devices need to reset secondary bus to reset the device which results in all the devices behind same PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge be reset. In your case, you need to hide all NICs (04:06.0 and 04:07.0) behind the same bridge, and assign them together to a guest. or you can set "pci-passthrough-strict-check no" in /etc/xen/xend-config.sxp and restart xend to loose the check in xend, but in this way you should be aware of potential issues (e.g. assigned device doesn't work).

Regards,
Weidong


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

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