linux-kernel - Re: [PATCH v7 00/31] context_tracking,x86: Defer some IPIs until a user->kernel transition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176613180853.3684357.18339473690014642605.git-patchwork-notify@kernel.org>
Date: Fri, 19 Dec 2025 08:10:08 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Valentin Schneider <vschneid@...hat.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, rcu@...r.kernel.org, x86@...nel.org,
 linux-arm-kernel@...ts.infradead.org, loongarch@...ts.linux.dev,
 linux-arch@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
 dave.hansen@...ux.intel.com, hpa@...or.com, luto@...nel.org,
 peterz@...radead.org, acme@...nel.org, jpoimboe@...nel.org,
 pbonzini@...hat.com, arnd@...db.de, frederic@...nel.org, paulmck@...nel.org,
 jbaron@...mai.com, rostedt@...dmis.org, ardb@...nel.org,
 samitolvanen@...gle.com, davem@...emloft.net, neeraj.upadhyay@...nel.org,
 joelagnelf@...dia.com, josh@...htriplett.org, boqun.feng@...il.com,
 urezki@...il.com, mathieu.desnoyers@...icios.com, mgorman@...e.de,
 akpm@...ux-foundation.org, masahiroy@...nel.org, shenhan@...gle.com,
 riel@...riel.com, jannh@...gle.com, dan.carpenter@...aro.org,
 oleg@...hat.com, juri.lelli@...hat.com, williams@...hat.com,
 ypodemsk@...hat.com, mtosatti@...hat.com, dwagner@...e.de, ptesarik@...e.com,
 sshegde@...ux.ibm.com
Subject: Re: [PATCH v7 00/31] context_tracking,x86: Defer some IPIs until a
 user->kernel transition

Hello:

This series was applied to riscv/linux.git (fixes)
by Frederic Weisbecker <frederic@...nel.org>:

On Fri, 14 Nov 2025 16:01:02 +0100 you wrote:
> Context
> =======
> 
> We've observed within Red Hat that isolated, NOHZ_FULL CPUs running a
> pure-userspace application get regularly interrupted by IPIs sent from
> housekeeping CPUs. Those IPIs are caused by activity on the housekeeping CPUs
> leading to various on_each_cpu() calls, e.g.:
> 
> [...]

Here is the summary with links:
  - [v7,01/31] objtool: Make validate_call() recognize indirect calls to pv_ops[]
    (no matching commit)
  - [v7,02/31] objtool: Flesh out warning related to pv_ops[] calls
    (no matching commit)
  - [v7,03/31] rcu: Add a small-width RCU watching counter debug option
    https://git.kernel.org/riscv/c/d1e6d2773898
  - [v7,04/31] rcutorture: Make TREE04 use CONFIG_RCU_DYNTICKS_TORTURE
    https://git.kernel.org/riscv/c/82a224498005
  - [v7,05/31] jump_label: Add annotations for validating noinstr usage
    (no matching commit)
  - [v7,06/31] static_call: Add read-only-after-init static calls
    (no matching commit)
  - [v7,07/31] x86/paravirt: Mark pv_sched_clock static call as __ro_after_init
    (no matching commit)
  - [v7,08/31] x86/idle: Mark x86_idle static call as __ro_after_init
    (no matching commit)
  - [v7,09/31] x86/paravirt: Mark pv_steal_clock static call as __ro_after_init
    (no matching commit)
  - [v7,10/31] riscv/paravirt: Mark pv_steal_clock static call as __ro_after_init
    (no matching commit)
  - [v7,11/31] loongarch/paravirt: Mark pv_steal_clock static call as __ro_after_init
    (no matching commit)
  - [v7,12/31] arm64/paravirt: Mark pv_steal_clock static call as __ro_after_init
    (no matching commit)
  - [v7,13/31] arm/paravirt: Mark pv_steal_clock static call as __ro_after_init
    (no matching commit)
  - [v7,14/31] perf/x86/amd: Mark perf_lopwr_cb static call as __ro_after_init
    (no matching commit)
  - [v7,15/31] sched/clock: Mark sched_clock_running key as __ro_after_init
    (no matching commit)
  - [v7,16/31] KVM: VMX: Mark __kvm_is_using_evmcs static key as __ro_after_init
    (no matching commit)
  - [v7,17/31] x86/bugs: Mark cpu_buf_vm_clear key as allowed in .noinstr
    (no matching commit)
  - [v7,18/31] x86/speculation/mds: Mark cpu_buf_idle_clear key as allowed in .noinstr
    (no matching commit)
  - [v7,19/31] sched/clock, x86: Mark __sched_clock_stable key as allowed in .noinstr
    (no matching commit)
  - [v7,20/31] KVM: VMX: Mark vmx_l1d_should flush and vmx_l1d_flush_cond keys as allowed in .noinstr
    (no matching commit)
  - [v7,21/31] stackleack: Mark stack_erasing_bypass key as allowed in .noinstr
    (no matching commit)
  - [v7,22/31] objtool: Add noinstr validation for static branches/calls
    (no matching commit)
  - [v7,23/31] module: Add MOD_NOINSTR_TEXT mem_type
    (no matching commit)
  - [v7,24/31] context-tracking: Introduce work deferral infrastructure
    (no matching commit)
  - [v7,25/31] context_tracking,x86: Defer kernel text patching IPIs
    (no matching commit)
  - [v7,26/31] x86/jump_label: Add ASM support for static_branch_likely()
    (no matching commit)
  - [v7,27/31] x86/mm: Make INVPCID type macros available to assembly
    (no matching commit)
  - [RFC,v7,28/31] x86/mm/pti: Introduce a kernel/user CR3 software signal
    (no matching commit)
  - [RFC,v7,29/31] x86/mm/pti: Implement a TLB flush immediately after a switch to kernel CR3
    (no matching commit)
  - [RFC,v7,30/31] x86/mm, mm/vmalloc: Defer kernel TLB flush IPIs under CONFIG_COALESCE_TLBI=y
    (no matching commit)
  - [RFC,v7,31/31] x86/entry: Add an option to coalesce TLB flushes
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html