From: Alexander Merritt <alexander@edera.dev>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, "Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86: drop XSAVEOPT and CLWB build flags
Date: Fri, 04 Apr 2025 09:39:30 -0400 [thread overview]
Message-ID: <b8f4e43e93bac45204ff5fb43af3b589@edera.dev> (raw)
In-Reply-To: <9870999d-3a45-4c2b-a37b-2651e4d53c3b@citrix.com>
On 2025-04-03 19:34, Andrew Cooper wrote:
> On 04/04/2025 12:28 am, Andrew Cooper wrote:
> Also, I forgot to write in the ticket, clflushopt wants similar
> treatment, even if there isn't an outward define for it. I think the
> following two hunks should do:
>
> ~Andrew
>
> diff --git a/xen/arch/x86/flushtlb.c b/xen/arch/x86/flushtlb.c
> index 18748b2bc805..ef30ef546336 100644
> --- a/xen/arch/x86/flushtlb.c
> +++ b/xen/arch/x86/flushtlb.c
> @@ -287,7 +287,7 @@ void cache_flush(const void *addr, unsigned int
> size)
> * of letting the alternative framework fill the gap by
> appending nops.
> */
> alternative_io("ds; clflush %[p]",
> - "data16 clflush %[p]", /* clflushopt */
> + "clflushopt %[p]",
Agree on these changes. However, I see branch staging uses
alternative_input and the below /* no outputs */ does not exist.
> X86_FEATURE_CLFLUSHOPT,
> /* no outputs */,
> [p] "m" (*(const char *)(addr)));
> diff --git a/xen/arch/x86/include/asm/system.h
> b/xen/arch/x86/include/asm/system.h
> index 73cb16ca68d6..6f5b6d502911 100644
> --- a/xen/arch/x86/include/asm/system.h
> +++ b/xen/arch/x86/include/asm/system.h
> @@ -23,7 +23,7 @@ static inline void clflush(const void *p)
>
> static inline void clflushopt(const void *p)
> {
> - asm volatile ( "data16 clflush %0" :: "m" (*(const char *)p) );
> + asm volatile ( "clflushopt %0" :: "m" (*(const char *)p) );
> }
>
> static inline void clwb(const void *p)
next prev parent reply other threads:[~2025-04-04 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 23:22 [PATCH] x86: drop XSAVEOPT and CLWB build flags Alexander M. Merritt
2025-04-03 23:28 ` Andrew Cooper
2025-04-03 23:34 ` Andrew Cooper
2025-04-04 13:39 ` Alexander Merritt [this message]
2025-04-03 23:45 ` Alexander Merritt
2025-04-04 7:21 ` Jan Beulich
2025-04-04 10:13 ` Andrew Cooper
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=b8f4e43e93bac45204ff5fb43af3b589@edera.dev \
--to=alexander@edera.dev \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.