From: Nikolay Borisov <nik.borisov@suse.com>
To: Youling Tang <youling.tang@linux.dev>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>,
Youling Tang <tangyouling@kylinos.cn>
Subject: Re: [PATCH 1/2] x86: Remove the prefetch() specific implementation on x86_64
Date: Thu, 30 May 2024 18:26:19 +0300 [thread overview]
Message-ID: <ca6c512a-c9cd-4210-bd71-c72c729c95a9@suse.com> (raw)
In-Reply-To: <20240529032059.899347-1-youling.tang@linux.dev>
On 29.05.24 г. 6:20 ч., Youling Tang wrote:
> From: Youling Tang <tangyouling@kylinos.cn>
>
> After commit ab483570a13b ("x86 & generic: change to __builtin_prefetch()"),
> x86_64 directly uses __builtin_prefetch() without the specific implementation
> of prefetch(). Also, x86_64 use a generic definition until commit ae2e15eb3b6c
> ("x86: unify prefetch operations"). So remove it.
So this patch just ensures the x86-specific prefetch() implementation is
defined only for 32bit case, otherwise we have it defined for the 64bit
case as well but effectively it's not used since ARCH_HAS_PREFETCH is
not defined for 64bit, meaning in the 64bit case prefetch() is still
defined to __builtint_prefetch in include/linux/prefetch.h.
In essence this is a purely cosmetic cleanup , am I right?
I compiled a file that utilizes prefetch with and without your patch and
the generated assembly is identical.
Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
>
> Signed-off-by: Youling Tang <tangyouling@kylinos.cn>
> ---
> arch/x86/include/asm/processor.h | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
> index cb4f6c513c48..44371bdcc59d 100644
> --- a/arch/x86/include/asm/processor.h
> +++ b/arch/x86/include/asm/processor.h
> @@ -599,9 +599,6 @@ extern char ignore_fpu_irq;
> #ifdef CONFIG_X86_32
> # define BASE_PREFETCH ""
> # define ARCH_HAS_PREFETCH
> -#else
> -# define BASE_PREFETCH "prefetcht0 %1"
> -#endif
>
> /*
> * Prefetch instructions for Pentium III (+) and AMD Athlon (+)
> @@ -616,6 +613,10 @@ static inline void prefetch(const void *x)
> "m" (*(const char *)x));
> }
>
> +#else
> +# define BASE_PREFETCH "prefetcht0 %1"
> +#endif
> +
> /*
> * 3dnow prefetch to get an exclusive cache line.
> * Useful for spinlocks to avoid one state transition in the
next prev parent reply other threads:[~2024-05-30 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 3:20 Youling Tang
2024-05-29 3:20 ` [PATCH 2/2] prefetch: Add ARCH_HAS_PREFETCH definition when the architecture is not defined Youling Tang
2024-05-30 15:30 ` Nikolay Borisov
2024-05-29 20:03 ` [PATCH 1/2] x86: Remove the prefetch() specific implementation on x86_64 kernel test robot
2024-05-30 1:51 ` Youling Tang
2024-05-30 15:26 ` Nikolay Borisov [this message]
2024-05-31 1:17 ` Youling Tang
2024-07-24 7:45 ` Youling Tang
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=ca6c512a-c9cd-4210-bd71-c72c729c95a9@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=tangyouling@kylinos.cn \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=youling.tang@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
all inboxes | Powered by JetHome®