From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
Tiwei Bie <tiwei.bie@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Dhanoa, Kully" <kully.dhanoa@intel.com>
Subject: Re: [virtio] [PATCH v12] VIRTIO_F_NOTIFICATION_DATA: extra data to devices
Date: Thu, 29 Mar 2018 15:04:55 +0200 [thread overview]
Message-ID: <20180329150455.179fe87c.cohuck@redhat.com> (raw)
In-Reply-To: <20180329154839-mutt-send-email-mst@kernel.org>
On Thu, 29 Mar 2018 15:52:34 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Mar 29, 2018 at 11:05:55AM +0200, Cornelia Huck wrote:
> > On Wed, 28 Mar 2018 20:21:47 +0300
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >
> > > On Wed, Mar 28, 2018 at 06:56:13PM +0200, Halil Pasic wrote:
> > > > The notifications *sent by the device to the driver (virtqueue or
> > > > configuration change)* are often referred to as *interrupts* but occasionally
> > > > also as notifications (e.g. 'host->guest notification').
> >
> > I think 'notifications' is a better term for these. I'm thinking of a
> > driver polling for outstanding notifications from the device, no
> > interrupts involved.
>
> In this context when polling there are no notifications - rememeber we are
> talking about notification suppression.
OK, that's my s390 background again. We can easily make notification
status available (setting indicators, making a subchannel status
pending), but not deliver an interrupt because the guest has not
enabled interrupts and polls instead. (In fact, such an operation mode
is not uncommon for the traditional s390 OSs.)
But we can also just keep this as-is, it's probably not confusing for
most people anyway.
---------------------------------------------------------------------
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 prev parent reply other threads:[~2018-03-29 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 16:37 [virtio] [PATCH v12] VIRTIO_F_NOTIFICATION_DATA: extra data to devices Michael S. Tsirkin
2018-03-28 16:56 ` Halil Pasic
2018-03-28 17:21 ` Michael S. Tsirkin
2018-03-29 9:05 ` Cornelia Huck
2018-03-29 12:52 ` Michael S. Tsirkin
2018-03-29 13:04 ` Cornelia Huck [this message]
2018-03-29 13:10 ` Michael S. Tsirkin
2018-03-29 14:15 ` Halil Pasic
2018-03-29 14:30 ` Michael S. Tsirkin
2018-04-02 15:34 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-04-03 14:32 ` Cornelia Huck
2018-03-28 22:30 ` [virtio] on spec clarifications Michael S. Tsirkin
2018-04-03 0:11 ` Halil Pasic
2018-04-08 20:57 ` Halil Pasic
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=20180329150455.179fe87c.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=kully.dhanoa@intel.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.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 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.