From: Catalin Marinas <catalin.marinas@arm.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu, maz@kernel.org,
alexandru.elisei@arm.com, will@kernel.org,
Liao Chang <liaochang1@huawei.com>,
palmer@dabbelt.com, guoren@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org
Subject: Re: (subset) [PATCH V4 0/3] kprobe: Optimize the performance of patching ss
Date: Fri, 30 Sep 2022 17:25:53 +0100 [thread overview]
Message-ID: <166455513411.3737568.2438972272060446845.b4-ty@arm.com> (raw)
In-Reply-To: <20220927022435.129965-1-liaochang1@huawei.com>
On Tue, 27 Sep 2022 10:24:32 +0800, Liao Chang wrote:
> Single-step slot would not be used until kprobe is enabled, that means
> no race condition occurs on it under SMP, hence it is safe to pacth ss
> slot without stopping machine.
>
> v4:
> 1. Add Acked-by from Will Deacon
> 2. Mark Rutland provides some subtleties on arm64 micro-architecture
> that needs to follow.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[3/3] arm64/kprobe: Optimize the performance of patching single-step slot
https://git.kernel.org/arm64/c/a0caebbd0460
--
Catalin
prev parent reply other threads:[~2022-09-30 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 2:24 [PATCH V4 0/3] kprobe: Optimize the performance of patching ss Liao Chang
2022-09-27 2:24 ` [PATCH 1/3] riscv/kprobe: Optimize the performance of patching single-step slot Liao Chang
2022-09-27 2:24 ` [PATCH 2/3] csky/kprobe: " Liao Chang
2022-09-27 2:24 ` [PATCH 3/3] arm64/kprobe: " Liao Chang
2022-09-29 16:50 ` Catalin Marinas
2022-09-30 1:02 ` liaochang (A)
2022-09-30 8:15 ` Catalin Marinas
2022-09-30 16:25 ` Catalin Marinas [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=166455513411.3737568.2438972272060446845.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=will@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).