From: Andrzej Hajda <andrzej.hajda@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>
Subject: [PATCH v3 0/2] drm/xe: flush engine buffers before signalling user fence on all engines
Date: Wed, 05 Jun 2024 09:29:46 +0200 [thread overview]
Message-ID: <20240605-fix_user_fence_posted-v3-0-06e7932f784a@intel.com> (raw)
According to the discussion result on my previous patch [1] I have prepared
new patchset, which reverts previous patch and adds barrier before
user fence signalling.
Tested on LNL.
v3: added fixes tag to patch 1, and r-b to both
[1]: https://lore.kernel.org/intel-xe/Zl5DcuZeZiFgxVdJ@DUT025-TGLU.fm.intel.com/T/#m0b4420045908bac70426728d460108c0b2b65dca
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
- Link to v1: https://lore.kernel.org/r/20240603-fix_user_fence_posted-v1-1-61c76ef69cea@intel.com
- Link to v2: https://lore.kernel.org/r/20240604-fix_user_fence_posted-v2-0-9276ecef973a@intel.com
---
Andrzej Hajda (2):
Revert "drm/xe: flush gtt before signalling user fence on all engines"
drm/xe: flush engine buffers before signalling user fence on all engines
drivers/gpu/drm/xe/xe_ring_ops.c | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
---
base-commit: fe3d637a9c72b22297da0c731fa5e217bd182d2d
change-id: 20240603-fix_user_fence_posted-ca56c79c0662
Best regards,
--
Andrzej Hajda <andrzej.hajda@intel.com>
next reply other threads:[~2024-06-05 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:29 Andrzej Hajda [this message]
2024-06-05 7:29 ` [PATCH v3 1/2] Revert "drm/xe: flush gtt before signalling user fence on all engines" Andrzej Hajda
2024-06-05 19:48 ` Cavitt, Jonathan
2024-06-05 7:29 ` [PATCH v3 2/2] drm/xe: flush engine buffers before signalling user fence on all engines Andrzej Hajda
2024-06-05 19:41 ` Cavitt, Jonathan
2024-06-05 8:17 ` ✓ CI.Patch_applied: success for drm/xe: flush engine buffers before signalling user fence on all engines (rev2) Patchwork
2024-06-05 8:17 ` ✓ CI.checkpatch: " Patchwork
2024-06-05 8:18 ` ✓ CI.KUnit: " Patchwork
2024-06-05 8:29 ` ✓ CI.Build: " Patchwork
2024-06-05 8:29 ` ✗ CI.Hooks: failure " Patchwork
2024-06-05 8:31 ` ✓ CI.checksparse: success " Patchwork
2024-06-05 8:58 ` ✓ CI.BAT: " Patchwork
2024-06-05 20:33 ` ✗ CI.FULL: failure " Patchwork
2024-06-11 12:53 ` â " Andrzej Hajda
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=20240605-fix_user_fence_posted-v3-0-06e7932f784a@intel.com \
--to=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=matthew.brost@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