Comment 5 for bug 1943549

Regarding the testcases for Hybrid scheduling, we run the following workloads for ADL-S/P:
1. Geekbench
2. Speedometer
3. Netperf
4. SpecInt
5. OpenVino (benchmark app) with Resnet50

All of these are standard Linux applications, hence you can use them for your testing.

We have used Geekbench extensively for this purpose. The sample command which we have used is:
./geekbench_x86_64 --no-upload --multi-core --cpu-workers <no of cores to be used> --iterations <no of iteration>

Strategy:
For ADL-S 881 SKU, we have 8 big cores and 8 atom config, where we have started geekbench for first 8 cores and observed the work distribution among multiple threads, we can use top or turbostat for this analysis. Second experiment is to execute geekbench with 16 cores(cpu workers) and then third experiment with 24 cores.

We can also manually disable and enable cores just to make sure if the results are same as the geekbench’s internal core pinning.

WARNING: When running on sensitive (e.g., pre-release or otherwise confidential)
platforms, always keep the system unplugged from the internet. Do not trust a
command line feature to protect sensitive information, as it introduces
more opportunity for human error or a benchmark bug to cause a leak.