From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: [virtio] [PATCH] pci: strengthen requirement of the correct subsystem id
Date: Mon, 28 Oct 2019 12:12:49 -0400 [thread overview]
Message-ID: <20191028161240.24806-1-mst@redhat.com> (raw)
If a hardware implementation of virtio does not have
the correct subsystem id, then drivers can't report
ir properly, or detect and work around bugs.
Change the requirement from MAY to SHOULD.
We can't make it a MUST since we did not require this
historically.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
content.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content.tex b/content.tex
index 4bcb728..8f1518c 100644
--- a/content.tex
+++ b/content.tex
@@ -562,7 +562,7 @@ \subsection{PCI Device Discovery}\label{sec:Virtio Transport Options / Virtio Ov
For example, the network card device with the Virtio Device ID 1
has the PCI Device ID 0x1041 or the Transitional PCI Device ID 0x1000.
-The PCI Subsystem Vendor ID and the PCI Subsystem Device ID MAY reflect
+The PCI Subsystem Vendor ID and the PCI Subsystem Device ID SHOULD reflect
the PCI Vendor and Device ID of the environment (for informational purposes by the driver).
Non-transitional devices SHOULD have a PCI Device ID in the range
--
MST
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next reply other threads:[~2019-10-28 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 16:12 Michael S. Tsirkin [this message]
2019-11-24 12:29 ` [virtio] [PATCH] pci: strengthen requirement of the correct subsystem id Michael S. Tsirkin
2019-11-25 6:41 ` Jan Kiszka
2019-11-25 8:22 ` Michael S. Tsirkin
2019-11-25 10:14 ` Cornelia Huck
2019-11-27 13:02 ` [virtio] Re: [virtio-dev] " 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=20191028161240.24806-1-mst@redhat.com \
--to=mst@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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