From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Set memory size per machine
Date: Sun, 20 Apr 2008 19:27:55 +0200 [thread overview]
Message-ID: <fb249edb0804201027v2efdc356uac7a9375fb136c6b@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580804192357h362f016ka71549a71aad96d0@mail.gmail.com>
On 20/04/2008, Blue Swirl <blauwirbel@gmail.com> wrote:
> On 4/20/08, andrzej zaborowski <balrogg@gmail.com> wrote:
> > This patch lets a machine decide on the amount of space it'll use in
> > phys_ram_base in addition to that specified with "-m", default is
> > zero. Currently that amount was the maximum of BIOS size + VGA RAM
> > size over all machines of all archs, and that was not enough for the
> > MusicPal and even if extended it may be not enough for a machine
> > supported in the future.
> >
> > This also lets a machine OR the specified value with a RAMSIZE_FIXED
> > flag to indicate that it ignores the value given with "-m" (true for
> > almost half of the machines in qemu).
>
> In addition to minimum, higher level code could handle the maximum
> memory size supported, like sun4m.c does currently. Then I'd use
> ram_min and ram_max or something similar.
ram_require doesn't set a minimum for the "-m" value, this value is
passed as is to machine->init. It only set the maximum RAM the
machine can use in addition to that specified with "-m".
I can add ram_min and ram_max but that would as far as I can tell be
used only by sun4m.c at the moment.
>
> > +#define RAMSIZE_FIXED (1 << 0)
> > + size_t ram_require;
> > + const char *boot_letters;
>
> boot_letters?
Oops, this was an idea I gave up (for this patch) for QEMUMachine to
optionally specify allowed -boot values against main() could validate.
Regards
--
Please do not print this email unless absolutely necessary. Spread
environmental awareness.
prev parent reply other threads:[~2008-04-20 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 3:33 [Qemu-devel] [PATCH] Set memory size per machine andrzej zaborowski
2008-04-20 6:57 ` Blue Swirl
2008-04-20 17:27 ` andrzej zaborowski [this message]
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=fb249edb0804201027v2efdc356uac7a9375fb136c6b@mail.gmail.com \
--to=balrogg@gmail.com \
--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).