From: Arjan van de Ven <arjan@linux.intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Tobias Doerffel <tobias.doerffel@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Kelly Bowa <kelly.bowa@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Atom processor inclusion
Date: Fri, 21 Aug 2009 11:23:02 -0700 [thread overview]
Message-ID: <4A8EE606.7000807@linux.intel.com> (raw)
In-Reply-To: <4A8EE544.6020002@zytor.com>
H. Peter Anvin wrote:
> On 08/20/2009 05:33 AM, Tobias Doerffel wrote:
>> Hi,
>>
>> Am Donnerstag, 20. August 2009 12:50:29 schrieb Ingo Molnar:
>>> Yep, it looked acceptable - Tobias, do you have any
>>> updates / latest version of that patch?
>> No - it's still the improved version I posted at the end of May [1]. The
>> question is what to do with MODULE_PROC_FAMILY (CORE2 or ATOM) and the mtune-
>> fallback (generic, i686, ...)?
>>
>
> Without benchmarks, we're flying blind on that one... although in
> general, "generic" is probably best in the sense that it doesn't imply
> that anything else has been done to it.
>
> As far as MODULE_PROC_FAMILY it really comes down to if we use movbe or
> not, which I don't believe your patch does. On the other hand, I really
> think it's extremely unlikely that anyone will use modules compiled for
> a different CPU, so I'm personally fine with changing that string.
>
> That whole mechanism is kind of broken, anyway.
>
personally, I would prefer it if we did a simple hash of the WHOLE cflags,
and put that into the module version string.
Anything else is just a weak, and useless, substitute for that.
Using different CFLAGS in any shape or form should disqualify the module
as "incompatible".. and a simple hash is sufficient for that.....
next prev parent reply other threads:[~2009-08-21 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 1:06 Atom processor inclusion Kelly Bowa
2009-08-20 10:50 ` Ingo Molnar
2009-08-20 12:33 ` Tobias Doerffel
2009-08-21 18:19 ` H. Peter Anvin
2009-08-21 18:23 ` Arjan van de Ven [this message]
2009-08-21 19:38 ` Ingo Molnar
2009-08-21 20:33 ` H. Peter Anvin
2009-08-21 20:36 ` Ingo Molnar
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=4A8EE606.7000807@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kelly.bowa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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