All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: Emulating CPUs with larger atomic accesses
Date: Tue, 24 May 2022 13:51:00 +0200	[thread overview]
Message-ID: <87r14jtahn.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6d4b89e8-452f-521e-3464-7981e89794e0@linaro.org> (Richard Henderson's message of "Tue, 24 May 2022 04:48:08 -0700")

* Richard Henderson:

> On 5/24/22 02:27, Florian Weimer wrote:
>> * Richard Henderson:
>> 
>>> On 5/13/22 03:00, Florian Weimer wrote:
>>>> 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?
>>>
>>> Well, it doesn't work, no.  In practice, x86_64 supports 128-bit
>>> atomic operations, and guest requires more than that.  No one really
>>> cares anymore about 32-bit hosts with smaller atomic operations.
>> Which part doesn't work?  Full-system emulation?
>
> No, user-only.
>
>> Do guests really require wider-than-128 atomics?  That's quite
>> surprising?
>
> Typo there -- "and no guest requires...".

Okay, thanks.  So the overall situation is okay even if we end up with
x86 guests that require CPU support for 128-bit loads.

Florian



      reply	other threads:[~2022-05-24 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 10:00 Emulating CPUs with larger atomic accesses Florian Weimer
2022-05-22  1:07 ` Richard Henderson
2022-05-24  9:27   ` Florian Weimer
2022-05-24 11:48     ` Richard Henderson
2022-05-24 11:51       ` Florian Weimer [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=87r14jtahn.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --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 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.