virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: jroedel@suse.de, kvm@vger.kernel.org, arnd@arndb.de,
	mst@redhat.com, netdev@vger.kernel.org, cohuck@redhat.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, pasic@linux.ibm.com
Subject: [PULL] virtio,vhost: cleanups and fixes
Date: Sat, 9 Mar 2019 22:44:35 -0500	[thread overview]
Message-ID: <20190309224435-mutt-send-email-mst@kernel.org> (raw)

The following changes since commit 1c163f4c7b3f621efff9b28a47abb36f7378d783:

  Linux 5.0 (2019-03-03 15:21:29 -0800)

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 cfdbb4ed31aa777d59b288810f66eb06249ee5b7:

  vhost: silence an unused-variable warning (2019-03-06 11:32:37 -0500)

----------------------------------------------------------------
virtio: fixes, cleanups

Several fixes, most notably fix for virtio on swiotlb systems.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Arnd Bergmann (1):
      vhost: silence an unused-variable warning

Cornelia Huck (3):
      virtio-ccw: diag 500 may return a negative cookie
      virtio-ccw: wire up ->bus_name callback
      virtio: hint if callbacks surprisingly might sleep

Halil Pasic (1):
      s390/virtio: handle find on invalid queue gracefully

Joerg Roedel (5):
      swiotlb: Introduce swiotlb_max_mapping_size()
      swiotlb: Add is_swiotlb_active() function
      dma: Introduce dma_max_mapping_size()
      virtio: Introduce virtio_max_dma_size()
      virtio-blk: Consider virtio_max_dma_size() for maximum segment size

Wei Wang (2):
      virtio-balloon: improve update_balloon_size_func
      virtio_balloon: remove the unnecessary 0-initialization

 Documentation/DMA-API.txt               |  8 ++++++++
 Documentation/virtual/kvm/s390-diag.txt |  3 ++-
 drivers/block/virtio_blk.c              | 10 ++++++----
 drivers/s390/virtio/virtio_ccw.c        | 12 +++++++++++-
 drivers/vhost/vhost.c                   |  2 +-
 drivers/virtio/virtio.c                 |  2 ++
 drivers/virtio/virtio_balloon.c         |  6 ++++--
 drivers/virtio/virtio_ring.c            | 11 +++++++++++
 include/linux/dma-mapping.h             |  8 ++++++++
 include/linux/swiotlb.h                 | 11 +++++++++++
 include/linux/virtio.h                  |  2 ++
 include/linux/virtio_config.h           | 13 +++++++++++++
 kernel/dma/direct.c                     | 11 +++++++++++
 kernel/dma/mapping.c                    | 14 ++++++++++++++
 kernel/dma/swiotlb.c                    | 14 ++++++++++++++
 15 files changed, 118 insertions(+), 9 deletions(-)

                 reply	other threads:[~2019-03-10  3:44 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=20190309224435-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=arnd@arndb.de \
    --cc=cohuck@redhat.com \
    --cc=jroedel@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).