virtio — archive

[PATCH v3 0/6] rework notifications terminology

From: Cornelia Huck <[email protected]>
To: [email protected]
Date: Tue, 03 Jul 2018 07:46:00 -0000

On Tue, 3 Jul 2018 03:01:56 +0300 "Michael S. Tsirkin" <[email protected]> wrote: > On Mon, Jun 25, 2018 at 02:21:26PM +0200, Halil Pasic wrote: > > Abstract > > -------- > > The terminology around notifications is currently somewhat > > fragmented. Unify notifications terminology using available and used > > buffer notification consistently for the virtqueue notifications. > > Consistent use of the term configuration change notification is of > > concern. > > OK I see there are acks already - do you want to start voting on this? Let's do that, the less dangling series we have, the better. > > > > > Changelog: > > --------- > > v2 -> v3: > > * Addressed all comments from the previous round > > * Added r-b's > > > > v1 -> v2: > > * Addressed Stefan's comments (mostly typos, grammar and inconsistencies). > > Thanks Stefan! > > * Rebased onto the current master. > > > > RFC -> v1: > > * Devices and the transports PCI and MMIO were omitted. > > Now the rework should be complete. > > * Addressed review comments and minor changes for the first > > three patches. > > > > Halil Pasic (6): > > notifications: unify notifications wording in core > > notifications: notifications as basic virtio facility > > ccw: map common notifications terminology to ccw > > pci: map common notifications terminology to PCI > > mmio: map common notifications terminology to MMIO > > notifications: update notifications terminology for devices > > > > cl-os.tex | 2 +- > > conformance.tex | 10 ++-- > > content.tex | 164 +++++++++++++++++++++++++++++++++++++++++ ------------- > > packed-ring.tex | 60 +++++++++++ --------- > > split-ring.tex | 72 ++++++++++++++ ---------- > > 5 files changed, 206 insertions(+), 102 deletions(-) > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected]