From: Steven Rostedt <rostedt@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Breno Leitao <leitao@debian.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Laura Abbott <labbott@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
puranjay@kernel.org, usamaarif642@gmail.com,
kernel-team@meta.com, stable@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Fix annotated branch unbootable kernel
Date: Fri, 9 Jan 2026 14:50:22 -0500 [thread overview]
Message-ID: <20260109145022.35da01a3@gandalf.local.home> (raw)
In-Reply-To: <aVwp_BJx84gXHPlD@willie-the-truck>
[ Resending with my kernel.org email, as I received a bunch of messages from gmail saying it's blocking me :-p ]
On Mon, 5 Jan 2026 21:15:40 +0000
Will Deacon <will@kernel.org> wrote:
> > Another approach is to disable profiling on all arch/arm64 code, similarly to
> > x86, where DISABLE_BRANCH_PROFILING is called for all arch/x86 code. See
> > commit 2cbb20b008dba ("tracing: Disable branch profiling in noinstr
> > code").
>
> Yes, let's start with arch/arm64/. We know that's safe and then if
> somebody wants to make it finer-grained, it's on them to figure out a
> way to do it without playing whack-a-mole.
OK, so by adding -DDISABLE_BRANCH_PROFILING to the Makefile configs and for
the files that were audited, could be opt-in?
CFLAGS_REMOVE_<autdit_file>.o = -DDISABLE_BRANCH_PROFILING
And add that for each file that has been fully audited?
-- Steve
next prev parent reply other threads:[~2026-01-09 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 12:44 [PATCH] arm64/mm: Fix annotated branch unbootable kernel Breno Leitao
2026-01-05 21:15 ` Will Deacon
2026-01-09 19:47 ` Steven Rostedt
2026-01-09 19:50 ` Steven Rostedt [this message]
2026-01-12 9:42 ` Breno Leitao
2026-01-12 15:46 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260109145022.35da01a3@gandalf.local.home \
--to=rostedt@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=labbott@redhat.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=puranjay@kernel.org \
--cc=stable@vger.kernel.org \
--cc=usamaarif642@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox