Re: [PATCH] clocksource: riscv_timer: Provide sched_clock

2018-12-06 Thread Anup Patel
On Fri, Dec 7, 2018 at 2:02 AM Palmer Dabbelt wrote: > > On Mon, 03 Dec 2018 04:35:24 PST (-0800), a...@brainfault.org 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.

Re: [PATCH] clocksource: riscv_timer: Provide sched_clock

2018-12-06 Thread Palmer Dabbelt
On Mon, 03 Dec 2018 04:35:24 PST (-0800), a...@brainfault.org 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 rdtim

Re: [PATCH] clocksource: riscv_timer: Provide sched_clock

2018-12-03 Thread Daniel Lezcano
On 03/12/2018 15:50, Anup Patel wrote: > On Mon, Dec 3, 2018 at 6:29 PM Daniel Lezcano > 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 >>> defa

Re: [PATCH] clocksource: riscv_timer: Provide sched_clock

2018-12-03 Thread Anup Patel
On Mon, Dec 3, 2018 at 6:29 PM Daniel Lezcano 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 exp

Re: [PATCH] clocksource: riscv_timer: Provide sched_clock

2018-12-03 Thread Daniel Lezcano
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 (simil