Comment 4 for bug 1732865

------- Comment From <email address hidden> 2018-01-24 02:09 EDT-------
Testcase:
On Host:
#lscpu
#service kdump-tools stop
#echo 10 > /proc/sys/kernel/panic

On FSP:
$ getscom pu.ex 10013100 -all
$ putscom pu.ex 10013100 1000000000000000 -n0 -p00 -c6
Here -p00--> Is the chip id, -c6 ---> is the core id under that chip, these should be selecte from the output
of the first command "getscom pu.ex 10013100 -all"

Repeat the above process 4 times with each time on a different chip with master core getting injected.

Then run

lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 88
On-line CPU(s) list: 16-39,48-71,80-95,104-127
Thread(s) per core: 8
Core(s) per socket: 2
Socket(s): 4
NUMA node(s): 4
Model: 2.1 (pvr 004b 0201)
Model name: POWER8E (raw), altivec supported
CPU max MHz: (null)
CPU min MHz: (null)
L1d cache: 64K
L1i cache: 32K
L2 cache: 512K
L3 cache: 8192K
NUMA node0 CPU(s): 16-31
NUMA node1 CPU(s): 32-39,48-63
NUMA node16 CPU(s): 64-71,80-95
NUMA node17 CPU(s): 104-127

And also there is a automated testcase for this in https://github.com/open-power/op-test-framework
1. Clone the above repo.
2. Runt this command to GUARD the cpu.
./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert

Run it multiple times to make multiple CPU's are garded.

This patch makes the customers to easily identify the CPU minimum and maximum frequencies at which it can run(This happens only when there are multiple CPU's are Garded.