vhost-vdpa: skip TPM CRB memory section
cover vhost-vdpa: skip TPM CRB memory section
An error is reported for vhost-vdpa case:
qemu-kvm: vhost_vdpa_listener_region_add received unaligned region
Marc-André has proposed a fix to this problem by skipping the memory region owned by the TPM CRB but it seems more generic to skip not DMA-able memory.
We have a memory flag for that, RAM_PROTECTED.
This series expands the memory API to provide a way to initialize a "protected" memory region and use it with the TPM CRB object.
For the previous discussions, see
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
and from Eric for VFIO:
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/all/[email protected]/
Thanks,
Laurent
Laurent Vivier (2):
memory: introduce memory_region_init_ram_protected()
tpm_crb: mark memory as protected
hw/tpm/tpm_crb.c | 2 +- include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++ softmmu/memory.c | 33 +++++++++++++++++++++++++++------ softmmu/physmem.c | 4 ++-- 4 files changed, 63 insertions(+), 9 deletions(-)
Signature · 1 line
2.41.0
PATCH 1/2 memory: introduce memory_region_init_ram_protected()
Commit 56918a126a ("memory: Add RAM_PROTECTED flag to skip IOMMU mappings") has introduced the RAM_PROTECTED flag to denote "protected" memory.
This flags is only used with qemu_ram_alloc_from_fd() for now.
To be able to register memory region with this flag, define memory_region_init_ram_protected() and declare the flag as valid in qemu_ram_alloc_internal() and qemu_ram_alloc().
--- include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++ softmmu/memory.c | 33 +++++++++++++++++++++++++++------ softmmu/physmem.c | 4 ++-- 3 files changed, 62 insertions(+), 8 deletions(-)
include/exec/memory.h +33 -0
@@ -1520,6 +1520,39 @@ void memory_region_init_iommu(void *_iommu_mr,const char *name, uint64_t size); +/** +* memory_region_init_ram_protected - Initialize RAM memory region. Accesses +* into the region will modify memory +* directly. +* +* The memory is created with the RAM_PROTECTED flag, for memory that +* looks and acts like RAM but inaccessible via normal mechanisms, +* including DMA. +* +* @mr: the #MemoryRegion to be initialized +* @owner: the object that tracks the region's reference count (must be +* TYPE_DEVICE or a subclass of TYPE_DEVICE, or NULL) +* @name: name of the memory region +* @size: size of the region in bytes +* @errp: pointer to Error*, to store an error if it happens. +* +* This function allocates RAM for a board model or device, and +* arranges for it to be migrated (by calling vmstate_register_ram() +* if @owner is a DeviceState, or vmstate_register_ram_global() if +* @owner is NULL). +* +* TODO: Currently we restrict @owner to being either NULL (for +* global RAM regions with no owner) or devices, so that we can +* give the RAM block a unique name for migration purposes. +* We should lift this restriction and allow arbitrary Objects. +* If you pass a non-NULL non-device @owner then we will assert. +*/ +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp); +/** * memory_region_init_ram - Initialize RAM memory region. Accesses into the * region will modify memory directly.
softmmu/memory.c +27 -6
@@ -3551,16 +3551,18 @@ void mtree_info(bool flatview, bool dispatch_tree, bool owner, bool disabled) } } -void memory_region_init_ram (MemoryRegion *mr, -Object *owner, -const char *name, -uint64_t size, -Error **errp) +static void memory_region_init_ram_flags (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +uint32_t ram_flags, +Error **errp) {DeviceState *owner_dev;Error *err =NULL ; -memory_region_init_ram_nomigrate (mr, owner, name, size, &err); +memory_region_init_ram_flags_nomigrate (mr, owner, name, size, ram_flags, + &err);if (err) {error_propagate (errp, err);return ;
@@ -3575,6 +3577,25 @@ void memory_region_init_ram(MemoryRegion *mr,vmstate_register_ram (mr, owner_dev); } +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,RAM_PROTECTED , + errp); +} + +void memory_region_init_ram (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,0 , errp); +} + void memory_region_init_rom(MemoryRegion *mr, Object *owner, const char *name,
softmmu/physmem.c +2 -2
@@ -1978,7 +1978,7 @@ RAMBlock *qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,Error *local_err =NULL ;assert ((ram_flags & ~(RAM_SHARED |RAM_RESIZEABLE |RAM_PREALLOC | -RAM_NORESERVE )) ==0 ); +RAM_NORESERVE |RAM_PROTECTED )) ==0 );assert (!host ^ (ram_flags &RAM_PREALLOC )); size =HOST_PAGE_ALIGN (size);
@@ -2012,7 +2012,7 @@ RAMBlock *qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,RAMBlock *qemu_ram_alloc (ram_addr_t size,uint32_t ram_flags,MemoryRegion *mr,Error **errp) { -assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE )) ==0 ); +assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE |RAM_PROTECTED )) ==0 );return qemu_ram_alloc_internal (size, size,NULL ,NULL , ram_flags, mr, errp); }
Signature · 1 line
2.41.0
Re: [PATCH 1/2] memory: introduce memory_region_init_ram_protected()
Quoted 21 lines · Laurent Vivier
Commit
56918a126a("memory: AddRAM_PROTECTEDflag to skip IOMMU mappings") has introduced theRAM_PROTECTEDflag to denote "protected" memory.This flags is only used with
qemu_ram_alloc_from_fd()for now.To be able to register memory region with this flag, define
memory_region_init_ram_protected()and declare the flag as valid inqemu_ram_alloc_internal()andqemu_ram_alloc().Signed-off-by Laurent Vivier <[email protected]>--- include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++ softmmu/memory.c | 33 +++++++++++++++++++++++++++------ softmmu/physmem.c | 4 ++-- 3 files changed, 62 insertions(+), 8 deletions(-)include/exec/memory.h +0
-0
include/exec/memory.h void memory_region_init_iommu(void *_iommu_mr, · line 1529
Quoted 10 lines
include/exec/memory.h +7
-0@@ -1520,6 +1520,39 @@ void memory_region_init_iommu(void *_iommu_mr,const char *name, uint64_t size); +/** +* memory_region_init_ram_protected - Initialize RAM memory region. Accesses +* into the region will modify memory +* directly. +* +* The memory is created with the RAM_PROTECTED flag, for memory that +* looks and acts like RAM but inaccessible via normal mechanisms,
but is inaccessible
Quoted 98 lines
include/exec/memory.h +26
-0+* including DMA. +* +* @mr: the #MemoryRegion to be initialized +* @owner: the object that tracks the region's reference count (must be +* TYPE_DEVICE or a subclass of TYPE_DEVICE, or NULL) +* @name: name of the memory region +* @size: size of the region in bytes +* @errp: pointer to Error*, to store an error if it happens. +* +* This function allocates RAM for a board model or device, and +* arranges for it to be migrated (by calling vmstate_register_ram() +* if @owner is a DeviceState, or vmstate_register_ram_global() if +* @owner is NULL). +* +* TODO: Currently we restrict @owner to being either NULL (for +* global RAM regions with no owner) or devices, so that we can +* give the RAM block a unique name for migration purposes. +* We should lift this restriction and allow arbitrary Objects. +* If you pass a non-NULL non-device @owner then we will assert. +*/ +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp); +/** * memory_region_init_ram - Initialize RAM memory region. Accesses into the * region will modify memory directly. softmmu/memory.c +27
-6@@ -3551,16 +3551,18 @@ void mtree_info(bool flatview, bool dispatch_tree, bool owner, bool disabled) } } -void memory_region_init_ram (MemoryRegion *mr, -Object *owner, -const char *name, -uint64_t size, -Error **errp) +static void memory_region_init_ram_flags (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +uint32_t ram_flags, +Error **errp) {DeviceState *owner_dev;Error *err =NULL ; -memory_region_init_ram_nomigrate (mr, owner, name, size, &err); +memory_region_init_ram_flags_nomigrate (mr, owner, name, size, ram_flags, + &err);if (err) {error_propagate (errp, err);return ;@@ -3575,6 +3577,25 @@ void memory_region_init_ram(MemoryRegion *mr,vmstate_register_ram (mr, owner_dev); } +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,RAM_PROTECTED , + errp); +} + +void memory_region_init_ram (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,0 , errp); +} + void memory_region_init_rom(MemoryRegion *mr, Object *owner, const char *name,softmmu/physmem.c +1
-1@@ -1978,7 +1978,7 @@ RAMBlock *qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,Error *local_err =NULL ;assert ((ram_flags & ~(RAM_SHARED |RAM_RESIZEABLE |RAM_PREALLOC | -RAM_NORESERVE )) ==0 ); +RAM_NORESERVE |RAM_PROTECTED )) ==0 );assert (!host ^ (ram_flags &RAM_PREALLOC )); size =HOST_PAGE_ALIGN (size);
softmmu/physmem.c RAMBlock *qemu_ram_alloc_from_ptr(ram_addr_t size, void *host, · line 2018
Quoted 8 lines
softmmu/physmem.c +1
-1@@ -2012,7 +2012,7 @@ RAMBlock *qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,RAMBlock *qemu_ram_alloc (ram_addr_t size,uint32_t ram_flags,MemoryRegion *mr,Error **errp) { -assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE )) ==0 ); +assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE |RAM_PROTECTED )) ==0 );return qemu_ram_alloc_internal (size, size,NULL ,NULL , ram_flags, mr, errp); }
Re: [PATCH 1/2] memory: introduce memory_region_init_ram_protected()
In reply to Laurent VivierQuoted 129 lines · Laurent Vivier
Commit
56918a126a("memory: AddRAM_PROTECTEDflag to skip IOMMU mappings") has introduced theRAM_PROTECTEDflag to denote "protected" memory.This flags is only used with
qemu_ram_alloc_from_fd()for now.To be able to register memory region with this flag, define
memory_region_init_ram_protected()and declare the flag as valid inqemu_ram_alloc_internal()andqemu_ram_alloc().Signed-off-by Laurent Vivier <[email protected]>--- include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++ softmmu/memory.c | 33 +++++++++++++++++++++++++++------ softmmu/physmem.c | 4 ++-- 3 files changed, 62 insertions(+), 8 deletions(-)include/exec/memory.h +33
-0@@ -1520,6 +1520,39 @@ void memory_region_init_iommu(void *_iommu_mr,const char *name, uint64_t size); +/** +* memory_region_init_ram_protected - Initialize RAM memory region. Accesses +* into the region will modify memory +* directly. +* +* The memory is created with the RAM_PROTECTED flag, for memory that +* looks and acts like RAM but inaccessible via normal mechanisms, +* including DMA. +* +* @mr: the #MemoryRegion to be initialized +* @owner: the object that tracks the region's reference count (must be +* TYPE_DEVICE or a subclass of TYPE_DEVICE, or NULL) +* @name: name of the memory region +* @size: size of the region in bytes +* @errp: pointer to Error*, to store an error if it happens. +* +* This function allocates RAM for a board model or device, and +* arranges for it to be migrated (by calling vmstate_register_ram() +* if @owner is a DeviceState, or vmstate_register_ram_global() if +* @owner is NULL). +* +* TODO: Currently we restrict @owner to being either NULL (for +* global RAM regions with no owner) or devices, so that we can +* give the RAM block a unique name for migration purposes. +* We should lift this restriction and allow arbitrary Objects. +* If you pass a non-NULL non-device @owner then we will assert. +*/ +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp); +/** * memory_region_init_ram - Initialize RAM memory region. Accesses into the * region will modify memory directly. softmmu/memory.c +27
-6@@ -3551,16 +3551,18 @@ void mtree_info(bool flatview, bool dispatch_tree, bool owner, bool disabled) } } -void memory_region_init_ram (MemoryRegion *mr, -Object *owner, -const char *name, -uint64_t size, -Error **errp) +static void memory_region_init_ram_flags (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +uint32_t ram_flags, +Error **errp) {DeviceState *owner_dev;Error *err =NULL ; -memory_region_init_ram_nomigrate (mr, owner, name, size, &err); +memory_region_init_ram_flags_nomigrate (mr, owner, name, size, ram_flags, + &err);if (err) {error_propagate (errp, err);return ;@@ -3575,6 +3577,25 @@ void memory_region_init_ram(MemoryRegion *mr,vmstate_register_ram (mr, owner_dev); } +void memory_region_init_ram_protected (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,RAM_PROTECTED , + errp); +} + +void memory_region_init_ram (MemoryRegion *mr, +Object *owner, +const char *name, +uint64_t size, +Error **errp) +{ +memory_region_init_ram_flags (mr, owner, name, size,0 , errp); +} + void memory_region_init_rom(MemoryRegion *mr, Object *owner, const char *name,softmmu/physmem.c +1
-1@@ -1978,7 +1978,7 @@ RAMBlock *qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,Error *local_err =NULL ;assert ((ram_flags & ~(RAM_SHARED |RAM_RESIZEABLE |RAM_PREALLOC | -RAM_NORESERVE )) ==0 ); +RAM_NORESERVE |RAM_PROTECTED )) ==0 );assert (!host ^ (ram_flags &RAM_PREALLOC )); size =HOST_PAGE_ALIGN (size);
softmmu/physmem.c RAMBlock *qemu_ram_alloc_from_ptr(ram_addr_t size, void *host, · line 2018
Quoted 8 lines
softmmu/physmem.c +1
-1@@ -2012,7 +2012,7 @@ RAMBlock *qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,RAMBlock *qemu_ram_alloc (ram_addr_t size,uint32_t ram_flags,MemoryRegion *mr,Error **errp) { -assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE )) ==0 ); +assert ((ram_flags & ~(RAM_SHARED |RAM_NORESERVE |RAM_PROTECTED )) ==0 );return qemu_ram_alloc_internal (size, size,NULL ,NULL , ram_flags, mr, errp); }
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH 1/2] memory: introduce memory_region_init_ram_protected()
In reply to Laurent VivierQuoted 23 lines · Laurent Vivier
Commit
56918a126a("memory: AddRAM_PROTECTEDflag to skip IOMMU mappings") has introduced theRAM_PROTECTEDflag to denote "protected" memory.This flags is only used with
qemu_ram_alloc_from_fd()for now.To be able to register memory region with this flag, define
memory_region_init_ram_protected()and declare the flag as valid inqemu_ram_alloc_internal()andqemu_ram_alloc().Signed-off-by Laurent Vivier <[email protected]>--- include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++ softmmu/memory.c | 33 +++++++++++++++++++++++++++------ softmmu/physmem.c | 4 ++-- 3 files changed, 62 insertions(+), 8 deletions(-)include/exec/memory.h +0
-0@@ -1520,6 +1520,39 @@ void memory_region_init_iommu(void *_iommu_mr, const char *name,
include/exec/memory.h void memory_region_init_iommu(void *_iommu_mr, · line 1530
Quoted 10 lines
include/exec/memory.h +8
-0uint64_t size); +/** +* memory_region_init_ram_protected - Initialize RAM memory region. Accesses +* into the region will modify memory +* directly. +* +* The memory is created with the RAM_PROTECTED flag, for memory that +* looks and acts like RAM but inaccessible via normal mechanisms, +* including DMA.
This doesn't really tell me why you might want to mark a region as RAM_PROTECTED. What kind of memory region is not DMAable to? What are "normal mechanisms" here? What are the "non-normal mechanisms" that you *can* use on this memory region?
At the moment we only seem to use RAM_PROTECTED for the SGX EPC memory backend. The commit message adding that flag is pretty vague about what it means...
thanks
-- PMM
PATCH 2/2 tpm_crb: mark memory as protected
In reply to Laurent VivierThis memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm: vhost_vdpa_listener_region_add received unaligned region
To make it ignored by VFIO and vDPA devices, mark it as RAM_PROTECTED.
The RAM_PROTECTED flag has been introduced to skip memory region that looks like RAM but is not accessible via normal mechanims, including DMA.
See 56918a126a ("memory: Add RAM_PROTECTED flag to skip IOMMU mappings")
--- hw/tpm/tpm_crb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
hw/tpm/tpm_crb.c +1 -1
@@ -296,7 +296,7 @@ static void tpm_crb_realize(DeviceState *dev, Error **errp)memory_region_init_io (&s->mmio,OBJECT (s), &tpm_crb_memory_ops, s,"tpm-crb-mmio" ,sizeof (s->regs)); -memory_region_init_ram (&s->cmdmem,OBJECT (s), +memory_region_init_ram_protected (&s->cmdmem,OBJECT (s),"tpm-crb-cmd" ,CRB_CTRL_CMD_SIZE , errp); memory_region_add_subregion(get_system_memory(),
Signature · 1 line
2.41.0
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Quoted 7 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionTo make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.
So, VFIO will simply skip these sections via vfio_listener_valid_section() I guess.
Yes, it will report an error but it will happily continue.
So regarding vDPA, we're also only concerned about removing the reported error, everything else works as expected?
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Quoted 7 lines · David Hildenbrand
Quoted 6 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned region
Quoted 8 lines
Quoted 1 line
To make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.So, VFIO will simply skip these sections via
vfio_listener_valid_section()I guess.Yes, it will report an error but it will happily continue.
So regarding vDPA, we're also only concerned about removing the reported error, everything else works as expected?
Yes, it has been tested and vDPA works as expected.
Thanks,
Laurent
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Quoted 12 lines · Laurent Vivier
Quoted 11 lines · David Hildenbrand
Quoted 7 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionTo make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.So, VFIO will simply skip these sections via
vfio_listener_valid_section()I guess.
Quoted 7 lines
Quoted 5 lines
Yes, it will report an error but it will happily continue.
So regarding vDPA, we're also only concerned about removing the reported error, everything else works as expected?
Yes, it has been tested and vDPA works as expected.
Okay, so no Fixes: tags required
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH 2/2] tpm_crb: mark memory as protected
In reply to Laurent VivierQuoted 14 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionTo make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.The
RAM_PROTECTEDflag has been introduced to skip memory region that looks like RAM but is not accessible via normal mechanims, including DMA.See
56918a126a("memory: AddRAM_PROTECTEDflag to skip IOMMU mappings")
Quoted 8 lines
Quoted 17 lines
--- hw/tpm/tpm_crb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)hw/tpm/tpm_crb.c +1
-1@@ -296,7 +296,7 @@ static void tpm_crb_realize(DeviceState *dev, Error **errp)memory_region_init_io (&s->mmio,OBJECT (s), &tpm_crb_memory_ops, s,"tpm-crb-mmio" ,sizeof (s->regs)); -memory_region_init_ram (&s->cmdmem,OBJECT (s), +memory_region_init_ram_protected (&s->cmdmem,OBJECT (s),"tpm-crb-cmd" ,CRB_CTRL_CMD_SIZE , errp); memory_region_add_subregion(get_system_memory(),
Re: [PATCH 2/2] tpm_crb: mark memory as protected
In reply to Laurent VivierQuoted 31 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionTo make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.The
RAM_PROTECTEDflag has been introduced to skip memory region that looks like RAM but is not accessible via normal mechanims, including DMA.See
56918a126a("memory: AddRAM_PROTECTEDflag to skip IOMMU mappings")Signed-off-by Laurent Vivier <[email protected]>--- hw/tpm/tpm_crb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)hw/tpm/tpm_crb.c +0
-0
hw/tpm/tpm_crb.c static void tpm_crb_realize(DeviceState *dev, Error **errp) · line 302
Quoted 8 lines
hw/tpm/tpm_crb.c +1
-1@@ -296,7 +296,7 @@ static void tpm_crb_realize(DeviceState *dev, Error **errp)memory_region_init_io (&s->mmio,OBJECT (s), &tpm_crb_memory_ops, s,"tpm-crb-mmio" ,sizeof (s->regs)); -memory_region_init_ram (&s->cmdmem,OBJECT (s), +memory_region_init_ram_protected (&s->cmdmem,OBJECT (s),"tpm-crb-cmd" ,CRB_CTRL_CMD_SIZE , errp); memory_region_add_subregion(get_system_memory(),
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH 2/2] tpm_crb: mark memory as protected
In reply to Laurent VivierQuoted 3 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
Isn't this a vDPA/VFIO problem? There's no requirement for RAM MemoryRegions to be aligned in any way. Code that doesn't want to work with small or weirdly aligned regions should skip them if that's the right behaviour for that particular code IMHO.
Quoted 8 lines
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionTo make it ignored by VFIO and vDPA devices, mark it as
RAM_PROTECTED.The
RAM_PROTECTEDflag has been introduced to skip memory region that looks like RAM but is not accessible via normal mechanims, including DMA.
You can DMA to a small RAM region if you want to...
thanks
-- PMM
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Quoted 11 lines · Peter Maydell
Quoted 3 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
Isn't this a vDPA/VFIO problem? There's no requirement for RAM MemoryRegions to be aligned in any way. Code that doesn't want to work with small or weirdly aligned regions should skip them if that's the right behaviour for that particular code IMHO.
Marc-André proposed to modify vDPA code to skip the region but Michal disagreed:
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
No one wants the modification, so the problem cannot be fixed.
Thanks,
Laurent
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Quoted 14 lines · Laurent Vivier
Quoted 11 lines · Peter Maydell
Quoted 3 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
Isn't this a vDPA/VFIO problem? There's no requirement for RAM MemoryRegions to be aligned in any way. Code that doesn't want to work with small or weirdly aligned regions should skip them if that's the right behaviour for that particular code IMHO.
Quoted 3 lines
Marc-André proposed to modify vDPA code to skip the region but Michal disagreed:
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
"Special case the TPM device in the vhost-vdpa" is clearly also not the right way to solve the issue, so I agree with Michael about that.
The vhost-vdpa code already seems able to correctly detect whether a region is unaligned and ignores it. If that's the right thing to do, maybe we should just remove the error_report() ? Listeners are going to see MemoryRegions which are RAM and which aren't necessarily page-aligned, so they should handle them, not complain about them.
thanks
-- PMM
Re: [PATCH 2/2] tpm_crb: mark memory as protected
In reply to Laurent VivierQuoted 9 lines · Laurent Vivier
Quoted 7 lines · Peter Maydell
Quoted 3 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
Isn't this a vDPA/VFIO problem? There's no requirement for RAM MemoryRegions to be aligned in any way.
It's more about the limitation of the IOMMU which can't do subpage protection.
Quoted 4 lines
Quoted 4 lines
Code
that doesn't want to work with small or weirdly aligned regions should skip them if that's the right behaviour for that particular code IMHO.
We had already had this:
if ((!memory_region_is_ram(section->mr) &&
!memory_region_is_iommu(section->mr)) ||
memory_region_is_protected(section->mr) ||
/* vhost-vDPA doesn't allow MMIO to be mapped */
memory_region_is_ram_device(section->mr)) {
return true;
}Quoted 8 lines
Quoted 1 line
Marc-André proposed to modify vDPA code to skip the region but Michal disagreed:
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
No one wants the modification, so the problem cannot be fixed.
Yes, otherwise we end up with explicit check for TPM crb in vhost code...
Thanks
Quoted 3 lines
Thanks,
Laurent
Re: [PATCH 2/2] tpm_crb: mark memory as protected
Hi,
as the region is already skipped by the test of the memory region alignment, I'm going to update my patches by only removing the error_report() as proposed by Peter.
I will replace it by a trace to help to debug.
Thanks,
Laurent
Quoted 45 lines · Jason Wang
Quoted 9 lines · Laurent Vivier
Quoted 7 lines · Peter Maydell
Quoted 3 lines · Laurent Vivier
This memory is not correctly aligned and cannot be registered by vDPA and VFIO.
Isn't this a vDPA/VFIO problem? There's no requirement for RAM MemoryRegions to be aligned in any way.
It's more about the limitation of the IOMMU which can't do subpage protection.
Quoted 4 lines
Quoted 4 lines
Code
that doesn't want to work with small or weirdly aligned regions should skip them if that's the right behaviour for that particular code IMHO.We had already had this:
if ((!memory_region_is_ram(section->mr) && !memory_region_is_iommu(section->mr)) || memory_region_is_protected(section->mr) || /* vhost-vDPA doesn't allow MMIO to be mapped */ memory_region_is_ram_device(section->mr)) { return true; }Quoted 8 lines
Quoted 1 line
Marc-André proposed to modify vDPA code to skip the region but Michal disagreed:
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
No one wants the modification, so the problem cannot be fixed.
Yes, otherwise we end up with explicit check for TPM crb in vhost code...
Thanks
Quoted 3 lines
Thanks,
Laurent
Quoted 21 lines · Laurent Vivier
An error is reported for vhost-vdpa case:
qemu-kvm:vhost_vdpa_listener_region_addreceived unaligned regionMarc-André has proposed a fix to this problem by skipping the memory region owned by the TPM CRB but it seems more generic to skip not DMA-able memory.
We have a memory flag for that,
RAM_PROTECTED.This series expands the memory API to provide a way to initialize a "protected" memory region and use it with the TPM CRB object.
For the previous discussions, see
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
and from Eric for VFIO:
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/all/[email protected]/
Quoted 8 lines
Thanks,
LaurentLaurent Vivier (2):
memory: introducememory_region_init_ram_protected()
tpm_crb: mark memory as protected
Signature · 1 line
Peter Xu