ajan
Subject: Re: GLibC AMD CPUID cache reporting regression (was Re: qemu-user self
emulation broken with default CPU on x86/x64)
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
* Daniel P. Berrangé:
>
* Daniel P. Berrangé:
> On Mon, Jul 03, 2023 at 06:03:08PM +0200, Pierrick Bouvier wrote:
>> Hi everyone,
>>
>> Recently (in d135f781 [1], between v7.0.0 and v8.0.0), qemu-user default cpu
>> was updated to "max" instead of qemu32/qemu64.
>>
>> This change "broke" qemu self emulation if this new
Thanks for this deep analysis.
Even if the bug is potentially on glibc side, would that be worth to
change something in qemu CPU description to avoid it (like changing cpuid)?
On 7/3/23 23:05, Daniel P. Berrangé wrote:
On Mon, Jul 03, 2023 at 06:03:08PM +0200, Pierrick Bouvier wrote:
Hi ever
On Mon, Jul 03, 2023 at 06:03:08PM +0200, Pierrick Bouvier wrote:
> Hi everyone,
>
> Recently (in d135f781 [1], between v7.0.0 and v8.0.0), qemu-user default cpu
> was updated to "max" instead of qemu32/qemu64.
>
> This change "broke" qemu self emulation if this new default cpu is used.
>
> $ ./
On Mon, Jul 03, 2023 at 06:03:08PM +0200, Pierrick Bouvier wrote:
> Hi everyone,
>
> Recently (in d135f781 [1], between v7.0.0 and v8.0.0), qemu-user default cpu
> was updated to "max" instead of qemu32/qemu64.
>
> This change "broke" qemu self emulation if this new default cpu is used.
>
> $ ./
Hi everyone,
Recently (in d135f781 [1], between v7.0.0 and v8.0.0), qemu-user default
cpu was updated to "max" instead of qemu32/qemu64.
This change "broke" qemu self emulation if this new default cpu is used.
$ ./qemu-x86_64 ./qemu-x86_64 --version
qemu-x86_64: ../util/cacheflush.c:212: init
