From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57632) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvUO6-0004e1-V2 for qemu-devel@nongnu.org; Mon, 22 Aug 2011 09:17:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QvUO6-0001g3-24 for qemu-devel@nongnu.org; Mon, 22 Aug 2011 09:17:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7703) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvUO5-0001fr-KA for qemu-devel@nongnu.org; Mon, 22 Aug 2011 09:17:58 -0400 Message-ID: <4E5256F5.3090909@redhat.com> Date: Mon, 22 Aug 2011 16:17:41 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1312932258.4524.55.camel@bling.home> <1312944513.29273.28.camel@pasglop> <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> In-Reply-To: <20110822131508.GG2079@amd.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] kvm PCI assignment & VFIO ramblings List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Roedel, Joerg" 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 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. -- error compiling committee.c: too many arguments to function