From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>
Cc: Eric Farman <farman@linux.ibm.com>, Christoph Hellwig <hch@lst.de>
Subject: [PATCH v4 0/4] Move vfio_ccw to the new mdev API
Date: Tue, 26 Oct 2021 14:57:29 -0300 [thread overview]
Message-ID: <0-v4-cea4f5bd2c00+b52-ccw_mdev_jgg@nvidia.com> (raw)
This is the first 4 patches of the v3 series which only change CCW to use
the new VFIO API for mdevs and leaves the lifetime model as-is.
As agreed, we will go ahead with this set and IBM can take the remaining
patches of cleanup when they want. (I won't resend them)
Alex: as Eric has now ack'd them please take them to the VFIO tree for
this upcoming merge window
This is on github: https://github.com/jgunthorpe/linux/commits/vfio_ccw
Thanks,
Jason
v4:
- Rebase to vfio-next (9cef73918), no change
- Add acks
v3: https://lore.kernel.org/r/0-v3-57c1502c62fd+2190-ccw_mdev_jgg@nvidia.com
- Rebase to Christoph's group work & rc3; use
vfio_register_emulated_iommu_dev()
- Remove GFP_DMA
- Order mdev_unregister_driver() symmetrically with init
- Rework what is considered a BROKEN event in fsm_close()
- NOP both CCW_EVENT_OPEN/CLOSE
- Documentation updates
- Remane goto label to err_init vfio_ccw_mdev_probe()
- Fix NULL pointer deref in mdev_device_create()
v2: https://lore.kernel.org/r/0-v2-7d3a384024cf+2060-ccw_mdev_jgg@nvidia.com
- Clean up the lifecycle in ccw with 7 new patches
- Rebase
v1: https://lore.kernel.org/all/7-v2-7667f42c9bad+935-vfio3_jgg@nvidia.com
Jason Gunthorpe (4):
vfio/ccw: Remove unneeded GFP_DMA
vfio/ccw: Use functions for alloc/free of the vfio_ccw_private
vfio/ccw: Pass vfio_ccw_private not mdev_device to various functions
vfio/ccw: Convert to use vfio_register_emulated_iommu_dev()
drivers/s390/cio/vfio_ccw_drv.c | 158 ++++++++++++++++------------
drivers/s390/cio/vfio_ccw_ops.c | 142 ++++++++++++++-----------
drivers/s390/cio/vfio_ccw_private.h | 5 +
3 files changed, 177 insertions(+), 128 deletions(-)
base-commit: 9cef73918e15d2284e71022291a8a07901e80bad
--
2.33.0
next reply other threads:[~2021-10-26 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:57 Jason Gunthorpe [this message]
2021-10-26 17:57 ` [PATCH v4 1/4] vfio/ccw: Remove unneeded GFP_DMA Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 2/4] vfio/ccw: Use functions for alloc/free of the vfio_ccw_private Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 3/4] vfio/ccw: Pass vfio_ccw_private not mdev_device to various functions Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 4/4] vfio/ccw: Convert to use vfio_register_emulated_iommu_dev() Jason Gunthorpe
2021-10-28 18:40 ` [PATCH v4 0/4] Move vfio_ccw to the new mdev API Alex Williamson
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=0-v4-cea4f5bd2c00+b52-ccw_mdev_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=vneethv@linux.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