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, 23 Apr 2018 13:25:53 +0300	[thread overview]
Message-ID: <877eoydxse.fsf@intel.com> (raw)
In-Reply-To: <679fe225-6963-5a5f-e869-913a206640c0@intel.com>

On Mon, 23 Apr 2018, Zhi Wang <zhi.a.wang@intel.com> wrote:
> Hi Jani:
>
> I picked out the patch which causes conflicts and may put it back in the 
> next back merge from drm-intel-next to gvt-next. So there shouldn't be 
> any conflict in this pull. Thanks for your efforts.

Thanks, pulled to drm-intel-next-queued.

Just as a reminder, if you have more stuff for v4.18 the deadline is in
about three weeks.

BR,
Jani.


>
> Thanks,
> Zhi.
>
> On 04/23/18 16:11, Zhi Wang wrote:
>> The following changes since commit 
>> fadec6eefe232696c5c471b40df33e6db616e854:
>> 
>>    drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)
>> 
>> are available in the git repository at:
>> 
>>    https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-23
>> 
>> for you to fetch changes up to 3eda0d22ead04f81ea59c9584bcbf5b496745e92:
>> 
>>    drm/i915/gvt: Mark expected switch fall-through in 
>> handle_g2v_notification (2018-04-23 13:09:36 +0800)
>> 
>> ----------------------------------------------------------------
>> - Minor condition check improvment (Gustavo A. R. Silva)
>> - Non-priviliged batch buffer scan (Yan Zhao)
>> - Scheduling optimizations (Zhipeng Gong)
>> 
>> ----------------------------------------------------------------
>> Gustavo A. R. Silva (2):
>>        drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
>>        drm/i915/gvt: Mark expected switch fall-through in 
>> handle_g2v_notification
>> 
>> Zhao Yan (1):
>>        drm/i915/gvt: scan non-privileged batch buffer for debug purpose
>> 
>> Zhipeng Gong (2):
>>        drm/i915/gvt: Use real time to do timer check
>>        drm/i915/gvt: Update time slice more frequently
>> 
>>   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 ++++++++++++++++++++-------
>>   drivers/gpu/drm/i915/gvt/debugfs.c      | 67 
>> +++++++++++++++++++++++++++++++++
>>   drivers/gpu/drm/i915/gvt/gvt.h          |  1 +
>>   drivers/gpu/drm/i915/gvt/handlers.c     |  1 +
>>   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ++++++++-------
>>   drivers/gpu/drm/i915/gvt/scheduler.c    | 66 
>> +++++++++++++++++++++-----------
>>   drivers/gpu/drm/i915/gvt/scheduler.h    |  1 +
>>   drivers/gpu/drm/i915/gvt/trace.h        | 24 +++++++++---
>>   8 files changed, 193 insertions(+), 53 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-04-23 10:25 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 [this message]
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
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=877eoydxse.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