From: "Tian, Kevin" <kevin.tian@intel.com>
To: "Christopherson,, Sean" <seanjc@google.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
"Wang, Zhi A" <zhi.a.wang@intel.com>
Cc: "intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/2] drm/i915/gvt: Unconditionally put reference to KVM when detaching vGPU
Date: Fri, 11 Nov 2022 02:50:02 +0000 [thread overview]
Message-ID: <BN9PR11MB527612BB4FF14878D7BD4CD48C009@BN9PR11MB5276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221111002225.2418386-3-seanjc@google.com>
> From: Sean Christopherson <seanjc@google.com>
> Sent: Friday, November 11, 2022 8:22 AM
>
> Always put the KVM reference when closing a vCPU device, as
> intel_vgpu_open_device() succeeds if and only if the KVM pointer is
> valid and a reference to KVM is acquired. And if that doesn't hold true,
> the call to kvm_page_track_unregister_notifier() a few lines earlier is
> doomed.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
next prev parent reply other threads:[~2022-11-11 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 0:22 [PATCH 0/2] drm/i915/gvt: Fix for KVM refcounting bug Sean Christopherson
2022-11-11 0:22 ` [PATCH 1/2] drm/i915/gvt: Get reference to KVM iff attachment to VM is successful Sean Christopherson
2022-11-11 2:49 ` Tian, Kevin
2022-11-11 0:22 ` [PATCH 2/2] drm/i915/gvt: Unconditionally put reference to KVM when detaching vGPU Sean Christopherson
2022-11-11 2:50 ` Tian, Kevin [this message]
2022-11-11 5:16 ` [PATCH 0/2] drm/i915/gvt: Fix for KVM refcounting bug Zhenyu Wang
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=BN9PR11MB527612BB4FF14878D7BD4CD48C009@BN9PR11MB5276.namprd11.prod.outlook.com \
--to=kevin.tian@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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).