Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Matt Roper <matthew.d.roper@intel.com>,
	Jonathan Cavitt <jonathan.cavitt@intel.com>,
	<ashutosh.dixit@intel.com>
Subject: Re: [PATCH 2/5] drm/xe/reg_sr: Write all whitelist slots
Date: Thu, 5 Dec 2024 14:51:00 -0800	[thread overview]
Message-ID: <dee410d2-f96e-4819-aa5f-7060b1d376c8@intel.com> (raw)
In-Reply-To: <20241205182240.3463027-3-lucas.demarchi@intel.com>

On 12/5/2024 10:22, Lucas De Marchi wrote:
> Currently if there's 1 whitelisted register in the engine, on slot is
> written with that register and all the others are written to a sane
> value. For the free slots, there's no reason to change the behavior
> if there are 0, 1 or slots occupied. If the default value from HW is not
> trusted, all values should be written to.
>
> Also, later on all values are passed to GuC via ADS to be restored on
The values are not passed to GuC, only the register addresses. GuC does 
a read prior to reset and a write post reset of the registers to 
preserve their value at the point of reset. It does not blanket restore 
a fixed value set by the KMD at start of day.

John.

> engine reset, so make sure they are also written to when probing the
> device.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_reg_sr.c | 3 ---
>   1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_reg_sr.c b/drivers/gpu/drm/xe/xe_reg_sr.c
> index c13123008e903..f982c1cdb369c 100644
> --- a/drivers/gpu/drm/xe/xe_reg_sr.c
> +++ b/drivers/gpu/drm/xe/xe_reg_sr.c
> @@ -204,9 +204,6 @@ void xe_reg_sr_apply_whitelist(struct xe_hw_engine *hwe)
>   	unsigned int slot = 0;
>   	unsigned int fw_ref;
>   
> -	if (xa_empty(&sr->xa))
> -		return;
> -
>   	drm_dbg(&xe->drm, "Whitelisting %s registers\n", sr->name);
>   
>   	fw_ref = xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL);


  parent reply	other threads:[~2024-12-05 22:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 18:22 [PATCH 0/5] reg_sr/whitelist fixes and refactors Lucas De Marchi
2024-12-05 18:22 ` [PATCH 1/5] drm/xe/reg_sr: Remove register pool Lucas De Marchi
2024-12-05 18:37   ` Matt Roper
2024-12-05 18:43     ` Lucas De Marchi
2024-12-05 18:22 ` [PATCH 2/5] drm/xe/reg_sr: Write all whitelist slots Lucas De Marchi
2024-12-05 19:25   ` Matt Roper
2024-12-06  5:03     ` Lucas De Marchi
2024-12-05 22:51   ` John Harrison [this message]
2024-12-06  5:02     ` Lucas De Marchi
2024-12-05 18:22 ` [PATCH 3/5] drm/xe: Add xe_gt_dbg_printer Lucas De Marchi
2024-12-05 19:27   ` Matt Roper
2024-12-05 19:51   ` Michal Wajdeczko
2024-12-05 18:22 ` [PATCH 4/5] drmxe/reg_sr: Convert whitelist to gt logging Lucas De Marchi
2024-12-05 19:27   ` Matt Roper
2024-12-05 18:22 ` [PATCH 5/5] drm/xe: Apply whitelist to engine save-restore Lucas De Marchi
2024-12-05 20:42   ` Matt Roper
2024-12-06  5:06     ` Lucas De Marchi
2024-12-09 21:13     ` Lucas De Marchi
2024-12-05 23:14   ` John Harrison
2024-12-09 21:53     ` Lucas De Marchi
2024-12-05 18:32 ` ✓ CI.Patch_applied: success for reg_sr/whitelist fixes and refactors Patchwork
2024-12-05 18:32 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-05 18:34 ` ✓ CI.KUnit: success " Patchwork
2024-12-05 19:06 ` ✓ CI.Build: " Patchwork
2024-12-05 19:08 ` ✓ CI.Hooks: " Patchwork
2024-12-05 19:10 ` ✓ CI.checksparse: " Patchwork
2024-12-05 19:30 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-12-05 20:32 ` ✗ Xe.CI.Full: " 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=dee410d2-f96e-4819-aa5f-7060b1d376c8@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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