From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: David Hildenbrand <david@redhat.com>
Subject: [PATCH v1 0/5] virtio-mem: block size and address-assignment optimizations
Date: Wed, 23 Sep 2020 13:38:55 +0200 [thread overview]
Message-ID: <20200923113900.72718-1-david@redhat.com> (raw)
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
next reply other threads:[~2020-09-23 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:38 David Hildenbrand [this message]
2020-09-23 11:38 ` [PATCH v1 1/5] virtio-mem: Probe THP size to determine default block size David Hildenbrand
2020-09-25 13:46 ` Pankaj Gupta
2020-09-28 8:58 ` David Hildenbrand
2020-09-28 9:31 ` Pankaj Gupta
2020-09-28 9:36 ` David Hildenbrand
2020-09-23 11:38 ` [PATCH v1 2/5] virtio-mem: Check that "memaddr" is multiples of the " David Hildenbrand
2020-09-25 13:57 ` Pankaj Gupta
2020-09-23 11:38 ` [PATCH v1 3/5] memory-device: Support big alignment requirements David Hildenbrand
2020-09-25 14:18 ` Pankaj Gupta
2020-09-23 11:38 ` [PATCH v1 4/5] memory-device: Add get_min_alignment() callback David Hildenbrand
2020-09-26 21:07 ` Pankaj Gupta
2020-09-23 11:39 ` [PATCH v1 5/5] virito-mem: Implement get_min_alignment() David Hildenbrand
2020-09-26 21:23 ` Pankaj Gupta
2020-09-25 10:16 ` [PATCH v1 0/5] virtio-mem: block size and address-assignment optimizations David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200923113900.72718-1-david@redhat.com \
--to=david@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).