[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <cd172d05-15f6-427c-b6e3-d68fc746b940@app.fastmail.com>
Date: Mon, 22 Apr 2024 11:25:25 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Mark Rutland" <mark.rutland@....com>,
"Naresh Kamboju" <naresh.kamboju@...aro.org>
Cc: "open list" <linux-kernel@...r.kernel.org>,
"Linux ARM" <linux-arm-kernel@...ts.infradead.org>,
lkft-triage@...ts.linaro.org,
"Linux Regressions" <regressions@...ts.linux.dev>,
"Anders Roxell" <anders.roxell@...aro.org>, "Marc Zyngier" <maz@...nel.org>,
joey.gouly@....com, "Oliver Upton" <oliver.upton@...ux.dev>
Subject: Re: gcc-8: arm64/kvm/pauth.: Error: unknown architectural extension `pauth'
On Mon, Apr 22, 2024, at 11:13, Mark Rutland wrote:
> On Mon, Apr 22, 2024 at 02:04:43PM +0530, Naresh Kamboju wrote:
> Given the minimum supported toolchain comes with an assembler that doesn't
> necessarily support ARMv8.3, I reckon we'll either have to make NV pauth
> support depend upon AS_HAS_ARMV8_3, or manually assemble the PACGA instruction.
>
> I suspect the latter is the better option.
The .config linked from the report shows
CONFIG_AS_VERSION=23101
CONFIG_ARM64_PTR_AUTH_KERNEL=y
CONFIG_AS_HAS_ARMV8_3=y
So it gets detected as supporting ARMv8.3. Is this the wrong
conditional to check, or does it get misdetected for an unsupported
assembler?
Arnd
Powered by blists - more mailing lists