Let's try to detect the actual THP size and use it as default block size
(unless the page size of the backend is bigger). Handle large block sizes
better, avoiding a virtio-spec violation and optimizing address
auto-detection.

David Hildenbrand (5):
  virtio-mem: Probe THP size to determine default block size
  virtio-mem: Check that "memaddr" is multiples of the block size
  memory-device: Support big alignment requirements
  memory-device: Add get_min_alignment() callback
  virito-mem: Implement get_min_alignment()

 hw/mem/memory-device.c         | 20 ++++---
 hw/virtio/virtio-mem-pci.c     | 14 +++++
 hw/virtio/virtio-mem.c         | 95 ++++++++++++++++++++++++++++++++--
 include/hw/mem/memory-device.h | 11 ++++
 4 files changed, 130 insertions(+), 10 deletions(-)

-- 
2.26.2

On 23.09.20 13:38, David Hildenbrand wrote:
> Let's try to detect the actual THP size and use it as default block size
> (unless the page size of the backend is bigger). Handle large block sizes
> better, avoiding a virtio-spec violation and optimizing address
> auto-detection.
> 
> David Hildenbrand (5):
>   virtio-mem: Probe THP size to determine default block size
>   virtio-mem: Check that "memaddr" is multiples of the block size
>   memory-device: Support big alignment requirements
>   memory-device: Add get_min_alignment() callback
>   virito-mem: Implement get_min_alignment()
> 
>  hw/mem/memory-device.c         | 20 ++++---
>  hw/virtio/virtio-mem-pci.c     | 14 +++++
>  hw/virtio/virtio-mem.c         | 95 ++++++++++++++++++++++++++++++++--
>  include/hw/mem/memory-device.h | 11 ++++
>  4 files changed, 130 insertions(+), 10 deletions(-)
> 

Just noticed that spring cleaning due to meson change removed my
cc-cmd.sh script, so adding people manually to the cover for context.

-- 
Thanks,

David / dhildenb