On Thu, 5 Nov 2026 at 12:42, Daniel P. Berrangé <[email protected]> wrote:
> So that essentially matches the historical semantics where one
> CPU class magically changes its behaviour based on what target
> is running.  So in that sense, it works, and is no worse than
> the semantics we've had for 'max' models forever.
>
> Splitting into 2 distinct types is worthwhile if we want to
> make it possible for the aarch64 emulator to support a runtime
> choice of both 32-bit and 64-bit "max" models.

What would the difference between that and configuring the 64-bit
capable "max" to not have AArch64 via "-cpu max-v8:aarch64=off"
(which should work today) ?

-- PMM

Reply via email to