From: Zou Nan hai <nanhai.zou@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC Patch]Use ar.kr2 for smp_processor_id
Date: Thu, 08 Feb 2007 04:27:31 +0000 [thread overview]
Message-ID: <1170908851.3230.18.camel@linux-znh> (raw)
In-Reply-To: <1170905324.3230.7.camel@linux-znh>
On Thu, 2007-02-08 at 14:04, Keith Owens wrote:
> Zou Nan hai (on 08 Feb 2007 11:28:44 +0800) wrote:
> >Pin ar.kr2 of each CPU, so that smp_processor_id can use it.
>
> Historically ar.k2 has been reserved for debugging purposes, for
> example in ivt.S. Debuggers often need a location that can be used to
> track progress, it has to be somewhere that does not rely on TLB
> entries and is guaranteed to appear in MCA/INIT records - ar.k2 is
> perfect for this.
>
Ok, seems that current kr3 is only used by ia64_itc_printk_clock?
> Use Tony's suggestion of testing for a change in ar.k3 (guaranteed to
> be unique on every cpu) and caching the corresponding cpu number when
> it changes.
>
But why do we even need to cache it?
It is already in a register if we put it to kr3.
so smp_processor_id() could be very fast. and later sys_getcpu can
also be very fast.
Thanks
Zou Nan hai
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-02-08 4:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 3:28 [RFC Patch]Use ar.kr2 for smp_processor_id Zou Nan hai
2007-02-08 4:27 ` Zou Nan hai [this message]
2007-02-08 4:59 ` Zou Nan hai
2007-02-08 5:11 ` Zou Nan hai
2007-02-08 6:04 ` Keith Owens
2007-02-08 6:37 ` Keith Owens
2007-02-08 6:55 ` Keith Owens
2007-02-08 7:14 ` Zou Nan hai
2007-02-08 7:38 ` Zou Nan hai
2007-02-08 8:28 ` peterc
2007-02-08 8:40 ` Keith Owens
2007-02-08 18:03 ` Luck, Tony
2007-02-08 23:59 ` Keith Owens
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=1170908851.3230.18.camel@linux-znh \
--to=nanhai.zou@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox