From: Willy Tarreau <w@1wt.eu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Tobias Doerffel <tobias.doerffel@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Specific support for Intel Atom architecture
Date: Sun, 3 May 2009 07:38:23 +0200 [thread overview]
Message-ID: <20090503053821.GI570@1wt.eu> (raw)
In-Reply-To: <49F9DB70.2050906@zytor.com>
On Thu, Apr 30, 2009 at 10:10:08AM -0700, H. Peter Anvin wrote:
> Ingo Molnar wrote:
> >> diff --git a/arch/x86/Makefile_32.cpu b/arch/x86/Makefile_32.cpu
> >> index 80177ec..07a11b0 100644
> >> --- a/arch/x86/Makefile_32.cpu
> >> +++ b/arch/x86/Makefile_32.cpu
> >> @@ -33,6 +33,7 @@ cflags-$(CONFIG_MCYRIXIII) += $(call cc-option,-march=c3,-march=i486) $(align)-f
> >> cflags-$(CONFIG_MVIAC3_2) += $(call cc-option,-march=c3-2,-march=i686)
> >> cflags-$(CONFIG_MVIAC7) += -march=i686
> >> cflags-$(CONFIG_MCORE2) += -march=i686 $(call tune,core2)
> >> +cflags-$(CONFIG_MATOM) += -march=atom $(call tune,atom)
> >>
>
> There should be a fallback option used here rather than requiring a new
> gcc, e.g. something like:
>
> $(call cc-option,-march=atom,-march=i686)
if it's an in-order architecture, wouldn't it be better to tune for i386
or i486 instead ?
Willy
next prev parent reply other threads:[~2009-05-03 5:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 12:08 Specific support for Intel Atom architecture Tobias Doerffel
2009-04-30 15:40 ` Ingo Molnar
2009-04-30 17:03 ` H. Peter Anvin
2009-04-30 17:10 ` H. Peter Anvin
2009-05-03 5:38 ` Willy Tarreau [this message]
2009-05-03 6:48 ` H. Peter Anvin
2009-05-03 11:08 ` Tobias Doerffel
2009-05-04 13:14 ` Ingo Molnar
2009-05-04 13:32 ` Arjan van de Ven
2009-05-04 17:55 ` Ingo Molnar
2009-05-03 14:53 ` Arjan van de Ven
2009-05-03 18:30 ` Willy Tarreau
2009-05-03 18:37 ` H. Peter Anvin
2009-05-03 19:38 ` Måns Rullgård
2009-05-04 7:22 ` Andi Kleen
2009-05-11 21:30 ` Tobias Doerffel
2009-05-12 6:53 ` Andi Kleen
2009-05-12 14:20 ` Ulrich Drepper
2009-05-12 15:04 ` Andi Kleen
2009-05-12 17:45 ` Ulrich Drepper
2009-05-12 18:13 ` Andi Kleen
2009-05-14 5:04 ` Harvey Harrison
2009-05-14 13:38 ` Ulrich Drepper
2009-05-14 14:01 ` Andi Kleen
2009-05-14 16:19 ` Ulrich Drepper
2009-05-14 17:29 ` Andi Kleen
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=20090503053821.GI570@1wt.eu \
--to=w@1wt.eu \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tobias.doerffel@gmail.com \
--cc=venkatesh.pallipadi@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