Re: [PATCH v4 7/9] virt: geniezone: Add memory region support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 09/06/23 10:52, Yi-De Wu ha scritto:
From: "Jerry Wang" <ze-yu.wang@xxxxxxxxxxxx>

Hypervisor might need to know the precise purpose of each memory
region, so that it can provide specific memory protection. We add a new
uapi to pass address and size of a memory region and its purpose.

Signed-off-by: Jerry Wang <ze-yu.wang@xxxxxxxxxxxx>
Signed-off-by: Liju-clr Chen <liju-clr.chen@xxxxxxxxxxxx>
Signed-off-by: Yi-De Wu <yi-de.wu@xxxxxxxxxxxx>
---
  arch/arm64/geniezone/gzvm_arch_common.h | 2 ++
  arch/arm64/geniezone/vm.c               | 9 +++++++++
  drivers/virt/geniezone/gzvm_vm.c        | 1 +
  include/linux/gzvm_drv.h                | 2 ++
  4 files changed, 14 insertions(+)

diff --git a/arch/arm64/geniezone/gzvm_arch_common.h b/arch/arm64/geniezone/gzvm_arch_common.h
index 5affa28b935a..5cfeb4df84c5 100644
--- a/arch/arm64/geniezone/gzvm_arch_common.h
+++ b/arch/arm64/geniezone/gzvm_arch_common.h
@@ -23,6 +23,7 @@ enum {
  	GZVM_FUNC_CREATE_DEVICE,
  	GZVM_FUNC_PROBE,
  	GZVM_FUNC_ENABLE_CAP,
+	GZVM_FUNC_MEMREGION_PURPOSE,
  	NR_GZVM_FUNC
  };
@@ -46,6 +47,7 @@ enum {
  #define MT_HVC_GZVM_CREATE_DEVICE	GZVM_HCALL_ID(GZVM_FUNC_CREATE_DEVICE)
  #define MT_HVC_GZVM_PROBE		GZVM_HCALL_ID(GZVM_FUNC_PROBE)
  #define MT_HVC_GZVM_ENABLE_CAP		GZVM_HCALL_ID(GZVM_FUNC_ENABLE_CAP)
+#define MT_HVC_GZVM_MEMREGION_PURPOSE	GZVM_HCALL_ID(GZVM_FUNC_MEMREGION_PURPOSE)
  #define GIC_V3_NR_LRS			16
/**
diff --git a/arch/arm64/geniezone/vm.c b/arch/arm64/geniezone/vm.c
index 9f1f14f71b99..e19a66d6a75d 100644
--- a/arch/arm64/geniezone/vm.c
+++ b/arch/arm64/geniezone/vm.c
@@ -97,6 +97,15 @@ int gzvm_arch_destroy_vm(gzvm_id_t vm_id)
  				    0, 0, &res);
  }
+int gzvm_arch_memregion_purpose(struct gzvm *gzvm, struct gzvm_userspace_memory_region *mem)
+{
+	struct arm_smccc_res res;
+
+	return gzvm_hypcall_wrapper(MT_HVC_GZVM_MEMREGION_PURPOSE, gzvm->vm_id,
+				    mem->guest_phys_addr, mem->memory_size,
+				    mem->flags, 0, 0, 0, &res);
+}
+
  static int gzvm_vm_arch_enable_cap(struct gzvm *gzvm, struct gzvm_enable_cap *cap,
  				   struct arm_smccc_res *res)
  {
diff --git a/drivers/virt/geniezone/gzvm_vm.c b/drivers/virt/geniezone/gzvm_vm.c
index ba5412acfa7d..3b1cb715ef34 100644
--- a/drivers/virt/geniezone/gzvm_vm.c
+++ b/drivers/virt/geniezone/gzvm_vm.c
@@ -248,6 +248,7 @@ gzvm_vm_ioctl_set_memory_region(struct gzvm *gzvm,
  	memslot->vma = vma;
  	memslot->flags = mem->flags;
  	memslot->slot_id = mem->slot;
+	gzvm_arch_memregion_purpose(gzvm, mem);

ret = gzvm_arch_memregion_purpose(...)
if (ret)
	......

  	return register_memslot_addr_range(gzvm, memslot);
  }

Regards,
Angelo




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux