All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Michael Lothian <mike@fireburn.co.uk>,
	Gabriel C <nix.or.die@googlemail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Possibility of adding -march=native to x86
Date: Thu, 25 Oct 2007 15:04:26 -0700	[thread overview]
Message-ID: <472112EA.3020604@zytor.com> (raw)
In-Reply-To: <20071025214647.GX30533@stusta.de>

Adrian Bunk wrote:
>>>
>> Yes for something like a distro kernel it is bad but as I said before
>> this isn't what this is for.
>>
>> Eventually it would be nice to to a make localkernel and for a
>> customised kernel to be build compiling in all pci / pci express
>> drivers into the kernel and all usb devices as modules.
>>
>> Auto magically detecting the cpu would be part of that
>>
>> I hate getting a new piece of kit and then have to figure out from
>> lspci which options need to be turned on and the the really iritation
>> part of finding the option in make menuconfig
> 
> What exactly is irritating?
> Please name the problems so that they can be fixed.
> 
>> Detecting the cpu and using march=native could be all part of that
> 
> You don't need march=native for this.
> 
> You have to set the right config option for your CPU and you 
> automatically get the right compiler options.
> 

There was a long discussion years ago -- the infamous "Aunt Tillie" 
thread -- about automatically configuring customized kernels for 
specific hardware.

It's somewhat of an unusual thing to bother with these days, except for 
people who develop and maintain the kernel.

	-hpa

  reply	other threads:[~2007-10-25 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0EC33A59AA72084CA28B83816B40929F02682BB3@REEDXCLSXM01V03.rbsres01.net>
2007-10-25 18:33 ` Possibility of adding -march=native to x86 Michael Lothian
2007-10-25 18:50   ` Adrian Bunk
2007-10-25 19:09     ` Michael Lothian
2007-10-25 19:17       ` Adrian Bunk
2007-10-25 19:32         ` Michael Lothian
2007-10-25 19:50           ` Adrian Bunk
2007-10-25 20:12             ` Michael Lothian
2007-10-25 20:20               ` Adrian Bunk
2007-10-25 20:20                 ` Arjan van de Ven
2007-10-26 10:41                 ` Pádraig Brady
2007-10-26 11:45                   ` Adrian Bunk
2007-10-25 20:40               ` Gabriel C
2007-10-25 21:30                 ` Michael Lothian
2007-10-25 21:46                   ` Adrian Bunk
2007-10-25 22:04                     ` H. Peter Anvin [this message]
2007-10-25 22:42                     ` Michael Lothian
2007-10-25 22:58                       ` Adrian Bunk
     [not found]                     ` <fc94aae90710251518l1cc129eahf570177e5b516197@mail.gmail.com>
     [not found]                       ` <20071025222826.GY30533@stusta.de>
2007-10-25 22:58                         ` Michael Lothian
2007-10-26  9:16   ` Thomas Gleixner

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=472112EA.3020604@zytor.com \
    --to=hpa@zytor.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@fireburn.co.uk \
    --cc=nix.or.die@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.