qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
	Cao jin <caoj.fnst@cn.fujitsu.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Fabiano Rosas <farosas@linux.ibm.com>, Greg Kurz <groug@kaod.org>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	Richard Henderson <rth@twiddle.net>,
	mopsfelder@gmail.com
Subject: [Qemu-devel] [PATCH 0/2] mmap-alloc: fix hugetlbfs misaligned length in ppc64
Date: Wed, 30 Jan 2019 21:36:03 -0200	[thread overview]
Message-ID: <20190130233605.22163-1-muriloo@linux.ibm.com> (raw)

The first patch unfolds parts of qemu_ram_mmap() to make it clearer.
No changes in the function behaviour.

The second one fixes the alignment of the length given to munmap().

I am pretty sure there is room for improvement, so I would love to
hear your feedback.

Thank you!

Murilo Opsfelder Araujo (2):
  mmap-alloc: unfold qemu_ram_mmap()
  mmap-alloc: fix hugetlbfs misaligned length in ppc64

 exec.c                    |  4 +--
 include/qemu/mmap-alloc.h |  2 +-
 util/mmap-alloc.c         | 73 ++++++++++++++++++++++++++-------------
 util/oslib-posix.c        |  2 +-
 4 files changed, 53 insertions(+), 28 deletions(-)

--
2.20.1

             reply	other threads:[~2019-01-30 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 23:36 Murilo Opsfelder Araujo [this message]
2019-01-30 23:36 ` [Qemu-devel] [PATCH 1/2] mmap-alloc: unfold qemu_ram_mmap() Murilo Opsfelder Araujo
2019-01-31  9:49   ` Greg Kurz
2019-02-01 13:44   ` Balamuruhan S
2019-01-30 23:36 ` [Qemu-devel] [PATCH 2/2] mmap-alloc: fix hugetlbfs misaligned length in ppc64 Murilo Opsfelder Araujo
2019-01-31  9:58   ` Greg Kurz
2019-02-01 13:43   ` Balamuruhan S
2019-02-04  0:08 ` [Qemu-devel] [PATCH 0/2] " David Gibson
2019-02-04 14:27   ` Murilo Opsfelder Araujo

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=20190130233605.22163-1-muriloo@linux.ibm.com \
    --to=muriloo@linux.ibm.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=farosas@linux.ibm.com \
    --cc=groug@kaod.org \
    --cc=mopsfelder@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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).