From: "tip-bot2 for Masahiro Yamada" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/vdso] x86/vdso: Simplify obj-y addition
Date: Thu, 08 Feb 2024 13:04:40 -0000 [thread overview]
Message-ID: <170739748071.398.15183510010318290284.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231121235701.239606-3-masahiroy@kernel.org>
The following commit has been merged into the x86/vdso branch of tip:
Commit-ID: 329b77b59f83440e98d792800501e5a398806860
Gitweb: https://git.kernel.org/tip/329b77b59f83440e98d792800501e5a398806860
Author: Masahiro Yamada <masahiroy@kernel.org>
AuthorDate: Wed, 22 Nov 2023 08:56:59 +09:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Thu, 08 Feb 2024 13:22:08 +01:00
x86/vdso: Simplify obj-y addition
Add objects to obj-y in a more straightforward way.
CONFIG_X86_32 and CONFIG_IA32_EMULATION are not enabled simultaneously,
but even if they are, Kbuild graciously deduplicates obj-y entries.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20231121235701.239606-3-masahiroy@kernel.org
---
arch/x86/entry/vdso/Makefile | 16 ++++------------
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/arch/x86/entry/vdso/Makefile b/arch/x86/entry/vdso/Makefile
index 2038d9c..cbfb5aa 100644
--- a/arch/x86/entry/vdso/Makefile
+++ b/arch/x86/entry/vdso/Makefile
@@ -18,11 +18,6 @@ OBJECT_FILES_NON_STANDARD := y
# Prevents link failures: __sanitizer_cov_trace_pc() is not linked in.
KCOV_INSTRUMENT := n
-VDSO64-$(CONFIG_X86_64) := y
-VDSOX32-$(CONFIG_X86_X32_ABI) := y
-VDSO32-$(CONFIG_X86_32) := y
-VDSO32-$(CONFIG_IA32_EMULATION) := y
-
# files to link into the vdso
vobjs-y := vdso-note.o vclock_gettime.o vgetcpu.o
vobjs32-y := vdso32/note.o vdso32/system_call.o vdso32/sigreturn.o
@@ -38,11 +33,11 @@ OBJECT_FILES_NON_STANDARD_vma.o := n
OBJECT_FILES_NON_STANDARD_extable.o := n
# vDSO images to build
-vdso_img-$(VDSO64-y) += 64
-vdso_img-$(VDSOX32-y) += x32
-vdso_img-$(VDSO32-y) += 32
+obj-$(CONFIG_X86_64) += vdso-image-64.o
+obj-$(CONFIG_X86_X32_ABI) += vdso-image-x32.o
+obj-$(CONFIG_X86_32) += vdso-image-32.o vdso32-setup.o
+obj-$(CONFIG_IA32_EMULATION) += vdso-image-32.o vdso32-setup.o
-obj-$(VDSO32-y) += vdso32-setup.o
OBJECT_FILES_NON_STANDARD_vdso32-setup.o := n
vobjs := $(foreach F,$(vobjs-y),$(obj)/$F)
@@ -53,9 +48,6 @@ $(obj)/vdso.o: $(obj)/vdso.so
targets += vdso.lds $(vobjs-y)
targets += vdso32/vdso32.lds $(vobjs32-y)
-# Build the vDSO image C files and link them in.
-vdso_img_objs := $(vdso_img-y:%=vdso-image-%.o)
-obj-y += $(vdso_img_objs)
targets += $(foreach x, 64 x32 32, vdso-image-$(x).c vdso$(x).so vdso$(x).so.dbg)
CPPFLAGS_vdso.lds += -P -C
next prev parent reply other threads:[~2024-02-08 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 23:56 [PATCH 0/4] x86: vdso: clean up vdso Makefile Masahiro Yamada
2023-11-21 23:56 ` [PATCH 1/4] x86: vdso: consolidate targets and clean-files Masahiro Yamada
2024-02-08 13:04 ` [tip: x86/vdso] x86/vdso: Consolidate " tip-bot2 for Masahiro Yamada
2023-11-21 23:56 ` [PATCH 2/4] x86: vdso: simplify obj-y addition Masahiro Yamada
2024-02-08 13:04 ` tip-bot2 for Masahiro Yamada [this message]
2023-11-21 23:57 ` [PATCH 3/4] x86: vdso: use $(addprefix ) instead of $(foreach ) Masahiro Yamada
2024-02-08 13:04 ` [tip: x86/vdso] x86/vdso: Use " tip-bot2 for Masahiro Yamada
2023-11-21 23:57 ` [PATCH 4/4] x86: vdso: use CONFIG_COMPAT_32 to specify vdso32 Masahiro Yamada
2024-02-08 13:04 ` [tip: x86/vdso] x86/vdso: Use " tip-bot2 for Masahiro Yamada
2024-02-02 15:56 ` [PATCH 0/4] x86: vdso: clean up vdso Makefile Masahiro Yamada
2024-02-07 8:24 ` Borislav Petkov
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=170739748071.398.15183510010318290284.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=masahiroy@kernel.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
all inboxes | Powered by JetHome®