From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Zhang, Austin" <austin.zhang@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: manual merge of the crypto tree
Date: Thu, 28 Aug 2008 09:27:33 +0200 [thread overview]
Message-ID: <20080828072733.GE21875@elte.hu> (raw)
In-Reply-To: <48B5E78E.9010007@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> Zhang, Austin wrote:
>>>> new x86 feature bits should definitely show up in the x86 tree too
>> So can we add sse4.1 into this patch also as: #define
>> X86_FEATURE_XMM4_1 (4*32+19)
>> even though now no obvious user is asking it in kernel.
>
> The best would be to:
>
> 1. rename all the feature bits which have inconsistent names in their
> #defines and in /proc/cpuinfo;
> 2. generate the /proc/cpuinfo table
> (arch/x86/kernel/cpu/feature_names.c) automatically from
> cpufeature.h.
>
> 2. is quite trivial, and 1. can be done largely automatically. I will
> experiment with this.
i see you committed that into tip/x86/cpu - i just integrated that into
tip/master and pushed out the result. This way starting at v2.6.28 we'll
have only a single, non-redundant definition for CPU feature
information, from which we auto-generate the rest.
Ingo
next prev parent reply other threads:[~2008-08-28 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 3:35 linux-next: manual merge of the crypto tree Stephen Rothwell
2008-08-07 3:43 ` Herbert Xu
2008-08-25 6:44 ` Stephen Rothwell
2008-08-25 6:53 ` Stephen Rothwell
2008-08-25 6:55 ` Herbert Xu
2008-08-25 7:39 ` Ingo Molnar
2008-08-25 8:05 ` Zhang, Austin
2008-08-27 23:47 ` H. Peter Anvin
2008-08-28 7:27 ` Ingo Molnar [this message]
2008-08-28 17:52 ` H. Peter Anvin
2008-08-28 7:28 ` Ingo Molnar
2008-08-28 7:33 ` Herbert Xu
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=20080828072733.GE21875@elte.hu \
--to=mingo@elte.hu \
--cc=austin.zhang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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).