Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: 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: [PULL] gvt-next for 4.18
Date: Mon, 14 May 2018 11:35:49 +0300	[thread overview]
Message-ID: <87603q4ot6.fsf@intel.com> (raw)
In-Reply-To: <ebae7cf1-6550-bb44-74a2-d3a014051804@intel.com>

On Mon, 14 May 2018, Zhi Wang <zhi.a.wang@intel.com> wrote:
> The following changes since commit 0c79f9cb77eae28d48a4f9fc1b3341aacbbd260c:
>
>    drm/i915/gen9: Add WaClearHIZ_WM_CHICKEN3 for bxt and glk (2018-05-13 
> 10:29:44 +0100)
>
> are available in the git repository at:
>
>    https://github.com/intel/gvt-linux.git tags/gvt-next-2018-05-14
>
> for you to fetch changes up to 41e403d04e7050c8d88682939febcdbe117d4c82:
>
>    Revert "drm/i915/gvt: set max priority for gvt context" (2018-05-14 
> 05:26:09 +0800)

Pulled, thanks.

Please try to avoid rebases; it looks like you're now the committer for
each commit but without Signed-off-by.

BR,
Jani.


>
> ----------------------------------------------------------------
> - Improve the emulation of virtual non-priv register. (Yan)
> - Reverse the hack of host of preemption of GVT-g. (Weinan)
> - Improve untracked warning message.(Changbin)
>
> ----------------------------------------------------------------
> Changbin Du (1):
>        drm/i915/gvt: Remove disable_warn_untrack and print untracked 
> mmio with debug level
>
> Weinan Li (1):
>        Revert "drm/i915/gvt: set max priority for gvt context"
>
> Zhao Yan (3):
>        drm/i915/gvt: let NOPID be the default value of force_to_nonpriv 
> registers
>        drm/i915/gvt: do not return error on handling force_to_nonpriv 
> registers
>        drm/i915/gvt: let force_to_nonpriv cmd handler only valid for LRI cmd
>
> Zhi Wang (1):
>        Merge branch 'drm-intel-next-queued' into gvt-next
>
>   drivers/gpu/drm/i915/gvt/cmd_parser.c | 26 +++++++++++++++++++++-----
>   drivers/gpu/drm/i915/gvt/gvt.h        |  1 -
>   drivers/gpu/drm/i915/gvt/handlers.c   | 35 
> ++++++++++++++++++-----------------
>   drivers/gpu/drm/i915/gvt/mmio.c       |  2 --
>   drivers/gpu/drm/i915/gvt/scheduler.c  |  3 ---
>   5 files changed, 39 insertions(+), 28 deletions(-)
>

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

  reply	other threads:[~2018-05-14  8:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19  7:39 [PULL] gvt-fixes for 4.17 Zhenyu Wang
2018-04-19  9:17 ` [PULL] gvt-next " Zhi Wang
2018-04-19  9:21   ` Zhi Wang
2018-04-19  9:34   ` Jani Nikula
2018-04-19  9:41     ` Zhenyu Wang
2018-04-19  9:50     ` Zhi Wang
2018-04-19 10:16       ` Zhi Wang
2018-04-23  8:11         ` [PULL] gvt-next for 4.18 Zhi Wang
2018-04-23  8:13           ` Zhi Wang
2018-04-23 10:25             ` Jani Nikula
2018-04-23 16:01               ` Zhi Wang
2018-04-24 10:17             ` Zhi Wang
2018-05-13 22:17               ` Zhi Wang
2018-05-14  8:35                 ` Jani Nikula [this message]
2018-05-14 12:13                   ` Wang, Zhi A
2018-06-06  7:49 ` [PULL] gvt-fixes for 4.17 Zhenyu Wang
2018-06-06 13:11   ` Joonas Lahtinen
2018-06-08 12:04     ` 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=87603q4ot6.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=rodrigo.vivi@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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