From: David Gibson <david@gibson.dropbear.id.au>
To: ehabkost@redhat.com, imammedo@redhat.com
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, pbonzini@redhat.com,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCHv3 for-2.13 0/2] Helpers to obtain host page sizes for guest RAM
Date: Wed, 11 Apr 2018 17:04:16 +1000 [thread overview]
Message-ID: <20180411070418.6304-1-david@gibson.dropbear.id.au> (raw)
This series makes some small changes to make it easier to obtain the
host page size backing given portions of guest RAM. We use this in a
couple of places currently, and I have one or two more to add in some
upcoming code.
Assuming there are no objections, what should be the procedure for
staging this? Can I put it in my for-2.13 ppc tree, even though it's
technically generic code, or should it go through someone else's tree?
Changes since v2:
* Corrected grammar error in commit message
* Correct build error on non-linux hosts
Changes since v1:
* Reworked design based on Eduardo's feedback
* Split into two patches
David Gibson (2):
Make qemu_mempath_getpagesize() accept NULL
Add host_memory_backend_pagesize() helper
backends/hostmem.c | 18 ++++++++++++++++++
exec.c | 20 +++++---------------
include/sysemu/hostmem.h | 2 ++
target/ppc/kvm.c | 10 +---------
util/mmap-alloc.c | 26 ++++++++++++++------------
5 files changed, 40 insertions(+), 36 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-11 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:04 David Gibson [this message]
2018-04-11 7:04 ` [Qemu-devel] [PATCHv3 for-2.13 1/2] Make qemu_mempath_getpagesize() accept NULL David Gibson
2018-04-11 7:04 ` [Qemu-devel] [PATCHv3 for-2.13 2/2] Add host_memory_backend_pagesize() helper David Gibson
2018-04-11 13:54 ` [Qemu-devel] [PATCHv3 for-2.13 0/2] Helpers to obtain host page sizes for guest RAM Paolo Bonzini
2018-04-12 0:30 ` 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=20180411070418.6304-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).