All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhi Wang <zhi.a.wang@intel.com>
To: Jani Nikula <jani.nikula@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: Tue, 24 Apr 2018 18:17:13 +0800	[thread overview]
Message-ID: <d90e03d6-2e0f-4d0b-2865-a15d9cc23f62@intel.com> (raw)
In-Reply-To: <679fe225-6963-5a5f-e869-913a206640c0@intel.com>

The patch which causes conflict:

---
 From 2e8ea2777af45fe651dbd14b8b8e000e94467c24 Mon Sep 17 00:00:00 2001
From: Weinan Li <weinan.z.li@intel.com>
Date: Wed, 21 Mar 2018 15:40:32 +0800
Subject: [PATCH] Revert "drm/i915/gvt: set max priority for gvt context"

This reverts commit 11474e9091cf2002e948647fd9f63a7f027e488a.

There are issues which will block the host preemption before, instead of
disabling it use one workaround "setting max priority for gvt context"
to avoid the gvt context be preempted by the host. Now the issues have been
cleared, so revert this patch to enable host preemption.

v2:
- refine description(Zhenyu)

Signed-off-by: Weinan Li <weinan.z.li@intel.com>
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>
---

has a dependency with the following patch which is missing in git tag 
drm-next-intel-2018-04-13:

---
commit b7268c5eed0ab4f052d614b4b0e3fe8a51c9d5a1
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Apr 18 19:40:52 2018 +0100

     drm/i915: Pack params to engine->schedule() into a struct

     Today we only want to pass along the priority to 
engine->schedule(), but
     in the future we want to have much more control over the various 
aspects
     of the GPU during a context's execution, for example controlling the
     frequency allowed. As we need an ever growing number of parameters for
     scheduling, move those into a struct for convenience.

     v2: Move the anonymous struct into its own function for legibility and
     ye olde gcc.

     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
     Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
     Link: 
https://patchwork.freedesktop.org/patch/msgid/20180418184052.7129-3-chris@chris-wilson.co.uk
---

I found it in drm-tip. Looks I have to send another pull request when 
the patch above is in a new drm-intel-next tag.

Thanks for everyone's efforts.

Thanks,
Zhi.

On 04/23/18 16:13, Zhi Wang 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,
> 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(-)
>>
> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-04-24 10:17 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 [this message]
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=d90e03d6-2e0f-4d0b-2865-a15d9cc23f62@intel.com \
    --to=zhi.a.wang@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=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@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 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.