linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@bytedance.com>
To: palmer@dabbelt.com, Palmer Dabbelt <palmer@rivosinc.com>
Cc: paul.walmsley@sifive.com, costa.shul@redhat.com,
	aou@eecs.berkeley.edu, samitolvanen@google.com,  corbet@lwn.net,
	Anup Patel <anup@brainfault.org>,
	 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 jesse@rivosinc.com, conor.dooley@microchip.com,
	 Yunhui Cui <cuiyunhui@bytedance.com>,
	andy.chiu@sifive.com,  cleger@rivosinc.com,
	linux-riscv@lists.infradead.org,  jrtc27@jrtc27.com,
	evan@rivosinc.com, Punit Agrawal <punit.agrawal@bytedance.com>
Subject: Re: [PATCH v4] RISC-V: Provide the frequency of time CSR via hwprobe
Date: Mon, 22 Jul 2024 22:05:05 +0100	[thread overview]
Message-ID: <87bk2pkuim.fsf@gmail.com> (raw)
In-Reply-To: <87jzhtmvqg.fsf@bytedance.com> (Punit Agrawal's message of "Wed, 10 Jul 2024 10:39:35 +0100")

Punit Agrawal <punit.agrawal@bytedance.com> writes:

> Hi,
>
> Yunhui Cui <cuiyunhui@bytedance.com> writes:
>
>> 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.
>>
>> Add support to the hwprobe system call to export the time CSR
>> frequency to code running in U-mode.
>>
>> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
>> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
>> Reviewed-by: Evan Green <evan@rivosinc.com>
>> Reviewed-by: Anup Patel <anup@brainfault.org>
>> Acked-by: Punit Agrawal <punit.agrawal@bytedance.com>
>> ---
>>  Documentation/arch/riscv/hwprobe.rst  | 2 ++
>>  arch/riscv/include/asm/hwprobe.h      | 2 +-
>>  arch/riscv/include/uapi/asm/hwprobe.h | 1 +
>>  arch/riscv/kernel/sys_hwprobe.c       | 5 +++++
>>  4 files changed, 9 insertions(+), 1 deletion(-)
>
> The commit looks ready to be merged. Will this picked up for the 6.11
> release?
>
> Once this is merged, we can send out the DPDK change relying on the
> newly added key.

I see the first part of RISC-V patches got merged for 6.11. Any chance
for this patch to still make it for this cycle?

  reply	other threads:[~2024-07-22 21:05 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 [this message]
2024-07-25 13:20   ` patchwork-bot+linux-riscv

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=87bk2pkuim.fsf@gmail.com \
    --to=punit.agrawal@bytedance.com \
    --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=samitolvanen@google.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).