public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: stable@vger.kernel.org, jgg@nvidia.com, kevin.tian@intel.com,
	hch@lst.de, sashal@kernel.org
Subject: Re: [PATCH 6.0] drm/i915/gvt: Add missing vfio_unregister_group_dev() call
Date: Fri, 11 Nov 2022 09:57:23 +0100	[thread overview]
Message-ID: <Y24Oc6J1VGd+JsDC@kroah.com> (raw)
In-Reply-To: <166803668167.3399708.615075636176057580.stgit@omen>

On Wed, Nov 09, 2022 at 04:31:45PM -0700, Alex Williamson wrote:
> From: Jason Gunthorpe <jgg@nvidia.com>
> 
> [ Upstream commit  f423fa1bc9fe1978e6b9f54927411b62cb43eb04 ]
> 
> When converting to directly create the vfio_device the mdev driver has to
> put a vfio_register_emulated_iommu_dev() in the probe() and a pairing
> vfio_unregister_group_dev() in the remove.
> 
> This was missed for gvt, add it.
> 
> Cc: stable@vger.kernel.org
> Fixes: 978cf586ac35 ("drm/i915/gvt: convert to use vfio_register_emulated_iommu_dev")
> Reported-by: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Link: https://lore.kernel.org/r/0-v1-013609965fe8+9d-vfio_gvt_unregister_jgg@nvidia.com
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> 
> Reviewed-by: Kevin Tian <kevin.tian@intel.com> # v6.0 backport
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com> # v6.0 backport
> ---
>  drivers/gpu/drm/i915/gvt/kvmgt.c |    3 +++
>  1 file changed, 3 insertions(+)
> 

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-11-11  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 23:31 [PATCH 6.0] drm/i915/gvt: Add missing vfio_unregister_group_dev() call Alex Williamson
2022-11-11  8:57 ` Greg KH [this message]

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=Y24Oc6J1VGd+JsDC@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=hch@lst.de \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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