From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Yunqiang Su <ysu@wavecomp.com>,
Aurelien Jarno <aurelien@aurel32.net>,
qemu-devel@nongnu.org
Cc: "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH 0/7] hw/mips/malta: Rework to allow more than 2GB of RAM on 64-bit
Date: Tue, 30 Jun 2020 10:13:15 +0200 [thread overview]
Message-ID: <20200630081322.19146-1-f4bug@amsat.org> (raw)
Hi,
Following Jiaxun Yang's patch and discussion:
https://patchwork.kernel.org/patch/11416915/
- Rename the current machine as 'malta-virt' (keeping 'malta' aliased)
Suggestions for better names are welcome, maybe 'malta-unreal' or
'malta-unleashed' instead?
- Add 'malta-phys' which respects hardware restrictions (on RAM so far)
- Unleash 'malta-virt' to allow more than 2GB on 64-bit
Philippe Mathieu-Daudé (7):
hw/mips/malta: Trivial code movement
hw/mips/malta: Register the machine as a TypeInfo
hw/mips/malta: Rename 'malta' machine as 'malta-virt'
hw/mips/malta: Introduce MaltaMachineClass::max_ramsize
hw/mips/malta: Introduce the 'malta-phys' machine
hw/mips/malta: Verify malta-phys machine uses correct DIMM sizes
hw/mips/malta: Allow more than 2GB on 64-bit malta-virt
hw/mips/malta.c | 121 +++++++++++++++++++++++++++++++++++++++---------
1 file changed, 99 insertions(+), 22 deletions(-)
--
2.21.3
next reply other threads:[~2020-06-30 8:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 8:13 Philippe Mathieu-Daudé [this message]
2020-06-30 8:13 ` [PATCH 1/7] hw/mips/malta: Trivial code movement Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 2/7] hw/mips/malta: Register the machine as a TypeInfo Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 3/7] hw/mips/malta: Rename 'malta' machine as 'malta-virt' Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 4/7] hw/mips/malta: Introduce MaltaMachineClass::max_ramsize Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 5/7] hw/mips/malta: Introduce the 'malta-phys' machine Philippe Mathieu-Daudé
2020-06-30 8:54 ` Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 6/7] hw/mips/malta: Verify malta-phys machine uses correct DIMM sizes Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 7/7] hw/mips/malta: Allow more than 2GB on 64-bit malta-virt Philippe Mathieu-Daudé
2020-06-30 10:48 ` [PATCH 0/7] hw/mips/malta: Rework to allow more than 2GB of RAM on 64-bit Aleksandar Markovic
2020-06-30 10:52 ` Philippe Mathieu-Daudé
2020-06-30 10:53 ` Philippe Mathieu-Daudé
2020-06-30 11:01 ` Aleksandar Markovic
2020-06-30 11:04 ` Philippe Mathieu-Daudé
2020-06-30 11:17 ` Aleksandar Markovic
2020-06-30 11:34 ` Philippe Mathieu-Daudé
2020-06-30 11:55 ` Aleksandar Markovic
2020-06-30 11:59 ` Philippe Mathieu-Daudé
2020-06-30 12:07 ` Aleksandar Markovic
2020-06-30 13:36 ` Thomas Huth
2020-06-30 13:45 ` Philippe Mathieu-Daudé
2020-06-30 10:54 ` Aleksandar Markovic
2020-06-30 10:58 ` Philippe Mathieu-Daudé
2020-06-30 11:05 ` Aleksandar Markovic
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=20200630081322.19146-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=imammedo@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ysu@wavecomp.com \
/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).