Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1195848

Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio

From Peter Maydell <peter.maydell@linaro.org>
Newsgroups linux.kernel
Subject Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio
Date 2015-07-30 11:30 +0200
Message-ID <pRSk2-2Bd-17@gated-at.bofh.it> (permalink)
References <pRF3s-pr-1@gated-at.bofh.it> <pRKPv-9Z-5@gated-at.bofh.it> <pRR4C-Ty-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 30 July 2015 at 09:04, Michael S. Tsirkin <mst@redhat.com> wrote:
> On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote:
>>
>> 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.

I don't understand this sentence. If there are pre-existing
non-QEMU virtio-mmio implementations, then they're using
LNRO0005, and we should use it too. If there are going to
be implementations of virtio-mmio in future, then they will
use whatever identifier we pick here. Either way, we get
interoperability. I don't see any difference between our
saying "the ID for virtio-mmio is QEMU0005" and saying
"the ID for virtio-mmio is 1AF4103F".

(The latter seems unnecessarily opaque to me, to be honest.
At least an ID string QEMUxxxx gives you a clue where to
look for who owns the thing.)

Note also that strictly you don't mean "non-QEMU implementations
of virtio-mmio", you mean "non-QEMU implementations of the
ACPI tables". The hardware implementation of virtio-mmio
doesn't care at all about the ACPI ID. (In fact the most
plausible other-implementation would be UEFI using its
own (hard-coded) ACPI tables on top of a QEMU vexpress-a15
model or something similar.)

-- PMM
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v2] arm: change vendor ID for virtio-mmio "Michael S. Tsirkin" <mst@redhat.com> - 2015-07-29 21:20 +0200
  Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Shannon Zhao <shannon.zhao@linaro.org> - 2015-07-30 03:30 +0200
    Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio "Michael S. Tsirkin" <mst@redhat.com> - 2015-07-30 10:10 +0200
      Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Peter Maydell <peter.maydell@linaro.org> - 2015-07-30 11:30 +0200
        Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio G Gregory <graeme.gregory@linaro.org> - 2015-07-30 11:40 +0200
          Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio G Gregory <graeme.gregory@linaro.org> - 2015-07-30 11:50 +0200
        Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio "Michael S. Tsirkin" <mst@redhat.com> - 2015-07-30 17:10 +0200
      Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Shannon Zhao <zhaoshenglong@huawei.com> - 2015-07-30 11:30 +0200
        Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio "Michael S. Tsirkin" <mst@redhat.com> - 2015-07-30 17:10 +0200
  Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio Andrew Jones <drjones@redhat.com> - 2015-08-03 14:20 +0200

csiph-web