From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZFStR-0005cu-Mo for qemu-devel@nongnu.org; Wed, 15 Jul 2015 16:03:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZFStQ-0000lE-FS for qemu-devel@nongnu.org; Wed, 15 Jul 2015 16:03:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58429) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZFStQ-0000l8-9B for qemu-devel@nongnu.org; Wed, 15 Jul 2015 16:03:00 -0400 Date: Wed, 15 Jul 2015 23:02:57 +0300 From: "Michael S. Tsirkin" Message-ID: <20150715225707-mutt-send-email-mst@redhat.com> References: <20150428162442-mutt-send-email-mst@redhat.com> <20150510115413-mutt-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [aswg-chair] register QEMU ACPI ID List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Doran, Mark" Cc: "qemu-devel@nongnu.org" On Sun, May 10, 2015 at 06:52:28PM +0000, Doran, Mark wrote: > Hi Michael: >=20 > Fortunately the ID element of ACPI in and of itself can be discussed in > public forum venues so no problem to copy the mailing list (added to cc= for > this reply). >=20 > I don't know that naming a project that is not a legally identifiable e= ntity > will cause an issue. I just live in the school of not asking questions= that > I don't know the answers to for this sort of thing as much as possible.= If, > for example, it would equally make sense to name a company (like say Re= d > Hat) or an incorporated organization (like say Linux Foundation) then I= know > there's not going to be a question. There _may_ be no question about n= ame a > project as the owner; it's just an unknown so I wanted to bring that to= your > attention -- I'm not sure what your urgency is and/or whether searching= for > the absolute line of least resistance path matters to you or not. We have discussed this on the project mailing list. Everyone seems to be OK with simply making Red Hat Inc. the owner of the "QEMU" ACPI ID. Red Hat will own it on behalf of the community. This should make things simpler as Red Hat is a legal entity. >=20 > If a guess OS is required to load QEMU-specific drivers for certain "so= ft" > devices to function correctly then I think your use case should not run= us > into any hard questions. Exactly, OS needs this to load drivers for certain "soft" or "para-virtual" devices. > I asked just to make sure, not being personally > familiar with the way QEMU works at that level. >=20 > In other words, I don't think there are problems here, I'm just trying = to > make sure I know what to tell the review group (if anything) about a > slightly unusual request to minimize back-and-forth (I can't include th= e > qemu-devel mailing list on the Forum internal list review thread as tha= t one > is in a UEFI Forum Confidential venue). >=20 > Just reply and let me know whether you want me to go ahead with the pro= ject > as the named owner or not and I can take it from there. To conclude, please simply register the ID "QEMU" for Red Hat inc. > -- > Cheers, > =A0 > Mark. > =A0 >=20 > > -----Original Message----- > > From: Michael S. Tsirkin [mailto:mst@redhat.com] > > Sent: Sunday, May 10, 2015 3:09 AM > > To: Doran, Mark > > Subject: Re: [aswg-chair] register QEMU ACPI ID > >=20 > > On Fri, May 08, 2015 at 06:57:36PM +0000, Doran, Mark wrote: > > > Hi Michael: > > > > > > First, sorry for the delay in reply; entirely down to me I'm afraid= . > > > > > > That said, I anticipate there may be some questions raised if I ask > > > the work group to review this request. It's unusual but not > > > unprecedented to register something with UEFI on behalf of a projec= t > > > that's not a legally identifiable entity...that may raise an eyebro= w > > > though because we haven't done it for ACPI IDs as yet. > >=20 > > If this is a problem, we'd like to discuss this on the mailing list. > > I would like to add the project mailing list: qemu-devel@nongnu.org t= o > > Cc - can I do this? > >=20 > > > Secondly, I'm wondering what the intended use model is -- quasi > > > technical curiosity perhaps. Normally vendors IDs are used to make= up > > > device IDs that match device drivers to devices in the platform and= as > > > such it's usually a device vendor that has the need for an ID. Is > > > there some notional device "manufactured" by the QEMU project that > > > needs to be so identified?? Or are you considering some other kind= of > > > usage?? > > > > > > -- > > > Cheers, > > > > > > Mark. > >=20 > > Yes. QEMU is a hypervisor, and so presents virtual devices and a set = of > > ACPI tables describing them to operating systems it runs. > >=20 > > Some of these devices need the operating system within the guest to l= oad > > matching drivers, and we've been using IDs such as QEMU0001 for this > > purpose. > >=20 > >=20 > > > > > > > -----Original Message----- > > > > From: aswg-chair@uefi.org [mailto:aswg-chair@uefi.org] On Behalf = Of > > > > Michael S. Tsirkin > > > > Sent: Tuesday, April 28, 2015 7:29 AM > > > > To: qemu-devel@nongnu.org > > > > Cc: aswg-chair@uefi.org > > > > Subject: [aswg-chair] register QEMU ACPI ID > > > > > > > > Hello! > > > > Please register the ACPI Vendor ID "QEMU" to the qemu emulator > > project. > > > > > > > > Thanks! > > > > > > > > -- > > > > MST > >=20 >=20