From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>, linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, rostedt@goodmis.org,
revest@chromium.org, mhiramat@kernel.org
Subject: Re: [PATCH v2 0/4] arm64/ftrace: move to DYNAMIC_FTRACE_WITH_ARGS
Date: Fri, 18 Nov 2022 19:40:47 +0000 [thread overview]
Message-ID: <166877980236.3587415.12262525621041241675.b4-ty@kernel.org> (raw)
In-Reply-To: <20221103170520.931305-1-mark.rutland@arm.com>
On Thu, 3 Nov 2022 17:05:16 +0000, Mark Rutland wrote:
> This series replaces arm64's support for FTRACE_WITH_REGS with support
> for FTRACE_WITH_ARGS. This removes some overhead and complexity, and
> removes some latent issues with inconsistent presentation of struct
> pt_regs (which can only be reliably saved/restored at exception
> boundaries).
>
> The existing FTRACE_WITH_REGS support was added for two major reasons:
>
> [...]
Applied to arm64 (for-next/ftrace), thanks!
[1/4] ftrace: pass fregs to arch_ftrace_set_direct_caller()
https://git.kernel.org/arm64/c/9705bc709604
[2/4] ftrace: rename ftrace_instruction_pointer_set() -> ftrace_regs_set_instruction_pointer()
https://git.kernel.org/arm64/c/0ef86097f127
[3/4] ftrace: abstract DYNAMIC_FTRACE_WITH_ARGS accesses
https://git.kernel.org/arm64/c/94d095ffa0e1
[4/4] ftrace: arm64: move from REGS to ARGS
https://git.kernel.org/arm64/c/26299b3f6ba2
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-11-18 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:05 Mark Rutland
2022-11-03 17:05 ` [PATCH v2 1/4] ftrace: pass fregs to arch_ftrace_set_direct_caller() Mark Rutland
2022-11-03 17:05 ` [PATCH v2 2/4] ftrace: rename ftrace_instruction_pointer_set() -> ftrace_regs_set_instruction_pointer() Mark Rutland
2022-11-03 17:05 ` [PATCH v2 3/4] ftrace: abstract DYNAMIC_FTRACE_WITH_ARGS accesses Mark Rutland
2022-11-03 17:05 ` [PATCH v2 4/4] ftrace: arm64: move from REGS to ARGS Mark Rutland
2022-11-15 11:27 ` Will Deacon
2022-11-17 10:52 ` Mark Rutland
2022-11-18 12:31 ` Will Deacon
2022-11-18 13:57 ` Mark Rutland
2022-11-18 14:09 ` Will Deacon
2022-11-15 15:01 ` [PATCH v2 0/4] arm64/ftrace: move to DYNAMIC_FTRACE_WITH_ARGS Steven Rostedt
2022-11-15 15:48 ` Mark Rutland
2022-11-18 0:04 ` Masami Hiramatsu
2022-11-18 19:40 ` 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=166877980236.3587415.12262525621041241675.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.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®