mbox series

[v2,0/2] Provide sched_clock for riscv_timer

Message ID 20181204102952.21297-1-anup@brainfault.org (mailing list archive)
Headers show
Series Provide sched_clock for riscv_timer | expand

Message

Anup Patel Dec. 4, 2018, 10:29 a.m. UTC
This patchset extends riscv_timer to provide sched_clock using generic
sched_clock framework.

The patchset is tested on QEMU virt machine. It is based on Linux-4.20-rc5
and can be found at riscv_sched_clock_v2 branch of:
https://github.com/avpatel/linux.git

Changes since v1:
 - Added patch to select GENERIC_SCHED_CLOCK for RISC-V
 - Kconfig RISCV_TIMER depends on GENERIC_SCHED_CLOCK

Anup Patel (2):
  RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers
  clocksource: riscv_timer: Provide sched_clock

 arch/riscv/Kconfig                | 1 +
 drivers/clocksource/Kconfig       | 2 +-
 drivers/clocksource/riscv_timer.c | 9 +++++++++
 3 files changed, 11 insertions(+), 1 deletion(-)

Comments

Palmer Dabbelt Dec. 7, 2018, 5:59 p.m. UTC | #1
On Tue, 04 Dec 2018 02:29:50 PST (-0800), anup@brainfault.org wrote:
> This patchset extends riscv_timer to provide sched_clock using generic
> sched_clock framework.
>
> The patchset is tested on QEMU virt machine. It is based on Linux-4.20-rc5
> and can be found at riscv_sched_clock_v2 branch of:
> https://github.com/avpatel/linux.git
>
> Changes since v1:
>  - Added patch to select GENERIC_SCHED_CLOCK for RISC-V
>  - Kconfig RISCV_TIMER depends on GENERIC_SCHED_CLOCK
>
> Anup Patel (2):
>   RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers
>   clocksource: riscv_timer: Provide sched_clock
>
>  arch/riscv/Kconfig                | 1 +
>  drivers/clocksource/Kconfig       | 2 +-
>  drivers/clocksource/riscv_timer.c | 9 +++++++++
>  3 files changed, 11 insertions(+), 1 deletion(-)

I'm going to add these to my for-next, but let me know if these should go 
through a clock maintainer's tree instead and I'll drop them.
Daniel Lezcano Dec. 9, 2018, 4:30 p.m. UTC | #2
On 07/12/2018 18:59, Palmer Dabbelt wrote:
> On Tue, 04 Dec 2018 02:29:50 PST (-0800), anup@brainfault.org wrote:
>> This patchset extends riscv_timer to provide sched_clock using generic
>> sched_clock framework.
>>
>> The patchset is tested on QEMU virt machine. It is based on
>> Linux-4.20-rc5
>> and can be found at riscv_sched_clock_v2 branch of:
>> https://github.com/avpatel/linux.git
>>
>> Changes since v1:
>>  - Added patch to select GENERIC_SCHED_CLOCK for RISC-V
>>  - Kconfig RISCV_TIMER depends on GENERIC_SCHED_CLOCK
>>
>> Anup Patel (2):
>>   RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers
>>   clocksource: riscv_timer: Provide sched_clock
>>
>>  arch/riscv/Kconfig                | 1 +
>>  drivers/clocksource/Kconfig       | 2 +-
>>  drivers/clocksource/riscv_timer.c | 9 +++++++++
>>  3 files changed, 11 insertions(+), 1 deletion(-)
> 
> I'm going to add these to my for-next, but let me know if these should
> go through a clock maintainer's tree instead and I'll drop them.

I'll take the second one through my tree.

  -- Daniel
Palmer Dabbelt Dec. 10, 2018, 5:31 p.m. UTC | #3
On Sun, 09 Dec 2018 08:30:34 PST (-0800), daniel.lezcano@linaro.org wrote:
> On 07/12/2018 18:59, Palmer Dabbelt wrote:
>> On Tue, 04 Dec 2018 02:29:50 PST (-0800), anup@brainfault.org wrote:
>>> This patchset extends riscv_timer to provide sched_clock using generic
>>> sched_clock framework.
>>>
>>> The patchset is tested on QEMU virt machine. It is based on
>>> Linux-4.20-rc5
>>> and can be found at riscv_sched_clock_v2 branch of:
>>> https://github.com/avpatel/linux.git
>>>
>>> Changes since v1:
>>>  - Added patch to select GENERIC_SCHED_CLOCK for RISC-V
>>>  - Kconfig RISCV_TIMER depends on GENERIC_SCHED_CLOCK
>>>
>>> Anup Patel (2):
>>>   RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers
>>>   clocksource: riscv_timer: Provide sched_clock
>>>
>>>  arch/riscv/Kconfig                | 1 +
>>>  drivers/clocksource/Kconfig       | 2 +-
>>>  drivers/clocksource/riscv_timer.c | 9 +++++++++
>>>  3 files changed, 11 insertions(+), 1 deletion(-)
>>
>> I'm going to add these to my for-next, but let me know if these should
>> go through a clock maintainer's tree instead and I'll drop them.
>
> I'll take the second one through my tree.

OK, I dropped it.