mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Hadimani, Jagadish" <Jagadish.Hadimani@amd.com>
Cc: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
	"a.zummo@towertech.it" <a.zummo@towertech.it>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: Kernel without RTC
Date: Wed, 8 Mar 2017 14:47:48 +0100	[thread overview]
Message-ID: <20170308134748.yk52f7aqm7d4kwdg@piout.net> (raw)
In-Reply-To: <016032B5-A966-48A9-B60D-AD75B8B857EE@amd.com>

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@free-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

  reply	other threads:[~2017-03-08 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 19:18 Shah, Nehal-bakulchandra
2017-03-08 13:17 ` Alexandre Belloni
2017-03-08 13:33   ` Hadimani, Jagadish
2017-03-08 13:47     ` Alexandre Belloni [this message]
2017-03-08 15:06       ` Thomas Gleixner

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=20170308134748.yk52f7aqm7d4kwdg@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=Jagadish.Hadimani@amd.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=a.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rtc-linux@googlegroups.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

all inboxes | Powered by JetHome®