[Skiboot] [PATCH] occ: Skip setting cores to nominal frequency in P9
ppaidipe
ppaidipe at linux.vnet.ibm.com
Mon Apr 3 16:02:55 AEST 2017
Hi Shilpa
On 2017-04-01 14:59, Shilpasri G Bhat wrote:
> In P9, once OCC is up, it is supposed to setup the cores to nominal
> frequency. So skip this step in OPAL.
>
> Signed-off-by: Shilpasri G Bhat <shilpa.bhat at linux.vnet.ibm.com>
> ---
> hw/occ.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/hw/occ.c b/hw/occ.c
> index 2ffb677..b222521 100644
> --- a/hw/occ.c
> +++ b/hw/occ.c
> @@ -897,11 +897,14 @@ void occ_pstates_init(void)
> return;
> }
>
> - /* Setup host based pstates and set nominal frequency */
> - for_each_chip(chip) {
> - for_each_available_core_in_chip(c, chip->id) {
> - cpu_pstates_prepare_core(chip, c, pstate_nom);
> - }
> + /*
> + * Setup host based pstates and set nominal frequency only in
> + * P8.
> + */
Instead of skipping, is it good to add validating whether core comes
with nominal frequency
or psafe frequency? So that we can catch in OPAL log about any failure
if OCC doesn't set
up the core nominal frequency properly during boot time.
What will be the impact, if core comes with psafe frequency?
> + if (proc_gen == proc_gen_p8) {
> + for_each_chip(chip)
> + for_each_available_core_in_chip(c, chip->id)
> + cpu_pstates_prepare_core(chip, c, pstate_nom);
> }
>
> /* Add opal_poller to poll OCC throttle status of each chip */
More information about the Skiboot
mailing list