From: "Michael S. Tsirkin" <mst@redhat•com>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: ohad@wizery•com, kevin@guarana•org, kvm@vger•kernel.org,
mst@redhat•com, netdev@vger•kernel.org,
linux-remoteproc@vger•kernel.org, linux-kernel@vger•kernel.org,
stable@vger•kernel.org, bjorn.andersson@linaro•org,
syzbot+87cfa083e727a224754b@syzkaller•appspotmail.com,
virtualization@lists•linux-foundation.org
Subject: [PULL v2] vhost, virtio
Date: Thu, 14 Jun 2018 02:45:06 +0300 [thread overview]
Message-ID: <20180614024506-mutt-send-email-mst@kernel.org> (raw)
Page hints are reworked - I dropped them for now.
The following changes since commit 29dcea88779c856c7dc92040a0c01233263101d4:
Linux 4.17 (2018-06-03 14:15:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 2eb98105f8c7f4b867f7f714a998f5b8c1bb009b:
virtio: update the comments for transport features (2018-06-12 04:59:29 +0300)
----------------------------------------------------------------
virtio, vhost: features, fixes
VF support for virtio.
DMA barriers for virtio strong barriers.
Bugfixes.
Signed-off-by: Michael S. Tsirkin <mst@redhat•com>
----------------------------------------------------------------
Michael S. Tsirkin (2):
virtio_ring: switch to dma_XX barriers for rpmsg
vhost: fix info leak due to uninitialized memory
Tiwei Bie (2):
virtio_pci: support enabling VFs
virtio: update the comments for transport features
drivers/vhost/vhost.c | 3 +++
drivers/virtio/virtio_pci_common.c | 30 ++++++++++++++++++++++++++++++
drivers/virtio/virtio_pci_modern.c | 14 ++++++++++++++
include/linux/virtio_ring.h | 4 ++--
include/uapi/linux/virtio_config.h | 16 ++++++++++++----
5 files changed, 61 insertions(+), 6 deletions(-)
reply other threads:[~2018-06-13 23:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180614024506-mutt-send-email-mst@kernel.org \
--to=mst@redhat$(echo .)com \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=kevin@guarana$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-remoteproc@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ohad@wizery$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=syzbot+87cfa083e727a224754b@syzkaller$(echo .)appspotmail.com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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