Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH v2 07/11] arm64: debug: split single stepping exception entry
Date: Thu, 29 May 2025 11:10:54 +0100	[thread overview]
Message-ID: <20250529101053.GA29082@willie-the-truck> (raw)
In-Reply-To: <aDcqHaQx6favgsoK@J2N7QTR9R3.cambridge.arm.com>

On Wed, May 28, 2025 at 04:22:05PM +0100, Mark Rutland wrote:
> On Tue, May 20, 2025 at 05:29:14PM +0100, Will Deacon wrote:
> > On Mon, May 12, 2025 at 06:43:22PM +0100, Ada Couprie Diaz wrote:
> > > +	enter_from_user_mode(regs);
> > > +	/*
> > > +	 * After handling a breakpoint, we suspend the breakpoint
> > > +	 * and use single-step to move to the next instruction.
> > > +	 * If we have a suspended breakpoint there's nothing more to do:
> > > +	 * complete the single-step.
> > > +	 */
> > > +	if (reinstall_suspended_bps(regs)) {
> > > +		local_daif_restore(DAIF_PROCCTX);
> > > +		do_softstep(esr, regs);
> > > +	}
> > > +	exit_to_user_mode(regs);
> > 
> > I quite like the look of this now, but perhaps we could rename
> > reinstall_suspended_bps() and change the return value to make things a
> > bit more readable? For example, 'if (!stepped_suspended_breakpt(regs))'
> > or something like that? What do you think?
> 
> How about:
> 
> 	if (!try_step_suspended_breakpoints(regs))
> 
> ... that'd match the naming in do_el0_undef() and do_el1_undef() in
> traps.c, where we have try_${HANDLE_POTENTIAL_CASE}() for a few cases,
> e.g.

That's even better, thanks.

Will


  reply	other threads:[~2025-05-29 10:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 17:43 [PATCH v2 00/11] arm64: debug: remove hook registration, split exception entry Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 01/11] arm64: debug: clean up single_step_handler logic Ada Couprie Diaz
2025-05-20 15:35   ` Will Deacon
2025-05-12 17:43 ` [PATCH v2 02/11] arm64: debug: call software break handlers statically Ada Couprie Diaz
2025-05-20 15:35   ` Will Deacon
2025-06-02 16:39     ` Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 03/11] arm64: debug: call step " Ada Couprie Diaz
2025-05-20 15:35   ` Will Deacon
2025-05-28 16:02     ` Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 04/11] arm64: debug: remove break/step handler registration infrastructure Ada Couprie Diaz
2025-05-20 15:36   ` Will Deacon
2025-05-12 17:43 ` [PATCH v2 05/11] arm64: entry: Add entry and exit functions for debug exceptions Ada Couprie Diaz
2025-05-20 15:36   ` Will Deacon
2025-05-28 14:08     ` Ada Couprie Diaz
2025-05-29 10:11       ` Will Deacon
2025-05-12 17:43 ` [PATCH v2 06/11] arm64: debug: split hardware breakpoint exeception entry Ada Couprie Diaz
2025-05-20 15:36   ` Will Deacon
2025-05-28 15:17     ` Mark Rutland
2025-05-28 16:10       ` Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 07/11] arm64: debug: split single stepping exception entry Ada Couprie Diaz
2025-05-20 16:29   ` Will Deacon
2025-05-28 15:22     ` Mark Rutland
2025-05-29 10:10       ` Will Deacon [this message]
2025-05-29 10:48         ` Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 08/11] arm64: debug: split hardware watchpoint " Ada Couprie Diaz
2025-05-20 16:59   ` Will Deacon
2025-05-28 13:47     ` Ada Couprie Diaz
2025-05-28 15:42       ` Mark Rutland
2025-05-29 10:13         ` Will Deacon
2025-05-12 17:43 ` [PATCH v2 09/11] arm64: debug: split brk64 " Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 10/11] arm64: debug: split bkpt32 " Ada Couprie Diaz
2025-05-21  9:07   ` Will Deacon
2025-05-29 10:43     ` Ada Couprie Diaz
2025-05-12 17:43 ` [PATCH v2 11/11] arm64: debug: remove debug exception registration infrastructure Ada Couprie Diaz
2025-05-21  9:38   ` Will Deacon
2025-05-28 16:41     ` Ada Couprie Diaz
2025-05-29 10:15       ` Will Deacon
2025-05-13 12:25 ` [PATCH v2 00/11] arm64: debug: remove hook registration, split exception entry Luis Claudio R. Goncalves
2025-05-13 15:19   ` Ada Couprie Diaz
2025-05-16 11:57     ` Luis Claudio R. Goncalves
2025-05-28 10:38       ` Ada Couprie Diaz
2025-06-03 16:10         ` Ada Couprie Diaz

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=20250529101053.GA29082@willie-the-truck \
    --to=will@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=catalin.marinas@arm.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    /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