From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Dhanoa, Kully" <kully.dhanoa@intel.com>
Subject: [virtio] Re: [PATCH v8 00/16] packed ring layout spec
Date: Sun, 25 Feb 2018 20:43:19 +0200 [thread overview]
Message-ID: <20180225204144-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ee4e36ca-8eba-8ba4-84c5-ccc65ce1f641@linux.vnet.ibm.com>
On Fri, Feb 16, 2018 at 02:22:21PM +0100, Halil Pasic wrote:
>
>
> On 02/16/2018 08:20 AM, Michael S. Tsirkin wrote:
> > This addresses comments on v7. A compiled version can
> > be found under https://github.com/oasis-tcs/virtio-docs.git
> >
> > virtio-v1.1-packed-wd08-diff.pdf virtio-v1.1-packed-wd08.pdf
> >
> > for redline and clean versions, respectively.
> >
> > Note: please do not try to edit the pdf and post comments
> > in the edited file. Please post comments in a text
> > format, as pdfs are not archived with the list.
> >
> > TODO: support for actual passthrough devices will likely
> > require more new features, such as requirement for
> > stronger memory barriers.
> >
> > Thanks to everyone who commented! You know who you are.
> >
> > changes from v7:
> > - new notitfication_data feature, supported for all
> > transports and formats
> > - addressed all outstanding comments
>
> I don't agree about 'addressed all outstanding comments'. Should
> Remind you about the not addressed comments I find important in the
> v7 thread, or should I repeat the comments here?
>
> Regards,
> Halil
There were suggestions for improving the spec generally,
improving wording already present in the spec.
I was under the impression that we agreed to address this
separately from this proposal.
Let me know if that's not the case.
--
MST
---------------------------------------------------------------------
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-02-25 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 7:20 [PATCH v8 00/16] packed ring layout spec Michael S. Tsirkin
2018-02-16 13:22 ` [virtio] " Halil Pasic
2018-02-25 18:43 ` Michael S. Tsirkin [this message]
2018-02-16 17:02 ` Cornelia Huck
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=20180225204144-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=kully.dhanoa@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox