s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest1 patch 4 repliesIn review
- v21 patch 18 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystemdrivers/ drivers/ drivers/ | +38 | 4 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Christian Borntraeger | Cornelia Huck | Halil Pasic | Tony Krowiak |
|---|---|---|---|---|
| 1/1 | T-b | R-b | A-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 4 reviewers.
Cover letter [PATCH v3 0/1] s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem
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 | 44 ++++++++++++++++++++++++++++------- drivers/s390/crypto/vfio_ap_ops.c | 4 ++-- drivers/s390/crypto/vfio_ap_private.h | 1 + 3 files changed, 38 insertions(+), 11 deletions(-)
Signature · 1 line
2.7.4