From: Igor Mammedov <imammedo@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: qemu-trivial@nongnu.org, luonengjun@huawei.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH v2] vl: Print maxmem in hex format for error message
Date: Tue, 16 Sep 2014 11:12:58 +0200 [thread overview]
Message-ID: <20140916111258.7f842ab8@nial.usersys.redhat.com> (raw)
In-Reply-To: <1410853532-9956-1-git-send-email-zhang.zhanghailiang@huawei.com>
On Tue, 16 Sep 2014 15:45:32 +0800
zhanghailiang <zhang.zhanghailiang@huawei.com> wrote:
> In error message, maxmem is printed in Dec but ram_size in Hex.
> It is better to print them in same format.
> Also use error_report instead of fprintf.
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
> v2:
> - Remove redundant "qemu:" in error message, for error_report already prepend
> a variation of "qemu" (comment of Eric Blake)
> ---
> vl.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index 5db0d08..71a831b 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -3358,34 +3358,34 @@ int main(int argc, char **argv, char **envp)
>
> sz = qemu_opt_get_size(opts, "maxmem", 0);
> if (sz < ram_size) {
> - fprintf(stderr, "qemu: invalid -m option value: maxmem "
> - "(%" PRIu64 ") <= initial memory ("
> - RAM_ADDR_FMT ")\n", sz, ram_size);
> + error_report("invalid -m option value: maxmem "
> + "(0x%" PRIx64 ") <= initial memory (0x"
> + RAM_ADDR_FMT ")", 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 ("
> + error_report("invalid -m option value: maxmem "
> + "(0x%" PRIx64 ") more than initial memory (0x"
> RAM_ADDR_FMT ") but no hotplug slots where "
> - "specified\n", sz, ram_size);
> + "specified", sz, ram_size);
> exit(EXIT_FAILURE);
> }
>
> if ((sz <= ram_size) && slots) {
> - fprintf(stderr, "qemu: invalid -m option value: %"
> + error_report("invalid -m option value: %"
> PRIu64 " hotplug slots where specified but "
> - "maxmem (%" PRIu64 ") <= initial memory ("
> - RAM_ADDR_FMT ")\n", slots, sz, ram_size);
> + "maxmem (0x%" PRIx64 ") <= initial memory (0x"
> + RAM_ADDR_FMT ")", 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");
> + error_report("invalid -m option value: missing "
indent error
> + "'%s' option", slots_str ? "maxmem" : "slots");
> exit(EXIT_FAILURE);
> }
> break;
with above fixed,
Reviewed-By: Igor Mammedov <imammedo@redhat.com>
next prev parent reply other threads:[~2014-09-16 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 7:45 [Qemu-devel] [PATCH v2] vl: Print maxmem in hex format for error message zhanghailiang
2014-09-16 9:12 ` Igor Mammedov [this message]
2014-09-16 9:23 ` 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=20140916111258.7f842ab8@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).