qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: missing entries from docs/specs/pci-ids.txt ?
Date: Tue, 27 Sep 2022 13:05:36 +0100	[thread overview]
Message-ID: <CAFEAcA9dcDNw6QvKSs8BZgjzueEPi0v6R5LAPpsiJU3J_p=AXw@mail.gmail.com> (raw)

I noticed today that docs/specs/pci-ids.txt doesn't have
an entry for the virtio-iommu, which is defined in pci.h as

#define PCI_DEVICE_ID_VIRTIO_IOMMU       0x1014

There seem to be a few other virtio ID values defined in the
header but not in the txt file too -- do we need to update it?

Conversely, none of the "modern" ID values in the txt file seem
to have a #define. I suspect I'm missing something about how
this works.

thanks
-- PMM


             reply	other threads:[~2022-09-27 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 12:05 Peter Maydell [this message]
2022-09-29 13:31 ` missing entries from docs/specs/pci-ids.txt ? Gerd Hoffmann
2022-09-29 13:48   ` Peter Maydell

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='CAFEAcA9dcDNw6QvKSs8BZgjzueEPi0v6R5LAPpsiJU3J_p=AXw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=kraxel@redhat.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;
as well as URLs for NNTP newsgroup(s).