From: Alexander Duyck <alexander.duyck@gmail.com>
To: pbonzini@redhat.com, david@redhat.com, mst@redhat.com
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org
Subject: [PATCH v19 QEMU 0/4] virtio-balloon: add support for free page reporting
Date: Thu, 09 Apr 2020 20:41:22 -0700 [thread overview]
Message-ID: <20200410033729.24738.22879.stgit@localhost.localdomain> (raw)
This series provides an asynchronous means of reporting free guest pages
to QEMU through virtio-balloon so that the memory associated with those
pages can be dropped and reused by other processes and/or guests on the
host. Using this it is possible to avoid unnecessary I/O to disk and
greatly improve performance in the case of memory overcommit on the host.
I originally submitted this patch series back on February 11th 2020[1],
but at that time I was focused primarily on the kernel portion of this
patch set. However as of April 7th those patches are now included in
Linus's kernel tree[2] and so I am submitting the QEMU pieces for
inclusion.
[1]: https://lore.kernel.org/lkml/20200211224416.29318.44077.stgit@localhost.localdomain/
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0c504f154718904ae49349147e3b7e6ae91ffdc
Changes from v17:
Fixed typo in patch 1 title
Addressed white-space issues reported via checkpatch
Added braces {} for two if statements to match expected coding style
Changes from v18:
Updated patches 2 and 3 based on input from dhildenb
Added comment to patch 2 describing what keeps us from reporting a bad page
Added patch to address issue with ROM devices being directly writable
---
Alexander Duyck (4):
virtio-balloon: Implement support for page poison tracking feature
linux-headers: update to contain virito-balloon free page reporting
virtio-balloon: Provide an interface for free page reporting
memory: Do not allow direct write access to rom_device regions
hw/virtio/virtio-balloon.c | 85 ++++++++++++++++++++++-
include/exec/memory.h | 4 +
include/hw/virtio/virtio-balloon.h | 3 +
include/standard-headers/linux/virtio_balloon.h | 1
4 files changed, 86 insertions(+), 7 deletions(-)
--
next reply other threads:[~2020-04-10 3:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:41 Alexander Duyck [this message]
2020-04-10 3:41 ` [PATCH v19 QEMU 1/4] virtio-balloon: Implement support for page poison tracking feature Alexander Duyck
2020-04-15 8:08 ` David Hildenbrand
2020-04-15 17:17 ` Alexander Duyck
2020-04-15 18:16 ` David Hildenbrand
2020-04-15 19:28 ` Alexander Duyck
2020-04-15 19:46 ` David Hildenbrand
2020-04-15 21:16 ` Alexander Duyck
2020-04-16 8:18 ` David Hildenbrand
2020-04-16 8:36 ` David Hildenbrand
2020-04-16 14:33 ` Michael S. Tsirkin
2020-04-16 14:55 ` David Hildenbrand
2020-04-16 18:21 ` Alexander Duyck
2020-04-16 18:33 ` David Hildenbrand
2020-04-10 3:41 ` [PATCH v19 QEMU 2/4] linux-headers: update to contain virito-balloon free page reporting Alexander Duyck
2020-04-10 3:41 ` [PATCH v19 QEMU 3/4] virtio-balloon: Provide an interface for " Alexander Duyck
2020-04-15 8:17 ` David Hildenbrand
2020-04-15 9:03 ` David Hildenbrand
2020-04-15 15:31 ` Alexander Duyck
2020-04-10 3:41 ` [PATCH v19 QEMU 4/4] memory: Do not allow direct write access to rom_device regions Alexander Duyck
2020-04-10 10:50 ` Paolo Bonzini
2020-04-13 22:48 ` Alexander Duyck
2020-04-14 7:36 ` 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=20200410033729.24738.22879.stgit@localhost.localdomain \
--to=alexander.duyck@gmail.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.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).