Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/3] drm/xe: Fix devcoredump readout of IPEHR
Date: Wed, 4 Oct 2023 13:10:40 -0400	[thread overview]
Message-ID: <ZR2ckGE1I01c46HT@intel.com> (raw)
In-Reply-To: <20231003202728.132545-2-jose.souza@intel.com>

On Tue, Oct 03, 2023 at 01:27:27PM -0700, José Roberto de Souza wrote:
> It was reading (base) + 0x88 but that is not a valid register

s/88/8c

but you probably need a similar commit message used in commit 3.
After updating it,

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> and instead it should read (base) + 0x68.
> 
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
>  drivers/gpu/drm/xe/regs/xe_engine_regs.h | 1 -
>  drivers/gpu/drm/xe/xe_hw_engine.c        | 2 +-
>  2 files changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/regs/xe_engine_regs.h b/drivers/gpu/drm/xe/regs/xe_engine_regs.h
> index 692213d09ceaa..792d431161c68 100644
> --- a/drivers/gpu/drm/xe/regs/xe_engine_regs.h
> +++ b/drivers/gpu/drm/xe/regs/xe_engine_regs.h
> @@ -37,7 +37,6 @@
>  #define RING_DMA_FADD(base)			XE_REG((base) + 0x78)
>  #define RING_HWS_PGA(base)			XE_REG((base) + 0x80)
>  #define IPEIR(base)				XE_REG((base) + 0x88)
> -#define IPEHR(base)				XE_REG((base) + 0x8c)
>  #define RING_HWSTAM(base)			XE_REG((base) + 0x98)
>  #define RING_MI_MODE(base)			XE_REG((base) + 0x9c)
>  #define RING_NOPID(base)			XE_REG((base) + 0x94)
> diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
> index dc9dd83d99c52..c2db391cf2674 100644
> --- a/drivers/gpu/drm/xe/xe_hw_engine.c
> +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
> @@ -728,7 +728,7 @@ xe_hw_engine_snapshot_capture(struct xe_hw_engine *hwe)
>  	snapshot->reg.ring_dma_fadd =
>  		hw_engine_mmio_read32(hwe, RING_DMA_FADD(0));
>  	snapshot->reg.ipeir = hw_engine_mmio_read32(hwe, IPEIR(0));
> -	snapshot->reg.ipehr = hw_engine_mmio_read32(hwe, IPEHR(0));
> +	snapshot->reg.ipehr = hw_engine_mmio_read32(hwe, RING_IPEHR(0));
>  
>  	if (snapshot->class == XE_ENGINE_CLASS_COMPUTE)
>  		snapshot->reg.rcu_mode = xe_mmio_read32(hwe->gt, RCU_MODE);
> -- 
> 2.42.0
> 

  reply	other threads:[~2023-10-04 17:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 20:27 [Intel-xe] [PATCH 1/3] drm/xe: Fix RING_MI_MODE label in devcoredump José Roberto de Souza
2023-10-03 20:27 ` [Intel-xe] [PATCH 2/3] drm/xe: Fix devcoredump readout of IPEHR José Roberto de Souza
2023-10-04 17:10   ` Rodrigo Vivi [this message]
2023-10-03 20:27 ` [Intel-xe] [PATCH 3/3] drm/xe: Remove devcoredump readout of IPEIR José Roberto de Souza
2023-10-04 17:11   ` Rodrigo Vivi
2023-10-04 17:15     ` Souza, Jose
2023-10-04 17:32       ` Rodrigo Vivi
2023-10-03 21:14 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: Fix RING_MI_MODE label in devcoredump Patchwork
2023-10-03 21:14 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-10-03 21:16 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-10-03 21:23 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 21:23 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 21:24 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 22:02 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-10-04 17:11 ` [Intel-xe] [PATCH 1/3] " Rodrigo Vivi

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=ZR2ckGE1I01c46HT@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@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