On Thu, Jun 06, 2019 at 02:36:10PM -0300, Claudio Carvalho wrote:
From: Michael Anderson <redacted>
When running under an ultravisor, the ultravisor controls the real
partition table and has it in secure memory where the hypervisor can't
access it, and therefore we (the HV) have to do a ucall whenever we want
to update an entry.
The HV still keeps a copy of its view of the partition table in normal
memory so that the nest MMU can access it.
Both partition tables will have PATE entries for HV and normal virtual
machines.
As discussed before, all of this should depend only on
CONFIG_PPC_POWERNV.
Paul.