[Qemu-devel] register QEMU ACPI ID

[Qemu-devel] register QEMU ACPI ID

[Michael S. Tsirkin]

Hello!
Please register the ACPI Vendor ID "QEMU" to the qemu emulator project.

Thanks!

-- 
MST

Re: [Qemu-devel] [aswg-chair] register QEMU ACPI ID

[Doran, Mark]

[-- Attachment #1: Type: text/plain, Size: 3800 bytes --]

Hi Michael:

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).

I don't know that naming a project that is not a legally identifiable entity
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 Red
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 name 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.

If a guess OS is required to load QEMU-specific drivers for certain "soft"
devices to function correctly then I think your use case should not run us
into any hard questions.  I asked just to make sure, not being personally
familiar with the way QEMU works at that level.

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 the
qemu-devel mailing list on the Forum internal list review thread as that one
is in a UEFI Forum Confidential venue).

Just reply and let me know whether you want me to go ahead with the project
as the named owner or not and I can take it from there.
--
Cheers,
 
Mark.
 

> -----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
> 
> 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 project
> > that's not a legally identifiable entity...that may raise an eyebrow
> > though because we haven't done it for ACPI IDs as yet.
> 
> 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 to
> Cc - can I do this?
> 
> >  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.
> 
> Yes. QEMU is a hypervisor, and so presents virtual devices and a set of
> ACPI tables describing them to operating systems it runs.
> 
> Some of these devices need the operating system within the guest to load
> matching drivers, and we've been using IDs such as QEMU0001 for this
> purpose.
> 
> 
> >
> > > -----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
> 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6283 bytes --]

[Qemu-devel] registering QEMU ACPI ID

[Michael S. Tsirkin]

Hello!
QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
it generates. This is a bit of a spec violation:
all IDs must be registered with the ASWG.

>From the ASWG point of view, things are easier if a legal entity owns a
vendor ID, so Red Hat could ask to own the ID on behalf of the
community.

I intend to ask the ASWG to register this ID for Red Hat 2 weeks from
now, July 7th.

If anyone has questions or concerns, please speak now.

Thanks!

-- 
MST

Re: [Qemu-devel] registering QEMU ACPI ID

[Peter Maydell]

On 23 June 2015 at 15:07, Michael S. Tsirkin <mst@redhat.com> wrote:
> Hello!
> QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
> it generates. This is a bit of a spec violation:
> all IDs must be registered with the ASWG.
>
> From the ASWG point of view, things are easier if a legal entity owns a
> vendor ID, so Red Hat could ask to own the ID on behalf of the
> community.
>
> I intend to ask the ASWG to register this ID for Red Hat 2 weeks from
> now, July 7th.

RedHat already officially "own" our PCI ID space (see
docs/specs/pci-ids.txt) so having them also deal with ACPI IDs
seems a reasonable plan to me.

Is the plan that we register "QEMU" as the vendor ID, or are the
ASWG likely to require a different ID string?

thanks
-- PMM

Re: [Qemu-devel] registering QEMU ACPI ID

[Michael S. Tsirkin]

On Tue, Jun 23, 2015 at 03:18:38PM +0100, Peter Maydell wrote:
> On 23 June 2015 at 15:07, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Hello!
> > QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
> > it generates. This is a bit of a spec violation:
> > all IDs must be registered with the ASWG.
> >
> > From the ASWG point of view, things are easier if a legal entity owns a
> > vendor ID, so Red Hat could ask to own the ID on behalf of the
> > community.
> >
> > I intend to ask the ASWG to register this ID for Red Hat 2 weeks from
> > now, July 7th.
> 
> RedHat already officially "own" our PCI ID space (see
> docs/specs/pci-ids.txt) so having them also deal with ACPI IDs
> seems a reasonable plan to me.
> 
> Is the plan that we register "QEMU" as the vendor ID, or are the
> ASWG likely to require a different ID string?
> 
> thanks
> -- PMM

Yes, I'd like to register "QEMU" since we are already using it.
A bit less work for everyone involved.  It seems free at this point.

-- 
MST

Re: [Qemu-devel] registering QEMU ACPI ID

[Michael S. Tsirkin]

On Tue, Jun 23, 2015 at 04:07:29PM +0200, Michael S. Tsirkin wrote:
> Hello!
> QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables
> it generates. This is a bit of a spec violation:
> all IDs must be registered with the ASWG.
> 
> From the ASWG point of view, things are easier if a legal entity owns a
> vendor ID, so Red Hat could ask to own the ID on behalf of the
> community.
> 
> I intend to ask the ASWG to register this ID for Red Hat 2 weeks from
> now, July 7th.
> 
> If anyone has questions or concerns, please speak now.
> 
> Thanks!

OK, no objections received, so I will now ask the acpi wg
to register "QEMU" to Red Hat.


> -- 
> MST

Re: [Qemu-devel] [aswg-chair] register QEMU ACPI ID

[Michael S. Tsirkin]

On Sun, May 10, 2015 at 06:52:28PM +0000, Doran, Mark wrote:
> Hi Michael:
> 
> 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).
> 
> I don't know that naming a project that is not a legally identifiable entity
> 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 Red
> 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 name 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.

> 
> If a guess OS is required to load QEMU-specific drivers for certain "soft"
> 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.
> 
> 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 the
> qemu-devel mailing list on the Forum internal list review thread as that one
> is in a UEFI Forum Confidential venue).
> 
> Just reply and let me know whether you want me to go ahead with the project
> 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,
>  
> Mark.
>  
> 
> > -----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
> > 
> > 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 project
> > > that's not a legally identifiable entity...that may raise an eyebrow
> > > though because we haven't done it for ACPI IDs as yet.
> > 
> > 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 to
> > Cc - can I do this?
> > 
> > >  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.
> > 
> > Yes. QEMU is a hypervisor, and so presents virtual devices and a set of
> > ACPI tables describing them to operating systems it runs.
> > 
> > Some of these devices need the operating system within the guest to load
> > matching drivers, and we've been using IDs such as QEMU0001 for this
> > purpose.
> > 
> > 
> > >
> > > > -----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
> > 
>