From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: 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: Mon, 28 Oct 2024 09:36:32 -0700 [thread overview]
Message-ID: <854j4wtca7.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20241023200716.82624-1-jonathan.cavitt@intel.com>
On Wed, 23 Oct 2024 13:07:15 -0700, Jonathan Cavitt wrote:
>
Hi Umesh,
> @@ -748,6 +754,14 @@ static unsigned int guc_mmio_regset_write(struct xe_guc_ads *ads,
> }
> }
>
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL0, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL1, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL2, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL3, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL4, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL5, count++);
> + guc_mmio_regset_write_one(ads, regset_map, EU_PERF_CNTL6, count++);
I am trying to understand how this works. So these registers are
saved/restored by GuC because they are not part of HW context image and
that is why GuC needs to do the save/restore? Bspec 46458/56839 do seem to
be saying that these registers are context saved/restored? If that is
indeed true (though not sure), do they need to be here?
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2024-10-28 16:36 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 ` Dixit, Ashutosh [this message]
2024-10-28 20:38 ` [PATCH v3] drm/xe/xe_guc_ads: save/restore OA registers 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
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=854j4wtca7.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=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 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.