Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Riana Tauro <riana.tauro@intel.com>, intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, umesh.nerlige.ramappa@intel.com,
	lucas.demarchi@intel.com, vinay.belgaumkar@intel.com,
	soham.purkait@intel.com
Subject: Re: [PATCH v5 7/8] drm/xe/xe_pmu: Add pmu support for per-function engine activity stats
Date: Thu, 6 Feb 2025 20:15:42 +0100	[thread overview]
Message-ID: <61dd8ba7-5fa2-47db-a03f-81fae29cc1e9@intel.com> (raw)
In-Reply-To: <20250206104358.3436519-8-riana.tauro@intel.com>



On 06.02.2025 11:43, Riana Tauro wrote:
> Add pmu support for per-function engine activity
> stats.

PMU ?
unneeded line wrap ?

> 
> per-function engine activity is enabled when sriov_numvfs
> are set. If sriov_numvfs is set to 2, then the applicable function
> values are
> 
> 0 - PF engine activity
> 1,2 - per-VF engine activity from PF

0 - PF engine activity
1 - VF1 engine activity
2 - VF2 engine activity

but maybe better to show full entries:

xe_0000_03_00.0/engine...ticks/ - PF activity
xe_0000_03_00.1/engine...ticks/ - VF1 activity
xe_0000_03_00.2/engine...ticks/ - VF2 activity

as 'function' term here matches 'PCI function'

