From: Eric Farman <farman@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akrowiak@linux.ibm.com, alex.williamson@redhat.com,
intel-gvt-dev@lists.freedesktop.org, jgg@nvidia.com,
jjherne@linux.ibm.com, kvm@vger.kernel.org, kwankhede@nvidia.com,
linux-s390@vger.kernel.org, mjrosato@linux.ibm.com,
pasic@linux.ibm.com, vneethv@linux.ibm.com,
zhenyuw@linux.intel.com, zhi.a.wang@intel.com
Subject: Re: [RFC PATCH] vfio/ccw: Move mdev stuff out of struct subchannel
Date: Tue, 26 Jul 2022 14:03:28 -0400 [thread overview]
Message-ID: <d23d6ef67bb709cbde3886ea24d528c3036bff9b.camel@linux.ibm.com> (raw)
In-Reply-To: <20220726174817.GB14002@lst.de>
On Tue, 2022-07-26 at 19:48 +0200, Christoph Hellwig wrote:
> On Tue, Jul 26, 2022 at 05:37:25PM +0200, Eric Farman wrote:
> > Here's my swipe at a cleanup patch that can be folded in
> > to this series, to get the mdev stuff in a more proper
> > location for vfio-ccw.
> >
> > As previously described, the subchannel is a device-agnostic
> > structure that does/should not need to know about specific
> > nuances such as mediated devices. This is why things like
> > struct vfio_ccw_private exist, so move these details there.
>
> Should I resend the series with that folded in?
That would be great. I'll give it another spin and can look over the
ccw changes without the smattering of fixups I have.
> At this point we're
> probably not talking about 5.20 anyway.
next prev parent reply other threads:[~2022-07-26 18:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 4:54 simplify the mdev interface v6 Christoph Hellwig
2022-07-09 4:54 ` [PATCH 01/14] drm/i915/gvt: fix a memory leak in intel_gvt_init_vgpu_types Christoph Hellwig
2022-07-09 4:54 ` [PATCH 02/14] drm/i915/gvt: simplify vgpu configuration management Christoph Hellwig
2022-07-09 4:54 ` [PATCH 03/14] vfio/mdev: make mdev.h standalone includable Christoph Hellwig
2022-07-19 17:03 ` Jason J. Herne
2022-07-09 4:54 ` [PATCH 04/14] vfio/mdev: embedd struct mdev_parent in the parent data structure Christoph Hellwig
2022-07-09 4:54 ` [PATCH 05/14] vfio/mdev: simplify mdev_type handling Christoph Hellwig
2022-07-20 20:47 ` Eric Farman
2022-07-09 4:54 ` [PATCH 06/14] vfio/mdev: remove mdev_from_dev Christoph Hellwig
2022-07-09 4:54 ` [PATCH 07/14] vfio/mdev: unexport mdev_bus_type Christoph Hellwig
2022-07-09 4:54 ` [PATCH 08/14] vfio/mdev: remove mdev_parent_dev Christoph Hellwig
2022-07-09 4:54 ` [PATCH 09/14] vfio/mdev: remove mtype_get_parent_dev Christoph Hellwig
2022-07-09 4:54 ` [PATCH 10/14] vfio/mdev: consolidate all the device_api sysfs into the core code Christoph Hellwig
2022-07-09 4:54 ` [PATCH 11/14] vfio/mdev: consolidate all the name " Christoph Hellwig
2022-07-09 4:54 ` [PATCH 12/14] vfio/mdev: consolidate all the available_instance " Christoph Hellwig
2022-07-09 4:54 ` [PATCH 13/14] vfio/mdev: consolidate all the description " Christoph Hellwig
2022-07-09 4:54 ` [PATCH 14/14] vfio/mdev: add mdev available instance checking to the core Christoph Hellwig
2022-07-19 2:00 ` Eric Farman
2022-07-19 14:48 ` Christoph Hellwig
2022-07-18 5:43 ` simplify the mdev interface v6 Christoph Hellwig
2022-07-18 21:33 ` Alex Williamson
2022-07-19 0:22 ` Zhenyu Wang
2022-07-19 2:01 ` Eric Farman
2022-07-19 14:49 ` Christoph Hellwig
2022-07-19 15:26 ` Alex Williamson
2022-07-19 17:49 ` Eric Farman
2022-07-20 2:41 ` Eric Farman
2022-07-20 5:06 ` Christoph Hellwig
2022-07-26 15:37 ` [RFC PATCH] vfio/ccw: Move mdev stuff out of struct subchannel Eric Farman
2022-07-26 17:48 ` Christoph Hellwig
2022-07-26 18:03 ` Eric Farman [this message]
2022-08-18 6:53 ` Tian, Kevin
2022-08-18 13:24 ` Eric Farman
2022-08-27 10:08 ` Tian, Kevin
2022-07-20 12:14 ` simplify the mdev interface v6 Jason Gunthorpe
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=d23d6ef67bb709cbde3886ea24d528c3036bff9b.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=hch@lst.de \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=vneethv@linux.ibm.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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;
as well as URLs for NNTP newsgroup(s).