Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Valentin Schneider <valentin.schneider@arm.com>
To:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-rt-users@vger.kernel.org, x86@kernel.org
Cc:     Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Steven Rostedt <rostedt@goodmis.org>,
        Daniel Bristot de Oliveira <bristot@redhat.com>,
        "Peter Zijlstra (Intel)" <peterz@infradead.org>,
        Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
        "H. Peter Anvin" <hpa@zytor.com>, Mark Brown <broonie@kernel.org>,
        Dave Martin <Dave.Martin@arm.com>,
        Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/3] sched, x86, arm64: PREEMPT_RT, FPU and preemption
Date:   Thu, 22 Jul 2021 18:51:54 +0100
Message-Id: <20210722175157.1367122-1-valentin.schneider@arm.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi folks,

This stems from some more v5.13-rt1 breakage on arm64. This time per-CPU access
safety isn't sufficient, we really need to keep preemption disabled.

In a happy accident I stumbled on

  cba08c5dc6dc ("x86/fpu: Make kernel FPU protection RT friendly")

so I packaged what was done there into some common helpers and plastered them
over the problematic areas.

Cheers,
Valentin

Valentin Schneider (3):
  sched/preempt: Introduce preempt_{enable, disable}_bh()
  x86/fpu: Make FPU protection reuse common helper
  arm64/fpsimd: Fix FPSIMD context handling vs PREEMPT_RT

 arch/arm64/kernel/fpsimd.c     |  6 ++++--
 arch/x86/include/asm/fpu/api.h | 19 ++-----------------
 include/linux/bottom_half.h    | 26 ++++++++++++++++++++++++++
 3 files changed, 32 insertions(+), 19 deletions(-)

--
2.25.1