From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
richard.henderson@linaro.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] meson: ensure we enable CMPXCHG128 on x86_64
Date: Mon, 7 Oct 2024 09:42:40 +0100 [thread overview]
Message-ID: <ZwOfAE7hk503w11E@redhat.com> (raw)
In-Reply-To: <20241004220123.978938-1-pierrick.bouvier@linaro.org>
On Fri, Oct 04, 2024 at 03:01:23PM -0700, Pierrick Bouvier wrote:
> Alex discovered that CMPXCHG128 was not enabled when building for
> x86_64, resulting in slow execution for wide atomic instructions,
> creating a huge contention when combined with a high number of cpus
> (found while booting android aarch64 guest on x86_64 host).
>
> The problem is that even though we enable -mcx16 option for x86_64, this
> is not used when testing for CMPXCHG128. Thus, we silently turn it off.
>
> x86_64 is the only architecture adding machine flags for now, so the
> problem is limited to this host architecture.
>
> Meson compiler tests are supposed to be independent of environment flags
> (https://mesonbuild.com/Reference-manual_returned_compiler.html#returned-by).
> However, CFLAGS are used anyway, thus masking the problem when using
> something like CFLAGS='-march=native'. This is a meson bug and was reported:
> https://github.com/mesonbuild/meson/issues/13757
>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> meson.build | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index b18c2a54ab5..af2ce595dcc 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -2867,6 +2867,13 @@ if has_int128_type
> config_host_data.set('CONFIG_ATOMIC128_OPT', has_atomic128_opt)
>
> if not has_atomic128_opt
> +
> + host_flags = []
> + if host_arch == 'x86_64'
> + # for x86_64, x86_version must be >= 1, and we always enable cmpxchg16
> + # in this case.
> + host_flags += ['-mcx16']
> + endif
IMHO, we shouldn't be assuming that the earlier code passed '-mcx16',
as it requires that we keep 2 far away parts of meson.build in sync.
> config_host_data.set('CONFIG_CMPXCHG128', cc.links('''
> int main(void)
> {
> @@ -2874,7 +2881,8 @@ if has_int128_type
> __sync_val_compare_and_swap_16(&x, y, x);
> return 0;
> }
> - '''))
> + ''',
> + args: host_flags))
Just pass 'qemu_common_flags' here.
> endif
> endif
> endif
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-10-07 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 22:01 [PATCH] meson: ensure we enable CMPXCHG128 on x86_64 Pierrick Bouvier
2024-10-05 16:16 ` Michael Tokarev
2024-10-05 16:20 ` Richard Henderson
2024-10-05 16:22 ` Michael Tokarev
2024-10-05 16:30 ` Michael Tokarev
2024-10-05 17:34 ` Pierrick Bouvier
2024-10-05 17:44 ` Pierrick Bouvier
2024-10-07 8:42 ` Daniel P. Berrangé [this message]
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=ZwOfAE7hk503w11E@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).