mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] clocksource/cadence_ttc: Reuse clocksource as sched_clock
Date: Fri, 5 Jul 2013 08:30:47 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1307050819000.11637@ionos.tec.linutronix.de> (raw)
In-Reply-To: <1372888216-10726-1-git-send-email-soren.brinkmann@xilinx.com>

On Wed, 3 Jul 2013, Soren Brinkmann wrote:

> Reuse the TTC clocksource timer as sched clock, too. Since only a single
> sched clock is supported in Linux, this feature optional and can be
> selected through Kconfig.

This changelog doesn't make sense.

There can be only one active sched_clock, but that does no mean, that
you cannot have different implementations compiled in.

So if you disable this config which sched_clock is your kernel using?
And if you enable it, how is guaranteed that you end up with the ttc
sched_clock as the active one? Just due to initcall ordering?

Thanks,

	tglx

  parent reply	other threads:[~2013-07-05  6:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 21:50 Soren Brinkmann
2013-07-04  3:30 ` Baruch Siach
2013-07-05 20:12   ` Sören Brinkmann
2013-07-05 20:42     ` Thomas Gleixner
2013-07-05 20:56       ` Sören Brinkmann
2013-07-05 20:59         ` Thomas Gleixner
2013-07-05 21:10           ` Sören Brinkmann
2013-07-05  6:30 ` Thomas Gleixner [this message]
2013-07-05 15:43   ` Sören Brinkmann
2013-07-05 16:05     ` Thomas Gleixner
2013-07-05 16:12       ` Sören Brinkmann
2013-07-05 16:23         ` Thomas Gleixner
2013-07-08 16:27           ` Sören Brinkmann

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=alpine.DEB.2.02.1307050819000.11637@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.com \
    /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®