From: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
To: qemu-devel@nongnu.org
Cc: mopsfelder@gmail.com,
"Murilo Opsfelder Araujo" <muriloo@linux.ibm.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Eric Blake" <eblake@redhat.com>,
qemu-ppc@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/3] ppc/pnv: increase kernel size limit to 256MiB
Date: Mon, 25 Feb 2019 14:01:52 -0300 [thread overview]
Message-ID: <20190225170155.1972-1-muriloo@linux.ibm.com> (raw)
First patch increases kernel size limit to 256MiB to fit images generated with
CONFIG_DEBUG_INFO.
Second patch just fixes a misleading comment regarding initrd size limit.
Third patch uses IEC prefixes to represent size constants.
v1..v2:
Use IEC prefixes as per Eric Blake' suggestion.
Murilo Opsfelder Araujo (3):
ppc/pnv: increase kernel size limit to 256MiB
ppc/pnv: add INITRD_MAX_SIZE constant
ppc/pnv: use IEC binary prefixes to represent sizes
hw/ppc/pnv.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-25 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 17:01 Murilo Opsfelder Araujo [this message]
2019-02-25 17:01 ` [Qemu-devel] [PATCH v2 1/3] ppc/pnv: increase kernel size limit to 256MiB Murilo Opsfelder Araujo
2019-02-25 18:55 ` Cédric Le Goater
2019-02-25 17:01 ` [Qemu-devel] [PATCH v2 2/3] ppc/pnv: add INITRD_MAX_SIZE constant Murilo Opsfelder Araujo
2019-02-25 18:55 ` Cédric Le Goater
2019-02-25 17:01 ` [Qemu-devel] [PATCH v2 3/3] ppc/pnv: use IEC binary prefixes to represent sizes Murilo Opsfelder Araujo
2019-02-25 18:56 ` Cédric Le Goater
2019-02-25 18:58 ` [Qemu-devel] [PATCH v2 0/3] ppc/pnv: increase kernel size limit to 256MiB Cédric Le Goater
2019-02-25 20:52 ` [Qemu-devel] [Qemu-ppc] " 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=20190225170155.1972-1-muriloo@linux.ibm.com \
--to=mopsfelder@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=muriloo@linux.ibm.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).