From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, luonengjun@huawei.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] vl: Print maxmem in hex format for error message
Date: Tue, 16 Sep 2014 10:51:55 +0800 [thread overview]
Message-ID: <5417A5CB.4010901@huawei.com> (raw)
In-Reply-To: <5417A394.7050104@redhat.com>
On 2014/9/16 10:42, Eric Blake wrote:
> On 09/15/2014 08:36 PM, zhanghailiang 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>
>> ---
>> vl.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/vl.c b/vl.c
>> index 5db0d08..ea60f93 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("qemu: 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("qemu: invalid -m option value: maxmem "
>
> doesn't error_report already prepend a variation of "qemu", making your
> "qemu: " redundant?
>
Yes, you are right, i will remove them, thanks;)
WARNING: multiple messages have this Message-ID (diff)
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, luonengjun@huawei.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH] vl: Print maxmem in hex format for error message
Date: Tue, 16 Sep 2014 10:51:55 +0800 [thread overview]
Message-ID: <5417A5CB.4010901@huawei.com> (raw)
In-Reply-To: <5417A394.7050104@redhat.com>
On 2014/9/16 10:42, Eric Blake wrote:
> On 09/15/2014 08:36 PM, zhanghailiang 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>
>> ---
>> vl.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/vl.c b/vl.c
>> index 5db0d08..ea60f93 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("qemu: 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("qemu: invalid -m option value: maxmem "
>
> doesn't error_report already prepend a variation of "qemu", making your
> "qemu: " redundant?
>
Yes, you are right, i will remove them, thanks;)
next prev parent reply other threads:[~2014-09-16 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 2:36 [Qemu-trivial] [PATCH] vl: Print maxmem in hex format for error message zhanghailiang
2014-09-16 2:36 ` [Qemu-devel] " zhanghailiang
2014-09-16 2:42 ` [Qemu-trivial] " Eric Blake
2014-09-16 2:42 ` Eric Blake
2014-09-16 2:51 ` zhanghailiang [this message]
2014-09-16 2:51 ` 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=5417A5CB.4010901@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=eblake@redhat.com \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.