Skip to content
Permalink
Branch: 9.0.0-sultan
Commits on Apr 2, 2019
  1. Revert "cpufreq: Limit gold cluster to 2553600 kHz due to performance…

    kerneltoast committed Apr 2, 2019
    … issues"
    
    Mystery solved: this problem occurred due to disabling
    CONFIG_QTI_THERMAL_LIMITS_DCVS, which writes some magical values to TZ
    that make the CPU stable at all frequencies.
    
    This reverts commit 44fd8fb.
  2. drivers: thermal: limits-dcvs: Always build driver

    kerneltoast committed Apr 2, 2019
    The routines in this driver are required to enable stable performance at
    all supported CPU frequencies. Instead of allowing the driver to be
    removed completely, always compile it and simply stub out the actual CPU
    throttle components, in order to enable full CPU performance.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  3. Merge tag 'android-9.0.0_r0.73' into 9.0.0-sultan

    kerneltoast committed Apr 2, 2019
    Android 9.0.0 Release 0.73
  4. Revert "string: Use faster alternatives when constant arguments are u…

    kerneltoast committed Apr 2, 2019
    …sed"
    
    Rasimus Villemoes on the mailing list pointed out that an unaligned
    word read can occur on architectures with efficient unaligned memory
    accesses, that could then cause a strcmp replaced by a memcmp to read
    across a page boundary and thus cause issues.
    
    His response is here:
    https://lore.kernel.org/lkml/ec88d9a2-272e-973e-55ce-f3d411aafcd1@rasmusvillemoes.dk
    
    This reverts commit 3aec6b1.
  5. b1c1_defconfig: Configure max-boost frequencies for cpu_input_boost

    kerneltoast committed Apr 2, 2019
    1996 MHz on the performance cluster uses significantly less power than
    the frequencies above it, making it an excellent choice for frequent
    boosts.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  6. kernel: Adjust top-app boost

    kerneltoast committed Apr 1, 2019
    Top-app transitions are more so CPU-bound than memory bound, so boost
    the CPU to the max for a longer period of period of time and remove the
    DDR bus max-boost entirely.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  7. cpu_input_boost: Allow configuration of each cluster's max-boost freq

    kerneltoast committed Apr 1, 2019
    On certain CPUs, the highest frequency could be very inefficient, and
    thus frequently boosting to the frequency for max boosts can incur a
    high power cost. To mitigate this, allow configuration of the max-boost
    frequency for each CPU cluster, so that a more efficient frequency can
    be selected for max boosts.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  8. cpu_input_boost: Fix SPDX identifier format in header

    kerneltoast committed Mar 31, 2019
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  9. cpu_input_boost: Mark boost kthread as performance critical

    kerneltoast committed Mar 31, 2019
    The boost kthread is performance critical for obvious reasons.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
  10. cpu_input_boost: Serialize everything with a master kthread

    kerneltoast committed Apr 2, 2019
    Allowing multiple workers, executing in parallel on multiple CPUs no
    less, to modify the CPU policy as they please is quite racy and adds
    additional complexity to the code. Instead of letting each type of boost
    modify the CPU policy directly, serialize the CPU policy updates through
    a master kthread to make the whole boost process cleaner, faster, and
    far more efficient.
    
    Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
You can’t perform that action at this time.