The "CPU frequency scaling tests" item of FWTS.

[Huang, Bryan]

Add Richard in the loop

From: Alex Hung [mailto:alex.hung at canonical.com]
Sent: Wednesday, February 10, 2021 10:57 AM
To: Huang, Bryan <bryanhuang at hpe.com>
Cc: fwts-devel at lists.ubuntu.com; Kuan, Bob <bob.kuan at hpe.com>; Lin, Kevin (ISS ROMQA) <kevin.lin at hpe.com>; Chuang, Brian (HPE DVT UEFI) <brian.chuang2 at hpe.com>
Subject: Re: The "CPU frequency scaling tests" item of FWTS.

Current fwts cpufreq test skips on most of Intel platforms so I guess you are running on non-Intel platforms.

I tried this on an AMD system that I have access to but I wasn't able to reproduce it. There can be something new to your platforms.

However, you can check the "CoordType" of the  _PSD objects. On Linux, you can use acpidbg to extract _PSD such as below:

~$ sudo acpidbg

- find _PSD
                  \_SB.PR00._PSD Method       000000007c8c89b5 2BB Args 0 Len 0068 Aml 00000000a73baf04
                  \_SB.PR01._PSD Method       00000000379cf5e1 2D2 Args 0 Len 0068 Aml 000000000da97980
                  \_SB.PR02._PSD Method       00000000919af435 2D2 Args 0 Len 0069 Aml 00000000adf3ae6e
                  \_SB.PR03._PSD Method       00000000f1106bc8 2D2 Args 0 Len 0069 Aml 00000000af2872d2
                  \_SB.PR04._PSD Method       0000000065f09c75 2D2 Args 0 Len 0069 Aml 000000008b693086
                  \_SB.PR05._PSD Method       00000000f6713d96 2D2 Args 0 Len 0069 Aml 0000000098cb3982
                  \_SB.PR06._PSD Method       00000000003166b7 2D2 Args 0 Len 0069 Aml 00000000625f8645
                  \_SB.PR07._PSD Method       0000000096791eaa 2D2 Args 0 Len 0069 Aml 000000007f62d735
                  \_SB.PR08._PSD Method       000000007d3facc1 2D2 Args 0 Len 0069 Aml 0000000039d69b35
                  \_SB.PR09._PSD Method       000000000108e70c 2D2 Args 0 Len 0069 Aml 000000002331e30a
                  \_SB.PR10._PSD Method       00000000012d9bb5 2D2 Args 0 Len 0069 Aml 0000000036d701c9
                  \_SB.PR11._PSD Method       000000007870aead 2D2 Args 0 Len 0069 Aml 00000000e1062a8a
                  \_SB.PR12._PSD Method       00000000a93d1817 2D2 Args 0 Len 0069 Aml 00000000f1efcfdb
                  \_SB.PR13._PSD Method       000000007cc9152f 2D2 Args 0 Len 0069 Aml 0000000002181b00
                  \_SB.PR14._PSD Method       00000000f091b6ce 2D2 Args 0 Len 0069 Aml 000000002f350a49
                  \_SB.PR15._PSD Method       00000000e161e2ed 2D2 Args 0 Len 0069 Aml 00000000036a7a99

- e _SB.PR00._PSD
Evaluating \_SB.PR00._PSD
Evaluation of \_SB.PR00._PSD returned object 000000003b93962e, external buffer length A8
 [Package] Contains 1 Elements:
  [Package] Contains 5 Elements:
   [Integer] = 0000000000000005
   [Integer] = 0000000000000000
   [Integer] = 0000000000000000
   [Integer] = 00000000000000FE
   [Integer] = 000000000000000C

On Mon, Feb 1, 2021 at 7:44 PM Huang, Bryan <bryanhuang at hpe.com<mailto:bryanhuang at hpe.com>> wrote:
Hi Alex and FWTS members,

Here is TPE HPE Bryan Huang.
We tried to run the “CPU frequency scaling tests” of FWTS and encountered the following issue.

[cid:image005.jpg at 01D6E2BC.FC31F5F0]

So we used the "Processors are set to SW_ANY." string to search the FWTS code.
We find the cpufreq_test_sw_any function to test the item.
The function will set all processor to their lowest speed first, and then set all processor to their highest speed.
Finally, the function will set all processor to their lowest speed again.

It seems that “if ((high_perf > newhigh_perf) && (high_perf - newhigh_perf > (high_perf - low_perf)/4) && (high_perf - low_perf > 20))” is satisfied, so the variable ok will be set to false.
Do you have any suggestions for the issue?

Please refer to the following information.

File location: src\cpu\cpufreq\cpufreq.c

[cid:image002.jpg at 01D7061A.A72A1BB0]
[cid:image003.jpg at 01D7061A.A72A1BB0]
[cid:image004.jpg at 01D7061A.A72A1BB0]



Thanks.
Best regards,
Bryan


--
Cheers,
Alex Hung
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20210218/a5afcc07/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56349 bytes
Desc: image001.jpg
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20210218/a5afcc07/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 72410 bytes
Desc: image002.jpg
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20210218/a5afcc07/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 65072 bytes
Desc: image003.jpg
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20210218/a5afcc07/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 53545 bytes
Desc: image004.jpg
URL: <https://lists.ubuntu.com/archives/fwts-devel/attachments/20210218/a5afcc07/attachment-0007.jpg>