* David Gibson (da...@gibson.dropbear.id.au) wrote:
> On Tue, Jan 12, 2021 at 11:59:59AM +0100, Greg Kurz wrote:
> > On Tue, 12 Jan 2021 15:45:00 +1100
> > David Gibson wrote:
> >
> > > Currently the "memory-encryption" property is only looked at once we
> > > get to kvm_init(). Although
On Tue, Jan 12, 2021 at 11:59:59AM +0100, Greg Kurz wrote:
> On Tue, 12 Jan 2021 15:45:00 +1100
> David Gibson wrote:
>
> > Currently the "memory-encryption" property is only looked at once we
> > get to kvm_init(). Although protection of guest memory from the
> > hypervisor isn't something
On Tue, 12 Jan 2021 15:45:00 +1100
David Gibson wrote:
> Currently the "memory-encryption" property is only looked at once we
> get to kvm_init(). Although protection of guest memory from the
> hypervisor isn't something that could really ever work with TCG, it's
> not conceptually tied to the
Currently the "memory-encryption" property is only looked at once we
get to kvm_init(). Although protection of guest memory from the
hypervisor isn't something that could really ever work with TCG, it's
not conceptually tied to the KVM accelerator.
In addition, the way the string property is
