From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: peter.maydell@linaro.org, jan.kiszka@siemens.com,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] Funny -m arguments can crash
Date: Mon, 13 Aug 2012 17:10:17 +0300 [thread overview]
Message-ID: <20120813141017.GB11194@redhat.com> (raw)
In-Reply-To: <5029096E.5020607@redhat.com>
On Mon, Aug 13, 2012 at 05:04:30PM +0300, Avi Kivity wrote:
> On 08/13/2012 05:02 PM, Gleb Natapov wrote:
>
> >> IMO we need to fix CMOS reporting.
> >>
> >> (technically we shouldn't touch CMOS NVRAM at all; seabios should
> >> discover memory size via fwcfg and program it itself. But it's
> >> pointless to change it now)
> >>
> > Chipset we emulate does not support all those crazy memory values you
> > can give to -m.
>
> Our chipset is a 440fx enhanced with fwcfg and other goodies, not a
> plain 440fx.
>
It has registers to program DIMM slots configs. fwcfg does not enhanced
it in any way. And you cannot program more than 4G memory there may be
even less. So what do you mean by "program it itself"? Program CMOS
itself? (What for? QEMU does not care). Or program 440fx DIMM config?
> But it's true it probably doesn't support 82.66642kB RAM.
It does not support much less exotic 4G.
--
Gleb.
next prev parent reply other threads:[~2012-08-13 14:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 11:49 [Qemu-devel] Funny -m arguments can crash Markus Armbruster
2012-07-27 19:00 ` Blue Swirl
2012-07-28 6:41 ` Markus Armbruster
2012-07-28 8:29 ` Blue Swirl
2012-07-30 12:56 ` Markus Armbruster
2012-07-30 15:05 ` Blue Swirl
2012-08-08 9:04 ` Markus Armbruster
2012-08-08 9:16 ` Peter Maydell
2012-08-08 10:02 ` Markus Armbruster
2012-08-08 9:48 ` Avi Kivity
2012-08-13 13:41 ` Markus Armbruster
2012-08-13 13:56 ` Avi Kivity
2012-08-13 14:02 ` Gleb Natapov
2012-08-13 14:04 ` Avi Kivity
2012-08-13 14:10 ` Gleb Natapov [this message]
2012-08-13 20:35 ` Blue Swirl
2012-08-19 19:26 ` Kevin O'Connor
2012-08-13 14:19 ` Anthony Liguori
2012-08-13 14:46 ` Markus Armbruster
2012-08-14 8:44 ` Markus Armbruster
2012-08-14 10:20 ` Avi Kivity
2012-08-14 10:44 ` Jan Kiszka
2012-08-14 10:51 ` Avi Kivity
2012-08-14 11:01 ` Jan Kiszka
2012-08-14 13:16 ` Avi Kivity
2012-08-14 13:25 ` Jan Kiszka
2012-08-14 13:42 ` Avi Kivity
2012-08-14 11:12 ` Markus Armbruster
2012-08-14 13:25 ` Avi Kivity
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=20120813141017.GB11194@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).