public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Tobias Doerffel <tobias.doerffel@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: add specific support for Intel Atom architecture
Date: Mon, 01 Jun 2009 10:15:24 +0200	[thread overview]
Message-ID: <87r5y4cqub.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1243638699-15194-1-git-send-email-tobias.doerffel@gmail.com> (Tobias Doerffel's message of "Sat, 30 May 2009 01:11:39 +0200")

Tobias Doerffel <tobias.doerffel@gmail.com> writes:

> This adds another option when selecting CPU family so the kernel can
> be optimized for Intel Atom CPUs. If GCC supports tuning options for
> Intel Atom they will be used.

You seem to have ignored the earlier review feedback?

Like

> diff --git a/arch/x86/include/asm/module.h b/arch/x86/include/asm/module.h
> index 47d6274..e959c4a 100644
> --- a/arch/x86/include/asm/module.h
> +++ b/arch/x86/include/asm/module.h
> @@ -28,6 +28,8 @@ struct mod_arch_specific {};
>  #define MODULE_PROC_FAMILY "586MMX "
>  #elif defined CONFIG_MCORE2
>  #define MODULE_PROC_FAMILY "CORE2 "
> +#elif defined CONFIG_MATOM
> +#define MODULE_PROC_FAMILY "ATOM "

This is not needed because Atom is compatible to CORE2 (except for
one instruction the kernel doesn't use)

+	cflags-$(CONFIG_MATOM) += $(call cc-option,-march=atom) \
+		$(call cc-option,-mtune=atom,$(call cc-option,-mtune=generic))

It's doubtful that tune=generic is the best fallback for Atom, likely
tune=p5 is better


-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2009-06-01  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 23:11 [PATCH] x86: add specific support for Intel Atom architecture Tobias Doerffel
2009-06-01  8:15 ` Andi Kleen [this message]
2009-06-01  8:48   ` Tobias Doerffel
2009-08-21 20:36 ` H. Peter Anvin
2009-08-21 21:06   ` Tobias Doerffel

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=87r5y4cqub.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias.doerffel@gmail.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