From: Will Deacon <will@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>, catalin.marinas@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
liwei391@huawei.com, mhiramat@kernel.org,
linux-kernel@vger.kernel.org, daniel.thompson@linaro.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
ardb@kernel.org, dianders@chromium.org, maz@kernel.org
Subject: Re: [PATCH v6 0/2] arm64: Fix pending single-step debugging issues
Date: Fri, 14 Apr 2023 15:38:39 +0100 [thread overview]
Message-ID: <168147598830.2391666.1506104508286330232.b4-ty@kernel.org> (raw)
In-Reply-To: <20230202073148.657746-1-sumit.garg@linaro.org>
On Thu, 2 Feb 2023 13:01:46 +0530, Sumit Garg wrote:
> This patch-set reworks pending fixes from Wei's series [1] to make
> single-step debugging via kgdb/kdb on arm64 work as expected. There was
> a prior discussion on ML [2] regarding if we should keep the interrupts
> enabled during single-stepping. So patch #1 follows suggestion from Will
> [3] to not disable interrupts during single stepping but rather skip
> single stepping within interrupt handler.
>
> [...]
Applied second patch to arm64 (for-next/misc), thanks!
[2/2] arm64: kgdb: Set PSTATE.SS to 1 to re-enable single-step
https://git.kernel.org/arm64/c/af6c0bd59f4f
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-04-14 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 7:31 Sumit Garg
2023-02-02 7:31 ` [PATCH v6 1/2] arm64: entry: Skip single stepping into interrupt handlers Sumit Garg
2025-09-24 11:59 ` Matthias Schiffer
2023-02-02 7:31 ` [PATCH v6 2/2] arm64: kgdb: Set PSTATE.SS to 1 to re-enable single-step Sumit Garg
2023-02-22 7:06 ` [PATCH v6 0/2] arm64: Fix pending single-step debugging issues Sumit Garg
2023-04-14 14:38 ` 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=168147598830.2391666.1506104508286330232.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=sumit.garg@linaro.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
all inboxes | Powered by JetHome®