linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, trini@kernel.crashing.org
Subject: Re: [PATCH] Set cpu explicitly in kernel compiles
Date: Wed, 4 May 2005 19:21:10 -0400	[thread overview]
Message-ID: <45e21c1ae2899849665fb894a2adcc20@embeddededge.com> (raw)
In-Reply-To: <17017.16478.767293.191940@cargo.ozlabs.ibm.com>


On May 4, 2005, at 5:36 PM, Paul Mackerras wrote:
> Well, what about them?  I didn't change anything for them (except to
> remove the -mstring).  What -mcpu or -mtune options do you want for 
> them?

The only reason I mentioned it is the "new" default behavior of the
compiler is appropriate for only a very small subset of the cores,
and your solution only addresses some of the ones affected.
In the past, the default behavior was fine for all but your
special case :-)

My concern wasn't specifically for which options I wanted, but
rather for the mechanism to set all of them now that it appears
we need to do that.

> No.  We already have enough configuration questions that are
> unanswerable by ordinary mortals.

OK, but we still need some kind of indication from the configuration
process.  It seems to me it would be easier (and more logical) to
have the default behavior work like it has in the past, and use the
special options for the POWER4, which we already know in
the configuration.

Thanks.


	-- Dan

  reply	other threads:[~2005-05-04 23:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04  7:05 [PATCH] Set cpu explicitly in kernel compiles Paul Mackerras
2005-05-04 11:28 ` Dan Malek
2005-05-04 15:34   ` Tom Rini
2005-05-04 16:06     ` Chris Friesen
2005-05-04 21:36   ` Paul Mackerras
2005-05-04 23:21     ` Dan Malek [this message]
2005-05-05  4:00       ` Paul Mackerras
2005-05-05  4:12         ` Tom Rini
2005-05-05  4:44           ` Paul Mackerras
2005-05-05  4:47             ` Tom Rini
2005-05-05  5:22               ` Paul Mackerras
2005-05-05 12:24                 ` Dan Malek
2005-05-05 14:00                   ` Kumar Gala
2005-05-05 14:23                     ` Tom Rini
2005-05-05 15:12                       ` Kumar Gala
2005-05-05 15:27                         ` Tom Rini
2005-05-05 16:22                           ` Kumar Gala
2005-05-05 16:29                             ` Tom Rini
2005-05-06 14:44                 ` Segher Boessenkool
2005-05-06 14:53                   ` Tom Rini
2005-05-06 15:28                     ` Segher Boessenkool
2005-05-06 15:34                       ` Tom Rini
2005-05-06 15:47                     ` Kumar Gala
2005-05-05 12:12             ` Dan Malek
2005-05-04 13:45 ` Kumar Gala
2005-05-04 15:28   ` Tom Rini
2005-07-03 17:29 ` Olaf Hering
2005-07-03 18:32   ` Tom Rini
2005-07-05 18:14     ` Olaf Hering
2005-07-05 19:47       ` Tom Rini
2005-07-05 19:54         ` Olaf Hering
2005-07-05 19:58           ` Tom Rini
2005-07-05 20:17             ` Olaf Hering
2005-07-05 20:27             ` Olaf Hering
2005-07-05 21:22               ` Tom Rini
2005-07-06  6:38                 ` Olaf Hering
2006-04-02 19:40 ` Olaf Hering
2006-04-06  4:37   ` Paul Mackerras
2006-04-11 18:42     ` Olaf Hering

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=45e21c1ae2899849665fb894a2adcc20@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).