From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Karl Mehltretter <kmehltretter@gmail.com>
Cc: mark.rutland@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Qi Zheng <qi.zheng@linux.dev>,
Arnd Bergmann <arnd@arndb.de>,
Andrey Konovalov <andreyknvl@gmail.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: irq: exclude the softirq stack switch from KCOV
Date: Thu, 8 Oct 2026 16:19:10 +0100 [thread overview]
Message-ID: <179136595191.1063015.6426776896396499376.b4-ty@kernel.org> (raw)
In-Reply-To: <20260926191325.79047-1-kmehltretter@gmail.com>
On Sat, 26 Sep 2026 21:13:25 +0200, Karl Mehltretter wrote:
> On IRQ exit, __irq_exit_rcu() drops HARDIRQ_OFFSET before calling
> invoke_softirq(). The arm64 do_softirq_own_stack() wrapper and its
> ____do_softirq() trampoline run before __do_softirq() establishes
> softirq context, so KCOV records their PCs in the interrupted task's
> coverage buffer. They also run outside softirq accounting when
> local_bh_enable() reaches do_softirq().
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: irq: exclude the softirq stack switch from KCOV
https://git.kernel.org/arm64/c/a9cd14bfb0c1
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-10-08 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 19:13 [PATCH] arm64: irq: exclude the softirq stack switch from KCOV Karl Mehltretter
2026-10-08 15:19 ` Will Deacon [this message]
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=179136595191.1063015.6426776896396499376.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@android.com \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=qi.zheng@linux.dev \
/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