All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Zhang, Austin" <austin.zhang@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	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: Wed, 27 Aug 2008 16:47:26 -0700	[thread overview]
Message-ID: <48B5E78E.9010007@zytor.com> (raw)
In-Reply-To: <9D7649D18729DE4BB2BD7B494F7FEDC201B96C98@pdsmsx415.ccr.corp.intel.com>

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.

	-hpa

  reply	other threads:[~2008-08-27 23:48 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 [this message]
2008-08-28  7:27           ` Ingo Molnar
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=48B5E78E.9010007@zytor.com \
    --to=hpa@zytor.com \
    --cc=austin.zhang@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.