From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 printk_clock()
Date: Thu, 02 Feb 2006 21:50:46 +0000 [thread overview]
Message-ID: <20060202215045.GA7760@sgi.com> (raw)
In-Reply-To: <20060202204422.GA27082@sgi.com>
On Thu, Feb 02, 2006 at 01:46:05PM -0800, Luck, Tony wrote:
> > Jack, I think this is the thread you are looking for:
> > http://marc.theaimsgroup.com/?l=linux-ia64&m\x112422250517703&w=2
>
> The current state of the tree is that Andrew added the patch
> to make the definition of printk_clock() in kernel/printk.c
> "__attribute__((weak))" so that architectures could override
> with their own version. Default version uses sched_clock().
>
> So far we haven't made use of this ... but we need to do it (partly
> because it crashes early on Altix, but also because it returns
> meaningless values on any system where the clocks are not synched
> on different cpus (perhaps just Altix).
>
> -Tony
Do you understand why it crashes only on Altix?? It looked to
me that all IA64 platforms would crash but obviously I'm wrong.
What did I miss...
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2006-02-02 21:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 20:44 ia64 printk_clock() Jack Steiner
2006-02-02 21:22 ` Dean Roe
2006-02-02 21:46 ` Luck, Tony
2006-02-02 21:50 ` Jack Steiner [this message]
2006-02-02 22:29 ` Luck, Tony
2006-02-02 22:52 ` Chen, Kenneth W
2006-02-03 17:43 ` Chen, Kenneth W
2006-02-03 18:04 ` Luck, Tony
2006-02-03 18:30 ` Chen, Kenneth W
2006-02-03 18:43 ` Luck, Tony
2006-02-03 18:55 ` Chen, Kenneth W
2006-02-04 0:16 ` Keith Owens
2006-02-04 0:28 ` Chen, Kenneth W
2006-02-04 0:32 ` Luck, Tony
2006-02-04 0:36 ` Keith Owens
2006-02-06 18:14 ` Luck, Tony
2006-02-06 18:34 ` Chen, Kenneth W
2006-02-06 20:40 ` Magenheimer, Dan (HP Labs Fort Collins)
2006-02-06 21:37 ` Chen, Kenneth W
2006-02-07 11:11 ` Jes Sorensen
2006-02-08 0:05 ` Luck, Tony
2006-02-08 6:29 ` Jes Sorensen
2006-02-08 18:18 ` Luck, Tony
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=20060202215045.GA7760@sgi.com \
--to=steiner@sgi.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.