From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
clang-built-linux@googlegroups.com, samitolvanen@google.com,
amit.kachhap@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: lse: Fix LSE atomics with LLVM
Date: Tue, 18 Feb 2020 17:42:59 +0000 [thread overview]
Message-ID: <b6bffd75-12fa-b91d-428e-2bf927636161@arm.com> (raw)
In-Reply-To: <20200218165451.GE1133@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 3337 bytes --]
Hi Will,
On 18/02/2020 16:54, Will Deacon wrote:
> [+Sami]
>
Thanks for this, I forgot to add Sami in Cc.
> On Tue, Feb 18, 2020 at 04:49:06PM +0000, Vincenzo Frascino wrote:
>> The introduction of the commit e0d5896bd356cd broke the compilation of
>> the kernel when the selected compiler is clang and it is used in
>> combination with "-no-integrated-as".
>
> Curious, but have you tested this change with the integrated assembler as
> well?
>
The integrated assembler as far as I am aware cannot assemble the kernel for
reasons independent from lse (AS=clang generates a lot of errors). Not sure how
Sami is testing it. I would be happy to learn it myself.
The default option for clang in the kernel Makefile is "-no-integrated-as"
though hence e0d5896bd356cd introduces a regression.
>> This happens because __LSE_PREAMBLE is defined as ".arch armv8-a+lse"
>> and this overrides the version of the architecture passed via -march
>> command line to the gas compiler.
>>
>> The issue was noticed during the development of pauth on arm64 and an
>> error example is reported below:
>>
>> $ aarch64-none-linux-gnu-as -EL -I ./arch/arm64/include
>> -I ./arch/arm64/include/generated
>> -I ./include -I ./include
>> -I ./arch/arm64/include/uapi
>> -I ./arch/arm64/include/generated/uapi
>> -I ./include/uapi -I ./include/generated/uapi
>> -I ./init -I ./init
>> -march=armv8.3-a -o init/do_mounts.o
>> /tmp/do_mounts-d7992a.s
>> /tmp/do_mounts-d7992a.s: Assembler messages:
>> /tmp/do_mounts-d7992a.s:1959: Error: selected processor does not support `autiasp'
>> /tmp/do_mounts-d7992a.s:2021: Error: selected processor does not support `paciasp'
>> /tmp/do_mounts-d7992a.s:2157: Error: selected processor does not support `autiasp'
>> /tmp/do_mounts-d7992a.s:2175: Error: selected processor does not support `paciasp'
>> /tmp/do_mounts-d7992a.s:2494: Error: selected processor does not support `autiasp'
>>
>> Fix the issue replacing ".arch armv8-a+lse" with ".arch_extension lse" that does
>> not override the command line parameter.
>>
>> Fixes: e0d5896bd356cd ("arm64: lse: fix LSE atomics with LLVM's integrated assembler")
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Reported-by: Amit Kachhap <Amit.Kachhap@arm.com>
>> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
>> ---
>> arch/arm64/include/asm/lse.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/include/asm/lse.h b/arch/arm64/include/asm/lse.h
>> index d429f7701c36..5d10051c3e62 100644
>> --- a/arch/arm64/include/asm/lse.h
>> +++ b/arch/arm64/include/asm/lse.h
>> @@ -6,7 +6,7 @@
>>
>> #ifdef CONFIG_ARM64_LSE_ATOMICS
>>
>> -#define __LSE_PREAMBLE ".arch armv8-a+lse\n"
>> +#define __LSE_PREAMBLE ".arch_extension lse\n"
>
> I'm ok with this, but Sami assumedly changed this for a reason in
> e0d5896bd356cd ("arm64: lse: fix LSE atomics with LLVM's integrated
> assembler").
>
> Sami?
>
> Will
>
--
Regards,
Vincenzo
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 14291 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2020-02-18 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 16:49 [PATCH] arm64: lse: Fix LSE atomics with LLVM Vincenzo Frascino
2020-02-18 16:54 ` Will Deacon
2020-02-18 17:42 ` Vincenzo Frascino [this message]
2020-02-18 18:03 ` Sami Tolvanen
2020-02-18 18:02 ` Sami Tolvanen
2020-02-18 18:05 ` Will Deacon
2020-02-18 18:11 ` Vincenzo Frascino
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=b6bffd75-12fa-b91d-428e-2bf927636161@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=amit.kachhap@arm.com \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=samitolvanen@google.com \
--cc=will.deacon@arm.com \
--cc=will@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