Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Flush to global observation point before breadcrumb write
Date: Thu, 29 Sep 2022 16:10:06 +0200	[thread overview]
Message-ID: <YzWnPlmn6lt9c0x5@ashyti-mobl2.lan> (raw)
In-Reply-To: <20220927171313.6553-1-nirmoy.das@intel.com>

Hi Nirmoy,

> From: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
> 
> Add flag to pipecontrol instruction to ensure in-flight writes are
> flushed to global observation point. Also split the pipecontrol
> instruction like we have in gen8.
> 
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/5886
> Signed-off-by: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>

pushed in drm-intel-gt-next.

Thanks,
Andi

  parent reply	other threads:[~2022-09-29 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 17:13 [Intel-gfx] [PATCH] drm/i915/gt: Flush to global observation point before breadcrumb write Nirmoy Das
2022-09-27 17:17 ` Das, Nirmoy
2022-09-28  2:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-09-28 13:25 ` [Intel-gfx] [PATCH] " Andi Shyti
2022-09-28 18:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-09-29 10:57   ` Andi Shyti
2022-09-29 14:10 ` Andi Shyti [this message]
2022-09-29 16:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gt: Flush to global observation point before breadcrumb write (rev2) Patchwork
2022-09-29 17:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-30 16:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=YzWnPlmn6lt9c0x5@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@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