From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 00/19] virtio: alignment issues
Date: Mon, 6 Apr 2020 23:44:05 -0400 (EDT) [thread overview]
Message-ID: <2049984978.20929266.1586231045581.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200407011612.478226-1-mst@redhat.com>
----- Original Message -----
>
>
> This is an alternative to
> vhost: force spec specified alignment on types
> which is a bit safer as it does not change UAPI.
> I still think it's best to change the UAPI header as well,
> we can do that as a follow-up cleanup.
>
> changes from v7:
> typo fix
> changes from v6:
> add missing header includes all over the place
> changes from v5:
> ack for mellanox patch
> fixup to remoteproc
> changes from v4:
> fixup to issues reported by kbuild
> changes from v3:
> tools/virtio fixes
> a bunch more cleanups that now become possible
>
> Changes from v2:
> don't change struct name, instead add ifndef
> so kernel does not see the legacy UAPI version.
>
> Jason, can you pls ack one of the approaches?
Btw, this sereis includes the bathing optimization which I think
should be done in another one.
Thanks
prev parent reply other threads:[~2020-04-07 3:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 1:16 [PATCH v8 00/19] virtio: alignment issues Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 01/19] tools/virtio: define aligned attribute Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 02/19] tools/virtio: make asm/barrier.h self contained Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 03/19] tools/virtio: define __KERNEL__ Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 04/19] virtio: add VIRTIO_RING_NO_LEGACY Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 05/19] virtgpu: pull in uaccess.h Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 06/19] virtio-rng: pull in slab.h Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 07/19] remoteproc: " Michael S. Tsirkin
2020-04-07 5:31 ` Bjorn Andersson
2020-04-07 1:16 ` [PATCH v8 08/19] virtio_input: " Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 09/19] virtio: stop using legacy struct vring in kernel Michael S. Tsirkin
2020-04-07 8:51 ` Stefan Hajnoczi
2020-04-07 1:16 ` [PATCH v8 10/19] vhost: force spec specified alignment on types Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 11/19] virtio: add legacy init/size APIs Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 12/19] virtio_ring: switch to virtio_legacy_init/size Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 13/19] tools/virtio: " Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 14/19] vop: " Michael S. Tsirkin
2020-04-07 1:16 ` [PATCH v8 15/19] remoteproc: " Michael S. Tsirkin
2020-04-07 5:30 ` Bjorn Andersson
2020-04-07 1:17 ` [PATCH v8 16/19] mellanox: " Michael S. Tsirkin
2020-04-07 1:17 ` [PATCH v8 17/19] vhost: option to fetch descriptors through an independent struct Michael S. Tsirkin
2020-04-07 1:17 ` [PATCH v8 18/19] vhost: use batched version by default Michael S. Tsirkin
2020-04-07 1:17 ` [PATCH v8 19/19] vhost: batching fetches Michael S. Tsirkin
2020-04-07 3:44 ` Jason Wang [this message]
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=2049984978.20929266.1586231045581.JavaMail.zimbra@redhat.com \
--to=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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