On Mon, 29 May 2023 at 11:15, Andrea Bolognani wrote:
>
> On Mon, May 22, 2023 at 02:04:28PM +0200, Cornelia Huck wrote:
> > On Fri, Apr 28 2023, Cornelia Huck wrote:
> > > Another open problem is mte vs mte3: tcg emulates mte3, kvm gives the
> > > guest
> > > whatever the host supports.
On Mon, May 22, 2023 at 02:04:28PM +0200, Cornelia Huck wrote:
> On Fri, Apr 28 2023, Cornelia Huck wrote:
> > Another open problem is mte vs mte3: tcg emulates mte3, kvm gives the guest
> > whatever the host supports. Without migration support, this is not too much
> > of a problem yet, but for
On Fri, Apr 28 2023, Cornelia Huck wrote:
> Another open problem is mte vs mte3: tcg emulates mte3, kvm gives the guest
> whatever the host supports. Without migration support, this is not too much
> of a problem yet, but for compatibility handling, we'll need a way to keep
> QEMU from handing
On Fri, 28 Apr 2023 at 10:55, Cornelia Huck wrote:
>
> v7 takes a different approach to wiring up MTE, so I still include a cover
> letter where I can explain things better, even though it is now only a
> single patch :)
Applied to target-arm.next, thanks.
-- PMM
v7 takes a different approach to wiring up MTE, so I still include a cover
letter where I can explain things better, even though it is now only a
single patch :)
Previous versions used a cpu property to control MTE enablement, while
keeping the same semantics for the virt machine "mte" property
