* 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 tha
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 pr
* 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
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
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
