From: David Miller <davem@davemloft.net>
To: tony.luck@intel.com
Cc: nacc@us.ibm.com, mingo@elte.hu, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state
Date: Mon, 04 Aug 2008 15:02:49 -0700 (PDT) [thread overview]
Message-ID: <20080804.150249.71509974.davem@davemloft.net> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA308329110@orsmsx505.amr.corp.intel.com>
From: "Luck, Tony" <tony.luck@intel.com>
Date: Mon, 4 Aug 2008 15:00:47 -0700
> > I'd bet resonable sums of money that we are (once again) accessing
> > per-cpu variables in code before ia64 has a chance to initialize
> > things so that they can actually work. :-(
>
> I tried this simple hack to check ... per-cpu variables are
> not usable until cpu_init() sets up the "ar.k3" register on
> ia64. So this hack checks to see if it is set before calling
> cpu_clock():
Can you guys on IA64 possibly set ar.k3 simply to zero or to some
other similar value which cancels out the per-cpu computation?
That's what sparc64 and other platforms do.
next prev parent reply other threads:[~2008-08-04 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 19:46 [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state Nishanth Aravamudan
2008-08-04 20:37 ` Luck, Tony
2008-08-04 22:00 ` Luck, Tony
2008-08-04 22:02 ` David Miller [this message]
2008-08-04 22:10 ` Luck, Tony
2008-08-04 22:14 ` David Miller
2008-08-04 22:22 ` Luck, Tony
2008-08-04 22:41 ` Luck, Tony
2008-08-04 22:45 ` Nishanth Aravamudan
2008-08-04 22:53 ` Luck, Tony
2008-08-04 23:30 ` Nishanth Aravamudan
2008-08-05 8:56 ` Peter Zijlstra
2008-08-05 14:59 ` Luck, Tony
2008-08-05 17:34 ` Nishanth Aravamudan
2008-08-13 0:37 ` Luck, Tony
2008-08-13 16:25 ` Ingo Molnar
2008-08-13 19:29 ` Nishanth Aravamudan
2008-08-13 20:11 ` Luck, Tony
2008-08-19 22:19 ` Nishanth Aravamudan
2008-08-19 22:34 ` 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=20080804.150249.71509974.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nacc@us.ibm.com \
--cc=tony.luck@intel.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