From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: jasowang@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
virtio-dev@lists.oasis-open.org, wexu@redhat.com,
jfreimann@redhat.com, maxime.coquelin@redhat.com
Subject: Re: [RFC 0/3] virtio_ring: define flags as shifts consistently
Date: Fri, 7 Dec 2018 13:11:42 -0500 [thread overview]
Message-ID: <20181207131058-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20181207084842.13133-1-tiwei.bie@intel.com>
On Fri, Dec 07, 2018 at 04:48:39PM +0800, Tiwei Bie wrote:
> This is a follow up of the discussion in this thread:
> https://patchwork.ozlabs.org/patch/1001015/#2042353
How was this tested? I'd suggest building virtio
before and after the changes, stripped binary
should be exactly the same.
> Tiwei Bie (3):
> virtio_ring: define flags as shifts consistently
> virtio_ring: add VIRTIO_RING_NO_LEGACY
> virtio_ring: use new vring flags
>
> drivers/virtio/virtio_ring.c | 100 ++++++++++++++++++-------------
> include/uapi/linux/virtio_ring.h | 61 +++++++++++++------
> 2 files changed, 103 insertions(+), 58 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2018-12-07 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 8:48 [RFC 0/3] virtio_ring: define flags as shifts consistently Tiwei Bie
2018-12-07 8:48 ` [RFC 1/3] " Tiwei Bie
2018-12-07 8:48 ` [RFC 2/3] virtio_ring: add VIRTIO_RING_NO_LEGACY Tiwei Bie
2018-12-07 18:05 ` Michael S. Tsirkin
2018-12-08 13:33 ` Tiwei Bie
2018-12-07 8:48 ` [RFC 3/3] virtio_ring: use new vring flags Tiwei Bie
2018-12-07 18:10 ` Michael S. Tsirkin
2018-12-08 13:47 ` Tiwei Bie
2018-12-09 14:33 ` Michael S. Tsirkin
2018-12-07 18:11 ` Michael S. Tsirkin [this message]
2018-12-08 13:26 ` [RFC 0/3] virtio_ring: define flags as shifts consistently Tiwei Bie
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=20181207131058-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).