From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
ajones@ventanamicro.com, aou@eecs.berkeley.edu,
alexghiti@rivosinc.com, apatel@ventanamicro.com, maz@kernel.org,
paul.walmsley@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: Add tracepoints for SBI calls and returns
Date: Fri, 12 Jul 2024 10:20:32 +0000 [thread overview]
Message-ID: <172077963264.4770.1010194114117186773.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240321230131.1838105-1-samuel.holland@sifive.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 21 Mar 2024 16:01:25 -0700 you wrote:
> These are useful for measuring the latency of SBI calls. The SBI HSM
> extension is excluded because those functions are called from contexts
> such as cpuidle where instrumentation is not allowed.
>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: Add tracepoints for SBI calls and returns
https://git.kernel.org/riscv/c/56c1c1a09ab9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-07-12 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 23:01 [PATCH v2] riscv: Add tracepoints for SBI calls and returns Samuel Holland
2024-03-22 9:27 ` Alexandre Ghiti
2024-03-26 3:39 ` Samuel Holland
2024-07-10 20:29 ` Palmer Dabbelt
2024-07-12 10:20 ` patchwork-bot+linux-riscv [this message]
2024-08-13 20:26 ` Conor Dooley
2024-08-16 17:29 ` Alexandre Ghiti
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=172077963264.4770.1010194114117186773.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.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