From: Florian Weimer <fweimer@redhat.com>
To: qemu-devel@nongnu.org
Subject: Emulating CPUs with larger atomic accesses
Date: Fri, 13 May 2022 12:00:14 +0200 [thread overview]
Message-ID: <87k0apeor5.fsf@oldenburg.str.redhat.com> (raw)
What's QEMU's approach to emulating CPU instructions that atomatically
operate on values larger than what is supported by the host CPU?
I assume that for full system emulation, this is not a problem, but
qemu-user will not achieve atomic behavior on shared memory mappings.
How much of a problem is this in practice?
Thanks,
Florian
next reply other threads:[~2022-05-13 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 10:00 Florian Weimer [this message]
2022-05-22 1:07 ` Emulating CPUs with larger atomic accesses Richard Henderson
2022-05-24 9:27 ` Florian Weimer
2022-05-24 11:48 ` Richard Henderson
2022-05-24 11:51 ` Florian Weimer
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=87k0apeor5.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.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).