Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, "Zhu,
	Lingshan" <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com
Subject: [virtio-comment] Re: [virtio-dev] spec inconsistency: Device Configuration Interrupt bit in ISR status
Date: Fri, 14 Jan 2022 17:33:58 +0100	[thread overview]
Message-ID: <87y23iuvih.fsf@redhat.com> (raw)
In-Reply-To: <20220114082838-mutt-send-email-mst@kernel.org>

On Fri, Jan 14 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> 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.

I agree that it would make sense to be more explicit, especially if
people have already fallen into this trap.

My main question is: do we still have time to do this for 1.2? By the
proposed timeline, we need to have a vote open by Jan 17th (next
Monday), which is cutting it awfully close.

[We seem to have quite some last minute stuff, sigh.]


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2022-01-14 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 13:39 [virtio-dev] spec inconsistency: Device Configuration Interrupt bit in ISR status Michael S. Tsirkin
2022-01-14 16:33 ` Cornelia Huck [this message]
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=87y23iuvih.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox