Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/guc: Promote GUC_GGTT_TOP definition to regs/xe_guc_regs.h
Date: Tue, 13 Feb 2024 17:24:03 -0500	[thread overview]
Message-ID: <ZcvsAxWzSAy_TEFs@intel.com> (raw)
In-Reply-To: <20240213213634.1437-1-michal.wajdeczko@intel.com>

On Tue, Feb 13, 2024 at 10:36:34PM +0100, Michal Wajdeczko wrote:
> This is a hardware based definition and instead of multiple local
> definitions it would be better to have just one common definition.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/regs/xe_guc_regs.h | 3 +++
>  drivers/gpu/drm/xe/xe_ggtt.c          | 4 +---
>  drivers/gpu/drm/xe/xe_guc.c           | 2 --
>  3 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/regs/xe_guc_regs.h b/drivers/gpu/drm/xe/regs/xe_guc_regs.h
> index 92320bbc9d3d..087eaa3b4d63 100644
> --- a/drivers/gpu/drm/xe/regs/xe_guc_regs.h
> +++ b/drivers/gpu/drm/xe/regs/xe_guc_regs.h
> @@ -140,4 +140,7 @@ struct guc_doorbell_info {
>  	u32 reserved[14];
>  } __packed;
>  
> +/* GuC addresses above GUC_GGTT_TOP also don't map through the GTT */
> +#define GUC_GGTT_TOP				0xFEE00000
> +
>  #endif
> diff --git a/drivers/gpu/drm/xe/xe_ggtt.c b/drivers/gpu/drm/xe/xe_ggtt.c
> index ab96edb058d6..df5c58c63b74 100644
> --- a/drivers/gpu/drm/xe/xe_ggtt.c
> +++ b/drivers/gpu/drm/xe/xe_ggtt.c
> @@ -11,6 +11,7 @@
>  #include <drm/i915_drm.h>
>  
>  #include "regs/xe_gt_regs.h"
> +#include "regs/xe_guc_regs.h"

xe_ggtt component having to access xe_guc_regs doesn't the right movement to me.

what about moving that to xe_gt_regs?

>  #include "regs/xe_regs.h"
>  #include "xe_assert.h"
>  #include "xe_bo.h"
> @@ -26,9 +27,6 @@
>  #define XELPG_GGTT_PTE_PAT0	BIT_ULL(52)
>  #define XELPG_GGTT_PTE_PAT1	BIT_ULL(53)
>  
> -/* GuC addresses above GUC_GGTT_TOP also don't map through the GTT */
> -#define GUC_GGTT_TOP	0xFEE00000
> -
>  static u64 xelp_ggtt_pte_encode_bo(struct xe_bo *bo, u64 bo_offset,
>  				   u16 pat_index)
>  {
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 868208a39829..53a72769d3b4 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -32,8 +32,6 @@
>  #include "xe_wa.h"
>  #include "xe_wopcm.h"
>  
> -/* GuC addresses above GUC_GGTT_TOP also don't map through the GTT */
> -#define GUC_GGTT_TOP    0xFEE00000
>  static u32 guc_bo_ggtt_addr(struct xe_guc *guc,
>  			    struct xe_bo *bo)
>  {
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-02-13 22:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 21:36 [PATCH] drm/xe/guc: Promote GUC_GGTT_TOP definition to regs/xe_guc_regs.h Michal Wajdeczko
2024-02-13 22:24 ` Rodrigo Vivi [this message]
2024-02-14 17:47   ` Michal Wajdeczko
2024-03-25 18:10     ` Matt Roper
2024-02-13 23:02 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-13 23:02 ` ✓ CI.checkpatch: " Patchwork
2024-02-13 23:03 ` ✓ CI.KUnit: " Patchwork
2024-02-13 23:13 ` ✓ CI.Build: " Patchwork
2024-02-13 23:14 ` ✓ CI.Hooks: " Patchwork
2024-02-13 23:15 ` ✓ CI.checksparse: " Patchwork
2024-02-13 23:37 ` ✓ CI.BAT: " 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=ZcvsAxWzSAy_TEFs@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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