public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Joshua Santosh" <joshua.santosh.ranjan@intel.com>,
	"José Roberto de Souza" <jose.souza@intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/xe/uapi: loosen used tracking restriction
Date: Fri, 19 Sep 2025 17:19:26 -0400	[thread overview]
Message-ID: <aM3I3oRNuZL86_3X@intel.com> (raw)
In-Reply-To: <20250919122052.420979-2-matthew.auld@intel.com>

On Fri, Sep 19, 2025 at 01:20:53PM +0100, Matthew Auld wrote:
> Currently this is hidden behind perfmon_capable() since this is
> technically an info leak, given that this is a system wide metric.
> However the granularity reported here is always PAGE_SIZE aligned, which
> matches what the core kernel is already willing to expose to userspace
> if querying how many free RAM pages there are on the system, and that
> doesn't need any special privileges. In addition other drm drivers seem
> happy to expose this.
> 
> The motivation here if with oneAPI where they want to use the system
> wide 'used' reporting here, so not the per-client fdinfo stats. This has
> also come up with some perf overlay applications wanting this
> information.
> 
> Fixes: 1105ac15d2a1 ("drm/xe/uapi: restrict system wide accounting")
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Joshua Santosh <joshua.santosh.ranjan@intel.com>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: <stable@vger.kernel.org> # v6.8+

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

> ---
>  drivers/gpu/drm/xe/xe_query.c | 15 ++++++---------
>  1 file changed, 6 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_query.c b/drivers/gpu/drm/xe/xe_query.c
> index e1b603aba61b..2e9ff33ed2fe 100644
> --- a/drivers/gpu/drm/xe/xe_query.c
> +++ b/drivers/gpu/drm/xe/xe_query.c
> @@ -276,8 +276,7 @@ static int query_mem_regions(struct xe_device *xe,
>  	mem_regions->mem_regions[0].instance = 0;
>  	mem_regions->mem_regions[0].min_page_size = PAGE_SIZE;
>  	mem_regions->mem_regions[0].total_size = man->size << PAGE_SHIFT;
> -	if (perfmon_capable())
> -		mem_regions->mem_regions[0].used = ttm_resource_manager_usage(man);
> +	mem_regions->mem_regions[0].used = ttm_resource_manager_usage(man);
>  	mem_regions->num_mem_regions = 1;
>  
>  	for (i = XE_PL_VRAM0; i <= XE_PL_VRAM1; ++i) {
> @@ -293,13 +292,11 @@ static int query_mem_regions(struct xe_device *xe,
>  			mem_regions->mem_regions[mem_regions->num_mem_regions].total_size =
>  				man->size;
>  
> -			if (perfmon_capable()) {
> -				xe_ttm_vram_get_used(man,
> -					&mem_regions->mem_regions
> -					[mem_regions->num_mem_regions].used,
> -					&mem_regions->mem_regions
> -					[mem_regions->num_mem_regions].cpu_visible_used);
> -			}
> +			xe_ttm_vram_get_used(man,
> +					     &mem_regions->mem_regions
> +					     [mem_regions->num_mem_regions].used,
> +					     &mem_regions->mem_regions
> +					     [mem_regions->num_mem_regions].cpu_visible_used);
>  
>  			mem_regions->mem_regions[mem_regions->num_mem_regions].cpu_visible_size =
>  				xe_ttm_vram_get_cpu_visible_size(man);
> -- 
> 2.51.0
> 

  reply	other threads:[~2025-09-19 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 12:20 [PATCH] drm/xe/uapi: loosen used tracking restriction Matthew Auld
2025-09-19 21:19 ` Rodrigo Vivi [this message]
2025-09-19 23:05 ` Lucas De Marchi

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=aM3I3oRNuZL86_3X@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=joshua.santosh.ranjan@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.hellstrom@linux.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