Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: "Purkait, Soham" <soham.purkait@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Tauro, Riana" <riana.tauro@intel.com>,
	"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [PATCH i-g-t v1] Add support for runtime pm for xe driver
Date: Thu, 6 Mar 2025 14:38:20 -0500	[thread overview]
Message-ID: <Z8n5rDS0VLtvQXQx@intel.com> (raw)
In-Reply-To: <CY5PR11MB6211574C038C2F3C46842E6295CA2@CY5PR11MB6211.namprd11.prod.outlook.com>

On Thu, Mar 06, 2025 at 11:45:15AM -0500, Gupta, Anshuman wrote:
> 
> offlist
> > -----Original Message-----
> > From: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Sent: Thursday, March 6, 2025 9:41 PM
> > To: Purkait, Soham <soham.purkait@intel.com>
> > Cc: igt-dev@lists.freedesktop.org; Tauro, Riana <riana.tauro@intel.com>;
> > Belgaumkar, Vinay <vinay.belgaumkar@intel.com>; Gupta, Anshuman
> > <anshuman.gupta@intel.com>; De Marchi, Lucas <lucas.demarchi@intel.com>
> > Subject: Re: [PATCH i-g-t v1] Add support for runtime pm for xe driver
> > 
> > On Thu, Mar 06, 2025 at 04:57:54PM +0530, Soham Purkait wrote:
> > > Add support for runtime power management for Xe driver.
> > 
> > Why?
> > 
> > We already have that covered with xe_pm d3hot and d3cold tests.
> We need to this tool for e2e validation to keep the card in d3cold for longer duration and verify the Package G state counters by Python SV. It is useful tool. 

Fair enough. If there are cases that we are not covering with the xe_pm,
let's do it. Just please let's explain that in the commit message.

> 
> Thanks,
> Anshuman.
> 
> > 
> > >
> > > ---
> > >  tools/intel_pm_rpm.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/tools/intel_pm_rpm.c b/tools/intel_pm_rpm.c index
> > > 08c25ca8a..945247d2e 100644
> > > --- a/tools/intel_pm_rpm.c
> > > +++ b/tools/intel_pm_rpm.c
> > > @@ -151,7 +151,7 @@ int main(int argc, char *argv[])
> > >  			goto exit;
> > >  		}
> > >  	} else {
> > > -		if (!igt_device_find_first_i915_discrete_card(&card)) {
> > > +		if (!igt_device_find_first_i915_discrete_card(&card) &&
> > > +!igt_device_find_first_xe_discrete_card(&card)) {
> > >  			igt_warn("No discrete gpu found\n");
> > >  			ret = EXIT_FAILURE;
> > >  			goto exit;
> > > --
> > > 2.34.1
> > >

  reply	other threads:[~2025-03-06 19:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 11:27 [PATCH i-g-t v1] Add support for runtime pm for xe driver Soham Purkait
2025-03-06 13:51 ` Kamil Konieczny
2025-03-06 15:49   ` Lucas De Marchi
2025-03-06 16:06     ` Gupta, Anshuman
2025-03-06 16:25       ` Lucas De Marchi
2025-03-06 19:55         ` Rodrigo Vivi
2025-03-06 16:10 ` Rodrigo Vivi
2025-03-06 16:45   ` Gupta, Anshuman
2025-03-06 19:38     ` Rodrigo Vivi [this message]
2025-03-07  2:07 ` ✓ i915.CI.BAT: success for " Patchwork
2025-03-07  2:14 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-07  4:25 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-07 11:44 ` ✗ 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=Z8n5rDS0VLtvQXQx@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=soham.purkait@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