QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org,
	Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 1/2] pci id: clarify pci subsystem id usage
Date: Thu, 15 Oct 2026 09:45:45 +0100	[thread overview]
Message-ID: <atCSufyPp8vdreSI@redhat.com> (raw)
In-Reply-To: <20261015081544.40310-2-kraxel@redhat.com>

On Thu, Oct 15, 2026 at 10:15:43AM +0200, Gerd Hoffmann wrote:
> Qemu uses the pci subsystem id not only for emulated devices, but also
> for virtio devices and generic pci class devices such as pci bridges,
> xhci + nvme controllers etc.  Update the documentation accordingly.
> 
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>  docs/specs/pci-ids.rst | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/docs/specs/pci-ids.rst b/docs/specs/pci-ids.rst
> index 261b0f359fe5..832f8bd1b802 100644
> --- a/docs/specs/pci-ids.rst
> +++ b/docs/specs/pci-ids.rst
> @@ -46,8 +46,9 @@ maintained as part of the virtio specification.
>    upstream merge or shipping a distro/product) to avoid conflicts.
>  
>  1af4:1100
> -  Used as PCI Subsystem ID for existing hardware devices emulated
> -  by QEMU.
> +  Used as PCI Subsystem ID for existing hardware devices emulated by
> +  QEMU, such as the intel chipset devices.  Also used for virtio
> +  devices and generic pci class devices (1b36:00xx, see below).

When talking virtio devices, does that include virtio devices
implemented outside QEMU via vhostuser, or only in-QEMU virtio
devices ?

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



  reply	other threads:[~2026-10-15  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  8:15 [PATCH 0/2] pci id documentation updates Gerd Hoffmann
2026-10-15  8:15 ` [PATCH 1/2] pci id: clarify pci subsystem id usage Gerd Hoffmann
2026-10-15  8:45   ` Daniel P. Berrangé [this message]
2026-10-15 10:20     ` Gerd Hoffmann
2026-10-15 10:28       ` Daniel P. Berrangé
2026-10-15  8:15 ` [PATCH 2/2] pci id: assign pci subsystem id for osmates Gerd Hoffmann
2026-10-15  8:38   ` Daniel P. Berrangé

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=atCSufyPp8vdreSI@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.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