Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe/guc: Allow MMIO communication even if CTB is enabled
Date: Fri, 12 Jan 2024 16:25:48 +0000	[thread overview]
Message-ID: <ZaFoDFQj58S+ODiQ@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240112132248.805-1-michal.wajdeczko@intel.com>

On Fri, Jan 12, 2024 at 02:22:48PM +0100, Michal Wajdeczko wrote:
> GuC is still able to communicate over MMIO even after we enable CTB
> communication channel.  While there are only few limited cases when
> we might want to use MMIO, we shouldn't block that with assert.
> 

What is the use case for this? I thought GuC arch team said we should
not use MMIO once CTBs are enabled. Maybe I'm misremebering?

Regardless I think we should probably leave it in until we have use
case.

Matt 

> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_guc.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 235d27b17ff9..d4db0a34adbf 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -674,7 +674,6 @@ int xe_guc_mmio_send_recv(struct xe_guc *guc, const u32 *request,
>  
>  	BUILD_BUG_ON(VF_SW_FLAG_COUNT != MED_VF_SW_FLAG_COUNT);
>  
> -	xe_assert(xe, !guc->ct.enabled);
>  	xe_assert(xe, len);
>  	xe_assert(xe, len <= VF_SW_FLAG_COUNT);
>  	xe_assert(xe, len <= MED_VF_SW_FLAG_COUNT);
> 
> base-commit: 7a20187068bed91b523795a18219e570f1e84eb1
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2024-01-12 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 13:22 [PATCH] drm/xe/guc: Allow MMIO communication even if CTB is enabled Michal Wajdeczko
2024-01-12 14:28 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-12 14:28 ` ✓ CI.checkpatch: " Patchwork
2024-01-12 14:29 ` ✓ CI.KUnit: " Patchwork
2024-01-12 14:36 ` ✓ CI.Build: " Patchwork
2024-01-12 14:37 ` ✓ CI.Hooks: " Patchwork
2024-01-12 14:38 ` ✓ CI.checksparse: " Patchwork
2024-01-12 15:01 ` ✓ CI.BAT: " Patchwork
2024-01-12 16:25 ` Matthew Brost [this message]

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=ZaFoDFQj58S+ODiQ@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@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