From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev, Jan Kiszka <jan.kiszka@siemens.com>,
Tobias Schaffner <tobias.schaffner@siemens.com>
Subject: Re: [PATCH Dovetail v3 3/6] arm: irq_pipeline: Fix dovetail_fault_{entry,exit} bypass in hw_breakpoint_pending
Date: Fri, 26 Jun 2026 07:51:11 +0200 [thread overview]
Message-ID: <87cxxdrgs0.fsf@xenomai.org> (raw)
In-Reply-To: <20260622-wip-flo-v7-1-arm-pipelining-fixes-v3-3-230f03227abb@siemens.com> (Florian Bezdeka's message of "Mon, 22 Jun 2026 10:05:27 +0200")
Hi Florian,
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> HW breakpoint / watchpoint handling was bypassing the
> dovetail_fault_{entry,exit} machinery. As a result it could happen that
> the inband IRQ mask was touched from the OOB stage.
>
> There is one more problem in the HW bp/wp handling related to
> interrupts_enabled(). This one will be fixed in a separate patch.
>
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
> arch/arm/include/asm/dovetail.h | 1 +
> arch/arm/include/asm/trace/exceptions.h | 3 ++-
> arch/arm/kernel/hw_breakpoint.c | 6 ++++++
> 3 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/include/asm/dovetail.h b/arch/arm/include/asm/dovetail.h
> index 795a1fb903ec29f4c2fb7b25e70980796804acc0..eeb5d16ad032044a2587822f6b35074d664a9bbc 100644
> --- a/arch/arm/include/asm/dovetail.h
> +++ b/arch/arm/include/asm/dovetail.h
> @@ -16,6 +16,7 @@
> #define ARM_TRAP_VFP 6 /* VFP floating point exception */
> #define ARM_TRAP_UNDEFINSTR 7 /* Undefined instruction */
> #define ARM_TRAP_ALIGNMENT 8 /* Unaligned access exception */
> +#define ARM_TRAP_HW_BREAK 9 /* HW break or watchpoint exception */
>
ARM_TRAP_HW_BREAK would not be caught by xnarch_fault_bp_p() and friends
without fixing them up. What is the expected upside of differentiating
ARM_TRAP_BREAK from ARM_TRAP_HW_BREAK?
--
Philippe.
next prev parent reply other threads:[~2026-06-26 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:05 [PATCH Dovetail v3 0/6] Dovetail: arm: Finalize review results Florian Bezdeka
2026-06-22 8:05 ` [PATCH Dovetail v3 1/6] arm: irq_pipeline: Rename and move fault_entry_{enter,exit} Florian Bezdeka
2026-06-22 8:05 ` [PATCH Dovetail v3 2/6] arm: irq_pipeline: Fix dovetail_fault_{entry,exit} bypass in do_kernel_address_page_fault Florian Bezdeka
2026-06-22 8:05 ` [PATCH Dovetail v3 3/6] arm: irq_pipeline: Fix dovetail_fault_{entry,exit} bypass in hw_breakpoint_pending Florian Bezdeka
2026-06-22 13:44 ` Florian Bezdeka
2026-06-22 13:51 ` Philippe Gerum
2026-06-26 5:51 ` Philippe Gerum [this message]
2026-06-26 13:37 ` Florian Bezdeka
2026-06-22 8:05 ` [PATCH Dovetail v3 4/6] arm: irq_pipeline: Fix ordering problem in alignment trap handling Florian Bezdeka
2026-06-22 8:05 ` [PATCH Dovetail v3 5/6] dovetail: Decouple kernel/irq/pipeline.c from irqstate bit definitions Florian Bezdeka
2026-06-26 6:16 ` Philippe Gerum
2026-06-22 8:05 ` [PATCH Dovetail v3 6/6] arm: irq_pipeline: Fix IRQ state checking in trap entry paths Florian Bezdeka
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=87cxxdrgs0.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.