From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Breno Leitao <leitao@debian.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, 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>,
kernel-team@meta.com, puranjay@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: Disable branch profiling for all arm64 code
Date: Tue, 6 Jan 2026 11:11:42 -0500 [thread overview]
Message-ID: <20260106111142.1c123f12@gandalf.local.home> (raw)
In-Reply-To: <aVz-6WozGIxGiTUR@J2N7QTR9R3>
On Tue, 6 Jan 2026 12:24:09 +0000
Mark Rutland <mark.rutland@arm.com> wrote:
> Whoops; s/CONFIG_DEBUG_VIRTUAL/PROFILE_ANNOTATED_BRANCHES/ in both
> places in my reply.
Note, it could still be useful ;-)
I've been running my yearly branch profiling build on both my main
workstation and my server. I post the results from my server publicly (this
is updated every night):
https://rostedt.org/branches/current
If you check out the branch_annotated file, you can see there's still quite
a bit that gets it wrong. Some of these is because of bad assumptions by
the developer, others is because the code moved around causing new branches
to make later annotated branches go the opposite way.
Note, its still slow to download, not only because my internet is 20mbs up,
but also because that web server is running on a machine with this
profiling still enabled. I'll rebuild the kernel and disable it this weekend.
-- Steve
next prev parent reply other threads:[~2026-01-06 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 10:16 [PATCH v2] arm64: Disable branch profiling for all arm64 code Breno Leitao
2026-01-06 12:21 ` Mark Rutland
2026-01-06 12:24 ` Mark Rutland
2026-01-06 16:11 ` Steven Rostedt [this message]
2026-01-07 9:37 ` Breno Leitao
2026-01-07 16:10 ` Steven Rostedt
2026-01-06 14:05 ` Breno Leitao
2026-01-06 15:31 ` Mark Rutland
2026-01-06 15:46 ` Breno Leitao
2026-01-08 22:29 ` Will Deacon
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=20260106111142.1c123f12@gandalf.local.home \
--to=rostedt@goodmis.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=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