Tags give the ability to mark specific points in history as being important
-
x86-urgent-2020-08-15
a6d996cb · ·Misc fixes and small updates all around the place: - Fix mitigation state sysfs output - Fix an FPU xstate/sxave code assumption bug triggered by Architectural LBR support - Fix Lightning Mountain SoC TSC frequency enumeration bug - Fix kexec debug output - Fix kexec memory range assumption bug - Fix a boundary condition in the crash kernel code - Optimize porgatory.ro generation a bit - Enable ACRN guests to use X2APIC mode - Reduce a __text_poke() IRQs-off critical section for the benefit of PREEMPT_RT Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
sched-urgent-2020-08-15
cc172ff3 · ·Two fixes: fix a new tracepoint's output value, and fix the formatting of show-state syslog printouts. Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
perf-urgent-2020-08-15
bcfd218b · ·Misc fixes, an expansion of perf syscall access to CAP_PERFMON privileged tools, plus a RAPL HW-enablement for Intel SPR platforms. Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
locking-urgent-2020-08-15
405fa8ac · ·A documentation fix and a 'fallthrough' macro update. Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
4.9.230-31
9f68d811 · · -
4.9.230-32
9f68d811 · · -
4.9.230-76
9f68d811 · · -
4.9.230-95
9f68d811 · · -
acpi-5.9-rc1-2
19fe87fd · ·More ACPI updates for 5.9-rc1 Add new hardware support to the ACPI driver for AMD SoCs, the x86 clk driver and the Designware i2c driver (changes from Akshu Agrawal and Pu Wen).
-
pm-5.9-rc1-3
f3db6de5 · ·One more power management update for 5.9-rc1 Modify the intel_pstate driver to allow it to work in the passive mode with hardware-managed P-states (HWP) enabled.
-
timers-urgent-2020-08-14
b0294f30 · ·A set oftimekeeping/VDSO updates: - Preparatory work to allow S390 to switch over to the generic VDSO implementation. S390 requires that the VDSO data pointer is handed in to the counter read function when time namespace support is enabled. Adding the pointer is a NOOP for all other architectures because the compiler is supposed to optimize that out when it is unused in the architecture specific inline. The change also solved a similar problem for MIPS which fortunately has time namespaces not yet enabled. S390 needs to update clock related VDSO data independent of the timekeeping updates. This was solved so far with yet another sequence counter in the S390 implementation. A better solution is to utilize the already existing VDSO sequence count for this. The core code now exposes helper functions which allow to serialize against the timekeeper code and against concurrent readers. S390 needs extra data for their clock readout function. The initial common VDSO data structure did not provide a way to add that. It now has an embedded architecture specific struct embedded which defaults to an empty struct. Doing this now avoids tree dependencies and conflicts post rc1 and allows all other architectures which work on generic VDSO support to work from a common upstream base. - A trivial comment fix.
-
timers-core-2020-08-14
00998085 · ·A set of posix CPU timer changes which allows to defer the heavy work of posix CPU timers into task work context. The tick interrupt is reduced to a quick check which queues the work which is doing the heavy lifting before returning to user space or going back to guest mode. Moving this out is deferring the signal delivery slightly but posix CPU timers are inaccurate by nature as they depend on the tick so there is no real damage. The relevant test cases all passed. This lifts the last offender for RT out of the hard interrupt context tick handler, but it also has the general benefit that the actual heavy work is accounted to the task/process and not to the tick interrupt itself. Further optimizations are possible to break long sighand lock hold and interrupt disabled (on !RT kernels) times when a massive amount of posix CPU timers (which are unpriviledged) is armed for a task/process. This is currently only enabled for x86 because the architecture has to ensure that task work is handled in KVM before entering a guest, which was just established for x86 with the new common entry/exit code which got merged post 5.8 and is not the case for other KVM architectures.
-
irq-urgent-2020-08-14
f107cee9 · ·Two fixes in the core interrupt code which ensure that all error exits unlock the descriptor lock.
-
-
4.9.230-75
5ea3d842 · · -
4.9.230-94
5ea3d842 · ·