From: Tony Lindgren <tony@atomide.com>
To: Stefan Agner <stefan@agner.ch>
Cc: nicolas.pitre@linaro.org, andrew@lunn.ch, mans@mansr.com,
robh@kernel.org, f.fainelli@gmail.com,
gregory.clement@bootlin.com, linux@armlinux.org.uk,
krzk@kernel.org, arm@kernel.org,
bcm-kernel-feedback-list@broadcom.com,
sebastian.hesselbarth@gmail.com, jason@lakedaemon.net,
arnd@arndb.de, marc.w.gonzalez@free.fr, rjui@broadcom.com,
ssantosh@kernel.org, linux-arm-kernel@lists.infradead.org,
sbranden@broadcom.com, ard.biesheuvel@linaro.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
kgene@kernel.org, robin.murphy@arm.com
Subject: Re: [PATCH v3 1/4] ARM: use arch_extension directive instead of arch argument
Date: Wed, 24 Apr 2019 07:12:17 -0700 [thread overview]
Message-ID: <20190424141217.GC8007@atomide.com> (raw)
In-Reply-To: <2f3d0fa7ba599f46960ad3e7419477fd@agner.ch>
* Stefan Agner <stefan@agner.ch> [190423 20:20]:
> On 11.04.2019 09:54, Stefan Agner wrote:
> > The LLVM Target parser currently does not allow to specify the security
> > extension as part of -march (see also LLVM Bug 40186 [0]). When trying
> > to use Clang with LLVM's integrated assembler, this leads to build
> > errors such as this:
> > clang-8: error: the clang compiler does not support '-Wa,-march=armv7-a+sec'
> >
> > Use ".arch_extension sec" to enable the security extension in a more
> > portable fasion. Also make sure to use ".arch armv7-a" in case a v6/v7
> > multi-platform kernel is being built.
> >
> > Note that this is technically not exactly the same as the old code
> > checked for availabilty of the security extension by calling as-instr.
> > However, there are already other sites which use ".arch_extension sec"
> > unconditionally, hence de-facto we need an assembler capable of
> > ".arch_extension sec" already today (arch/arm/mm/proc-v7.S). The
> > arch extension "sec" is available since binutils 2.21 according to
> > its documentation [1].
> >
> > [0] https://bugs.llvm.org/show_bug.cgi?id=40186
> > [1] https://sourceware.org/binutils/docs-2.21/as/ARM-Options.html
> >
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
> > Acked-by: Mans Rullgard <mans@mansr.com>
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
> > Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Arnd, Tony,
>
> Patch 3 and 4 got merged by Gregory. I think the other two patches are
> ready to be merged too. I think they should go in together to avoid
> merge conflicts. Tony, if you agree, can you Ack patch 2 so they can get
> merged through arm-soc?
Sure I just acked it for you.
Thanks,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-24 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 7:54 [PATCH v3 1/4] ARM: use arch_extension directive instead of arch argument Stefan Agner
2019-04-11 7:54 ` [PATCH v3 2/4] ARM: OMAP2: drop explicit assembler architecture Stefan Agner
2019-04-24 14:11 ` Tony Lindgren
2019-04-11 7:54 ` [PATCH v3 3/4] ARM: mvebu: drop unnecessary label Stefan Agner
2019-04-11 7:54 ` [PATCH v3 4/4] ARM: mvebu: prefix coprocessor operand with p Stefan Agner
2019-04-21 17:22 ` Gregory CLEMENT
2019-04-23 20:19 ` [PATCH v3 1/4] ARM: use arch_extension directive instead of arch argument Stefan Agner
2019-04-24 14:12 ` Tony Lindgren [this message]
2019-05-16 21:48 ` Olof Johansson
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=20190424141217.GC8007@atomide.com \
--to=tony@atomide.com \
--cc=andrew@lunn.ch \
--cc=ard.biesheuvel@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mans@mansr.com \
--cc=marc.w.gonzalez@free.fr \
--cc=ndesaulniers@google.com \
--cc=nicolas.pitre@linaro.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sbranden@broadcom.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ssantosh@kernel.org \
--cc=stefan@agner.ch \
/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).