From xen-devel-bounces@lists.xen.org Mon Nov 04 16:22:38 2013 Received: (at maildrop) by bugs.xenproject.org; 4 Nov 2013 16:22:38 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1VdMvG-0006I1-9O for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Mon, 04 Nov 2013 16:22:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VdMs0-00064A-9G; Mon, 04 Nov 2013 16:19:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VdMry-00063y-Q3 for xen-devel@lists.xen.org; Mon, 04 Nov 2013 16:19:15 +0000 Received: from [85.158.137.68:40650] by server-6.bemta-3.messagelabs.com id BB/7C-23777-109C7725; Mon, 04 Nov 2013 16:19:13 +0000 X-Env-Sender: linux@eikelenboom.it X-Msg-Ref: server-2.tower-31.messagelabs.com!1383581953!1522532!1 X-Originating-IP: [84.200.39.61] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.12; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29560 invoked from network); 4 Nov 2013 16:19:13 -0000 Received: from vserver.eikelenboom.it (HELO smtp.eikelenboom.it) (84.200.39.61) by server-2.tower-31.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 4 Nov 2013 16:19:13 -0000 Received: from 225-69-ftth.on.nl ([88.159.69.225]:53195 helo=[172.16.1.20]) by smtp.eikelenboom.it with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1VdMmn-000220-Ag; Mon, 04 Nov 2013 17:13:53 +0100 Date: Mon, 4 Nov 2013 17:19:11 +0100 From: Sander Eikelenboom Organization: Eikelenboom IT services X-Priority: 3 (Normal) Message-ID: <357587126.20131104171911@eikelenboom.it> To: Ian Campbell In-Reply-To: <1383579925.8826.102.camel@kazak.uk.xensource.com> References: <1383579925.8826.102.camel@kazak.uk.xensource.com> MIME-Version: 1.0 Cc: Saurabh Mishra , xen-devel@lists.xen.org Subject: Re: [Xen-devel] PCI Passthrough question (xm->xl migration in Xen 4.2.2) X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org Monday, November 4, 2013, 4:45:25 PM, you wrote: > create ^ > title it xl does not support specifying virtual function for passthrough device > thanks > On Thu, 2013-10-31 at 14:29 -0700, Saurabh Mishra wrote: >> In XM toolchain, we use to put pci = [ '0000:07:11.6=0@1a' ] but looks >> like in XL toolchain there is no way to specify function in the guest. > The code is a bit confusing, but that does appear to be the case. libxl > seems to have some degree of support but I can't see any code in xl (or > the libxlu helper library function which parses the PCI options) that > would support the =N@M syntax. > Given the lack of xl support there's a good chance that the libxl > support is relatively untested. FYI qemu-upstream xen passhthrough currently also doesn't support specifying a request for a certain dev/function nr. And it is vaguely related to the lacking ability to passthrough multifunction devices as multifunction devices. (the xm + qemu_trad require you to specify the virtual dev/func in this case, and additional some checks in libxl can't handle the multifunction mask and bail out early) >> Kindly let me know. >> >> >> XM - pci = [ '0000:07:11.6=0@1a' ] >> XL - pci = [ '0000:07:11.6@1a' ] >> >> >> In the guest VM we see that PCI device is getting 0 function in both >> the cases however, it may not work the same way in the future. > Do you happen to know (or can you easily do the experiment to find out) > what happens with '0000:07:11.6@1a' on xm? Does the guest see function 0 > or function 6? If it is 0 then I think we can safely say xl will not > change, but if it is 6 we'll have to have a think... > Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel