From: Uros Bizjak <ubizjak@gmail.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Uros Bizjak <ubizjak@gmail.com>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Nadav Amit <namit@vmware.com>, Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: [RFC PATCH 2/4] x86/percpu: Detect compiler support for named address spaces
Date: Sun, 1 Oct 2023 15:14:34 +0200 [thread overview]
Message-ID: <20231001131620.112484-3-ubizjak@gmail.com> (raw)
In-Reply-To: <20231001131620.112484-1-ubizjak@gmail.com>
Detect compiler support for named address spaces by trying
to compile a small testcase that includes __seg_gs and __seg_gs
keywords. Reflect successful compilation in CC_HAS_NAMED_AS
and set USE_X86_SEG_SUPPORT to signal when segment qualifiers
should be used.
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Nadav Amit <namit@vmware.com>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
---
arch/x86/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 66bfabae8814..f66fa5bf1f78 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2388,6 +2388,13 @@ source "kernel/livepatch/Kconfig"
endmenu
+config CC_HAS_NAMED_AS
+ def_bool $(success,echo 'int __seg_fs fs; int __seg_gs gs;' | $(CC) -x c - -c -o /dev/null)
+
+config USE_X86_SEG_SUPPORT
+ def_bool y
+ depends on CC_HAS_NAMED_AS && SMP
+
config CC_HAS_SLS
def_bool $(cc-option,-mharden-sls=all)
--
2.41.0
next prev parent reply other threads:[~2023-10-01 13:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 13:14 [RFC PATCH 0/4] x86/percpu: Use segment qualifiers Uros Bizjak
2023-10-01 13:14 ` [RFC PATCH 1/4] x86/percpu: Update arch/x86/include/asm/percpu.h to the current tip Uros Bizjak
2023-10-01 13:14 ` Uros Bizjak [this message]
2023-10-01 13:14 ` [RFC PATCH 3/4] x86/percpu: Use compiler segment prefix qualifier Uros Bizjak
2023-10-01 13:14 ` [RFC PATCH 4/4] x86/percpu: Use C for percpu read/write accessors Uros Bizjak
2023-10-01 17:07 ` [RFC PATCH 0/4] x86/percpu: Use segment qualifiers Linus Torvalds
2023-10-01 19:53 ` Uros Bizjak
2023-10-01 20:21 ` Linus Torvalds
2023-10-01 20:30 ` Linus Torvalds
2023-10-01 21:47 ` Uros Bizjak
2023-10-02 12:13 ` Uros Bizjak
2023-10-02 13:22 ` Ingo Molnar
2023-10-03 9:49 ` Uros Bizjak
2023-10-03 13:38 ` Ingo Molnar
2023-10-03 19:31 ` Linus Torvalds
2023-10-03 19:43 ` Ingo Molnar
2023-10-03 21:43 ` Linus Torvalds
2023-10-04 6:01 ` Uros Bizjak
2025-04-29 16:31 ` Uros Bizjak
2025-04-29 16:49 ` Linus Torvalds
2025-04-29 17:05 ` Uros Bizjak
2025-04-29 17:44 ` Linus Torvalds
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=20231001131620.112484-3-ubizjak@gmail.com \
--to=ubizjak@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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