All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"thomas.hellstrom@linux.intel.com"
	<thomas.hellstrom@linux.intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Brost,\ Matthew" <matthew.brost@intel.com>,
	"Nerlige Ramappa, Umesh" <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH] drm/xe: Force write completion of MI_STORE_DATA_IMM
Date: Thu, 19 Dec 2024 08:05:26 -0800	[thread overview]
Message-ID: <85v7vf1wvt.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <ea6999937576f73fa5e9c54e24f940d83bb3eef1.camel@intel.com>

On Thu, 19 Dec 2024 05:58:59 -0800, Souza, Jose wrote:
>
> On Wed, 2024-12-18 at 18:05 -0800, Dixit, Ashutosh wrote:
> > On Wed, 18 Dec 2024 09:27:36 -0800, Matthew Brost wrote:
> > >
> >
> > Folks,
> >
> > > On Wed, Dec 18, 2024 at 08:38:49AM -0700, Souza, Jose wrote:
> > > > On Tue, 2024-12-17 at 15:39 -0800, Matthew Brost wrote:
> > > > > On Tue, Dec 17, 2024 at 08:07:32AM -0800, José Roberto de Souza wrote:
> > > > > > With Force write completion unset there is no guarantees of when the
> > > > > > write will be globally visible what is not the behavior wanted.
> > > > > >
> > > > >
> > > > > Do we want this backported? If so, maybe add a fixes?
> > > >
> > > > Not sure, I don't have an actual issue that is fixed by this but I
> > > > think would be good to have it backported.  But what do you
> > > > suggest? Add a fixes tag to the patch removing force probe from
> > > > LNL?
> > > >
> > >
> > > Yea fixing LNL force probe removal sounds reasonable to me.
> >
> > Hmm the plan was add Fixes to this patch and also Cc: stable. Yet it was
> > merged without these:
> >
> > 1460bb1fef9c ("drm/xe: Force write completion of MI_STORE_DATA_IMM")
> >
> > Lucas/Thomas,
> >
> > Would it be possible to send it to -fixes with a Cc:stable. We have patches
> > depending on this one which we want to send to stable.
>
> Please correct me if I'm wrong but that is enough for it to be picked to
> stable, it will happen in the next Xe stable pull request.

Ah, ok, sorry I missed that there is a Fixes: in the merged patch, so maybe
that is sufficient for it to be picked to stable.

  reply	other threads:[~2024-12-19 16:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 16:07 [PATCH] drm/xe: Force write completion of MI_STORE_DATA_IMM José Roberto de Souza
2024-12-17 17:36 ` Dixit, Ashutosh
2024-12-17 21:58 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-17 21:58 ` ✓ CI.checkpatch: " Patchwork
2024-12-17 21:59 ` ✓ CI.KUnit: " Patchwork
2024-12-17 22:17 ` ✓ CI.Build: " Patchwork
2024-12-17 22:20 ` ✓ CI.Hooks: " Patchwork
2024-12-17 22:21 ` ✓ CI.checksparse: " Patchwork
2024-12-17 22:59 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-17 23:39 ` [PATCH] " Matthew Brost
2024-12-18 15:38   ` Souza, Jose
2024-12-18 17:27     ` Matthew Brost
2024-12-19  2:05       ` Dixit, Ashutosh
2024-12-19 13:58         ` Souza, Jose
2024-12-19 16:05           ` Dixit, Ashutosh [this message]
2024-12-23 15:14       ` Thomas Hellström
2024-12-18  9:07 ` ✗ Xe.CI.Full: failure for " 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=85v7vf1wvt.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=thomas.hellstrom@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.