From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Igor Mammedov <imammedo@redhat.com>, Helge Deller <deller@gmx.de>,
Sven Schnelle <svens@stackframe.org>,
qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: [PATCH v2 0/3] hw/hppa/machine: Restrict the total memory size to 3GB
Date: Thu, 9 Jan 2020 01:05:22 +0100 [thread overview]
Message-ID: <20200109000525.24744-1-f4bug@amsat.org> (raw)
Following the discussion of Igor's patch "hppa: allow max
ram size upto 4Gb" [1] I tried to simplify the current
code so Igor's series doesn't change the CLI with this
machine.
v2: Simplify by limiting to 3GB (Helge review)
[1] https://www.mail-archive.com/qemu-devel@nongnu.org/msg667903.html
[2] https://www.mail-archive.com/qemu-devel@nongnu.org/msg669309.html
Philippe Mathieu-Daudé (3):
hw/hppa/machine: Correctly check the firmware is in PDC range
hw/hppa/machine: Restrict the total memory size to 3GB
hw/hppa/machine: Map the PDC memory region with higher priority
hw/hppa/machine.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
--
2.21.1
next reply other threads:[~2020-01-09 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 0:05 Philippe Mathieu-Daudé [this message]
2020-01-09 0:05 ` [PATCH v2 1/3] hw/hppa/machine: Correctly check the firmware is in PDC range Philippe Mathieu-Daudé
2020-01-09 0:05 ` [PATCH v2 2/3] hw/hppa/machine: Restrict the total memory size to 3GB Philippe Mathieu-Daudé
2020-01-09 0:05 ` [PATCH v2 3/3] hw/hppa/machine: Map the PDC memory region with higher priority Philippe Mathieu-Daudé
2020-01-09 2:20 ` [PATCH v2 0/3] hw/hppa/machine: Restrict the total memory size to 3GB Richard Henderson
2020-01-09 6:48 ` Helge Deller
2020-01-17 1:03 ` Richard Henderson
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=20200109000525.24744-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=deller@gmx.de \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=svens@stackframe.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).