08 Feb, 2020

1 commit

• 10852347d   ANDROID: dummy-cpufreq: fix up 5.6-rc1 API changes ... Browse Code »

  The cpufreq api changed, so handle it properly in dummy-cpufreq so that
  things keep building.

  Signed-off-by: Greg Kroah-Hartman
  Change-Id: Iaf496cf2777bf0f7fceb388c8d3baabad232b576

  Greg Kroah-Hartman

  2020-02-08 23:06:57 +0800  

29 Oct, 2019

1 commit

• 50118fa88   ANDROID: dummy_cpufreq: Implement get() ... Browse Code »

  Fixes panic in time_cpufreq_notifier+0x94 caused by notifying the x86
  TSC synchronization code that a CPU frequency change has occurred, but
  not properly updating policy->cur beforehand, causing a division by
  zero.

  Link: https://github.com/ClangBuiltLinux/linux/issues/756
  Change-Id: I687093bbdb402a13341762bf9d91dd7f9daffe8b
  Signed-off-by: Alistair Delva

  Alistair Delva

  2019-10-29 10:58:15 +0800  

26 Oct, 2019

1 commit

• 18b7a1479   ANDROID: cpufreq: create dummy cpufreq driver ... Browse Code »

  /proc/uid_time_in_state has no data on cuttlefish because its cpu
  frequency tables are empty. Because time in state & concurrent time
  accounting are intertwined this causes the
  /proc/uid_concurrent_{policy,active}_time files to also not contain
  any data.

  Add a minimal, fake cpufreq driver that creates a freq table with 2
  frequencies per policy, to allow testing time in state functionality.

  Test: all 3 proc files show reasonable data on cuttlefish
  Test: log shows no errors from bad /proc/uid_time_in_state format
  Bug: 139763108
  Bug: 140796321
  Bug: 141206930
  Change-Id: I8c7fe1007a80c21a9bcba9455bf837947cf42963
  Signed-off-by: Connor O'Brien

  Connor O'Brien

  2019-10-26 07:22:48 +0800