From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: vasilis.liaskovitis@profitbricks.com, hutao@cn.fujitsu.com,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 02/16] vl: set default ram_size during variable initialization
Date: Mon, 09 Sep 2013 16:31:03 +0200 [thread overview]
Message-ID: <522DDBA7.3010405@redhat.com> (raw)
In-Reply-To: <20130909160654.7f76090f@nial.usersys.redhat.com>
Il 09/09/2013 16:06, Igor Mammedov ha scritto:
> On Fri, 02 Aug 2013 22:33:24 +0200
> Andreas Färber <afaerber@suse.de> wrote:
>
>> Am 23.07.2013 18:22, schrieb Igor Mammedov:
>>> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
>>> ---
>>> vl.c | 7 +------
>>> 1 files changed, 1 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/vl.c b/vl.c
>>> index 8190504..bf0c658 100644
>>> --- a/vl.c
>>> +++ b/vl.c
>>> @@ -2947,7 +2947,7 @@ int main(int argc, char **argv, char **envp)
>>> module_call_init(MODULE_INIT_MACHINE);
>>> machine = find_default_machine();
>>> cpu_model = NULL;
>>> - ram_size = 0;
>>> + ram_size = DEFAULT_RAM_SIZE * 1024 * 1024;
>>> snapshot = 0;
>>> cyls = heads = secs = 0;
>>> translation = BIOS_ATA_TRANSLATION_AUTO;
>>> @@ -4064,11 +4064,6 @@ int main(int argc, char **argv, char **envp)
>>> exit(1);
>>> }
>>>
>>> - /* init the memory */
>>> - if (ram_size == 0) {
>>> - ram_size = DEFAULT_RAM_SIZE * 1024 * 1024;
>>> - }
>>> -
>>> if (qemu_opts_foreach(qemu_find_opts("device"), device_help_func, NULL, 0)
>>> != 0) {
>>> exit(0);
>>
>> Commit message doesn't give any explanation why?
> it was intended as cleanup
>
>>
>> What happens with -m 0? My guess is the old code translates that to the
>> default size, where by intializing the default earlier it would stay.
> patch is broken in this aspect. It aborts on start up with -m 0
>
> The question is if -m 0 is correct value, perhaps QEMU should exit with
> error message in this case, instead of silent fallback to default?
I guess we have to keep it for backwards compatibility.
Paolo
next prev parent reply other threads:[~2013-09-09 14:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 16:22 [Qemu-devel] [PATCH 00/16 RFC v6] ACPI memory hotplug Igor Mammedov
2013-07-23 16:22 ` [Qemu-devel] [PATCH 01/16] pc: use pci_hole64 info consistently Igor Mammedov
2013-07-23 16:22 ` [Qemu-devel] [PATCH 02/16] vl: set default ram_size during variable initialization Igor Mammedov
2013-08-02 20:33 ` Andreas Färber
2013-09-09 14:06 ` Igor Mammedov
2013-09-09 14:31 ` Paolo Bonzini [this message]
2013-09-09 15:26 ` Igor Mammedov
2013-07-23 16:22 ` [Qemu-devel] [PATCH 03/16] vl: convert -m to qemu_opts_parse() Igor Mammedov
2013-07-23 17:11 ` Paolo Bonzini
2013-07-24 8:40 ` Igor Mammedov
2013-07-24 9:04 ` Paolo Bonzini
2013-07-24 9:27 ` Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 04/16] qapi: make visit_type_size fallback to type_int Igor Mammedov
2013-07-25 6:41 ` Hu Tao
2013-07-25 11:35 ` Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 05/16] qdev: Add SIZE type to qdev properties Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 06/16] dimm: implement dimm device abstraction Igor Mammedov
2013-07-25 6:52 ` Hu Tao
2013-07-23 16:23 ` [Qemu-devel] [PATCH 07/16] dimm: map DimmDevice into DimBus provided address space Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 08/16] pc: piix: make hotplug memory gap in high memory Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 09/16] pc: i440fx: add DimmBus to chipset and map it into hotplug memory region Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 10/16] dimm: add busy slot check and slot auto-allocation Igor Mammedov
2013-07-23 17:09 ` Paolo Bonzini
2013-07-24 8:36 ` Igor Mammedov
2013-07-24 9:41 ` Paolo Bonzini
2013-07-24 11:34 ` Igor Mammedov
2013-07-24 12:41 ` Paolo Bonzini
2013-07-26 7:38 ` Igor Mammedov
2013-07-26 9:26 ` Paolo Bonzini
2013-07-26 12:51 ` Igor Mammedov
2013-07-26 14:37 ` Paolo Bonzini
2013-08-03 13:56 ` Andreas Färber
2013-09-11 15:12 ` Igor Mammedov
2013-08-06 7:13 ` Markus Armbruster
2013-07-23 16:23 ` [Qemu-devel] [PATCH 11/16] dimm: add busy address check and address auto-allocation Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 12/16] dimm: introduce memory added notifier Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 13/16] acpi/piix4: introduce memory hot-plug interface QEMU<->ACPI BIOS Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 14/16] pc: ACPI BIOS: implement memory hotplug interface Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 15/16] pc: update acpi-dsdt.hex.generated and add ssdt-mem.hex.generated Igor Mammedov
2013-07-23 16:23 ` [Qemu-devel] [PATCH 16/16] pc: ACPI BIOS: reserve SRAT entry for hotplug mem hole Igor Mammedov
2013-07-24 9:52 ` [Qemu-devel] [PATCH 00/16 RFC v6] ACPI memory hotplug Hu Tao
2013-07-24 10:02 ` Igor Mammedov
2013-07-24 10:58 ` Vasilis Liaskovitis
2013-08-02 12:35 ` Anthony Liguori
2013-08-07 14:14 ` Erlon Cruz
2013-08-09 17:19 ` Anthony Liguori
2013-09-11 4:01 ` Hu Tao
2013-09-17 12:29 ` Igor Mammedov
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=522DDBA7.3010405@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vasilis.liaskovitis@profitbricks.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).