kernel-packages team mailing list archive

[Chris J Arges <1397928@xxxxxxxxxxxxxxxxxx>]

Tested by hotplugging CPUs and kexec'ing checking cpuinfo_cur_freq
before and after these events.

Before hotplug CPU can be at various frequencies.
After hotplug CPU is at minimum frequency.

Before kexec CPUs are around min frequency (mostly idle machine).
After kexec all CPUs are at 3690000 which is the highest freq for that machine, eventually cpufreq returns to minimal/lower values.


** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1397928

Title:
  Feature: Add powernv-cpufreq upstream bug fixes to ubuntu-14.04.02
  kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Users of ppc64el arches could have issues related to powernv-cpufreq.
  [Test Case]
  Ensure the pstate of various cpus respond properly after hotswapping/kexec/reboot events.
  [Fix]
  789ca24 cpufreq: Allow stop CPU callback to be used by all cpufreq drivers
  b120339 cpufreq: powernv: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum
  cf30af76 cpufreq: powernv: Set the cpus to nominal frequency during reboot/kexec

  --

  Problem Description
  ===========================
  This is a feature request to include the following upstream(3.18) commits to Ubuntu-14.04.02 kernel.
  1)789ca2 cpufreq: Allow stop CPU callback to be used by all cpufreq drivers
  2)b12033 cpufreq: powernv: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum
  3)cf30af cpufreq: powernv: Set the cpus to nominal frequency during reboot/kexec

  == Comment: #1 - Shilpasri G. Bhat <shigbhat@xxxxxxxxxx>  ==
  This patch was applied on top of  kernel(3.16) ubuntu-trusty/lts-backport-utopic
  (8bf5db16 UBUNTU: Ubuntu-lts-3.16.0-26.34~14.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397928/+subscriptions