Skip to content

Conversation

@anvesh-intel
Copy link
Contributor

Related-To: VLCLJ-2648

Signed-off-by: Anvesh Bakwad anvesh.bakwad@intel.com

Related-To: VLCLJ-2648

Signed-off-by: Anvesh Bakwad <anvesh.bakwad@intel.com>
EXPECT_LT(pThreshold.processId, UINT32_MAX);
else
EXPECT_EQ(pThreshold.processId, UINT32_MAX);
EXPECT_LT(pThreshold.processId, UINT32_MAX);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If threshold has not been set, then this processId will be UINT32_MAX.

Copy link
Contributor Author

@anvesh-intel anvesh-intel Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

used EXPECT_LE() now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we specifically check this condition
"
If threshold has not been set, then this processId will be UINT32_MAX."

Related-To: VLCLJ-2648

Signed-off-by: Anvesh Bakwad <anvesh.bakwad@intel.com>
}
LZT_TEST_F(
POWER_TEST,
GivenValidPowerHandleWhenGettingEnergyThresholdThenSuccessIsReturnedAndParameterValuesAreValid) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joshuaranjan Is this test needed now as we're deprecating the support of zesPowerGetEnergyThreshold() API as mentioned in https://docs.intel.com/documents/GfxSWAT/Common/sysman/SysmanAPI.html#power ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Anvesh, this needs to be supported for platforms till CRI.
So lets add the test

@anvesh-intel anvesh-intel requested a review from aviralni December 2, 2025 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants