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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 8 Mar 2017 14:47:48 +0100
From:   Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:     "Hadimani, Jagadish" <Jagadish.Hadimani@....com>
Cc:     "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@....com>,
        "a.zummo@...ertech.it" <a.zummo@...ertech.it>,
        "rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: Kernel without RTC

On 08/03/2017 at 13:33:33 +0000, Hadimani, Jagadish wrote:
> Hello Alexandre,
> 
> I guess the Linux kernel uses HPET timer...
> But can we can force Linux kernel to use Tsc or per core timer...
> 

That is probably the case but your are targeting the wrong subsystem.
The timekeeping is done using two different devices: clocksource and
clockevent. Usually, the drivers are in drivers/clocksource. I'm
definitively not an expert in x86 but the clockevent seems to be
registered from arch/x86/kernel/hpet.c and the clocksource from
arch/x86/kernel/tsc.c

IIRC the clocksource is optional but the clockevent is mandatory so if
you don't have an HPET, you will need to register a clockevent device
from somewhere else.

Maybe the simplest thing to do is to ask the x86 maintainers and the
time maintainers. Luckily for you, they are the same people (Thomas and
Ingo, added in cc).


> Sent from my iPhone
> 
> > On 8 Mar 2017, at 6:47 PM, Alexandre Belloni <alexandre.belloni@...e-electrons.com> wrote:
> > 
> > Hi,
> > 
> >> On 07/03/2017 at 00:48:18 +0530, Shah, Nehal-bakulchandra wrote:
> >> Hi,
> >> 
> >> Currently we are having hardware which does not have RTC. It is single processor system. However it does have TSC timer.
> >> 
> >> Now, how to use scheduler with only TSC as current kernel scheduler leverage the RTC for scheduling? I had seen one old patch
> >> 
> >> http://marc.info/?l=linux-kernel&m=112013203625990&w=2 
> >> 
> >> But i guess this patch was later on not taken, It will be great if you can some pointers to move forward?
> >> 
> > 
> > The kernel doesn't use the RTC for its time source so it can
> > already work without an RTC.
> > 
> > 
> > -- 
> > Alexandre Belloni, Free Electrons
> > Embedded Linux and Kernel engineering
> > http://free-electrons.com

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