All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: luonengjun@huawei.com, qemu-devel@nongnu.org,
	aliguori@amazon.com, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH 1/2] vl: Fix the confused logic for '-m' option
Date: Fri, 12 Sep 2014 15:52:09 +0200	[thread overview]
Message-ID: <20140912155209.22ffc535@nial.usersys.redhat.com> (raw)
In-Reply-To: <1410501536-1516-1-git-send-email-zhang.zhanghailiang@huawei.com>

On Fri, 12 Sep 2014 13:58:55 +0800
zhanghailiang <zhang.zhanghailiang@huawei.com> wrote:

> It should be valid for the follow configure:
> -m 256,slots=0
> -m 256,maxmem=256M
Doc comment/help says that slots & maxmem must be in pair so above is not valid CLI
"
-m[emory] [size=]megs[,slots=n,maxmem=size]
                configure guest RAM
                size: initial amount of guest memory (default: 128MiB)
                slots: number of hotplug slots (default: none)
                maxmem: maximum amount of guest memory (default: none)
"

> -m 256,slots=0,maxmem=256M
> -m 256,slots=x,maxmem=y  where x > 0 and y > 256M
s/-m 256,slots=x,maxmem=y  where x > 0 and y > 256M/-m z,slots=x,maxmem=y  where x > 0 and y > z(M)

> 
> Fix the confused code logic and use error_report instead of fprintf.
> 
> Printing the maxmem in hex, same with ram_size.
> 
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
>  vl.c | 46 +++++++++++++++++++++++++++-------------------
>  1 file changed, 27 insertions(+), 19 deletions(-)
> 
> diff --git a/vl.c b/vl.c
> index 9c9acf5..f547405 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -3306,6 +3306,7 @@ int main(int argc, char **argv, char **envp)
>                  break;
>              case QEMU_OPTION_m: {
>                  uint64_t sz;
> +                uint64_t slots;
>                  const char *mem_str;
>                  const char *maxmem_str, *slots_str;
>  
> @@ -3353,40 +3354,47 @@ int main(int argc, char **argv, char **envp)
>  
>                  maxmem_str = qemu_opt_get(opts, "maxmem");
>                  slots_str = qemu_opt_get(opts, "slots");
> -                if (maxmem_str && slots_str) {
> -                    uint64_t slots;
> -
> +                if (maxmem_str) {
>                      sz = qemu_opt_get_size(opts, "maxmem", 0);
> +                }
> +                if (slots_str) {
> +                    slots = qemu_opt_get_number(opts, "slots", 0);
> +                }
> +                if (maxmem_str && slots_str) {
>                      if (sz < ram_size) {
> -                        fprintf(stderr, "qemu: invalid -m option value: maxmem "
> -                                "(%" PRIu64 ") <= initial memory ("
> +                        error_report("qemu: invalid -m option value: maxmem "
> +                                "(%" PRIx64 ") < initial memory ("
it may be worth to add 0x before hex number,
maybe printing maxmem_str instead of number here would be better, since
user would able to match easily maxmem value and what is printed in error message.


>                                  RAM_ADDR_FMT ")\n", sz, ram_size);
>                          exit(EXIT_FAILURE);
>                      }
> -
> -                    slots = qemu_opt_get_number(opts, "slots", 0);
> -                    if ((sz > ram_size) && !slots) {
> -                        fprintf(stderr, "qemu: invalid -m option value: maxmem "
> -                                "(%" PRIu64 ") more than initial memory ("
> +                    if (!slots && (sz != ram_size)) {
it would report wrong message in case of "-m 256,slots=0,maxmem=128M"

> +                        error_report("qemu: invalid -m option value: maxmem "
> +                                "(%" PRIx64 ") more than initial memory ("
>                                  RAM_ADDR_FMT ") but no hotplug slots where "
>                                  "specified\n", sz, ram_size);
>                          exit(EXIT_FAILURE);
>                      }
> -
> -                    if ((sz <= ram_size) && slots) {
> -                        fprintf(stderr, "qemu: invalid -m option value:  %"
> +                    if (slots && (sz == ram_size)) {
What takes care about the case "-m 256,slots=1,maxmem=128M"?

> +                        error_report("qemu: invalid -m option value:  %"
>                                  PRIu64 " hotplug slots where specified but "
> -                                "maxmem (%" PRIu64 ") <= initial memory ("
> +                                "maxmem (%" PRIx64 ") = initial memory ("
>                                  RAM_ADDR_FMT ")\n", slots, sz, ram_size);
>                          exit(EXIT_FAILURE);
>                      }
>                      maxram_size = sz;
>                      ram_slots = slots;
> -                } else if ((!maxmem_str && slots_str) ||
> -                           (maxmem_str && !slots_str)) {
> -                    fprintf(stderr, "qemu: invalid -m option value: missing "
> -                            "'%s' option\n", slots_str ? "maxmem" : "slots");
> -                    exit(EXIT_FAILURE);
> +                } else if (!maxmem_str && slots_str) {
> +                    if (slots > 0) {
> +                        error_report("qemu: invalid -m option value: missing "
> +                                "'maxmem' option\n");
> +                        exit(EXIT_FAILURE);
> +                    }
> +                } else if (maxmem_str && !slots_str) {
> +                    if (sz != ram_size) {
> +                        error_report("qemu: invalid -m option value: missing "
> +                                "'slot' option\n");
> +                        exit(EXIT_FAILURE);
> +                    }
>                  }
>                  break;
>              }

  parent reply	other threads:[~2014-09-12 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  5:58 [Qemu-devel] [PATCH 1/2] vl: Fix the confused logic for '-m' option zhanghailiang
2014-09-12  6:46 ` Li Liu
2014-09-12 13:52 ` Igor Mammedov [this message]
2014-09-15  7:15   ` zhanghailiang

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=20140912155209.22ffc535@nial.usersys.redhat.com \
    --to=imammedo@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=luonengjun@huawei.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.