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>,
	Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH 1/2] drm/xe/guc: Unblock GuC buffer cache for all modes
Date: Mon, 12 May 2025 15:11:52 -0700	[thread overview]
Message-ID: <aCJyKEpaPHvz/noD@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250512220018.172-2-michal.wajdeczko@intel.com>

On Tue, May 13, 2025 at 12:00:17AM +0200, Michal Wajdeczko wrote:
> Today we were using GuC buffer cache only in the PF mode, but
> shortly we will want to use it also in native and VF mode.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Should we mark these patches as fixes? A malicious user could consume
all the VRAM on the device by changing wedged mode via debugfs enough
times... 

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_guc.c     | 4 ++++
>  drivers/gpu/drm/xe/xe_guc_buf.c | 4 ----
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index bac5471a1a78..350434a8b953 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -710,6 +710,10 @@ static int vf_guc_init_post_hwconfig(struct xe_guc *guc)
>  	if (err)
>  		return err;
>  
> +	err = xe_guc_buf_cache_init(&guc->buf);
> +	if (err)
> +		return err;
> +
>  	/* XXX xe_guc_db_mgr_init not needed for now */
>  
>  	return 0;
> diff --git a/drivers/gpu/drm/xe/xe_guc_buf.c b/drivers/gpu/drm/xe/xe_guc_buf.c
> index 0193c94dd6a0..14a07dca48e7 100644
> --- a/drivers/gpu/drm/xe/xe_guc_buf.c
> +++ b/drivers/gpu/drm/xe/xe_guc_buf.c
> @@ -37,10 +37,6 @@ int xe_guc_buf_cache_init(struct xe_guc_buf_cache *cache)
>  	struct xe_gt *gt = cache_to_gt(cache);
>  	struct xe_sa_manager *sam;
>  
> -	/* XXX: currently it's useful only for the PF actions */
> -	if (!IS_SRIOV_PF(gt_to_xe(gt)))
> -		return 0;
> -
>  	sam = __xe_sa_bo_manager_init(gt_to_tile(gt), SZ_8K, 0, sizeof(u32));
>  	if (IS_ERR(sam))
>  		return PTR_ERR(sam);
> -- 
> 2.47.1
> 

  reply	other threads:[~2025-05-12 22:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 22:00 [PATCH 0/2] Don't allocate managed BO for each policy change Michal Wajdeczko
2025-05-12 22:00 ` [PATCH 1/2] drm/xe/guc: Unblock GuC buffer cache for all modes Michal Wajdeczko
2025-05-12 22:11   ` Matthew Brost [this message]
2025-05-13 20:57     ` Lucas De Marchi
2025-05-12 22:32   ` Daniele Ceraolo Spurio
2025-05-12 22:00 ` [PATCH 2/2] drm/xe/guc: Don't allocate managed BO for each policy change Michal Wajdeczko
2025-05-12 22:12   ` Matthew Brost
2025-05-12 22:15 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-12 22:15 ` ✓ CI.checkpatch: " Patchwork
2025-05-12 22:16 ` ✓ CI.KUnit: " Patchwork
2025-05-12 22:26 ` ✗ CI.Build: failure " Patchwork
2025-05-13 14:24 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-13 14:24 ` ✓ CI.checkpatch: " Patchwork
2025-05-13 14:25 ` ✓ CI.KUnit: " Patchwork
2025-05-13 14:35 ` ✓ CI.Build: " Patchwork
2025-05-14 18:51 ` ✓ CI.Patch_applied: success for Don't allocate managed BO for each policy change (rev2) Patchwork
2025-05-14 18:51 ` ✓ CI.checkpatch: " Patchwork
2025-05-14 18:53 ` ✓ CI.KUnit: " Patchwork
2025-05-14 19:03 ` ✓ CI.Build: " Patchwork
2025-05-14 19:06 ` ✓ CI.Hooks: " Patchwork
2025-05-14 19:07 ` ✓ CI.checksparse: " Patchwork
2025-05-14 19:59 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-15  3:31 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-15  6:29   ` Michal Wajdeczko
2025-05-27  0:49 ` ✗ CI.Patch_applied: " 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=aCJyKEpaPHvz/noD@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=daniele.ceraolospurio@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