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

On 11/04/2018 09:04, David Gibson wrote:
> 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?

Yes, go ahead:

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

On Wed, Apr 11, 2018 at 03:54:20PM +0200, Paolo Bonzini wrote:
> On 11/04/2018 09:04, David Gibson wrote:
> > 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?
> 
> Yes, go ahead:
> 
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>

I'm assuming that's an ack to putting it through my tree.

In which case, done, thanks.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson