Intel-XE Archive on lore.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
Subject: Re: [Intel-xe] [PATCH] drm/xe: add some debug info for d3cold
Date: Mon, 4 Dec 2023 09:16:05 -0500	[thread overview]
Message-ID: <ZW3fJehxYWB61ml1@intel.com> (raw)
In-Reply-To: <20231204105126.34751-2-matthew.auld@intel.com>

On Mon, Dec 04, 2023 at 10:51:27AM +0000, Matthew Auld wrote:
> From the CI logs we want to easily know if the machine is capable and
> allowed to enter d3cold, and can therefore potentially trigger the
> d3cold RPM suspend and resume path.
> 
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Cc: Riana Tauro <riana.tauro@intel.com>

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

> ---
>  drivers/gpu/drm/xe/xe_pci.c | 3 +++
>  drivers/gpu/drm/xe/xe_pm.c  | 3 +++
>  2 files changed, 6 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 6977f48b03c8..501b4489f9d4 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -751,6 +751,9 @@ static int xe_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>  
>  	xe_pm_init(xe);
>  
> +	drm_dbg(&xe->drm, "d3cold: capable=%s\n",
> +		str_yes_no(xe->d3cold.capable));
> +
>  	return 0;
>  }
>  
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index e31a91cf311c..b429c2876a76 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -399,4 +399,7 @@ void xe_pm_d3cold_allowed_toggle(struct xe_device *xe)
>  		xe->d3cold.allowed = false;
>  
>  	mutex_unlock(&xe->d3cold.lock);
> +
> +	drm_dbg(&xe->drm,
> +		"d3cold: allowed=%s\n", str_yes_no(xe->d3cold.allowed));
>  }
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2023-12-04 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 10:51 [Intel-xe] [PATCH] drm/xe: add some debug info for d3cold Matthew Auld
2023-12-04 10:59 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-12-04 10:59 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-12-04 11:00 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-12-04 11:07 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-12-04 11:08 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-12-04 11:09 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-12-04 11:45 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-12-04 14:16 ` Rodrigo Vivi [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=ZW3fJehxYWB61ml1@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@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