From: David Gibson <david@gibson.dropbear.id.au>
To: benh@kernel.crashing.org, paulus@samba.org
Cc: lvivier@redhat.com, thuth@redhat.com, agraf@suse.de,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
bharata@linux.vnet.ibm.com,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [RFC 0/3] Draft implementation of HPT resizing (qemu side)
Date: Mon, 18 Jan 2016 16:44:38 +1100 [thread overview]
Message-ID: <1453095881-16704-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Here is a draft qemu implementation of my proposed PAPR extension for
allowing runtime resizing of a KVM/ppc64 guest's hash page table.
That in turn will allow for more flexible memory hotplug.
This should work with the guest kernel side patches I also posted
recently [1].
Still required to make this into a full implementation:
* Guest needs to auto-resize HPT on memory hotplug events
* qemu needs to allocate HPT size based on current rather than
maximum memory if the guest is HPT resize aware
* KVM host side implementation
* PAPR standardization
[1] http://thread.gmane.org/gmane.linux.ports.ppc.embedded/90392
David Gibson (3):
pseries: Stub hypercalls for HPT resizing
pseries: Implement HPT resizing
pseries: Advertise HPT resize capability
hw/ppc/spapr.c | 5 +-
hw/ppc/spapr_hcall.c | 331 ++++++++++++++++++++++++++++++++++++++++++++++++
include/hw/ppc/spapr.h | 9 +-
target-ppc/mmu-hash64.h | 4 +
trace-events | 2 +
5 files changed, 348 insertions(+), 3 deletions(-)
--
2.5.0
next reply other threads:[~2016-01-18 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 5:44 David Gibson [this message]
2016-01-18 5:44 ` [Qemu-devel] [RFC 1/3] pseries: Stub hypercalls for HPT resizing David Gibson
2016-01-18 5:44 ` [Qemu-devel] [RFC 2/3] pseries: Implement " David Gibson
2016-01-18 5:44 ` [Qemu-devel] [RFC 3/3] pseries: Advertise HPT resize capability David Gibson
2016-01-18 5:45 ` [Qemu-devel] [RFC 0/3] Draft implementation of HPT resizing (qemu side) David Gibson
2016-01-19 7:48 ` Bharata B Rao
2016-01-19 11:02 ` David Gibson
2016-01-28 21:04 ` Alexander Graf
2016-01-28 22:09 ` Paul Mackerras
2016-01-29 2:47 ` David Gibson
2016-01-29 6:18 ` Alexander Graf
2016-01-29 23:11 ` David Gibson
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=1453095881-16704-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=lvivier@redhat.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).