Since MTE is new, and guest support for MTE is still under
development, let's disable it by default.

Peter mentioned memory hotplug on IRC as something that
would break MTE's assumptions.  By putting the enable flag
on the machine it's much easier to control.

For 5.1, we won't have kvm support, so error for that combo.


r~


Richard Henderson (3):
  hw/arm/virt: Enable MTE via a machine property
  hw/arm/virt: Error for MTE enabled with KVM
  hw/arm/virt: Disable memory hotplug when MTE is enabled

 include/hw/arm/virt.h |  1 +
 hw/arm/virt.c         | 50 ++++++++++++++++++++++++++++++++++++++-----
 target/arm/cpu.c      | 19 +++++++++-------
 target/arm/cpu64.c    |  5 +++--
 4 files changed, 60 insertions(+), 15 deletions(-)

-- 
2.25.1

On Mon, 13 Jul 2020 at 22:33, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> Since MTE is new, and guest support for MTE is still under
> development, let's disable it by default.
>
> Peter mentioned memory hotplug on IRC as something that
> would break MTE's assumptions.  By putting the enable flag
> on the machine it's much easier to control.
>
> For 5.1, we won't have kvm support, so error for that combo.

Applied to target-arm.next for 5.1, thanks.

-- PMM