From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Graeme Gregory" <graeme.gregory@linaro.org>,
"lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>,
qemu-devel@nongnu.org,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Shannon Zhao" <zhaoshenglong@huawei.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio
Date: Thu, 30 Jul 2015 11:04:38 +0300 [thread overview]
Message-ID: <20150730105923-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <55B97C88.6010004@linaro.org>
On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote:
>
>
> On 2015/7/30 3:16, Michael S. Tsirkin wrote:
> > ACPI spec 5.0 allows the use of PCI vendor IDs.
> >
> But virtio-mmio is not a PCI device, it's a platform device.
Yes. ACPI spec 5.0 says:
A valid PNP ID must be of the form "AAA####" where A is an uppercase
letter and # is a hex digit. A valid ACPI ID must be of the form
"NNNN####" where N is an uppercase letter or a digit ('0'-'9') and # is
a hex digit. This specification reserves the string "ACPI" for use only
with devices defined herein.
It further reserves all strings representing 4 HEX digits for
exclusive use with PCI-assigned Vendor IDs.
The second paragraph means if PCI SIG assigned you an ID, you
can use that without need to register it with ASWG.
> Why do we drop the previous way using "QEMUXXXX"? Something I missed?
So that guests that bind to this interface will work fine with non QEMU
implementations of virtio-mmio.
It's just playing nice with others.
We could have done something similar to pvpanic as well, except we
didn't and guests using the QEMU prefix have been released,
so we have to keep using that.
> > Since we have one for virtio, it seems neater to use that
> > rather than LNRO. For the device ID, use 103F which is a legacy ID that
> > isn't used in virtio PCI spec - seems to make sense since virtio-mmio is
> > a legacy device but we don't know the correct device type.
> >
> > Guests should probably match everything in the range 1000-103F
> > (just like legacy pci drivers do) which will allow us to pass in the
> > actual ID in the future if we want to.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > hw/arm/virt-acpi-build.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> > index f365140..dea61ba 100644
> > --- a/hw/arm/virt-acpi-build.c
> > +++ b/hw/arm/virt-acpi-build.c
> > @@ -145,7 +145,7 @@ static void acpi_dsdt_add_virtio(Aml *scope,
> >
> > for (i = 0; i < num; i++) {
> > Aml *dev = aml_device("VR%02u", i);
> > - aml_append(dev, aml_name_decl("_HID", aml_string("LNRO0005")));
> > + aml_append(dev, aml_name_decl("_HID", aml_string("1AF4103F")));
> > aml_append(dev, aml_name_decl("_UID", aml_int(i)));
> >
> > Aml *crs = aml_resource_template();
> >
>
> --
> Shannon
next prev parent reply other threads:[~2015-07-30 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:16 [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Michael S. Tsirkin
2015-07-30 1:23 ` Shannon Zhao
2015-07-30 8:04 ` Michael S. Tsirkin [this message]
2015-07-30 9:21 ` Shannon Zhao
2015-07-30 15:02 ` Michael S. Tsirkin
2015-07-30 9:24 ` Peter Maydell
2015-07-30 9:37 ` G Gregory
2015-07-30 9:43 ` G Gregory
2015-07-30 15:05 ` Michael S. Tsirkin
2015-07-31 12:37 ` Peter Maydell
2015-08-03 12:09 ` Andrew Jones
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=20150730105923-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=graeme.gregory@linaro.org \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zhaoshenglong@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).