From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] (comments requested) adding finer-grained timing to PPC add_timer_randomness()
Date: Thu, 23 Aug 2001 15:11:04 +0200 [thread overview]
Message-ID: <20010823131104.9016@smtp.adsl.oleane.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0108231137080.2015-100000@ltgp.iram.es>
In-Reply-To: <Pine.LNX.4.21.0108231137080.2015-100000@ltgp.iram.es>
>> In the 2.4 tree we have code that works out a cpu features word from
>> the PVR value. The cpu features word has bits for things like does
>> the cpu have the TB register, does the MMU use a hash table, does the
>> cpu have separate I and D caches, etc.
>
>Reading the PVR is probably faster in this case, since you avoid a
>potential cache miss. As I said in an earlier message the __USE_RTC macro
>should be made dependent on whether the kernel supports 601 or not.
The CPU features will nop-out sections of code that don't apply for
a given CPU if you use the assembly macros. If you nop'out a couple
of instructions, you win over reading the PVR, masking out bits,
comparing, and doing a conditional branch.
Ben.
next prev parent reply other threads:[~2001-08-23 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 20:57 Chris Friesen
2001-08-22 21:06 ` Ignacio Vazquez-Abrams
2001-08-22 21:27 ` Chris Friesen
2001-08-23 1:33 ` Paul Mackerras
2001-08-23 9:46 ` Gabriel Paubert
2001-08-23 13:11 ` Benjamin Herrenschmidt [this message]
2001-08-23 12:31 ` Paul Mackerras
2001-08-24 7:32 ` Gabriel Paubert
2001-08-24 13:59 ` Christopher Friesen
2001-08-28 20:50 ` Gabriel Paubert
2001-08-24 17:54 ` [PATCH] (comments requested) adding finer-grained timing to PPC Albert D. Cahalan
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=20010823131104.9016@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=paulus@samba.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®