From: patchwork-bot+linux-riscv@kernel.org
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: linux-riscv@lists.infradead.org, punit.agrawal@bytedance.com,
sunilvl@ventanamicro.com, jesse@rivosinc.com, jrtc27@jrtc27.com,
corbet@lwn.net, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, cleger@rivosinc.com, evan@rivosinc.com,
conor.dooley@microchip.com, costa.shul@redhat.com,
andy.chiu@sifive.com, samitolvanen@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
palmer@rivosinc.com, anup@brainfault.org
Subject: Re: [PATCH v4] RISC-V: Provide the frequency of time CSR via hwprobe
Date: Thu, 25 Jul 2024 13:20:39 +0000 [thread overview]
Message-ID: <172191363910.6240.3368503310574547091.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240702033731.71955-2-cuiyunhui@bytedance.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 2 Jul 2024 11:37:31 +0800 you wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> The RISC-V architecture makes a real time counter CSR (via RDTIME
> instruction) available for applications in U-mode but there is no
> architected mechanism for an application to discover the frequency
> the counter is running at. Some applications (e.g., DPDK) use the
> time counter for basic performance analysis as well as fine grained
> time-keeping.
>
> [...]
Here is the summary with links:
- [v4] RISC-V: Provide the frequency of time CSR via hwprobe
https://git.kernel.org/riscv/c/2709e400c2e0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-25 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 3:37 [PATCH v4 0/1] Provide the frequency of time CSR via hwprobe Yunhui Cui
2024-07-02 3:37 ` [PATCH v4] RISC-V: " Yunhui Cui
2024-07-10 9:39 ` Punit Agrawal
2024-07-22 21:05 ` Punit Agrawal
2024-07-25 13:20 ` patchwork-bot+linux-riscv [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=172191363910.6240.3368503310574547091.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=cuiyunhui@bytedance.com \
--cc=evan@rivosinc.com \
--cc=jesse@rivosinc.com \
--cc=jrtc27@jrtc27.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=punit.agrawal@bytedance.com \
--cc=samitolvanen@google.com \
--cc=sunilvl@ventanamicro.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;
as well as URLs for NNTP newsgroup(s).