From: WANG Rui <r@hev.cc>
To: Huacai Chen <chenhuacai@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
loongarch@lists.linux.dev, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, WANG Rui <r@hev.cc>
Subject: [RFC PATCH 1/3] LoongArch: Allow rdtime_h and rdtime_l in 64-bit builds
Date: Sun, 26 Apr 2026 20:02:29 +0800 [thread overview]
Message-ID: <20260426120231.532644-2-r@hev.cc> (raw)
In-Reply-To: <20260426120231.532644-1-r@hev.cc>
Remove the CONFIG_32BIT guard around rdtime_h() and rdtime_l()
so they can also be used in 64-bit builds.
Signed-off-by: WANG Rui <r@hev.cc>
---
arch/loongarch/include/asm/loongarch.h | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/loongarch/include/asm/loongarch.h b/arch/loongarch/include/asm/loongarch.h
index 2a6bc99177d8..bb2da9c58411 100644
--- a/arch/loongarch/include/asm/loongarch.h
+++ b/arch/loongarch/include/asm/loongarch.h
@@ -1248,8 +1248,6 @@
#ifndef __ASSEMBLER__
-#ifdef CONFIG_32BIT
-
static __always_inline u32 rdtime_h(void)
{
u32 val = 0;
@@ -1274,8 +1272,6 @@ static __always_inline u32 rdtime_l(void)
return val;
}
-#else
-
static __always_inline u64 rdtime_d(void)
{
u64 val = 0;
@@ -1288,8 +1284,6 @@ static __always_inline u64 rdtime_d(void)
return val;
}
-#endif
-
static inline unsigned int get_csr_cpuid(void)
{
return csr_read32(LOONGARCH_CSR_CPUID);
--
2.54.0
next prev parent reply other threads:[~2026-04-26 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 12:02 [RFC PATCH 0/3] LoongArch: Move KASLR to EFI stub to avoid initrd overlap WANG Rui
2026-04-26 12:02 ` WANG Rui [this message]
2026-04-26 12:02 ` [RFC PATCH 2/3] efi/loongarch: Randomize kernel preferred address for KASLR WANG Rui
2026-04-27 5:07 ` Lisa Robinson
2026-04-27 7:49 ` hev
2026-04-26 12:02 ` [RFC PATCH 3/3] LoongArch: Remove KASLR handling from relocate_kernel WANG Rui
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=20260426120231.532644-2-r@hev.cc \
--to=r@hev.cc \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kernel@xen0n.name \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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