From: "Michael S. Tsirkin" <mst@redhat.com>
To: Patrick Mosca <pmosca@apple.com>
Cc: Virtio-Dev <virtio-dev@lists.oasis-open.org>,
Cameron Esfahani <dirty@apple.com>
Subject: Re: [virtio-dev] Clarification of VIRTIO_F_EVENT_IDX driver conditions.
Date: Fri, 17 Jun 2022 06:30:21 -0400 [thread overview]
Message-ID: <20220617062446-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <F7C60FF0-08AC-4C61-B9C3-85C161818DE5@apple.com>
On Thu, Jun 16, 2022 at 01:53:38PM -0700, Patrick Mosca wrote:
> The issue may trigger in the unlikely uint16_t overflow case of
> computing the difference between two index positions.
Are you sure this is not an implementation bug? I don't see
anywhere in the spec where we suggest computing the difference
between two index positions.
> An
> example would be a network driver where the host and guest are
> producing and consuming steadily but at different rates. The
> producer is producing faster than the consumer such that the
> consumer never needed to be notified of new events, as it is
> still playing catch up processing the queue. If the producer
> finally catches up to the consumer and the catchup occurs just
> past the overflow point, there exists a case where a
> notification must be sent but is not sent according to the
> current ruleset.
>
> -Patrick Mosca
I don't see it sorry. Example?
--
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 prev parent reply other threads:[~2022-06-17 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:03 [virtio-dev] Clarification of VIRTIO_F_EVENT_IDX driver conditions Patrick Mosca
2022-06-05 20:29 ` Michael S. Tsirkin
2022-06-16 20:53 ` Patrick Mosca
2022-06-17 10:30 ` Michael S. Tsirkin [this message]
2022-06-24 22:39 ` Patrick Mosca
2022-08-11 16:58 ` Patrick Mosca
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=20220617062446-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dirty@apple.com \
--cc=pmosca@apple.com \
--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.