From: Paul Mackerras <paulus@samba•org>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Worst case performance of up()
Date: Fri, 8 Dec 2006 13:33:14 +1100 [thread overview]
Message-ID: <17784.52970.343161.782030@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1165356002.5469.16.camel@localhost.localdomain>
Benjamin Herrenschmidt writes:
> Paul, do you reckon the best solution here is to clear ppc_md.power_save
> when detecting an SMP powermac ? (Or the flush-on-lock property)
Yes, that sounds good. It would let us get rid of the runtime cpu
feature check in idle_6xx.c too.
Paul.
next prev parent reply other threads:[~2006-12-08 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 16:21 Worst case performance of up() Adrian Cox
2006-11-24 20:45 ` Benjamin Herrenschmidt
2006-11-27 21:02 ` Adrian Cox
2006-12-02 10:35 ` Adrian Cox
2006-12-02 11:15 ` Benjamin Herrenschmidt
2006-12-02 11:54 ` Adrian Cox
2006-12-02 20:52 ` Benjamin Herrenschmidt
2006-12-04 13:43 ` Adrian Cox
2006-12-04 20:25 ` Benjamin Herrenschmidt
2006-12-05 22:00 ` Benjamin Herrenschmidt
2006-12-08 2:33 ` Paul Mackerras [this message]
2006-12-08 3:10 ` Benjamin Herrenschmidt
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=17784.52970.343161.782030@cargo.ozlabs.ibm.com \
--to=paulus@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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