From: Uros Bizjak <ubizjak@gmail.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Uros Bizjak <ubizjak@gmail.com>,
kernel test robot <lkp@intel.com>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH -tip v3 3/3] x86/percpu: Avoid sparse warning with cast to named address space
Date: Mon, 4 Dec 2023 22:02:31 +0100 [thread overview]
Message-ID: <20231204210320.114429-3-ubizjak@gmail.com> (raw)
In-Reply-To: <20231204210320.114429-1-ubizjak@gmail.com>
Teach sparse about __seg_fs and __seg_gs named address space
qualifiers to to avoid warnings about unexpected keyword at
the end of cast operator.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202310080853.UhMe5iWa-lkp@intel.com/
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
---
v3: Teach sparse about __seg_gs and __seg_fs qualifiers instead
of removing these qualifiers when __CHECKER__ is defined.
---
arch/x86/include/asm/percpu.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/x86/include/asm/percpu.h b/arch/x86/include/asm/percpu.h
index 3859abad19ec..e56a37886143 100644
--- a/arch/x86/include/asm/percpu.h
+++ b/arch/x86/include/asm/percpu.h
@@ -36,6 +36,11 @@
#ifdef CONFIG_CC_HAS_NAMED_AS
+#ifdef __CHECKER__
+#define __seg_gs __attribute__((address_space(__seg_gs)))
+#define __seg_fs __attribute__((address_space(__seg_fs)))
+#endif
+
#ifdef CONFIG_X86_64
#define __percpu_seg_override __seg_gs
#else
--
2.42.0
next prev parent reply other threads:[~2023-12-04 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 21:02 [PATCH -tip v3 1/3] x86/percpu: Fix "const_pcpu_hot" version generation failure Uros Bizjak
2023-12-04 21:02 ` [PATCH -tip v3 2/3] x86/traps: Use current_top_of_stack() helper in traps.c Uros Bizjak
2023-12-11 12:06 ` [tip: x86/percpu] " tip-bot2 for Uros Bizjak
2023-12-04 21:02 ` Uros Bizjak [this message]
2023-12-05 0:21 ` [PATCH -tip v3 3/3] x86/percpu: Avoid sparse warning with cast to named address space Luc Van Oostenryck
2023-12-11 12:06 ` [tip: x86/percpu] " tip-bot2 for Uros Bizjak
2023-12-11 12:06 ` [tip: x86/percpu] x86/percpu: Fix "const_pcpu_hot" version generation failure tip-bot2 for Uros Bizjak
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=20231204210320.114429-3-ubizjak@gmail.com \
--to=ubizjak@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).