Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Riana Tauro <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <Michal.Wajdeczko@intel.com>,
	<ashutosh.dixit@intel.com>, <rodrigo.vivi@intel.com>,
	<matthew.brost@intel.com>
Subject: Re: [PATCH v2] drm/xe/throttle: Log throttle reasons
Date: Mon, 2 Dec 2024 12:20:45 +0530	[thread overview]
Message-ID: <9f227ba3-4f59-418e-bd20-dbb462aaccc4@intel.com> (raw)
In-Reply-To: <20241129074300.1304068-1-raag.jadav@intel.com>



On 11/29/2024 1:13 PM, Raag Jadav wrote:
> Log throttle register MMIO reads which will be useful for debugging.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
Looks good to me
Reviewed-by: Riana Tauro <riana.tauro@intel.com>

> ---
> 
> v2: Use gt oriented logging (Michal)
>      Drop local variables (Ashutosh, Rodrigo)
>      Move logging to status attribute and reduce spam (Matthew Brost)
> 
>   drivers/gpu/drm/xe/xe_gt_throttle.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_throttle.c b/drivers/gpu/drm/xe/xe_gt_throttle.c
> index 03b225364101..8db78d616b6f 100644
> --- a/drivers/gpu/drm/xe/xe_gt_throttle.c
> +++ b/drivers/gpu/drm/xe/xe_gt_throttle.c
> @@ -8,6 +8,7 @@
>   #include <regs/xe_gt_regs.h>
>   #include "xe_device.h"
>   #include "xe_gt.h"
> +#include "xe_gt_printk.h"
>   #include "xe_gt_sysfs.h"
>   #include "xe_gt_throttle.h"
>   #include "xe_mmio.h"
> @@ -53,6 +54,7 @@ static u32 read_status(struct xe_gt *gt)
>   {
>   	u32 status = xe_gt_throttle_get_limit_reasons(gt) & GT0_PERF_LIMIT_REASONS_MASK;
>   
> +	xe_gt_dbg(gt, "throttle reasons: 0x%08x\n", status);
>   	return status;
>   }
>   


  parent reply	other threads:[~2024-12-02  6:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  7:43 [PATCH v2] drm/xe/throttle: Log throttle reasons Raag Jadav
2024-11-29  7:52 ` ✓ CI.Patch_applied: success for drm/xe/throttle: Log throttle reasons (rev2) Patchwork
2024-11-29  7:52 ` ✓ CI.checkpatch: " Patchwork
2024-11-29  7:53 ` ✓ CI.KUnit: " Patchwork
2024-11-29  8:19 ` ✓ CI.Build: " Patchwork
2024-11-29  8:23 ` ✓ CI.Hooks: " Patchwork
2024-11-29  8:25 ` ✓ CI.checksparse: " Patchwork
2024-11-29  8:50 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-29 19:09 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-02  6:50 ` Riana Tauro [this message]
2024-12-02 14:02   ` [PATCH v2] drm/xe/throttle: Log throttle reasons Raag Jadav
2024-12-02 17:09     ` Rodrigo Vivi

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=9f227ba3-4f59-418e-bd20-dbb462aaccc4@intel.com \
    --to=riana.tauro@intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=rodrigo.vivi@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