> 
> This can be read from perf tool as shown below
> 
> ./perf stat -e xe_<bdf>/engine-active-ticks,gt=0,engine_class=0,
> 			 engine_instance=0,function=1/ -I 1000
> 
> v2: fix documentation (Umesh)
>     remove global for functions (Lucas, Michal)
> 
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pmu.c | 38 ++++++++++++++++++++++++++++++-------
>  1 file changed, 31 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pmu.c b/drivers/gpu/drm/xe/xe_pmu.c
> index a758fc517048..66cf2ece97ec 100644
> --- a/drivers/gpu/drm/xe/xe_pmu.c
> +++ b/drivers/gpu/drm/xe/xe_pmu.c
> @@ -13,6 +13,7 @@
>  #include "xe_hw_engine.h"
>  #include "xe_pm.h"
>  #include "xe_pmu.h"
> +#include "xe_sriov_pf_helpers.h"
>  
>  /**
>   * DOC: Xe PMU (Performance Monitoring Unit)
> @@ -32,9 +33,10 @@
>   *	gt[60:63]		Selects gt for the event
>   *	engine_class[20:27]	Selects engine-class for event
>   *	engine_instance[12:19]	Selects the engine-instance for the event
> + *	function[44:59]		Selects the function of the event (SRIOV enabled)
>   *
>   * For engine specific events (engine-*), gt, engine_class and engine_instance parameters must be
> - * set as populated by DRM_XE_DEVICE_QUERY_ENGINES.
> + * set as populated by DRM_XE_DEVICE_QUERY_ENGINES and function if SRIOV is enabled.
>   *
>   * For gt specific events (gt-*) gt parameter must be passed. All other parameters will be 0.
>   *
> @@ -49,6 +51,7 @@
>   */
>  
>  #define XE_PMU_EVENT_GT_MASK			GENMASK_ULL(63, 60)
> +#define XE_PMU_EVENT_FUNCTION_MASK		GENMASK_ULL(59, 44)
>  #define XE_PMU_EVENT_ENGINE_CLASS_MASK		GENMASK_ULL(27, 20)
>  #define XE_PMU_EVENT_ENGINE_INSTANCE_MASK	GENMASK_ULL(19, 12)
>  #define XE_PMU_EVENT_ID_MASK			GENMASK_ULL(11, 0)
> @@ -58,6 +61,11 @@ static unsigned int config_to_event_id(u64 config)
>  	return FIELD_GET(XE_PMU_EVENT_ID_MASK, config);
>  }
>  
> +static unsigned int config_to_function_id(u64 config)
> +{
> +	return FIELD_GET(XE_PMU_EVENT_FUNCTION_MASK, config);
> +}
> +
>  static unsigned int config_to_engine_class(u64 config)
>  {
>  	return FIELD_GET(XE_PMU_EVENT_ENGINE_CLASS_MASK, config);
> @@ -146,7 +154,7 @@ static bool event_supported(struct xe_pmu *pmu, unsigned int gt,
>  static bool event_param_valid(struct perf_event *event)
>  {
>  	struct xe_device *xe = container_of(event->pmu, typeof(*xe), pmu.base);
> -	unsigned int engine_class, engine_instance;
> +	unsigned int engine_class, engine_instance, function_id;
>  	u64 config = event->attr.config;
>  	struct xe_gt *gt;
>  
> @@ -154,18 +162,28 @@ static bool event_param_valid(struct perf_event *event)
>  	if (!gt)
>  		return false;
>  
> +	function_id = config_to_function_id(config);
> +	if (function_id && !IS_SRIOV_PF(xe))

hmm, it rather should be:

	if (function_id && IS_SRIOV_VF(xe))

but (see below)

> +		return false;
> +
>  	engine_class = config_to_engine_class(config);
>  	engine_instance = config_to_engine_instance(config);
>  
>  	switch (config_to_event_id(config)) {
>  	case XE_PMU_EVENT_GT_C6_RESIDENCY:
> -		if (engine_class || engine_instance)
> +		if (engine_class || engine_instance || function_id)
>  			return false;
>  		break;
>  	case XE_PMU_EVENT_ENGINE_ACTIVE_TICKS:
>  	case XE_PMU_EVENT_ENGINE_TOTAL_TICKS:
>  		if (!event_to_hwe(event))
>  			return false;
> +		/*
> +		 * PF(0) and total vfs when SRIOV is enabled
> +		 */
> +		if (function_id > xe_sriov_pf_get_totalvfs(xe))

shouldn't we rely on checks from one place?

likely xe_guc_engine_activity_xxx() will also have checks for
index/function and may use ea->num_functions for that

> +			return false;
> +
>  		break;
>  	}
>  
> @@ -233,18 +251,22 @@ static u64 read_engine_events(struct perf_event *event, u64 prev)
>  	struct xe_device *xe = container_of(event->pmu, typeof(*xe), pmu.base);
>  	struct xe_pmu *pmu = &xe->pmu;
>  	struct xe_hw_engine *hwe;
> -	u64 val = 0;
> +	unsigned int function_id;
> +	u64 config, val = 0;
>  
>  	if (!pmu->fw_count)
>  		return prev;
>  
> +	config = event->attr.config;
> +	function_id = config_to_function_id(config);
> +
>  	hwe = event_to_hwe(event);
>  	if (!hwe)
>  		drm_warn(&xe->drm, "unknown pmu engine\n");
> -	else if (config_to_event_id(event->attr.config) == XE_PMU_EVENT_ENGINE_ACTIVE_TICKS)
> -		val = xe_guc_engine_activity_active_ticks(hwe, 0);
> +	else if (config_to_event_id(config) == XE_PMU_EVENT_ENGINE_ACTIVE_TICKS)
> +		val = xe_guc_engine_activity_active_ticks(hwe, function_id);
>  	else
> -		val = xe_guc_engine_activity_total_ticks(hwe, 0);
> +		val = xe_guc_engine_activity_total_ticks(hwe, function_id);
>  
>  	return val;
>  }
> @@ -347,6 +369,7 @@ static void xe_pmu_event_del(struct perf_event *event, int flags)
>  }
>  
>  PMU_FORMAT_ATTR(gt,			"config:60-63");
> +PMU_FORMAT_ATTR(function,		"config:44-59");
>  PMU_FORMAT_ATTR(engine_class,		"config:20-27");
>  PMU_FORMAT_ATTR(engine_instance,	"config:12-19");
>  PMU_FORMAT_ATTR(event,			"config:0-11");
> @@ -355,6 +378,7 @@ static struct attribute *pmu_format_attrs[] = {
>  	&format_attr_event.attr,
>  	&format_attr_engine_class.attr,
>  	&format_attr_engine_instance.attr,
> +	&format_attr_function.attr,
>  	&format_attr_gt.attr,
>  	NULL,
>  };


  reply	other threads:[~2025-02-06 19:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 10:43 [PATCH v5 0/8] PMU support for engine activity Riana Tauro
2025-02-06 10:40 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-06 10:41 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-06 10:42 ` ✓ CI.KUnit: success " Patchwork
2025-02-06 10:43 ` [PATCH v5 1/8] drm/xe: Add engine activity support Riana Tauro
2025-02-06 18:28   ` Michal Wajdeczko
2025-02-10  7:07     ` Riana Tauro
2025-02-06 10:43 ` [PATCH v5 2/8] drm/xe/trace: Add trace for engine activity Riana Tauro
2025-02-06 10:43 ` [PATCH v5 3/8] drm/xe/guc: Expose engine activity only for supported GuC version Riana Tauro
2025-02-06 18:39   ` Michal Wajdeczko
2025-02-07  7:59     ` Riana Tauro
2025-02-07 21:37   ` Umesh Nerlige Ramappa
2025-02-10  7:28     ` Riana Tauro
2025-02-06 10:43 ` [PATCH v5 4/8] drm/xe/xe_pmu: Add PMU support for engine activity Riana Tauro
2025-02-07 22:47   ` Umesh Nerlige Ramappa
2025-02-06 10:43 ` [PATCH v5 5/8] drm/xe/xe_pmu: Acquire forcewake on event init for engine events Riana Tauro
2025-02-07  3:09   ` Ghimiray, Himal Prasad
2025-02-07  6:18     ` Riana Tauro
2025-02-07  6:51       ` Ghimiray, Himal Prasad
2025-02-07 23:31         ` Umesh Nerlige Ramappa
2025-02-10 10:20           ` Riana Tauro
2025-02-11 17:33             ` Umesh Nerlige Ramappa
2025-02-12  5:01               ` Riana Tauro
2025-02-06 10:43 ` [PATCH v5 6/8] drm/xe: Add support for per-function engine activity Riana Tauro
2025-02-06 19:06   ` Michal Wajdeczko
2025-02-07  8:11     ` Riana Tauro
2025-02-07 23:50       ` Umesh Nerlige Ramappa
2025-02-06 10:43 ` [PATCH v5 7/8] drm/xe/xe_pmu: Add pmu support for per-function engine activity stats Riana Tauro
2025-02-06 19:15   ` Michal Wajdeczko [this message]
2025-02-07  7:52     ` Riana Tauro
2025-02-06 10:43 ` [PATCH v5 8/8] drm/xe/pf: Enable " Riana Tauro
2025-02-06 11:20   ` Riana Tauro
2025-02-06 19:29   ` Michal Wajdeczko
2025-02-07  6:25     ` Riana Tauro
2025-02-06 10:58 ` ✓ CI.Build: success for PMU support for engine activity Patchwork
2025-02-06 11:01 ` ✗ CI.Hooks: failure " Patchwork
2025-02-06 11:02 ` ✓ CI.checksparse: success " Patchwork
2025-02-06 11:28 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-06 12:36 ` ✗ Xe.CI.Full: " 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=61dd8ba7-5fa2-47db-a03f-81fae29cc1e9@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=soham.purkait@intel.com \
    --cc=umesh.nerlige.ramappa@intel.com \
    --cc=vinay.belgaumkar@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