From: Ingo Molnar <mingo@kernel.org>
To: Li kunyu <kunyu@nfschina.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/boot/arch/variable: I don't think (void *) Pointers need to be cast
Date: Wed, 3 Aug 2022 11:33:42 +0200 [thread overview]
Message-ID: <YupA9iqo4PxDvVTY@gmail.com> (raw)
In-Reply-To: <20220725042358.3377-1-kunyu@nfschina.com>
* Li kunyu <kunyu@nfschina.com> wrote:
> I first observe (void *) type coercion and non coercion through assembly
> language. It seems that there is no difference.
> Then I output the assigned information through the print function and
> found that the pointer that is not coerced is directly assigned when
> executing the print function (opcode a1), while the coerced pointer
> needs to execute the assembly instruction xlat (opcode d7), which seems
> to be more efficient without coerced conversion.
> At present, I just started to try to analyze this part of knowledge
> (machine code), please forgive me if the analysis is wrong.
>
> Signed-off-by: Li kunyu <kunyu@nfschina.com>
> ---
> arch/x86/boot/bitops.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/boot/bitops.h b/arch/x86/boot/bitops.h
> index 02e1dea11d94..8518ae214c9b 100644
> --- a/arch/x86/boot/bitops.h
> +++ b/arch/x86/boot/bitops.h
> @@ -19,13 +19,13 @@
>
> static inline bool constant_test_bit(int nr, const void *addr)
> {
> - const u32 *p = (const u32 *)addr;
> + const u32 *p = addr;
> return ((1UL << (nr & 31)) & (p[nr >> 5])) != 0;
> }
> static inline bool variable_test_bit(int nr, const void *addr)
> {
> bool v;
> - const u32 *p = (const u32 *)addr;
> + const u32 *p = addr;
>
> asm("btl %2,%1" CC_SET(c) : CC_OUT(c) (v) : "m" (*p), "Ir" (nr));
> return v;
It's true that the forced-type casting of 'addr' is unnecessary in the
cases above, I'm not sure how the kernel would end up with an XLAT
instruction being generated in that sequence.
But your patch is a good cleanup in its own right - I've applied the patch
below to tip:x86/cleanups, with a different changelog.
Thanks,
Ingo
===================>
From: Li kunyu <kunyu@nfschina.com>
Date: Mon, 25 Jul 2022 12:23:58 +0800
Subject: [PATCH] x86/boot: Remove superfluous type casting from arch/x86/boot/bitops.h
'const void *' will auto-type-convert to just about any other const pointer type,
no need to force it.
[ mingo: Rewrote the changelog. ]
Signed-off-by: Li kunyu <kunyu@nfschina.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20220725042358.3377-1-kunyu@nfschina.com
---
arch/x86/boot/bitops.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/boot/bitops.h b/arch/x86/boot/bitops.h
index 02e1dea11d94..8518ae214c9b 100644
--- a/arch/x86/boot/bitops.h
+++ b/arch/x86/boot/bitops.h
@@ -19,13 +19,13 @@
static inline bool constant_test_bit(int nr, const void *addr)
{
- const u32 *p = (const u32 *)addr;
+ const u32 *p = addr;
return ((1UL << (nr & 31)) & (p[nr >> 5])) != 0;
}
static inline bool variable_test_bit(int nr, const void *addr)
{
bool v;
- const u32 *p = (const u32 *)addr;
+ const u32 *p = addr;
asm("btl %2,%1" CC_SET(c) : CC_OUT(c) (v) : "m" (*p), "Ir" (nr));
return v;
next prev parent reply other threads:[~2022-08-03 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 4:23 [PATCH] x86/boot/arch/variable: I don't think (void *) Pointers need to be cast Li kunyu
2022-08-03 9:33 ` Ingo Molnar [this message]
2022-08-03 15:42 ` [tip: x86/cleanups] x86/boot: Remove superfluous type casting from arch/x86/boot/bitops.h tip-bot2 for Li kunyu
2022-08-15 19:25 ` tip-bot2 for Li kunyu
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=YupA9iqo4PxDvVTY@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=kunyu@nfschina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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