All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"dim-tools@lits.freedesktop.org" <dim-tools@lits.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: [Intel-gfx] [PULL] gvt-next
Date: Mon, 14 Sep 2020 18:39:19 +0000	[thread overview]
Message-ID: <7E56BF0B-0E18-44D4-A332-0812A591F087@intel.com> (raw)
In-Reply-To: <20200914023420.GY28614@zhen-hp.sh.intel.com>



> On Sep 13, 2020, at 7:34 PM, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> 
> On 2020.09.11 19:58:25 -0400, Rodrigo Vivi wrote:
>> On Thu, Sep 10, 2020 at 01:37:20PM +0800, Zhenyu Wang wrote:
>>> 
>>> Hi,
>>> 
>>> As we split pull request for 5.10 this time, here's gvt-next pull
>>> for 5.10. For gvt ww lock fix, Zhi would send another pull based
>>> on gem-next.
>>> 
>>> This includes current command access flag cleanup for
>>> handlers which would be used for next refined cmd scan. And also
>>> two more recent fixes on workaround cmd access and MIA reset state.
>>> 
>>> Thanks
>>> --
>>> The following changes since commit ced026e959bec5046afa310d6474e147b6294da2:
>>> 
>>>  drm/i915: Update DRIVER_DATE to 20200824 (2020-08-24 14:26:38 -0400)
>>> 
>>> are available in the Git repository at:
>>> 
>>>  https://github.com/intel/gvt-linux tags/gvt-next-2020-09-10
>> 
>> This is a malformed pull request line which dim doesn't recognize.
>> Could you please regenerate it?
>> 
>> $ cat /tmp/gvt-next/cur/1599868544.259925_1.rdvivi-losangeles\:2\,S | dim apply-pull drm-intel-next-queued
>> dim: no pull request found
>> 
> 
> Hmm, strange, it pulls fine here when I tried this in local. I just copied in mutt and
>     cat /tmp/gvt-next.0910 | ./dim apply-pull drm-intel-next-queued

sorry... it was dim's fault ;)

dim now accepts python3, but a function used on email parser doesn't work in
the same way...

pulled now, thanks

> 
>>> 
>>> for you to fetch changes up to df398e33b8fd3ac28b3c7166de555e38d26e7391:
>>> 
>>>  drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET (2020-09-10 13:49:05 +0800)
>>> 
>>> ----------------------------------------------------------------
>>> gvt-next-2020-09-10
>>> 
>>> - Cleanup command access flag (Yan)
>>> - New workaround cmd access fix (Colin)
>>> - MIA reset state fix (Colin)
>>> 
>>> ----------------------------------------------------------------
>>> Colin Xu (2):
>>>      drm/i915/gvt: Add F_CMD_ACCESS for some GEN9 SKU WA MMIO access
>>>      drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET
>>> 
>>> Yan Zhao (4):
>>>      drm/i915/gvt: rename F_IN_CTX flag to F_SR_IN_CTX
>>>      drm/i915/gvt: remove flag F_CMD_ACCESSED
>>>      drm/i915/gvt: add/modify interfaces for flag F_CMD_ACCESS
>>>      drm/i915/gvt: remove F_CMD_ACCESS flag for some registers
>>> 
>>> drivers/gpu/drm/i915/gvt/cmd_parser.c   |  6 ++---
>>> drivers/gpu/drm/i915/gvt/gvt.h          | 44 +++++++++++++++++++--------------
>>> drivers/gpu/drm/i915/gvt/handlers.c     | 32 +++++++++++++-----------
>>> drivers/gpu/drm/i915/gvt/mmio.c         |  3 +++
>>> drivers/gpu/drm/i915/gvt/mmio_context.c |  2 +-
>>> 5 files changed, 49 insertions(+), 38 deletions(-)
>>> 
>>> -- 
>>> 
>>> $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
> 
> -- 
> 
> $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

  reply	other threads:[~2020-09-14 18:39 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  5:37 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2020-09-11 23:58 ` Rodrigo Vivi
2020-09-14  2:34   ` Zhenyu Wang
2020-09-14 18:39     ` Vivi, Rodrigo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-11  8:59 Zhenyu Wang
2022-11-15 15:36 ` Rodrigo Vivi
2022-11-17  3:02   ` Zhenyu Wang
2022-11-17  3:37     ` Vivi, Rodrigo
2022-11-17  5:28       ` Zhenyu Wang
2022-11-17  6:41       ` Zhenyu Wang
2022-11-17 13:49         ` Rodrigo Vivi
2022-04-26  7:58 Wang, Zhi A
2022-04-26  8:37 ` Jani Nikula
2022-04-26  8:38   ` Wang, Zhi A
2022-04-26  8:42   ` Wang, Zhi A
2022-04-26 11:52     ` Jason Gunthorpe
2022-04-28 21:35       ` Alex Williamson
2022-04-28 21:48         ` Alex Williamson
2022-04-26 15:53 ` Jason Gunthorpe
2022-04-26 16:58   ` Wang, Zhi A
2022-04-26 19:19     ` Robert Beckett
2022-04-20  8:04 Wang, Zhi A
2022-04-20 12:13 ` Jason Gunthorpe
2022-04-20 14:41   ` Wang, Zhi A
2022-04-20 15:02     ` Jason Gunthorpe
2022-04-20 16:13       ` Wang, Zhi A
2021-03-16  7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
2020-11-23  9:05 Zhenyu Wang
2020-11-23  9:32 ` Joonas Lahtinen
2020-11-24  3:13   ` Zhenyu Wang
2020-11-24  9:48     ` Jani Nikula
2020-11-27 13:26     ` Joonas Lahtinen
2020-07-20  8:05 Zhenyu Wang
2020-07-21 11:04 ` Joonas Lahtinen
2020-07-22  0:42   ` Zhenyu Wang
2020-07-27 16:39     ` Vivi, Rodrigo
2020-07-28  3:18       ` Zhenyu Wang
2020-05-12  9:40 Zhenyu Wang
2020-05-14 16:04 ` Joonas Lahtinen
2020-04-22  5:12 Zhenyu Wang
2020-04-26  2:46 ` Zhenyu Wang
2020-04-30 12:38   ` Joonas Lahtinen
2020-03-10  8:19 Zhenyu Wang
2020-03-10 22:50 ` Rodrigo Vivi
2020-02-26 10:38 Zhenyu Wang
2020-02-26 11:58 ` Jani Nikula
2020-02-27  9:31   ` Zhenyu Wang
2020-02-26 23:10 ` Rodrigo Vivi

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=7E56BF0B-0E18-44D4-A332-0812A591F087@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=dim-tools@lits.freedesktop.org \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@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.