From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Roedel, Joerg" Subject: Re: kvm PCI assignment & VFIO ramblings Date: Mon, 22 Aug 2011 16:37:12 +0200 Message-ID: <20110822143712.GH2079@amd.com> References: <1313859105.6866.192.camel@x201.home> <4E51F782.7060005@redhat.com> <20110822104635.GC2079@amd.com> <4E5234B7.7000700@redhat.com> <20110822123651.GD2079@amd.com> <4E524EBB.8090603@redhat.com> <20110822125502.GF2079@amd.com> <4E52543F.70104@redhat.com> <20110822131508.GG2079@amd.com> <4E5256F5.3090909@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Alex Williamson , chrisw , Alexey Kardashevskiy , "kvm@vger.kernel.org" , Paul Mackerras , Benjamin Herrenschmidt , qemu-devel , iommu , Anthony Liguori , "linux-pci@vger.kernel.org" , linuxppc-dev , "benve@cisco.com" To: Avi Kivity Return-path: Content-Disposition: inline In-Reply-To: <4E5256F5.3090909@redhat.com> Sender: linux-pci-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, Aug 22, 2011 at 09:17:41AM -0400, Avi Kivity wrote: > On 08/22/2011 04:15 PM, Roedel, Joerg wrote: > > On Mon, Aug 22, 2011 at 09:06:07AM -0400, Avi Kivity wrote: > > > On 08/22/2011 03:55 PM, Roedel, Joerg wrote: > > > > > > Well, I don't think its really meaningless, but we need some way to > > > > communicate the information about device groups to userspace. > > > > > > I mean the contents of the group descriptor. There are enough 42s in > > > the kernel, it's better if we can replace a synthetic number with > > > something meaningful. > > > > If we only look at PCI than a Segment:Bus:Dev.Fn Number would be > > sufficient, of course. But the idea was to make it generic enough so > > that it works with !PCI too. > > > > We could make it an arch defined string instead of a symlink. So it > doesn't return 42, rather something that can be used by the admin to > figure out what the problem was. Well, ok, it would certainly differ from the in-kernel representation then and introduce new architecture dependencies into libvirt. But if the 'group-string' is more meaningful to users then its certainly good. Suggestions? Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from VA3EHSOBE007.bigfish.com (va3ehsobe006.messaging.microsoft.com [216.32.180.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Microsoft Secure Server Authority" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 9EE38B6F65 for ; Tue, 23 Aug 2011 00:38:16 +1000 (EST) Date: Mon, 22 Aug 2011 16:37:12 +0200 From: "Roedel, Joerg" To: Avi Kivity Subject: Re: kvm PCI assignment & VFIO ramblings Message-ID: <20110822143712.GH2079@amd.com> References: <1313859105.6866.192.camel@x201.home> <4E51F782.7060005@redhat.com> <20110822104635.GC2079@amd.com> <4E5234B7.7000700@redhat.com> <20110822123651.GD2079@amd.com> <4E524EBB.8090603@redhat.com> <20110822125502.GF2079@amd.com> <4E52543F.70104@redhat.com> <20110822131508.GG2079@amd.com> <4E5256F5.3090909@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: <4E5256F5.3090909@redhat.com> Cc: Alexey Kardashevskiy , "kvm@vger.kernel.org" , Paul Mackerras , qemu-devel , iommu , chrisw , Alex Williamson , Anthony Liguori , "linux-pci@vger.kernel.org" , linuxppc-dev , "benve@cisco.com" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Aug 22, 2011 at 09:17:41AM -0400, Avi Kivity wrote: > On 08/22/2011 04:15 PM, Roedel, Joerg wrote: > > On Mon, Aug 22, 2011 at 09:06:07AM -0400, Avi Kivity wrote: > > > On 08/22/2011 03:55 PM, Roedel, Joerg wrote: > > > > > > Well, I don't think its really meaningless, but we need some way to > > > > communicate the information about device groups to userspace. > > > > > > I mean the contents of the group descriptor. There are enough 42s in > > > the kernel, it's better if we can replace a synthetic number with > > > something meaningful. > > > > If we only look at PCI than a Segment:Bus:Dev.Fn Number would be > > sufficient, of course. But the idea was to make it generic enough so > > that it works with !PCI too. > > > > We could make it an arch defined string instead of a symlink. So it > doesn't return 42, rather something that can be used by the admin to > figure out what the problem was. Well, ok, it would certainly differ from the in-kernel representation then and introduce new architecture dependencies into libvirt. But if the 'group-string' is more meaningful to users then its certainly good. Suggestions? Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvVdm-0000vr-Rq for qemu-devel@nongnu.org; Mon, 22 Aug 2011 10:38:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QvVdk-0002Zu-ON for qemu-devel@nongnu.org; Mon, 22 Aug 2011 10:38:14 -0400 Received: from va3ehsobe006.messaging.microsoft.com ([216.32.180.16]:21763 helo=VA3EHSOBE007.bigfish.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvVdk-0002ZY-Lx for qemu-devel@nongnu.org; Mon, 22 Aug 2011 10:38:12 -0400 Date: Mon, 22 Aug 2011 16:37:12 +0200 From: "Roedel, Joerg" Message-ID: <20110822143712.GH2079@amd.com> References: <1313859105.6866.192.camel@x201.home> <4E51F782.7060005@redhat.com> <20110822104635.GC2079@amd.com> <4E5234B7.7000700@redhat.com> <20110822123651.GD2079@amd.com> <4E524EBB.8090603@redhat.com> <20110822125502.GF2079@amd.com> <4E52543F.70104@redhat.com> <20110822131508.GG2079@amd.com> <4E5256F5.3090909@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <4E5256F5.3090909@redhat.com> Subject: Re: [Qemu-devel] kvm PCI assignment & VFIO ramblings List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Alexey Kardashevskiy , "kvm@vger.kernel.org" , Paul Mackerras , qemu-devel , iommu , chrisw , Alex Williamson , "linux-pci@vger.kernel.org" , linuxppc-dev , "benve@cisco.com" On Mon, Aug 22, 2011 at 09:17:41AM -0400, Avi Kivity wrote: > On 08/22/2011 04:15 PM, Roedel, Joerg wrote: > > On Mon, Aug 22, 2011 at 09:06:07AM -0400, Avi Kivity wrote: > > > On 08/22/2011 03:55 PM, Roedel, Joerg wrote: > > > > > > Well, I don't think its really meaningless, but we need some way to > > > > communicate the information about device groups to userspace. > > > > > > I mean the contents of the group descriptor. There are enough 42s in > > > the kernel, it's better if we can replace a synthetic number with > > > something meaningful. > > > > If we only look at PCI than a Segment:Bus:Dev.Fn Number would be > > sufficient, of course. But the idea was to make it generic enough so > > that it works with !PCI too. > > > > We could make it an arch defined string instead of a symlink. So it > doesn't return 42, rather something that can be used by the admin to > figure out what the problem was. Well, ok, it would certainly differ from the in-kernel representation then and introduce new architecture dependencies into libvirt. But if the 'group-string' is more meaningful to users then its certainly good. Suggestions? Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632