From: Matthew Brost <matthew.brost@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Matthew Auld" <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/xe: flush gtt before signalling user fence on media engines
Date: Tue, 21 May 2024 15:59:16 +0000 [thread overview]
Message-ID: <ZkzE1DFaYsl1bkv7@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240521-xu_flush_vcs_before_ufence-v1-1-ded38b56c8c9@intel.com>
On Tue, May 21, 2024 at 05:23:46PM +0200, Andrzej Hajda wrote:
> Tests show that user fence signalling requires kind of write barrier,
> otherwise not all writes performed by the workload will be available
> to userspace.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1488
> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
Fixes tag?
With a proper fixes tag:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_ring_ops.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_ring_ops.c b/drivers/gpu/drm/xe/xe_ring_ops.c
> index a3ca718456f6..eb36901f96ff 100644
> --- a/drivers/gpu/drm/xe/xe_ring_ops.c
> +++ b/drivers/gpu/drm/xe/xe_ring_ops.c
> @@ -293,13 +293,13 @@ static void __emit_job_gen12_video(struct xe_sched_job *job, struct xe_lrc *lrc,
>
> i = emit_bb_start(batch_addr, ppgtt_flag, dw, i);
>
> + i = emit_flush_imm_ggtt(xe_lrc_seqno_ggtt_addr(lrc), seqno, false, dw, i);
> +
> if (job->user_fence.used)
> i = emit_store_imm_ppgtt_posted(job->user_fence.addr,
> job->user_fence.value,
> dw, i);
>
> - i = emit_flush_imm_ggtt(xe_lrc_seqno_ggtt_addr(lrc), seqno, false, dw, i);
> -
> i = emit_user_interrupt(dw, i);
>
> xe_gt_assert(gt, i <= MAX_JOB_SIZE_DW);
>
> ---
> base-commit: 188ced1e0ff892f0948f20480e2e0122380ae46d
> change-id: 20240521-xu_flush_vcs_before_ufence-a7b45d94cf33
>
> Best regards,
> --
> Andrzej Hajda <andrzej.hajda@intel.com>
>
next prev parent reply other threads:[~2024-05-21 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:23 [PATCH] drm/xe: flush gtt before signalling user fence on media engines Andrzej Hajda
2024-05-21 15:59 ` Matthew Brost [this message]
2024-05-21 18:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-05-21 18:05 ` ✓ CI.checkpatch: " Patchwork
2024-05-21 18:06 ` ✓ CI.KUnit: " Patchwork
2024-05-21 18:19 ` ✓ CI.Build: " Patchwork
2024-05-21 18:23 ` ✓ CI.Hooks: " Patchwork
2024-05-21 18:25 ` ✓ CI.checksparse: " Patchwork
2024-05-21 18:55 ` ✗ CI.BAT: failure " Patchwork
2024-05-22 0:58 ` ✗ CI.FULL: " 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=ZkzE1DFaYsl1bkv7@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.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