qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Denis V. Lunev" <den@virtuozzo.com>
Cc: qemu-devel@nongnu.org,
	Denis Plotnikov <den-plotnikov@yandex-team.ru>,
	Yan Vugenfirer <yvugenfi@redhat.com>,
	Vadim Rozenfeld <vrozenfe@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Ben Warren <ben@skyportsystems.com>
Subject: Re: [PATCH 1/1] qxl: add subsystem_vendor_id property
Date: Tue, 4 Oct 2022 10:00:31 +0200	[thread overview]
Message-ID: <20221004080031.kemfawvj5auyfrei@sirius.home.kraxel.org> (raw)
In-Reply-To: <78f7c71f-4232-505a-e865-8e921f63815e@virtuozzo.com>

  Hi,

> Anyway, we need to support different PCI sub-vendor IDs
> in order to be compliant with Microsoft WHQL rules. Though,
> actually, at my opinion this requirement has nothing in
> common with libvirt people. The most convenient way
> here would be to specify these properties within vendor
> machine types and this place is a perfect match as any
> respectable has its own machine type.

Yes, when wiring this up via vendor machine types there
is no need to touch libvirt.

> I would also think that PCI level is not a good place for that
> as we would not be able to apply this change blindly as at
> PCI level this change would be too global and the same
> was initially noted by Michael Tsirkin here
> 
> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg04384.html
> 
> Any thoughts?
> What should we do with the original patch from Ben? We
> still need an ability to expose vendor identity in QXL/virtio...

I'd suggest to add properties to PCIDevice then.  That will allow to
override the default subsystem id for both specific pci devices and
all pci devices.

take care,
  Gerd



      reply	other threads:[~2022-10-04  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 15:52 [PATCH 1/1] qxl: add subsystem_vendor_id property Denis V. Lunev
2022-09-29  7:37 ` Gerd Hoffmann
2022-10-04  5:41   ` Denis V. Lunev
2022-10-04  8:00     ` Gerd Hoffmann [this message]

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=20221004080031.kemfawvj5auyfrei@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=ben@skyportsystems.com \
    --cc=den-plotnikov@yandex-team.ru \
    --cc=den@virtuozzo.com \
    --cc=mst@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 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).