The EncryptedRAMBlock Notifier lets SEV know which guest RAM pages
will contain encrypted guest data.
Using this notifier lets SEV skip pinning pages that do not contain
encrypted data.
Signed-off-by: Janakarajan Natarajan
---
target/i386/sev.c | 25 -
1 file changed, 8
Currently, the SEV guest launch registers to a RAM block notifier. When
called, we issue KVM_MEMORY_ENCRYPT_{REG,UNREG}_REGION ioctl to register
the memory with the KVM driver. These ioctls should be called only for
the region which contains the encrypted data but the RAM block notifier
gets called
A client can register to this notifier to know whether the newly added or
removed memory region is marked as encrypted. This information is needed
for the SEV guest launch. In SEV guest, some memory regions may contain
encrypted data (e.g guest RAM). The memory region which contains the
encrypted d
PC ram, pflash unit 0 rom and pc-dimm memory hotplug ram blocks need to be
encrypted.
Also, notify listeners when freeing a MemoryRegion if it has encrypted
data.
Signed-off-by: Janakarajan Natarajan
---
exec.c | 5 +
hw/i386/pc.c | 1 +
hw/i386/pc_sysfw.c | 2
On 5/3/2019 1:25 PM, Eduardo Habkost wrote:
> [CAUTION: External Email]
>
> On Fri, Apr 26, 2019 at 02:32:51PM +, Janakarajan Natarajan wrote:
>> On 4/26/19 7:29 AM, Igor Mammedov wrote:
> [...]
diff --git a/numa.c b/numa.c
index 3875e1efda..08601366c5 100644
--- a/numa.c
++
