public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Yuan, Hang" <hang.yuan@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-fixes
Date: Mon, 29 Jul 2019 14:05:05 +0300	[thread overview]
Message-ID: <87zhkxnlsu.fsf@intel.com> (raw)
In-Reply-To: <20190729033347.GQ8319@zhen-hp.sh.intel.com>

On Mon, 29 Jul 2019, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> ping..

Sorry for the delay. Unfortunately, dim hit the following issues:

Pulling https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-07-23 ...
From https://github.com/intel/gvt-linux
 * tag                         gvt-fixes-2019-07-23 -> FETCH_HEAD
dim: 8642656299cf ("drm/i915/gvt: fix incorrect cache entry for guest page mapping"): committer Signed-off-by missing.
dim: 4c2bb55ba7d6 ("drm/i915/gvt: remove duplicate include of trace.h"): mandatory review missing.
dim: 25fd1829ae4e ("drm/i915: Make the semaphore saturation mask global"): Fixes: SHA1 in not pointing at an ancestor:
dim:     ca6e56f654e7 ("drm/i915: Disable semaphore busywaits on saturated systems")
dim: ERROR: issues in commits detected, aborting

Please fix, and make it a habit to run the checks before sending the
pull requests.

BR,
Jani.



>
> On 2019.07.23 17:29:58 +0800, Zhenyu Wang wrote:
>> 
>> Hi,
>> 
>> Here's recent gvt-fixes for 5.3-rc. It includes safety guard
>> for possible ggtt access error with related checks, includecheck
>> fix and one cache entry size fix for 2MB ppgtt guest.
>> 
>> Thanks.
>> --
>> The following changes since commit d7e8a19b38c8ac1a32b6b03af049e2c88d4155db:
>> 
>>   drm/i915: Don't dereference request if it may have been retired when printing (2019-07-09 16:16:18 +0300)
>> 
>> are available in the Git repository at:
>> 
>>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-07-23
>> 
>> for you to fetch changes up to 8642656299cf86cfeceb1a48b0e1874de6874a2b:
>> 
>>   drm/i915/gvt: fix incorrect cache entry for guest page mapping (2019-07-18 11:06:41 +0800)
>> 
>> ----------------------------------------------------------------
>> gvt-fixes-2019-07-23
>> 
>> - Guard against potential ggtt access error (Xiong)
>> - Fix includecheck (Zhenyu)
>> - Fix cache entry for guest page mapping found by 2M ppgtt guest (Xiaolin)
>> 
>> ----------------------------------------------------------------
>> Xiaolin Zhang (1):
>>       drm/i915/gvt: fix incorrect cache entry for guest page mapping
>> 
>> Xiong Zhang (3):
>>       drm/i915/gvt: Warning for invalid ggtt access
>>       drm/i915/gvt: Don't use ggtt_validdate_range() with size=0
>>       drm/i915/gvt: Checking workload's gma earlier
>> 
>> Zhenyu Wang (1):
>>       drm/i915/gvt: remove duplicate include of trace.h
>> 
>>  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 10 ----------
>>  drivers/gpu/drm/i915/gvt/fb_decoder.c   |  6 +++---
>>  drivers/gpu/drm/i915/gvt/gtt.c          |  9 +++++++++
>>  drivers/gpu/drm/i915/gvt/kvmgt.c        | 12 ++++++++++++
>>  drivers/gpu/drm/i915/gvt/scheduler.c    | 28 ++++++++++++++++++++++++++++
>>  drivers/gpu/drm/i915/gvt/trace_points.c |  2 --
>>  6 files changed, 52 insertions(+), 15 deletions(-)
>> 
>> -- 
>> Open Source Technology Center, Intel ltd.
>> 
>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>
>
>
>> _______________________________________________
>> intel-gvt-dev mailing list
>> intel-gvt-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-29 11:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23  9:29 [PULL] gvt-fixes Zhenyu Wang
2019-07-29  3:33 ` Zhenyu Wang
2019-07-29 11:05   ` Jani Nikula [this message]
2019-07-30  7:00     ` Zhenyu Wang
2019-07-30  8:33       ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31  9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05  3:21   ` Zhenyu Wang
2019-11-22  3:33 Zhenyu Wang
2019-11-12  6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-08-13  9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-06-19  6:22 Zhenyu Wang
2019-06-19  7:56 ` Jani Nikula
2019-06-05  8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-05-29  9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30  3:41   ` Zhenyu Wang
2019-05-31  8:16     ` Joonas Lahtinen
2019-05-21  6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11  6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-04-02  9:40 Zhenyu Wang
2019-04-04  0:12 ` Rodrigo Vivi
2019-04-04  0:32   ` Zhenyu Wang
2019-04-04  1:03     ` Rodrigo Vivi
2019-04-04  0:39   ` Zhenyu Wang
2019-03-21  3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24  5:48 Zhenyu Wang
2019-01-31  9:45 ` Jani Nikula

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=87zhkxnlsu.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=zhenyuw@linux.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