From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, "Zhu,
Lingshan" <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com
Subject: [virtio-dev] spec inconsistency: Device Configuration Interrupt bit in ISR status
Date: Fri, 14 Jan 2022 08:39:50 -0500 [thread overview]
Message-ID: <20220114082838-mutt-send-email-mst@kernel.org> (raw)
The spec says (v1.1 4.1.4.5 ISR status capability):
The VIRTIO_PCI_CAP_ISR_CFG capability refers to at least a single byte, which contains the 8bit ISR
status field to be used for INT#x interrupt handling.
and
to avoid an extra access, simply reading this register resets it to 0 and causes the device to deassert the
interrupt.
In this way, driver read of ISR status causes the device to deassert an interrupt.
See sections 4.1.5.3 and 4.1.5.4 for how this is used.
and in 4.1.5.4 Notification of Device Configuration Changes
it says:
• If MSIX capability is disabled:
1. Set the second lower bit of the ISR Status field for the device.
2. Send the appropriate PCI interrupt for the device.
If MSIX capability is enabled:
1. If config_msix_vector is not NO_VECTOR, request the appropriate MSIX interrupt message for
the device, config_msix_vector sets the MSIX Table entry number.
all of the above make it looks like VIRTIO_PCI_CAP_ISR_CFG capability is
unused with MSIX.
This was actually the way the spec was understood by
Zhu Lingshan from Intel (Cc'd).
However, looking at the conformance statements, one finds out this is
not the case:
4.1.4.5.1 Device Requirements: ISR status capability
The device MUST present at least one VIRTIO_PCI_CAP_ISR_CFG capability.
The device MUST set the Device Configuration Interrupt bit in ISR status before sending a device configu
ration change notification to the driver.
If MSIX capability is disabled, the device MUST set the Queue Interrupt bit in ISR status before sending a
virtqueue notification to the driver.
which implies that the Device Configuration Interrupt bit is set unconditionally.
It is unfortunate that it does not copy this requirement in more places,
and that the non-conformance text is incomplete and does not
mention the MSI-X usage at all.
I propose to extend 4.1.4.5 ISR status capability and
4.1.5.4 Notification of Device Configuration Changes
to mention the MSI use.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2022-01-14 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 13:39 Michael S. Tsirkin [this message]
2022-01-14 16:33 ` [virtio-comment] Re: [virtio-dev] spec inconsistency: Device Configuration Interrupt bit in ISR status Cornelia Huck
2022-01-14 18:18 ` Michael S. Tsirkin
2022-01-17 6:15 ` [virtio-comment] " Jason Wang
2022-01-17 7:57 ` [virtio-dev] " Michael S. Tsirkin
2022-01-18 3:01 ` [virtio-comment] " Jason Wang
[not found] ` <e694e330-82a0-53c2-36b8-7d25885e4a97@intel.com>
2022-01-18 3:21 ` Jason Wang
2022-01-18 6:25 ` 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=20220114082838-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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 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.