All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-fixes
Date: Thu, 5 Jan 2023 08:15:28 +0800	[thread overview]
Message-ID: <Y7YWoFpz4plnSLCd@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <Y7VkRDNBOJU4qkYY@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2767 bytes --]

On 2023.01.04 06:34:28 -0500, Rodrigo Vivi wrote:
> On Wed, Jan 04, 2023 at 04:05:13PM +0800, Zhenyu Wang wrote:
> > 
> > Hi,
> > 
> > Here's accumulated current gvt-fixes. Several of them handle
> > for error or destroy path issues and one from Zhi to fix up
> > left vgpu status tracking.
> > 
> > thanks!
> > ---
> > The following changes since commit 6217e9f05a74df48c77ee68993d587cdfdb1feb7:
> 
> I'm kind of confused on your baseline here.
> 
> It is including a strange merge commit in the middle of the commits:
> Zhenyu Wang   ??? M?????? Merge tag 'drm-intel-fixes-2022-12-30' into gvt-fixes
> commit c063c8c07864246ba3831b017cea8d3096e236a8
> 
> Please rebase on top of v6.2-rc2 so we have the same base here.
> (and please remind to sign-off-by when pushing the commits)
> 

oh, I tried to sycn up by back merge with vfio iommufd of gvt changes
to apply Zhi's patch properly, so it should stand on that tag..but anyway
I just refresh with rebase and fixed two invalid r-b tags. Please pull
below one.

thanks!
---
The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:

  Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-fixes-2023-01-05

for you to fetch changes up to 4a61648af68f5ba4884f0e3b494ee1cabc4b6620:

  drm/i915/gvt: fix double free bug in split_2MB_gtt_entry (2023-01-04 23:21:19 +0800)

----------------------------------------------------------------
gvt-fixes-2023-01-05

- Fix one missed unpin in error of intel_vgpu_shadow_mm_pin()
- Fix two debugfs destroy oops issues for vgpu and gvt entries
- Fix one potential double free issue in gtt shadow pt code
- Fix to use atomic bit flag for vgpu status

----------------------------------------------------------------
Dan Carpenter (1):
      drm/i915: unpin on error in intel_vgpu_shadow_mm_pin()

Zheng Wang (1):
      drm/i915/gvt: fix double free bug in split_2MB_gtt_entry

Zhenyu Wang (2):
      drm/i915/gvt: fix gvt debugfs destroy
      drm/i915/gvt: fix vgpu debugfs clean in remove

Zhi Wang (1):
      drm/i915/gvt: use atomic operations to change the vGPU status

 drivers/gpu/drm/i915/gvt/debugfs.c   | 36 +++++++++++++++++++++++++++++++-----
 drivers/gpu/drm/i915/gvt/dmabuf.c    |  3 ++-
 drivers/gpu/drm/i915/gvt/gtt.c       | 21 +++++++++++++++------
 drivers/gpu/drm/i915/gvt/gvt.h       | 15 ++++++++++-----
 drivers/gpu/drm/i915/gvt/interrupt.c |  2 +-
 drivers/gpu/drm/i915/gvt/kvmgt.c     | 35 +++++++++++++----------------------
 drivers/gpu/drm/i915/gvt/scheduler.c |  4 +++-
 drivers/gpu/drm/i915/gvt/vgpu.c      | 12 +++++-------
 8 files changed, 80 insertions(+), 48 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-01-05  0:18 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  8:05 [Intel-gfx] [PULL] gvt-fixes Zhenyu Wang
2023-01-04 11:34 ` Rodrigo Vivi
2023-01-05  0:15   ` Zhenyu Wang [this message]
2023-01-05 13:10     ` Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  5:54 Zhenyu Wang
2023-08-02  7:17 ` Tvrtko Ursulin
2022-11-11  9:02 Zhenyu Wang
2022-11-22  5:11 ` Zhenyu Wang
2022-11-22  8:02   ` Tvrtko Ursulin
2022-08-15  2:38 Zhenyu Wang
2022-08-15 23:32 ` Rodrigo Vivi
2022-08-16  4:05   ` Zhenyu Wang
2022-08-16  4:43     ` Zhenyu Wang
2022-08-17 20:07       ` Vivi, Rodrigo
2022-08-17 21:34         ` Colin King (gmail)
2022-08-18 10:15           ` Jani Nikula
2022-08-18 14:27             ` Jani Nikula
2022-08-18 15:43               ` Vivi, Rodrigo
2022-08-22  3:00                 ` Zhenyu Wang
2022-07-11  5:20 Zhenyu Wang
2022-07-12 22:24 ` Rodrigo Vivi
2021-09-18  7:11 Zhenyu Wang
2021-09-27  9:39 ` Jani Nikula
2021-08-10  5:01 Zhenyu Wang
2021-08-10 13:52 ` Rodrigo Vivi
2021-07-15  2:22 Zhenyu Wang
2021-07-15 13:56 ` Rodrigo Vivi
2021-05-19  7:49 Zhenyu Wang
2021-05-19  8:50 ` Jani Nikula
2021-04-20  2:33 Zhenyu Wang
2021-04-20 13:43 ` Rodrigo Vivi
2021-01-08  4:59 Zhenyu Wang
2021-01-11 18:13 ` Jani Nikula
2020-11-17  2:39 Zhenyu Wang
2020-11-19  6:53 ` Rodrigo Vivi
2020-10-27  3:17 Zhenyu Wang
2020-10-27 20:46 ` Rodrigo Vivi
2020-10-28 11:18   ` Vivi, Rodrigo
2020-10-30  3:09     ` Zhenyu Wang
2020-10-30  5:21     ` Zhenyu Wang
2020-10-30 22:57       ` Vivi, Rodrigo
2020-09-17  6:42 Zhenyu Wang
2020-09-22 17:27 ` Jani Nikula
2020-06-17  4:34 Zhenyu Wang
2020-06-18 12:48 ` Joonas Lahtinen
2020-06-23  3:07   ` Zhenyu Wang
2020-06-29  8:18     ` Jani Nikula
2020-05-12  2:48 Zhenyu Wang
2020-05-12  7:00 ` Rodrigo Vivi
2020-04-14  8:36 Zhenyu Wang
2020-04-14 13:11 ` Rodrigo Vivi
2020-03-10  8:09 Zhenyu Wang
2020-03-10  9:33 ` Jani Nikula
2020-02-26 10:30 Zhenyu Wang
2020-02-26 22:00 ` Jani Nikula
2020-02-12  6:59 Zhenyu Wang
2020-02-12 14:54 ` Jani Nikula
2019-12-18  5:16 Zhenyu Wang
2019-12-18  9:20 ` Joonas Lahtinen
2019-11-22  3:33 Zhenyu Wang
2019-11-22  3:33 ` Zhenyu Wang
2019-11-12  6:18 Zhenyu Wang
2019-11-12  6:18 ` Zhenyu Wang
2019-11-12 20:36   ` Vivi, Rodrigo
2019-11-12 20:36     ` Vivi, Rodrigo

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=Y7YWoFpz4plnSLCd@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=zhiyuan.lv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.