From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Dan Williams <dan.j.williams@intel.com>,
Leon Romanovsky <leonro@nvidia.com>,
Christoph Hellwig <hch@lst.de>, Tarun Gupta <targupta@nvidia.com>
Subject: Re: [Intel-gfx] [PATCH 15/18] vfio/gvt: Make DRM_I915_GVT depend on VFIO_MDEV
Date: Tue, 23 Mar 2021 20:26:30 +0100 [thread overview]
Message-ID: <20210323192630.GM17735@lst.de> (raw)
In-Reply-To: <15-v1-7dedf20b2b75+4f785-vfio2_jgg@nvidia.com>
On Tue, Mar 23, 2021 at 02:55:32PM -0300, Jason Gunthorpe wrote:
> Ideally all of this would be moved to kvmgt.c, but it is entangled with
> the rest of the "generic" code in an odd way. Thus put in a kconfig
> dependency so we don't get randconfig failures when the next patch creates
> a link time dependency related to the use of MDEV_TYPE.
Ideally that weird struct intel_gvt_mpt would go away entirely. But
that is clearly out of scope for this patchset..
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-23 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 17:55 [Intel-gfx] [PATCH 00/18] Make vfio_mdev type safe Jason Gunthorpe
2021-03-23 17:55 ` [Intel-gfx] [PATCH 15/18] vfio/gvt: Make DRM_I915_GVT depend on VFIO_MDEV Jason Gunthorpe
2021-03-23 19:26 ` Christoph Hellwig [this message]
2021-03-23 19:39 ` Jason Gunthorpe
2021-03-30 4:39 ` Zhenyu Wang
2021-03-26 6:03 ` Tian, Kevin
2021-03-23 17:55 ` [Intel-gfx] [PATCH 16/18] vfio/gvt: Use mdev_get_type_group_id() Jason Gunthorpe
2021-03-23 19:28 ` Christoph Hellwig
2021-03-26 6:09 ` Tian, Kevin
2021-03-23 17:55 ` [Intel-gfx] [PATCH 17/18] vfio/mdev: Remove kobj from mdev_parent_ops->create() Jason Gunthorpe
2021-03-23 19:29 ` Christoph Hellwig
2021-03-26 6:11 ` Tian, Kevin
2021-03-30 16:29 ` Cornelia Huck
2021-03-23 17:55 ` [Intel-gfx] [PATCH 18/18] vfio/mdev: Correct the function signatures for the mdev_type_attributes Jason Gunthorpe
2021-03-23 19:31 ` Christoph Hellwig
2021-04-06 18:34 ` Jason Gunthorpe
2021-03-26 7:03 ` Tian, Kevin
2021-03-30 16:35 ` Cornelia Huck
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=20210323192630.GM17735@lst.de \
--to=hch@lst.de \
--cc=airlied@linux.ie \
--cc=ashok.raj@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=mgurtovoy@nvidia.com \
--cc=targupta@nvidia.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