From: Shannon Zhao <shannon.zhao@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
G Gregory <graeme.gregory@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] virtio_mmio: add ACPI probing
Date: Wed, 29 Jul 2015 10:01:35 +0800 [thread overview]
Message-ID: <55B833FF.20107@linaro.org> (raw)
In-Reply-To: <CAFEAcA9dHQkSyz7_V6Mb-gr=bA9BUdg4sGCDG7mwK3yiau9=Gw@mail.gmail.com>
On 2015/7/29 5:10, Peter Maydell wrote:
> On 28 July 2015 at 21:28, G Gregory <graeme.gregory@linaro.org> wrote:
>> > On 28 July 2015 at 21:12, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> >> Mmm. I'm not terribly happy about stuff being in QEMU before the
>>> >> ACPI spec for it has been finalised. We should not be picking
>>> >> stuff randomly on the fly...
>>> >>
>>> >> If we want to fix the ACPI IDs QEMU is using for 2.4 then we
>>> >> really need to do that now (ie within the next day or two).
>>> >>
>> > It is upto the owner of the QEMU prefix to allocate numbers. This is
>> > not an issue for ACPI spec at all.
> I mean "the specification for how this device should be advertised
> in an ACPI table". I don't care whether that's an official ACPI
> consortium thing or something less official. The table is
> constructed by QEMU and read by the kernel (and possibly
> also by UEFI?), so everybody needs to agree on what the
> string is...
I agree with Peter. Maybe we should record these IDs at some place.
Since QEMU is owner of this device and we register QEMU in ASWG, the
official ID can be assigned by QEMU and the ID could(or should) be
"QEMUXXXX". But what's the exact ID for this virtio-mmio? That's what we
need to agree on and record.
P.S. I don't see "QEMU" in the list of approved Vendor IDs for ACPI.
http://www.uefi.org/sites/default/files/resources/PNPID_List.pdf
http://www.uefi.org/sites/default/files/resources/ACPIID_List.pdf
--
Shannon
next prev parent reply other threads:[~2015-07-29 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 9:44 [PATCH] virtio_mmio: add ACPI probing Graeme Gregory
2015-07-28 10:08 ` Michael S. Tsirkin
2015-07-28 10:12 ` Peter Maydell
2015-07-28 10:27 ` Michael S. Tsirkin
2015-07-28 10:33 ` G Gregory
2015-07-29 17:52 ` Peter Maydell
2015-07-29 18:03 ` Michael S. Tsirkin
2015-07-28 20:12 ` Peter Maydell
2015-07-28 20:28 ` G Gregory
2015-07-28 21:10 ` Peter Maydell
2015-07-29 2:01 ` Shannon Zhao [this message]
2015-07-29 10:01 ` Michael S. Tsirkin
2015-07-29 18:17 ` Michael S. Tsirkin
2015-08-27 14:55 ` Graeme Gregory
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B833FF.20107@linaro.org \
--to=shannon.zhao@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=graeme.gregory@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox