All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ladi Prosek <lprosek@redhat.com>
Cc: qemu-devel@nongnu.org, vrozenfe@redhat.com, yvugenfi@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: Don't force Subsystem Vendor ID = Vendor ID
Date: Thu, 2 Nov 2017 16:52:26 +0200	[thread overview]
Message-ID: <20171102163348-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171102133115.19195-1-lprosek@redhat.com>

On Thu, Nov 02, 2017 at 02:31:15PM +0100, Ladi Prosek wrote:
> The statement being removed doesn't change anything as virtio PCI devices already
> have Subsystem Vendor ID set to pci_default_sub_vendor_id (0x1af4), same as Vendor
> ID. And the Virtio spec does not require the two to be equal, either:
> 
>   "The PCI Subsystem Vendor ID and the PCI Subsystem Device ID MAY reflect the PCI
>   Vendor and Device ID of the environment (for informational purposes by the driver)."
> 
> Background:
> 
> Following the recent virtio-win licensing change, several vendors are planning to
> ship their own certified version of Windows guest Virtio drivers, potentially taking
> advantage of Windows Update as a distribution channel. It is therefore critical that
> each vendor uses their own PCI Subsystem Vendor ID for Virtio devices to prevent
> drivers from other vendors binding to it.
> 
> This would be trivially done by adding:
> 
>   k->subsystem_vendor_id = ...
> 
> to virtio_pci_class_init(). Except for the problematic statement deleted by this
> patch, which reverts the Subsystem Vendor ID back to 0x1af4 for legacy devices for
> no good reason.
> 
> Signed-off-by: Ladi Prosek <lprosek@redhat.com>

I wonder whether it's a problem that legacy devices ignore
the subsystem ID (that's part of spec).

> ---
>  hw/virtio/virtio-pci.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> index e92837c42b..cb74aa3d85 100644
> --- a/hw/virtio/virtio-pci.c
> +++ b/hw/virtio/virtio-pci.c
> @@ -1589,8 +1589,6 @@ static void virtio_pci_device_plugged(DeviceState *d, Error **errp)
>              return ;
>          }
>          /* legacy and transitional */
> -        pci_set_word(config + PCI_SUBSYSTEM_VENDOR_ID,
> -                     pci_get_word(config + PCI_VENDOR_ID));


This happens to work because the default subsystem vendor id
within qemu is 0x1af4. Let's add a comment to that end.

>          pci_set_word(config + PCI_SUBSYSTEM_ID, virtio_bus_get_vdev_id(bus));
>      } else {
>          /* pure virtio-1.0 */
> -- 
> 2.13.5

  reply	other threads:[~2017-11-02 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 13:31 [Qemu-devel] [PATCH] virtio-pci: Don't force Subsystem Vendor ID = Vendor ID Ladi Prosek
2017-11-02 14:52 ` Michael S. Tsirkin [this message]
2017-11-03  6:25   ` Ladi Prosek
2017-11-03  7:20     ` Gerd Hoffmann
2017-11-03  8:23       ` Ladi Prosek
2017-11-03  8:44         ` Vadim Rozenfeld
2017-11-03 15:11         ` Michael S. Tsirkin
2017-11-06  9:02           ` Ladi Prosek
2017-11-06  9:18             ` Gerd Hoffmann
2017-11-06 16:53               ` Michael S. Tsirkin
2017-11-06 16:51             ` Michael S. Tsirkin
2017-11-07  8:30               ` Ladi Prosek
2017-11-03 15:03     ` Michael S. Tsirkin

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=20171102163348-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=lprosek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vrozenfe@redhat.com \
    --cc=yvugenfi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.