All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	james.t.kukunas@linux.intel.com, neilb@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/raid6: correctly check for assembler capabilities
Date: Tue, 03 Feb 2015 21:31:30 +0100	[thread overview]
Message-ID: <1422995490.23894.32.camel@x220> (raw)
In-Reply-To: <54C2148E02000078000588FB@mail.emea.novell.com>

On Fri, 2015-01-23 at 08:29 +0000, Jan Beulich wrote:
> Just like for AVX2 (which simply needs an #if -> #ifdef conversion),
> SSSE3 assembler support should be checked for before using it.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Jim Kukunas <james.t.kukunas@linux.intel.com>
> Cc: Neil Brown <neilb@suse.de>

This patch became commit be46ac86a81b ("x86/raid6: correctly check for
assembler capabilities") in today's linux-next (ie, next-20150203). I
noticed because a script I use to check linux-next spotted a potential
problem with it.

> ---
>  arch/x86/Makefile       |    1 +
>  lib/raid6/algos.c       |    2 +-
>  lib/raid6/recov_avx2.c  |    2 +-
>  lib/raid6/recov_ssse3.c |    6 ++++++
>  4 files changed, 9 insertions(+), 2 deletions(-)
> 
> --- 3.19-rc5/arch/x86/Makefile
> +++ 3.19-rc5-raid6-SSSE3/arch/x86/Makefile
> @@ -148,6 +148,7 @@ cfi-sections := $(call as-instr,.cfi_sec
>  
>  # does binutils support specific instructions?
>  asinstr := $(call as-instr,fxsaveq (%rax),-DCONFIG_AS_FXSAVEQ=1)
> +asinstr += $(call as-instr,pshufb %xmm0$(comma)%xmm0,-DCONFIG_AS_SSSE3=1)

This Makefile defines a preprocessor macro with a CONFIG_ prefix. Almost
all macros with that prefix are defined through the kconfig system. A
handful, like CONFIG_AS_SSSE3 and a few other macros defined in this
Makefile, are not. Apparently this is a pet peeve I share with few
people, but would any other prefix than CONFIG_ work for you too?

>  asinstr += $(call as-instr,crc32l %eax$(comma)%eax,-DCONFIG_AS_CRC32=1)
>  avx_instr := $(call as-instr,vxorps %ymm0$(comma)%ymm1$(comma)%ymm2,-DCONFIG_AS_AVX=1)
>  avx2_instr :=$(call as-instr,vpbroadcastb %xmm0$(comma)%ymm1,-DCONFIG_AS_AVX2=1)


Paul Bolle


  parent reply	other threads:[~2015-02-03 20:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  8:29 [PATCH] x86/raid6: correctly check for assembler capabilities Jan Beulich
2015-01-23 16:16 ` Thomas Gleixner
2015-01-28  5:02   ` NeilBrown
2015-02-03 20:31 ` Paul Bolle [this message]
2015-02-03 20:50   ` NeilBrown
2015-02-03 21:03     ` Paul Bolle
2015-02-03 21:09       ` NeilBrown
2015-02-03 21:24         ` Valentin Rothberg
2015-02-04  7:51       ` Jan Beulich
2015-06-16 19:46       ` H. Peter Anvin
2015-06-16 19:56         ` Paul Bolle
2015-06-16 20:05           ` H. Peter Anvin
2015-06-16 20:37             ` Paul Bolle
2015-06-16 20:42               ` H. Peter Anvin
2015-06-16 20:51                 ` Paul Bolle

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=1422995490.23894.32.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=JBeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=james.t.kukunas@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=neilb@suse.de \
    --cc=tglx@linutronix.de \
    --cc=valentinrothberg@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 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.