From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: [PATCH RFC Dovetail 6.16 1/5] kernel/entry: irq_pipeline: Do not leave .noinstr.text section
Date: Fri, 26 Sep 2025 10:49:54 +0200 [thread overview]
Message-ID: <87ikh5ha31.fsf@xenomai.org> (raw)
In-Reply-To: <20250925-wip-flo-cleanups-based-on-6-16-v1-1-8c4ac7b52cd8@siemens.com> (Florian Bezdeka's message of "Thu, 25 Sep 2025 15:05:47 +0200")
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> Fixing the following warning by moving the call to irqentry_syncstage()
> into a instrumentation_begin() section.
>
> vmlinux.o: warning: objtool: irqentry_exit+0xab: call to synchronize_pipeline() leaves .noinstr.text section
>
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
> kernel/entry/common.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/entry/common.c b/kernel/entry/common.c
> index 583dcef13c7c0..284d41cb1c918 100644
> --- a/kernel/entry/common.c
> +++ b/kernel/entry/common.c
> @@ -393,6 +393,7 @@ noinstr void irqentry_exit(struct pt_regs *regs, irqentry_state_t state)
> return;
> }
>
> + instrumentation_begin();
> synchronized = irqentry_syncstage(state);
>
This means that we won't have ftracing or anything that depends on
instrumentation in any inband irq handler triggered during stage sync
from this code path.
--
Philippe.
next prev parent reply other threads:[~2025-09-26 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 13:05 [PATCH RFC Dovetail 6.16 0/5] Dovetail: Minor cleanups found while debugging the pipeline entry code Florian Bezdeka
2025-09-25 13:05 ` [PATCH RFC Dovetail 6.16 1/5] kernel/entry: irq_pipeline: Do not leave .noinstr.text section Florian Bezdeka
2025-09-26 8:49 ` Philippe Gerum [this message]
2025-09-26 10:26 ` Florian Bezdeka
2025-09-26 10:37 ` Philippe Gerum
2025-09-25 13:05 ` [PATCH RFC Dovetail 6.16 2/5] kernel/irq/chip: Change return value of get_flow_step() to int Florian Bezdeka
2025-09-25 13:05 ` [PATCH RFC Dovetail 6.16 3/5] kernel/irq/chip: Simplify may_start_flow() Florian Bezdeka
2025-09-26 8:50 ` Philippe Gerum
2025-09-25 13:05 ` [PATCH RFC Dovetail 6.16 4/5] kernel/irq/chip: Simplify should_feed_pipeline() Florian Bezdeka
2025-09-25 13:05 ` [PATCH RFC Dovetail 6.16 5/5] kernel/irq/chip: Do not call low level irq chip hooks directly Florian Bezdeka
2025-09-28 8:12 ` Philippe Gerum
2025-09-28 8:21 ` Philippe Gerum
2025-09-29 21:15 ` Florian Bezdeka
2025-09-30 7:52 ` Philippe Gerum
2025-09-28 12:25 ` [PATCH RFC Dovetail 6.16 0/5] Dovetail: Minor cleanups found while debugging the pipeline entry code Philippe Gerum
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=87ikh5ha31.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=xenomai@lists.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