public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"Yuan, Hang" <hang.yuan@intel.com>
Subject: Re: [Intel-gfx] [PULL] gvt-fixes
Date: Fri, 30 Oct 2020 11:09:35 +0800	[thread overview]
Message-ID: <20201030030935.GX27141@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <C9292B4F-9A82-46AF-BFAB-D372D202F314@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 3105 bytes --]

On 2020.10.28 11:18:45 +0000, Vivi, Rodrigo wrote:
> 
> 
>     On Oct 27, 2020, at 1:46 PM, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> 
>     On Tue, Oct 27, 2020 at 11:17:40AM +0800, Zhenyu Wang wrote:
> 
> 
>         Hi,
> 
>         Here's first gvt fixes for 5.10 which includes more vGPU
>         suspend/resume fix in HWSP reset handling, and also fix for host i915
>         suspend regression when vGPU is created (not need to be active), and
>         one workaround for APL guest hang issue.
> 
> 
>     pulled to drm-intel-fixes
> 
> 
> I'm actually pulling it off. I had bypassed dim, considering this was an old
> issue with our email decoder,
> but it happens that 
> 
> $ git show 401ccfa87856 | grep Fixes
> Fixes: e6ba76480299 (drm/i915: Remove i915->kernel_context)
> 
> And this is what it should have:
> 
> $ dim fixes e6ba76480299 | grep Fixes
> Fixes: e6ba76480299 ("drm/i915: Remove i915->kernel_context")
> 
> Sorry for the trouble.
> Let's fix this in place so we don't propagate bad tag that might break other
> scripts on the way
>

Oops, sorry I missed this one. I'll refresh.

Thanks

> 
> 
> 
>         Thanks
>         --
>         The following changes since commit
>         16cce04cdb200ba905d1241b425ac48da5a9ace5:
> 
>          drm/i915/selftests: Push the fake iommu device from the stack to data
>         (2020-09-23 10:15:46 +0300)
> 
>         are available in the Git repository at:
> 
>          https://github.com/intel/gvt-linux tags/gvt-fixes-2020-10-27
> 
>         for you to fetch changes up to
>         401ccfa87856656b874c737522ea92721394a348:
> 
>          drm/i915/gvt: Only pin/unpin intel_context along with workload
>         (2020-10-19 16:54:28 +0800)
> 
>         ----------------------------------------------------------------
>         gvt-fixes-2020-10-27
> 
>         - Fix HWSP reset handling during vGPU suspend/resume (Colin)
>         - Apply flush workaround on APL now for possible guest hang (Colin)
>         - Fix vGPU context pin/unpin also for host suspend regression with
>          vGPU created (Colin)
> 
>         ----------------------------------------------------------------
>         Colin Xu (3):
>              drm/i915/gvt: Allow zero out HWSP addr on hws_pga_write
>              drm/i915/gvt: Set SNOOP for PAT3 on BXT/APL to workaround GPU BB
>         hang
>              drm/i915/gvt: Only pin/unpin intel_context along with workload
> 
>         drivers/gpu/drm/i915/gvt/handlers.c  | 35
>         +++++++++++++++++++++++++++++++++--
>         drivers/gpu/drm/i915/gvt/scheduler.c | 15 ++++++++-------
>         2 files changed, 41 insertions(+), 9 deletions(-)
> 
> 
>         -- 
> 
>         $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> 
> 
> 
>     _______________________________________________
>     Intel-gfx mailing list
>     Intel-gfx@lists.freedesktop.org
>     https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> 

-- 

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

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

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-10-30  3:30 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  3:17 [Intel-gfx] [PULL] gvt-fixes Zhenyu Wang
2020-10-27 20:46 ` Rodrigo Vivi
2020-10-28 11:18   ` Vivi, Rodrigo
2020-10-30  3:09     ` Zhenyu Wang [this message]
2020-10-30  5:21     ` Zhenyu Wang
2020-10-30 22:57       ` Vivi, Rodrigo
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  5:54 Zhenyu Wang
2023-08-02  7:17 ` Tvrtko Ursulin
2023-01-04  8:05 Zhenyu Wang
2023-01-04 11:34 ` Rodrigo Vivi
2023-01-05  0:15   ` Zhenyu Wang
2023-01-05 13:10     ` Rodrigo Vivi
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-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 ` [Intel-gfx] " Zhenyu Wang
2019-11-12  6:18 Zhenyu Wang
2019-11-12  6:18 ` [Intel-gfx] " Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-11-12 20:36   ` [Intel-gfx] " 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=20201030030935.GX27141@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=hang.yuan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox