linux-kernel - Re: [PATCH v2 0/2] Provide sched_clock for riscv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <mhng-5c8b0e7e-4eba-4800-87fd-4ef883fb5ac5@palmer-si-x1c4>
Date:   Mon, 10 Dec 2018 09:31:14 -0800 (PST)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     daniel.lezcano@...aro.org
CC:     anup@...infault.org, tglx@...utronix.de, aou@...s.berkeley.edu,
        atish.patra@....com, Christoph Hellwig <hch@...radead.org>,
        linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject:     Re: [PATCH v2 0/2] Provide sched_clock for riscv_timer

On Sun, 09 Dec 2018 08:30:34 PST (-0800), daniel.lezcano@...aro.org wrote:
> On 07/12/2018 18:59, Palmer Dabbelt wrote:
>> On Tue, 04 Dec 2018 02:29:50 PST (-0800), anup@...infault.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.