From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Pawel Moll <pawel.moll@arm.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [virtio] Re: [PATCH v3 2/6] notifications: notifications as basic virtio facility
Date: Mon, 25 Jun 2018 16:37:16 +0200 [thread overview]
Message-ID: <20180625163716.048baaf1.cohuck@redhat.com> (raw)
In-Reply-To: <1529929292-11900-3-git-send-email-pasic@linux.ibm.com>
On Mon, 25 Jun 2018 14:21:28 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:
> Let's introduce notifications as basic virtio facility early on. This
> shall not only increase the cohesion between core and transport
> description by having a well-defined place where notifications are
> introduced, but also give us the opportunity to explain some
> discrepancies.
>
> Namely notifications sent by the device to the driver were often called
> interrupts prior to v1.1. Getting completely rid of that terminology is
> however not viable in case of some names.
>
> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> ---
> v2 -> v3:
> * Consistent use of 'configuration change notification' (instead
> of 'device configuration space notification' -- thanks Connie)
> * s/semantic/semantics/ and comma (thanks Stefan)
> ---
> content.tex | 36 ++++++++++++++++++++++++++++++++++++
> 1 files changed, 36 insertions(+), 0 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
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-06-25 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:21 [virtio] [PATCH v3 0/6] rework notifications terminology Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 1/6] notifications: unify notifications wording in core Halil Pasic
2018-06-25 14:45 ` [virtio] " Cornelia Huck
2018-06-25 15:15 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 2/6] notifications: notifications as basic virtio facility Halil Pasic
2018-06-25 14:37 ` Cornelia Huck [this message]
2018-06-25 12:21 ` [virtio] [PATCH v3 3/6] ccw: map common notifications terminology to ccw Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 4/6] pci: map common notifications terminology to PCI Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 5/6] mmio: map common notifications terminology to MMIO Halil Pasic
2018-06-25 14:34 ` [virtio] " Cornelia Huck
2018-06-25 12:21 ` [virtio] [PATCH v3 6/6] notifications: update notifications terminology for devices Halil Pasic
2018-07-02 15:51 ` [virtio] Re: [PATCH v3 0/6] rework notifications terminology Stefan Hajnoczi
2018-07-03 0:01 ` [virtio] Re: [virtio-dev] " Michael S. Tsirkin
2018-07-03 7:45 ` Cornelia Huck
2018-07-03 9:00 ` Halil Pasic
2018-07-03 12:07 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-07-17 16:47 ` Halil Pasic
2018-07-27 11:33 ` Halil Pasic
2018-07-27 11:45 ` Michael S. Tsirkin
2018-08-01 13:04 ` Halil Pasic
2018-08-01 22:30 ` Michael S. Tsirkin
2018-08-02 17:12 ` 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=20180625163716.048baaf1.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pawel.moll@arm.com \
--cc=stefanha@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