Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Jani Nikula <jani.nikula@linux.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 09:17:20 -0700	[thread overview]
Message-ID: <8734m71o1b.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87wmjjke75.fsf@intel.com>

On Tue, 10 Sep 2024 03:14:54 -0700, Jani Nikula wrote:
>
> On Mon, 09 Sep 2024, Ashutosh Dixit <ashutosh.dixit@intel.com> 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
>
> Please do not resend patches just to tweak something in the commit
> message. It can be fixed while applying. Or when you have to make
> another version with actual functional changes.
>
> Please appreciate that this uses a full CI test run. It's not an
> unlimited resource.

OK, yeah, sorry, this patch especially was a bit excessive.

  reply	other threads:[~2024-09-10 16:17 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 [this message]
2024-09-10 16:14 ` Matthew Brost
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=8734m71o1b.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --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