From: Jessica Clarke <jrtc27@jrtc27.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Clément Léger" <cleger@rivosinc.com>,
"Evan Green" <evan@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
costa.shul@redhat.com, "Andy Chiu" <andy.chiu@sifive.com>,
samitolvanen@google.com, linux-doc@vger.kernel.org,
linux-riscv <linux-riscv@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Palmer Dabbelt" <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Provide the frequency of mtime via hwprobe
Date: Tue, 18 Jun 2024 18:11:04 +0100 [thread overview]
Message-ID: <2BA519C8-D258-4D98-AD49-AC7D30D8B0D2@jrtc27.com> (raw)
In-Reply-To: <20240618114653.12485-1-cuiyunhui@bytedance.com>
On 18 Jun 2024, at 12:46, Yunhui Cui <cuiyunhui@bytedance.com> wrote:
>
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> A handful of user-visible behavior is based on the frequency of the
> machine-mode time.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
I would suggest referring to the user-mode CSR instead, i.e. “time”
rather than “mtime” throughout in names and descriptions, since that’s
the thing that user-mode software is actually reading from.
Jess
next prev parent reply other threads:[~2024-06-18 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 11:46 Yunhui Cui
2024-06-18 17:11 ` Jessica Clarke [this message]
2024-06-18 23:51 ` Icenowy Zheng
2024-06-21 3:01 ` [External] " yunhui cui
2024-06-21 5:18 ` Icenowy Zheng
2024-06-21 10:34 ` yunhui cui
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=2BA519C8-D258-4D98-AD49-AC7D30D8B0D2@jrtc27.com \
--to=jrtc27@jrtc27.com \
--cc=andy.chiu@sifive.com \
--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=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
all inboxes | Powered by JetHome®