intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	<intel-xe@lists.freedesktop.org>,  <saurabhg.gupta@intel.com>,
	<alex.zuo@intel.com>, <umesh.nerlige.ramappa@intel.com>,
	 <john.c.harrison@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3] drm/xe/xe_guc_ads: save/restore OA registers
Date: Tue, 29 Oct 2024 10:15:54 -0700	[thread overview]
Message-ID: <854j4uzv79.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <pug6v3ckrvxd7hkrfmppwxck7nxz3ta36sorzcekpzdwgk5ljt@4hxdgwvuctwj>

On Tue, 29 Oct 2024 09:23:49 -0700, Lucas De Marchi wrote:
>
> On Wed, Oct 23, 2024 at 08:07:15PM +0000, Jonathan Cavitt wrote:
> > Several OA registers and allowlist registers were missing from the
> > save/restore list for GuC and could be lost during an engine reset.  Add
> > them to the list.
> >
> > v2:
> > - Fix commit message (Umesh)
> > - Add missing closes (Ashutosh)
> >
> > v3:
> > - Add missing fixes (Ashutosh)
> >
> > Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2249
> > Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> > Suggested-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> > Suggested-by: John Harrison <john.c.harrison@intel.com>
> > Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> > CC: stable@vger.kernel.org # v6.11+
> > Acked-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_guc_ads.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_guc_ads.c b/drivers/gpu/drm/xe/xe_guc_ads.c
> > index 4e746ae98888..a196c4fb90fc 100644
> > --- a/drivers/gpu/drm/xe/xe_guc_ads.c
> > +++ b/drivers/gpu/drm/xe/xe_guc_ads.c
> > @@ -15,6 +15,7 @@
> > #include "regs/xe_engine_regs.h"
> > #include "regs/xe_gt_regs.h"
> > #include "regs/xe_guc_regs.h"
> > +#include "regs/xe_oa_regs.h"
> > #include "xe_bo.h"
> > #include "xe_gt.h"
> > #include "xe_gt_ccs_mode.h"
> > @@ -740,6 +741,11 @@ static unsigned int guc_mmio_regset_write(struct xe_guc_ads *ads,
> >		guc_mmio_regset_write_one(ads, regset_map, e->reg, count++);
> >	}
> >
> > +	for (i = 0; i < RING_MAX_NONPRIV_SLOTS; i++)
> > +		guc_mmio_regset_write_one(ads, regset_map,
> > +					  RING_FORCE_TO_NONPRIV(hwe->mmio_base, i),
> > +					  count++);
>
> this is not the proper place. See drivers/gpu/drm/xe/xe_reg_whitelist.c.

Yikes, this got merged yesterday.

>
> The loop just before these added lines should be sufficient to go over
> all engine save/restore register and give them to guc.

You probably mean this one?

	xa_for_each(&hwe->reg_sr.xa, idx, entry)
		guc_mmio_regset_write_one(ads, regset_map, entry->reg, count++);

But then how come this patch fixed GL #2249?

Ashutosh

  reply	other threads:[~2024-10-29 17:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 20:07 [PATCH v3] drm/xe/xe_guc_ads: save/restore OA registers Jonathan Cavitt
2024-10-24 11:52 ` ✓ CI.Patch_applied: success for drm/xe/xe_guc_ads: save/restore OA registers (rev3) Patchwork
2024-10-24 11:52 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 11:53 ` ✓ CI.KUnit: " Patchwork
2024-10-24 12:05 ` ✓ CI.Build: " Patchwork
2024-10-24 12:07 ` ✓ CI.Hooks: " Patchwork
2024-10-24 12:08 ` ✓ CI.checksparse: " Patchwork
2024-10-24 12:30 ` ✗ CI.BAT: failure " Patchwork
2024-10-25  9:19 ` ✗ CI.FULL: " Patchwork
2024-10-28 16:36 ` [PATCH v3] drm/xe/xe_guc_ads: save/restore OA registers Dixit, Ashutosh
2024-10-28 20:38   ` Umesh Nerlige Ramappa
2024-10-28 20:48     ` Dixit, Ashutosh
2024-10-28 22:49 ` Dixit, Ashutosh
2024-10-29 16:23 ` Lucas De Marchi
2024-10-29 17:15   ` Dixit, Ashutosh [this message]
2024-10-29 17:32     ` Lucas De Marchi
2024-10-29 19:33       ` Matt Roper
2024-10-29 19:44         ` Dixit, Ashutosh
2024-10-29 19:50           ` Lucas De Marchi
2024-10-29 19:46         ` Lucas De Marchi
2024-10-29 21:19         ` Umesh Nerlige Ramappa
2024-10-29 19:38       ` Dixit, Ashutosh

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=854j4uzv79.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=alex.zuo@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=jonathan.cavitt@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=saurabhg.gupta@intel.com \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).