From: Cornelia Huck <cohuck@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Farhan Ali <alifm@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
Cornelia Huck <cohuck@redhat.com>
Subject: [PULL 0/9] vfio-ccw patches for 5.2
Date: Thu, 25 Apr 2019 11:15:50 +0200 [thread overview]
Message-ID: <20190425091559.15490-1-cohuck@redhat.com> (raw)
The following changes since commit 1c410fd6a561af452aba282b1cd3cabef2080d72:
s390/cpum_cf_diag: Add support for CPU-MF SVN 6 (2019-04-23 16:30:06 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20190425
for you to fetch changes up to d1ffa760d22aa1d8190478e5ef555c59a771db27:
vfio-ccw: Prevent quiesce function going into an infinite loop (2019-04-24 14:18:51 +0200)
----------------------------------------------------------------
- support for sending halt/clear requests to the device
- various bug fixes
----------------------------------------------------------------
Cornelia Huck (6):
vfio-ccw: make it safe to access channel programs
vfio-ccw: rework ssch state handling
vfio-ccw: protect the I/O region
vfio-ccw: add capabilities chain
s390/cio: export hsch to modules
vfio-ccw: add handling for async channel instructions
Farhan Ali (3):
vfio-ccw: Do not call flush_workqueue while holding the spinlock
vfio-ccw: Release any channel program when releasing/removing vfio-ccw
mdev
vfio-ccw: Prevent quiesce function going into an infinite loop
drivers/s390/cio/Makefile | 3 +-
drivers/s390/cio/ioasm.c | 1 +
drivers/s390/cio/vfio_ccw_async.c | 88 +++++++++++
drivers/s390/cio/vfio_ccw_cp.c | 21 ++-
drivers/s390/cio/vfio_ccw_cp.h | 2 +
drivers/s390/cio/vfio_ccw_drv.c | 81 ++++++----
drivers/s390/cio/vfio_ccw_fsm.c | 143 +++++++++++++++++-
drivers/s390/cio/vfio_ccw_ops.c | 227 ++++++++++++++++++++++++----
drivers/s390/cio/vfio_ccw_private.h | 48 +++++-
include/uapi/linux/vfio.h | 4 +
include/uapi/linux/vfio_ccw.h | 12 ++
11 files changed, 560 insertions(+), 70 deletions(-)
create mode 100644 drivers/s390/cio/vfio_ccw_async.c
--
2.17.2
next reply other threads:[~2019-04-25 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 9:15 Cornelia Huck [this message]
2019-04-25 9:15 ` [PULL 1/9] vfio-ccw: make it safe to access channel programs Cornelia Huck
2019-04-25 9:15 ` [PULL 2/9] vfio-ccw: rework ssch state handling Cornelia Huck
2019-04-25 9:15 ` [PULL 3/9] vfio-ccw: protect the I/O region Cornelia Huck
2019-04-25 9:15 ` [PULL 4/9] vfio-ccw: add capabilities chain Cornelia Huck
2019-04-25 9:15 ` [PULL 5/9] s390/cio: export hsch to modules Cornelia Huck
2019-04-25 9:15 ` [PULL 6/9] vfio-ccw: add handling for async channel instructions Cornelia Huck
2019-04-25 9:15 ` [PULL 7/9] vfio-ccw: Do not call flush_workqueue while holding the spinlock Cornelia Huck
2019-04-25 9:15 ` [PULL 8/9] vfio-ccw: Release any channel program when releasing/removing vfio-ccw mdev Cornelia Huck
2019-04-25 9:15 ` [PULL 9/9] vfio-ccw: Prevent quiesce function going into an infinite loop Cornelia Huck
2019-04-25 11:47 ` [PULL 0/9] vfio-ccw patches for 5.2 Martin Schwidefsky
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=20190425091559.15490-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.