[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2BA519C8-D258-4D98-AD49-AC7D30D8B0D2@jrtc27.com>
Date: Tue, 18 Jun 2024 18:11:04 +0100
From: Jessica Clarke <jrtc27@...c27.com>
To: Yunhui Cui <cuiyunhui@...edance.com>
Cc: Jonathan Corbet <corbet@....net>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Clément Léger <cleger@...osinc.com>,
Evan Green <evan@...osinc.com>,
Conor Dooley <conor.dooley@...rochip.com>,
costa.shul@...hat.com,
Andy Chiu <andy.chiu@...ive.com>,
samitolvanen@...gle.com,
linux-doc@...r.kernel.org,
linux-riscv <linux-riscv@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
Palmer Dabbelt <palmer@...osinc.com>
Subject: Re: [PATCH] RISC-V: Provide the frequency of mtime via hwprobe
On 18 Jun 2024, at 12:46, Yunhui Cui <cuiyunhui@...edance.com> wrote:
>
> From: Palmer Dabbelt <palmer@...osinc.com>
>
> A handful of user-visible behavior is based on the frequency of the
> machine-mode time.
>
> Signed-off-by: Palmer Dabbelt <palmer@...osinc.com>
> Signed-off-by: Yunhui Cui <cuiyunhui@...edance.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
Powered by blists - more mailing lists