From: Mauricio Faria de Oliveira <mfo@igalia.com>
To: Peter Zijlstra <peterz@infradead.org>, Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Juergen Gross <jgross@suse.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
kernel-dev@igalia.com, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH RESEND v5 1/3] x86/asm, x86/boot: expose inline memcmp
Date: Wed, 01 Jul 2026 11:58:26 -0300 [thread overview]
Message-ID: <a433b566c26191283da0506cc6781e45@igalia.com> (raw)
In-Reply-To: <20260701070531.GK48970@noisy.programming.kicks-ass.net>
On 2026-07-01 04:05, Peter Zijlstra wrote:
> On Tue, Jun 30, 2026 at 02:21:46PM -0300, Mauricio Faria de Oliveira wrote:
>> Move the inline memcmp function currently only available in 'boot/string.c'
>> into the shared string function header <asm/shared/string.h> to be reused.
>>
>> This is not done through <asm/string.h> to avoid pulling unnecessary code
>> in 'boot/string.c' that causes build errors in 'boot/compressed/string.c'
>> and 'purgatory/purgatory.ro'.
>>
>> Note that the inline memcmp() returns 0/1, not -1/0/1 as regular memcmp()
>> (reported by David Laight <david.laight.linux@gmail.com>).
>>
>> Signed-off-by: Mauricio Faria de Oliveira <mfo@igalia.com>
>> ---
>> arch/x86/boot/string.c | 6 ++----
>> arch/x86/include/asm/shared/string.h | 16 ++++++++++++++++
>> arch/x86/include/asm/string.h | 1 +
>> 3 files changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/boot/string.c b/arch/x86/boot/string.c
>> index ac0f900ebc47efa81c92e1bb2010ea41677899c4..be454a6864225f3a972c3e81826b77ed4e8a57fe 100644
>> --- a/arch/x86/boot/string.c
>> +++ b/arch/x86/boot/string.c
>> @@ -15,6 +15,7 @@
>> #include <linux/errno.h>
>> #include <linux/limits.h>
>> #include <asm/asm.h>
>> +#include <asm/shared/string.h>
>> #include "ctype.h"
>> #include "string.h"
>>
>> @@ -31,10 +32,7 @@
>>
>> int memcmp(const void *s1, const void *s2, size_t len)
>> {
>> - bool diff;
>> - asm("repe cmpsb"
>> - : "=@ccnz" (diff), "+D" (s1), "+S" (s2), "+c" (len));
>> - return diff;
>> + return __inline_memcmp(s1, s2, len);
>> }
>>
>> /*
>> diff --git a/arch/x86/include/asm/shared/string.h b/arch/x86/include/asm/shared/string.h
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..422952152f533ad75b98f3873297b39c4f5e2477
>> --- /dev/null
>> +++ b/arch/x86/include/asm/shared/string.h
>> @@ -0,0 +1,16 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>> +#ifndef _ASM_X86_SHARED_STRING_H
>> +#define _ASM_X86_SHARED_STRING_H
>> +
>> +/* Note: this memcmp() returns 0/1, not -1/0/1 as regular memcmp(). */
>> +static __always_inline int __inline_memcmp(const void *s1, const void *s2, size_t len)
>> +{
>> + bool diff;
>> +
>> + asm("repe cmpsb"
>> + : "=@ccnz" (diff), "+D" (s1), "+S" (s2), "+c" (len));
>> +
>> + return diff;
>> +}
>> +
>> +#endif /* _ASM_X86_SHARED_STRING_H */
>> diff --git a/arch/x86/include/asm/string.h b/arch/x86/include/asm/string.h
>> index 9cb5aae7fba9ffcf0f5af8f939d30467750ccaa9..f0f4fd8227bf992e78c69209efb31f0a9a0cc3b1 100644
>> --- a/arch/x86/include/asm/string.h
>> +++ b/arch/x86/include/asm/string.h
>> @@ -7,6 +7,7 @@
>> #else
>> # include <asm/string_64.h>
>> #endif
>> +#include <asm/shared/string.h>
>>
>> static __always_inline void *__inline_memcpy(void *to, const void *from, size_t len)
>> {
>
> It seems weird to have __inline_mem{cpy,set}() in a different header than
> __inline_memcmp(). I'm assuming this is because boot cannot include the
> normal string thing?
>
> Perhaps make inline_string.h or somesuch to carry all three of them and
> include that from the relevant places?
Thanks for looking into this.
Yes, your question and suggestion above are essentially patch 1 in v4
[1].
Borislav Petkov requested a clean header in arch/x86/include/asm/shared/
for this (without other code), which is patch 1 in v5.
cheers,
[1]
https://lore.kernel.org/all/20260526-pvh-kasan-inline-v4-1-a310e6a25ecd@igalia.com/
--
Mauricio
next prev parent reply other threads:[~2026-07-01 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 17:21 [PATCH RESEND v5 0/3] x86/pvh: fix unbootable VMs again (PVH + KASAN) Mauricio Faria de Oliveira
2026-06-30 17:21 ` [PATCH RESEND v5 1/3] x86/asm, x86/boot: expose inline memcmp Mauricio Faria de Oliveira
2026-07-01 7:05 ` Peter Zijlstra
2026-07-01 14:58 ` Mauricio Faria de Oliveira [this message]
2026-07-01 18:40 ` Borislav Petkov
2026-07-01 19:57 ` Mauricio Faria de Oliveira
2026-07-01 20:03 ` Mauricio Faria de Oliveira
2026-07-01 21:14 ` Borislav Petkov
2026-07-01 20:46 ` Borislav Petkov
2026-07-01 22:00 ` Mauricio Faria de Oliveira
2026-06-30 17:21 ` [PATCH RESEND v5 2/3] x86/cpuid: fix unbootable VMs by really inlining memcmp() in hypervisor_cpuid_base() Mauricio Faria de Oliveira
2026-06-30 17:21 ` [PATCH RESEND v5 3/3] x86/pvh: fix unbootable VMs by really inlining memset() in xen_prepare_pvh() Mauricio Faria de Oliveira
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=a433b566c26191283da0506cc6781e45@igalia.com \
--to=mfo@igalia.com \
--cc=adobriyan@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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