From: john stultz <johnstul@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] new timeofday core subsystem (v.A1)
Date: Wed, 08 Dec 2004 11:22:29 -0800 [thread overview]
Message-ID: <1102533749.1281.94.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412081043031.27324@schroedinger.engr.sgi.com>
On Wed, 2004-12-08 at 10:44, Christoph Lameter wrote:
> On Tue, 7 Dec 2004, john stultz wrote:
>
> > +struct timesource_t {
> > + char* name;
> > + int priority;
> > + enum {
> > + TIMESOURCE_FUNCTION,
> > + TIMESOURCE_MMIO_32,
> > + TIMESOURCE_MMIO_64
> > + } type;
> > + cycle_t (*read_fnct)(void);
> > + void* ptr;
> > + cycle_t mask;
> > + u32 mult;
> > + u32 shift;
> > +};
>
> Maybe add TIMESOURCE_CPU or so? How can one specify a time source in a
> cpu register?
Yea, for now its a function. I was thinking that get_cycles() could be
used as an arch independent way to do this.
Good suggestion!
Thanks!
-john
next prev parent reply other threads:[~2004-12-08 19:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 1:55 [RFC] New timeofday proposal (v.A1) john stultz
2004-12-08 1:56 ` [RFC] new timeofday core subsystem (v.A1) john stultz
2004-12-08 1:57 ` [RFC] new timeofday arch specific hooks (v.A1) john stultz
2004-12-08 1:58 ` [RFC] new timeofday timesources (v.A1) john stultz
2004-12-08 2:02 ` john stultz
2004-12-08 9:17 ` [RFC] new timeofday core subsystem (v.A1) Pavel Machek
2004-12-08 18:44 ` Christoph Lameter
2004-12-08 19:22 ` john stultz [this message]
2004-12-08 18:53 ` Christoph Lameter
2004-12-08 20:27 ` Martin Waitz
[not found] ` <1102555933.1281.301.camel@cog.beaverton.ibm.com>
2004-12-09 7:32 ` Martin Waitz
2004-12-08 18:25 ` [RFC] New timeofday proposal (v.A1) Christoph Lameter
2004-12-08 19:11 ` john stultz
2004-12-08 19:20 ` Christoph Lameter
2004-12-08 19:58 ` john stultz
2004-12-08 20:14 ` Christoph Lameter
2004-12-08 21:25 ` George Anzinger
2004-12-08 23:47 ` Christoph Lameter
2004-12-08 23:36 ` john stultz
2004-12-08 23:53 ` Christoph Lameter
2004-12-09 0:17 ` john stultz
2004-12-09 0:40 ` Christoph Lameter
2004-12-09 0:51 ` john stultz
2004-12-09 1:24 ` Christoph Lameter
2004-12-09 7:57 ` Ulrich Windl
2004-12-09 8:29 ` john stultz
2004-12-09 7:47 ` Ulrich Windl
2004-12-08 18:43 ` Nicolas Pitre
2004-12-08 18:57 ` john stultz
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=1102533749.1281.94.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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®