lp:~mreed8855/ubuntu/+source/linux/+git/lunar

Owned by Michael Reed
Get this repository:
git clone https://git.not.enabled/~mreed8855/ubuntu/+source/linux/+git/lunar
Only Michael Reed can upload to this repository. If you are Michael Reed please log in for upload directions.

Branches

Name Last Modified Last Commit
lunar_next_09012023 2023-09-01 12:02:16 UTC
UBUNTU: [Config] Mark sh-sci as built-in

Author: Stefan Bader
Author Date: 2023-09-01 11:57:36 UTC

UBUNTU: [Config] Mark sh-sci as built-in

BugLink: https://bugs.launchpad.net/bugs/2022361

Follow-up to the change which make this serial console built-in as
a boot console we have to drop them from the ABI.

Signed-off-by: Stefan Bader <stefan.bader@canonical.com>

cpuinfo_freq_lunar_2 2023-08-10 01:11:28 UTC
cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E...

Author: Srinivas Pandruvada
Author Date: 2023-06-29 19:45:09 UTC

cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores

BugLink: https://launchpad.net/bugs/2030924

Some system BIOS configuration may provide option to disable E-cores.
As part of this change, CPUID feature for hybrid (Leaf 7 sub leaf 0,
EDX[15] = 0) may not be set. But HWP performance limits will still be
using a scaling factor like any other hybrid enabled system.

The current check for applying scaling factor will fail when hybrid
CPUID feature is not set and the only way to make sure that scaling
should be applied by checking CPPC nominal frequency and nominal
performance.

First, or systems predating Alder Lake, the CPPC nominal frequency and
nominal performance are 0, which can be used to distinguish those
systems from hybrid systems with disabled E-cores.

Second, if the CPPC nominal frequency and nominal performance are
defined, which indicates the need to use a special scaling factor, and
the nominal performance value multiplied by 100 is not equal to the
nominal frequency one, use hybrid scaling factor.

This can be done for all HWP systems without additional CPU model check.

Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject and changelog edits, removal of unneeded parens, comment
  edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit 0fcfc9e51990246a9813475716746ff5eb98c6aa)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

lp_2020022_mreed 2023-08-10 00:35:23 UTC
x86: don't use REP_GOOD or ERMS for small memory clearing

Author: Linus Torvalds
Author Date: 2023-04-15 19:01:14 UTC

x86: don't use REP_GOOD or ERMS for small memory clearing

BugLink: https://bugs.launchpad.net/bugs/2020022

The modern target to use is FSRS (Fast Short REP STOS), and the other
cases should only be used for bigger areas (ie mainly things like page
clearing).

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 20f3337d350c4e1b4ac66d731fd4e98565bf6cc0)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

cpuinfo_freq_lunar 2023-07-18 21:57:56 UTC
cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E...

Author: Srinivas Pandruvada
Author Date: 2023-06-29 19:45:09 UTC

cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores

BugLink: https://bugs.launchpad.net/bugs/2026687

Some system BIOS configuration may provide option to disable E-cores.
As part of this change, CPUID feature for hybrid (Leaf 7 sub leaf 0,
EDX[15] = 0) may not be set. But HWP performance limits will still be
using a scaling factor like any other hybrid enabled system.

The current check for applying scaling factor will fail when hybrid
CPUID feature is not set and the only way to make sure that scaling
should be applied by checking CPPC nominal frequency and nominal
performance.

First, or systems predating Alder Lake, the CPPC nominal frequency and
nominal performance are 0, which can be used to distinguish those
systems from hybrid systems with disabled E-cores.

Second, if the CPPC nominal frequency and nominal performance are
defined, which indicates the need to use a special scaling factor, and
the nominal performance value multiplied by 100 is not equal to the
nominal frequency one, use hybrid scaling factor.

This can be done for all HWP systems without additional CPU model check.

Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject and changelog edits, removal of unneeded parens, comment
  edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit 0fcfc9e51990246a9813475716746ff5eb98c6aa)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

config_numa_emu_lunar_2 2023-05-25 21:45:22 UTC
UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Author: Michael Reed
Author Date: 2023-05-25 21:45:22 UTC

UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
BugLink: https://bugs.launchpad.net/bugs/2008745

Currently Ubuntu kernel has this kernel config disabled.
But in some cases, Intel's Sapphire Rapids High Bandwith
Memory (SPR-HBM) needs this option.

Memory bandwidth has been a bottleneck of increasingly memory bound
workloads. Sapphire Rapids plus HBM is specifically targeted to
cater to these workloads, traditionally served using overprovisioning
of memory devices.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

config_numa_emu_lunar_1 2023-05-24 21:37:23 UTC
UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Author: Michael Reed
Author Date: 2023-05-24 21:37:23 UTC

UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
BugLink: https://bugs.launchpad.net/bugs/2008745

Currently Ubuntu kernel has this kernel config disabled.
But in some cases, Intel's Sapphire Rapids High Bandwith
Memory (SPR-HBM) needs this option.

Memory bandwidth has been a bottleneck of increasingly memory bound
workloads. Sapphire Rapids plus HBM is specifically targeted to
cater to these workloads, traditionally served using overprovisioning
of memory devices.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

config_numa_emu_lunar 2023-04-13 20:02:51 UTC
UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Author: Michael Reed
Author Date: 2023-04-13 20:02:51 UTC

UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

BugLink: https://bugs.launchpad.net/bugs/2008745

Currently Ubuntu kernel has this kernel config disabled.
But in some cases, Intel's Sapphire Rapids High Bandwith
Memory (SPR-HBM) needs this option.

Memory bandwidth has been a bottleneck of increasingly memory bound
workloads. Sapphire Rapids plus HBM is specifically targeted to
cater to these workloads, traditionally served using overprovisioning
of memory devices.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

17 of 7 results
This repository contains Public information 
Everyone can see this information.

Subscribers