From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Anup Patel <anup@brainfault.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@sifive.com>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <atish.patra@wdc.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] clocksource: riscv_timer: Provide sched_clock
Date: Mon, 3 Dec 2018 15:53:11 +0100 [thread overview]
Message-ID: <63f67f2b-9e17-78e6-beb5-65d32ff2f85c@linaro.org> (raw)
In-Reply-To: <CAAhSdy2rw=4Uw8=MZtfHi_ML9ZBqeiJ2iv+tRmDnjQDh7yuUHg@mail.gmail.com>
On 03/12/2018 15:50, Anup Patel wrote:
> On Mon, Dec 3, 2018 at 6:29 PM Daniel Lezcano <daniel.lezcano@linaro.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@brainfault.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??
I prefer the riscv config option to be merged via the riscv tree.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-12-03 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:35 [PATCH] clocksource: riscv_timer: Provide sched_clock Anup Patel
2018-12-03 12:59 ` Daniel Lezcano
2018-12-03 14:50 ` Anup Patel
2018-12-03 14:53 ` Daniel Lezcano [this message]
2018-12-06 20:32 ` Palmer Dabbelt
2018-12-07 2:27 ` Anup Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63f67f2b-9e17-78e6-beb5-65d32ff2f85c@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).