From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Andy Lutomirski" <luto@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH 2/6] vDSO: Remove the dependency on HAVE_GENERIC_VDSO from ARCH_HAS_VDSO_ARCH_DATA
Date: Thu, 9 Jul 2026 10:28:39 +0100 [thread overview]
Message-ID: <86ee2905-4fa4-4f51-9d1d-6e404de320ed@arm.com> (raw)
In-Reply-To: <20260709-vdso-have_generic_vdso-v1-2-d2e1061f268b@linutronix.de>
On 09/07/2026 08:28, Thomas Weißschuh wrote:
> Align ARCH_HAS_VDSO_ARCH_DATA with ARCH_HAS_VDSO_TIME_DATA, making it
> selectable even without HAVE_GENERIC_VDSO.
>
> It will only have an effect when HAVE_GENERIC_VDSO is enabled anyways,
> but this make the architecture Kconfig files a bit simpler.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> ---
> arch/Kconfig | 1 -
> arch/riscv/Kconfig | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/Kconfig b/arch/Kconfig
> index fa7507ac8e13..8a8d1ab39757 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -1682,7 +1682,6 @@ config HAVE_SPARSE_SYSCALL_NR
> related optimizations for a given architecture.
>
> config ARCH_HAS_VDSO_ARCH_DATA
> - depends on HAVE_GENERIC_VDSO
> bool
>
> config ARCH_HAS_VDSO_TIME_DATA
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index 3f0a647218e4..353cbfcff783 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -54,7 +54,7 @@ config RISCV
> select ARCH_HAS_SYSCALL_WRAPPER
> select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
> select ARCH_HAS_UBSAN
> - select ARCH_HAS_VDSO_ARCH_DATA if HAVE_GENERIC_VDSO
> + select ARCH_HAS_VDSO_ARCH_DATA
> select ARCH_HAVE_NMI_SAFE_CMPXCHG
> select ARCH_KEEP_MEMBLOCK if ACPI || KEXEC
> select ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE if 64BIT && MMU
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2026-07-09 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:28 [PATCH 0/6] vDSO: Clean up the HAVE_GENERIC_VDSO kconfig symbol Thomas Weißschuh
2026-07-09 7:28 ` [PATCH 1/6] futex: Remove dependency on HAVE_GENERIC_VDSO from FUTEX_ROBUST_UNLOCK Thomas Weißschuh
2026-07-09 9:27 ` Vincenzo Frascino
2026-07-09 7:28 ` [PATCH 2/6] vDSO: Remove the dependency on HAVE_GENERIC_VDSO from ARCH_HAS_VDSO_ARCH_DATA Thomas Weißschuh
2026-07-09 9:28 ` Vincenzo Frascino [this message]
2026-07-09 7:28 ` [PATCH 3/6] MIPS: vdso: Stop using CONFIG_HAVE_GENERIC_VDSO Thomas Weißschuh
2026-07-09 9:29 ` Vincenzo Frascino
2026-07-09 7:28 ` [PATCH 4/6] vDSO: Automatically select HAVE_GENERIC_VDSO if necessary Thomas Weißschuh
2026-07-09 9:30 ` Vincenzo Frascino
2026-07-09 11:09 ` Philippe Mathieu-Daudé
2026-07-09 7:28 ` [PATCH 5/6] vDSO: Drop HAVE_GENERIC_VDSO from architecture kconfig files Thomas Weißschuh
2026-07-09 9:31 ` Vincenzo Frascino
2026-07-09 7:28 ` [PATCH 6/6] vDSO: Rename HAVE_GENERIC_VDSO to VDSO_DATASTORE Thomas Weißschuh
2026-07-09 9:31 ` Vincenzo Frascino
2026-07-09 11:10 ` Philippe Mathieu-Daudé
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=86ee2905-4fa4-4f51-9d1d-6e404de320ed@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/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