[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAhSdy2rw=4Uw8=MZtfHi_ML9ZBqeiJ2iv+tRmDnjQDh7yuUHg@mail.gmail.com>
Date: Mon, 3 Dec 2018 20:20:47 +0530
From: Anup Patel <anup@...infault.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <atish.patra@....com>,
Christoph Hellwig <hch@...radead.org>,
linux-riscv@...ts.infradead.org,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clocksource: riscv_timer: Provide sched_clock
On Mon, Dec 3, 2018 at 6:29 PM Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>
> On 03/12/2018 13:35, Anup Patel wrote:
> > Currently, we don't have a sched_clock registered for RISC-V systems.
> > This means Linux time keeping will use jiffies (running at HZ) as the
> > default sched_clock.
> >
> > To avoid this, we explicity provide sched_clock using RISC-V rdtime
> > instruction (similar to riscv_timer clocksource).
> >
> > Signed-off-by: Anup Patel <anup@...infault.org>
>
> Hi Anup,
>
> the GENERIC_SCHED_CLOCK dependency in the Kconfig is missing.
Sure, will do.
I also have another patch to select GENERIC_SCHED_CLOCK
for CONFIG_RISCV. Should I squash that patch with this patch??
Regards,
Anup
Powered by blists - more mailing lists