Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>,
	"Jakub Kolakowski" <jakub1.kolakowski@intel.com>,
	<igt-dev@lists.freedesktop.org>
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>,
	Lukasz Laguna <lukasz.laguna@intel.com>,
	"Gupta, Anshuman" <anshuman.gupta@intel.com>
Subject: Re: [PATCH i-g-t v4 2/2] tests/intel/xe_pm: Add a check for power management capability
Date: Wed, 19 Mar 2025 20:29:29 +0530	[thread overview]
Message-ID: <337176d1-41f4-481e-b81e-0f818f45a4ba@intel.com> (raw)
In-Reply-To: <5c0a4a66-8e05-4f14-acc0-96487cc43590@linux.intel.com>


On 19-03-2025 13:44, Bernatowicz, Marcin wrote:
>
>
> On 3/19/2025 9:05 AM, Poosa, Karthik wrote:
>>
>> On 18-03-2025 20:31, Jakub Kolakowski wrote:
>>> Add a check for power management capability of device tested in tests
>>> related to D3 states. Currently if test is started on configuration
>>> that does not support the PM capability it doesn't skip, instead
>>> depending on test it may fail, abort or timeout.
>>> With this change test will skip with a clear message why it did.
>>>
>>> Cc: Adam Miszczak<adam.miszczak@linux.intel.com>
>>> Cc: Lukasz Laguna<lukasz.laguna@intel.com>
>>> Cc: Marcin Bernatowicz<marcin.bernatowicz@linux.intel.com>
>>> Signed-off-by: Jakub Kolakowski<jakub1.kolakowski@intel.com>
>>> ---
>>>   tests/intel/xe_pm.c | 3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/tests/intel/xe_pm.c b/tests/intel/xe_pm.c
>>> index c2026474d..70f0613fb 100644
>>> --- a/tests/intel/xe_pm.c
>>> +++ b/tests/intel/xe_pm.c
>>> @@ -146,6 +146,9 @@ static void vram_d3cold_threshold_restore(int sig)
>>>   static bool setup_d3(device_t device, enum igt_acpi_d_state state)
>>>   {
>>> +    igt_require_f(igt_has_pci_pm_capability(device.pci_xe),
>>> +              "PCI power management capability not found\n");
>>
>> Hi Jakub,
>>
>> As per PCIe Base spec, all PCI Express Functions are required to 
>> support PCI Power Management Capability.
>>
>> Only legacy PCI devices wouldn't have it.
>>
>> Can you share details of failures without this capability.
>>
>> All Xe supported GPUs are PCIe complaint, this check may not be 
>> needed at all.
>
> This happens for runs with Virtual Function (VF) passed to Virtual 
> Machine (VM).
>
> "9.6 SR-IOV Power Management
> This section defines the PCI Express SR-IOV power management 
> capabilities and protocols.
> The Power Management Capability is required for PFs as described in 
> Chapter 5 .
> For VFs, the Power Management Capability is optional."
>
> -- 
> marcin
Okay, LGTM then.
Reviewed-by: Karthik Poosa <karthik.poosa@intel.com>
>>
>>> +
>>>       dpms_on_off(device, DRM_MODE_DPMS_OFF);
>>>       /*
>

  reply	other threads:[~2025-03-19 15:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 15:01 [PATCH i-g-t v4 0/2] Add a check for power management PCI capability Jakub Kolakowski
2025-03-18 15:01 ` [PATCH i-g-t v4 1/2] lib/igt_pm: Introduce helper to check for PM capability Jakub Kolakowski
2025-03-18 16:54   ` Kamil Konieczny
2025-03-18 15:01 ` [PATCH i-g-t v4 2/2] tests/intel/xe_pm: Add a check for power management capability Jakub Kolakowski
2025-03-19  8:05   ` Poosa, Karthik
2025-03-19  8:14     ` Bernatowicz, Marcin
2025-03-19 14:59       ` Poosa, Karthik [this message]
2025-03-24 18:17         ` Kamil Konieczny
2025-03-20 11:52       ` Kamil Konieczny
2025-03-19 14:05   ` Bernatowicz, Marcin
2025-03-18 15:36 ` ✓ Xe.CI.BAT: success for Add a check for power management PCI capability (rev5) Patchwork
2025-03-18 15:55 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-18 16:41 ` ✗ 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=337176d1-41f4-481e-b81e-0f818f45a4ba@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=marcin.bernatowicz@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