From: Dave Hansen <dave@sr71.net>
To: Borislav Petkov <bp@alien8.de>
Cc: dave.hansen@linux.intel.com, mingo@redhat.com, x86@kernel.org,
fenghua.yu@intel.com, tim.c.chen@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/11] x86, fpu: rename xfeature_bit
Date: Wed, 26 Aug 2015 09:10:09 -0700 [thread overview]
Message-ID: <55DDE4E1.3090203@sr71.net> (raw)
In-Reply-To: <20150826160627.GB7508@nazgul.tnic>
On 08/26/2015 09:06 AM, Borislav Petkov wrote:
>> > -enum xfeature_bit {
>> > - XSTATE_BIT_FP,
>> > - XSTATE_BIT_SSE,
>> > - XSTATE_BIT_YMM,
>> > - XSTATE_BIT_BNDREGS,
>> > - XSTATE_BIT_BNDCSR,
>> > - XSTATE_BIT_OPMASK,
>> > - XSTATE_BIT_ZMM_Hi256,
>> > - XSTATE_BIT_Hi16_ZMM,
>> > +enum xfeature_nr {
>> > + XFEATURE_NR_FP,
>> > + XFEATURE_NR_SSE,
>> > + /*
>> > + * Values above here are "legacy states".
>> > + * Those below are "extended states".
>> > + */
>> > + XFEATURE_NR_YMM,
>> > + XFEATURE_NR_BNDREGS,
>> > + XFEATURE_NR_BNDCSR,
>> > + XFEATURE_NR_OPMASK,
>> > + XFEATURE_NR_ZMM_Hi256,
>> > + XFEATURE_NR_Hi16_ZMM,
> Why not simply
>
> s/NR_//
>
> ?
>
> I.e., XFEATURE_FP, XFEATURE_SSE and so on...
I wanted to differentiate them from the
#define XSTATE_FP (1 << XSTATE_BIT_FP)
#define XSTATE_SSE (1 << XSTATE_BIT_SSE)
defines below. Those are really XFEATURE_MASK_... I think this gets a
lots more clear if you have a pair of #defines like:
XFEATURE_NR_BNDREGS
XFEATURE_MASK_BNDREGS
It's pretty obvious what's going on there. What we have now is
XSTATE_BIT_BNDREGS
XSTATE_BNDREGS
which I find much less clear.
next prev parent reply other threads:[~2015-08-26 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 20:12 [PATCH 00/11] x86, fpu: XSAVE cleanups and sanity checks Dave Hansen
2015-08-25 20:12 ` [PATCH 01/11] x86, fpu: kill LWP support Dave Hansen
2015-08-25 20:12 ` [PATCH 02/11] x86, fpu: rename xfeature_bit Dave Hansen
2015-08-26 16:06 ` Borislav Petkov
2015-08-26 16:10 ` Dave Hansen [this message]
2015-08-25 20:12 ` [PATCH 03/11] x86, fpu: rework XSTATE_* macros to remove magic '2' Dave Hansen
2015-08-25 20:12 ` [PATCH 04/11] x86, fpu: remove xfeature_nr Dave Hansen
2015-08-25 20:12 ` [PATCH 07/11] x86, fpu: rework YMM definition Dave Hansen
2015-08-25 20:12 ` [PATCH 05/11] x86, fpu: add helper xfeature_nr_enabled() instead of test_bit() Dave Hansen
2015-08-25 20:12 ` [PATCH 06/11] x86, fpu: rework MPX 'xstate' types Dave Hansen
2015-08-25 20:12 ` [PATCH 09/11] x86, fpu: correct and check XSAVE xstate size calculations Dave Hansen
2015-08-25 20:12 ` [PATCH 08/11] x86, fpu: add C structures for AVX-512 state components Dave Hansen
2015-08-25 20:12 ` [PATCH 11/11] x86, fpu: check CPU-provided sizes against struct declarations Dave Hansen
2015-08-26 16:18 ` Tim Chen
2015-08-26 16:19 ` Dave Hansen
2015-08-25 20:12 ` [PATCH 10/11] x86, fpu: check to ensure increasing-offset xstate offsets Dave Hansen
2015-08-27 17:11 [PATCH 00/11] [v2] x86, fpu: XSAVE cleanups and sanity checks Dave Hansen
2015-08-27 17:11 ` [PATCH 02/11] x86, fpu: rename xfeature_bit Dave Hansen
2015-08-28 5:16 ` 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=55DDE4E1.3090203@sr71.net \
--to=dave@sr71.net \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@kernel.org \
/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
Powered by JetHome