From: Richard Henderson <richard.henderson@linaro.org>
To: Petr Cvek <petrcvekcz@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"S. Tsirkin, Michael" <mst@redhat.com>
Subject: Re: [PATCH] qemu/timer: Don't use RDTSC on i486
Date: Wed, 29 Nov 2023 08:27:02 -0600 [thread overview]
Message-ID: <6de19df3-04d5-4179-adfe-ec642f8eb73c@linaro.org> (raw)
In-Reply-To: <7ac7d010-a984-48bf-b254-02f87324be83@gmail.com>
On 11/29/23 07:50, Petr Cvek wrote:
> I can agree that binary compiled for i486 doesn't contain cmpxchg8b and works OK with exception of setjmp bug I described in another thread [1]. glxgears which doesn't use signals works without problem. 64bit atomic operations seems to be emulated in util/atomic64.c.
>
> However I've found out the compilation for i386 seems to fail during configure due to the lack of i386 atomic instructions in my GCC 13.2.0 version. If this is normal behavior, I guess __tune_i386__ check doesn't make sense to add.
Correct, we cannot operate at all without the i486 atomic insns.
r~
next prev parent reply other threads:[~2023-11-29 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:23 [PATCH] qemu/timer: Don't use RDTSC on i486 Petr Cvek
2023-11-26 12:37 ` Samuel Tardieu
2023-11-26 12:59 ` Petr Cvek
2023-11-26 13:03 ` Samuel Tardieu
2023-11-26 22:49 ` Petr Cvek
2023-11-26 15:56 ` Paolo Bonzini
2023-11-26 22:52 ` Petr Cvek
2023-11-28 15:52 ` Richard Henderson
2023-11-29 13:50 ` Petr Cvek
2023-11-29 14:27 ` Richard Henderson [this message]
2023-11-27 9:49 ` Peter Maydell
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=6de19df3-04d5-4179-adfe-ec642f8eb73c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=petrcvekcz@gmail.com \
--cc=qemu-devel@nongnu.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).