From: Pierre Morel <pmorel@linux.ibm.com>
To: borntraeger@de.ibm.com
Cc: cohuck@redhat.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, frankja@linux.ibm.com,
akrowiak@linux.ibm.com, pasic@linux.ibm.com, david@redhat.com,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
freude@linux.ibm.com
Subject: [PATCH v2 0/1] s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem
Date: Mon, 18 Feb 2019 19:08:47 +0100 [thread overview]
Message-ID: <1550513328-12646-1-git-send-email-pmorel@linux.ibm.com> (raw)
This is the second version of this patch.
The first version was part of a patch series on VFIO AP IRQ.
The goal of this patch is to standardize the device-driver interface
for the VFIO_AP ap_matrix_device to satisfy user-land tools working on
hot-plug (UDEV/LIBVIRT).
Christian Borntraeger reported libvirt looping when a matrix device
was available before the libvirt start.
Marc Hartmayer debugged this and circumvented this in libvirt:
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html
Pierre Morel (1):
s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem
drivers/s390/crypto/vfio_ap_drv.c | 48 +++++++++++++++++++++++++++++------
drivers/s390/crypto/vfio_ap_ops.c | 4 +--
drivers/s390/crypto/vfio_ap_private.h | 1 +
3 files changed, 43 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2019-02-18 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 18:08 Pierre Morel [this message]
2019-02-18 18:08 ` [PATCH v2 1/1] s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem Pierre Morel
2019-02-19 8:13 ` Christian Borntraeger
2019-02-19 9:22 ` Cornelia Huck
2019-02-19 9:44 ` Christian Borntraeger
2019-02-21 11:34 ` Pierre Morel
2019-02-19 17:45 ` Halil Pasic
2019-02-19 18:52 ` Tony Krowiak
2019-02-19 21:31 ` Pierre Morel
2019-02-20 9:27 ` Cornelia Huck
2019-02-20 12:51 ` Halil Pasic
2019-02-21 12:10 ` Pierre Morel
2019-02-21 12:35 ` Christian Borntraeger
2019-02-21 12:51 ` Pierre Morel
2019-02-21 13:01 ` Christian Borntraeger
2019-02-21 13:20 ` Pierre Morel
2019-02-20 13:12 ` Harald Freudenberger
2019-02-21 7:37 ` Christian Borntraeger
2019-02-21 8:07 ` Harald Freudenberger
2019-02-21 9:57 ` Pierre Morel
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=1550513328-12646-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox