qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Krempa <pkrempa@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2 1/2] vl.c: Fix error messages when parsing maxmem parameters
Date: Wed, 28 Jan 2015 17:21:28 +0100	[thread overview]
Message-ID: <20150128162128.GD5003@andariel.home> (raw)
In-Reply-To: <20150128132941.6c593d29@nial.brq.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

On Wed, Jan 28, 2015 at 13:29:41 +0100, Igor Mammedov wrote:
> On Wed, 28 Jan 2015 09:35:03 +0100
> Peter Krempa <pkrempa@redhat.com> wrote:
> 
> > Produce more human readable error messages and fix few spelling
> > mistakes.
> > 
> > Also remove a redundant check for the max memory size.
> > 
> > Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> > ---
> > 
> > Notes:
> >     Version 2:
> >     - fixed spacing in error message
> >     - changed control flow to allow maxmem == ram_size in case slots == 0
> > 
> >  vl.c | 34 ++++++++++++++++------------------
> >  1 file changed, 16 insertions(+), 18 deletions(-)
> > 
> > diff --git a/vl.c b/vl.c
> > index 983259b..5a012f4 100644
> > --- a/vl.c
> > +++ b/vl.c
> > @@ -2694,29 +2694,27 @@ static void set_memory_options(uint64_t *ram_slots, ram_addr_t *maxram_size)
> >          uint64_t slots;
> > 
> >          sz = qemu_opt_get_size(opts, "maxmem", 0);
> > +        slots = qemu_opt_get_number(opts, "slots", 0);
> >          if (sz < ram_size) {
> > -            error_report("invalid -m option value: maxmem "
> > -                    "(0x%" PRIx64 ") <= initial memory (0x"
> > -                    RAM_ADDR_FMT ")", sz, ram_size);
> > +            error_report("invalid value of -m option maxmem: "
> > +                         "maximum memory size (0x%" PRIx64 ") must at least "
> typo??
> "must be at least"
> 

Hmm, right. Should I respin the series to fix it?

Peter

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-01-28 16:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  8:35 [Qemu-devel] [PATCHv2 0/2] pc: Fix startup with memory hotplug enabled Peter Krempa
2015-01-28  8:35 ` [Qemu-devel] [PATCHv2 1/2] vl.c: Fix error messages when parsing maxmem parameters Peter Krempa
2015-01-28 12:29   ` Igor Mammedov
2015-01-28 16:21     ` Peter Krempa [this message]
2015-01-28 17:01       ` Igor Mammedov
2015-01-28 18:32         ` Markus Armbruster
2015-01-28  8:35 ` [Qemu-devel] [PATCHv2 2/2] pc: memory: Validate alignment of maxram_size to page size Peter Krempa

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=20150128162128.GD5003@andariel.home \
    --to=pkrempa@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.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).