From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Explicitly build no BTI tests with BTI disabled
Date: Mon, 16 May 2022 19:09:36 +0100 [thread overview]
Message-ID: <YoKTYFtXMsZW/+Iq@arm.com> (raw)
In-Reply-To: <20220511161004.189348-1-broonie@kernel.org>
On Wed, May 11, 2022 at 05:10:04PM +0100, Mark Brown wrote:
> In case a distribution enables branch protection by default do as we do for
> the main kernel and explicitly disable branch protection when building the
> test case for having BTI disabled to ensure it doesn't get turned on by the
> toolchain defaults.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> tools/testing/selftests/arm64/bti/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/arm64/bti/Makefile b/tools/testing/selftests/arm64/bti/Makefile
> index 10a12c5e05e6..a3e59d7910b3 100644
> --- a/tools/testing/selftests/arm64/bti/Makefile
> +++ b/tools/testing/selftests/arm64/bti/Makefile
> @@ -14,7 +14,7 @@ CFLAGS += -I../../../../../usr/include/
>
> CFLAGS_STATIC = -ffreestanding
>
> -CFLAGS_NOBTI = -DBTI=0
> +CFLAGS_NOBTI = -mbranch-protection=none -DBTI=0
> CFLAGS_BTI = -mbranch-protection=standard -DBTI=1
Do I miss an patches? I can't see the CFLAGS_STATIC in the arm64
branches, nor in next.
--
Catalin
next prev parent reply other threads:[~2022-05-16 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 16:10 [PATCH] kselftest/arm64: Explicitly build no BTI tests with BTI disabled Mark Brown
2022-05-16 18:09 ` Catalin Marinas [this message]
2022-05-16 18:13 ` Mark Brown
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=YoKTYFtXMsZW/+Iq@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--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