mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"john stultz" <johnstul@us.ibm.com>,
	"Rabin VINCENT" <rabin.vincent@stericsson.com>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Colin Cross" <ccross@google.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] RFC: nomadik: expand timesource to 63 bits
Date: Fri, 12 Nov 2010 11:31:18 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1011121130350.2900@localhost6.localdomain6> (raw)
In-Reply-To: <4CDD120A.2050401@stericsson.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 555 bytes --]

On Fri, 12 Nov 2010, Linus Walleij wrote:

> Uwe Kleine-König wrote:
> 
> > Instead of implementing sched_clock for each architecture seperatly,
> > wouldn't it be nice to have a generic sched_clock that uses the
> > architecture's clocksource?  I tried to implement that some time ago,
> > but tglx shoot it down because of locking problems.
> 
> I was and still am a big fan of this approach, I am willing to help
> testing it if you want to dust off this patch set...

sched_clock is not necessarily the same as the current clocksource.

Thanks,

	tglx

  reply	other threads:[~2010-11-12 10:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  9:05 Linus Walleij
2010-11-11 10:16 ` Thomas Gleixner
2010-11-11 10:31   ` Linus Walleij
2010-11-11 11:05     ` Thomas Gleixner
2010-11-11 18:31       ` Nicolas Pitre
2010-11-11 19:00         ` Thomas Gleixner
2010-11-11 19:19           ` Nicolas Pitre
2010-11-11 21:33 ` john stultz
2010-11-12  9:43   ` Linus Walleij
2010-11-12  9:57   ` Uwe Kleine-König
2010-11-12 10:08     ` Linus Walleij
2010-11-12 10:31       ` Thomas Gleixner [this message]
2010-11-12 10:37         ` Linus Walleij
2010-11-12 11:08           ` Thomas Gleixner
2010-11-12 19:18           ` Nicolas Pitre
2010-11-12 20:22           ` john stultz
2010-11-12 19:15     ` Nicolas Pitre

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.LFD.2.00.1011121130350.2900@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=ccross@google.com \
    --cc=johnstul@us.ibm.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=rabin.vincent@stericsson.com \
    --cc=u.kleine-koenig@pengutronix.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®