From: Matthew Brost <matthew.brost@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH] drm/xe/oa: Insert wmb/sfence before enabling OA
Date: Tue, 10 Sep 2024 16:14:11 +0000 [thread overview]
Message-ID: <ZuBwU0mxzS2e9P5s@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240910025907.2667875-1-ashutosh.dixit@intel.com>
On Mon, Sep 09, 2024 at 07:59:07PM -0700, Ashutosh Dixit wrote:
> We are occasionally seeing that OA Buffer register is not programmed (has
> value 0) when OA is enabled. This means OA has been enabled before it has
> been fully configured. Or, the register write enabling OA has overtaken
> previous OA configuration register writes.
>
> Therefore, insert a wmb/sfence to preserve OA register write ordering
> before enabling OA.
>
> v2: s/wmb()/xe_device_wmb()/
>
> Fixes: e936f885f1e9 ("drm/xe/oa/uapi: Expose OA stream fd")
> Reported-by: Guy Zadicario <guy.zadicario@intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/xe/xe_oa.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> index 63286ed8457fa..4fb7aae37a94f 100644
> --- a/drivers/gpu/drm/xe/xe_oa.c
> +++ b/drivers/gpu/drm/xe/xe_oa.c
> @@ -440,6 +440,9 @@ static void xe_oa_enable(struct xe_oa_stream *stream)
> val = __format_to_oactrl(format, regs->oa_ctrl_counter_select_mask) |
> __oa_ccs_select(stream) | OAG_OACONTROL_OA_COUNTER_ENABLE;
>
> + /* Flush previous writes to HW before enabling OA */
> + xe_device_wmb(stream->oa->xe);
> +
So is preventing the xe_mmio_write32 passing the memset in
xe_oa_init_oa_buffer. Indeed a xe_device_wmb is needed.
I will say it a bit goofy that stream->oa_buffer.vaddr is accessed
directly in the OA code rather than using the xe_map layer which made it
a little harder to reach the above conclusion. You might want to fixup
the OA to use the xe_map layer rather than directly accessing pointers
if that is possible.
Anyways, this LGTM:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> xe_mmio_write32(stream->gt, regs->oa_ctrl, val);
> }
>
> --
> 2.41.0
>
next prev parent reply other threads:[~2024-09-10 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 2:59 [PATCH] drm/xe/oa: Insert wmb/sfence before enabling OA Ashutosh Dixit
2024-09-10 3:16 ` ✓ CI.Patch_applied: success for drm/xe/oa: Insert wmb/sfence before enabling OA (rev6) Patchwork
2024-09-10 3:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-10 3:19 ` ✓ CI.KUnit: success " Patchwork
2024-09-10 3:31 ` ✓ CI.Build: " Patchwork
2024-09-10 3:34 ` ✓ CI.Hooks: " Patchwork
2024-09-10 3:35 ` ✓ CI.checksparse: " Patchwork
2024-09-10 4:37 ` ✗ CI.BAT: failure " Patchwork
2024-09-10 6:36 ` ✗ CI.FULL: " Patchwork
2024-09-10 10:14 ` [PATCH] drm/xe/oa: Insert wmb/sfence before enabling OA Jani Nikula
2024-09-10 16:17 ` Dixit, Ashutosh
2024-09-10 16:14 ` Matthew Brost [this message]
2024-09-10 20:28 ` Dixit, Ashutosh
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 1:39 Ashutosh Dixit
2024-09-10 0:43 Ashutosh Dixit
2024-08-28 15:55 Ashutosh Dixit
2024-08-26 23:34 Ashutosh Dixit
2024-08-26 23:29 Ashutosh Dixit
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=ZuBwU0mxzS2e9P5s@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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