qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eric Blake <eblake@redhat.com>, Andrew Jones <drjones@redhat.com>,
	qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] numa: clarify error message when node index is out of range in -numa dist, ...
Date: Wed, 16 May 2018 16:32:34 +0200	[thread overview]
Message-ID: <20180516163234.79a6e692@redhat.com> (raw)
In-Reply-To: <87eficu8g1.fsf@dusky.pond.sub.org>

On Tue, 15 May 2018 19:37:02 +0200
Markus Armbruster <armbru@redhat.com> wrote:

> Eric Blake <eblake@redhat.com> writes:
> 
> > On 05/15/2018 10:26 AM, Andrew Jones wrote:  
> >> On Tue, May 15, 2018 at 04:48:33PM +0200, Igor Mammedov wrote:  
> >>> When using following CLI:
> >>>    -numa dist,src=128,dst=1,val=20
> >>> user gets a rather confusing error message:
> >>>     "Invalid node 128, max possible could be 128"
> >>>
> >>> Where 128 is number of nodes that QEMU supports (MAX_NODES),
> >>> while src/dst is an index up to that limit, so it should be
> >>> MAX_NODES - 1 in error message.
> >>> Make error message to explicitly state valid range for node
> >>> index to be more clear.
> >>>
> >>> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> >>> Reviewed-by: Andrew Jones <drjones@redhat.com>
> >>> ---  
> >  
> >>>       if (src >= MAX_NODES || dst >= MAX_NODES) {
> >>>           error_setg(errp,
> >>> -                   "Invalid node %d, max possible could be %d",
> >>> -                   MAX(src, dst), MAX_NODES);
> >>> +                   "Invalid node %d, The valid node range is [0 - %d]",  
> >>                                        ^ should be a '.'
> >>
> >> And maybe need a '.' at the end of the second sentence too, as it's not
> >> an error phrase, but a real sentence.
> >>  
> >>> +                   MAX(src, dst), MAX_NODES - 1);
> >>>          return;
> >>>      }  
> >
> > Actually, error_setg() is documented as taking a single phrase (no '.'
> > included), and that if you need a second sentence, it's better to use
> > error_append_hint(). 
well, using append_hint makes it less readable, before using it we get following error:

$ qemu-system-x86_64 -numa dist,src=128,dst=1,val=20
qemu-system-x86_64: -numa dist,src=128,dst=1,val=20: Invalid node 128, The valid node range is [0 - 127]
$

after using it we get:
  
$ qemu-system-x86_64 -numa dist,src=128,dst=1,val=20
qemu-system-x86_64: -numa dist,src=128,dst=1,val=20: Invalid node value 128
The valid node range is [0 - 127]$ 

i.e. an extra newline in the middle of error message and looses automatic
newline at the end so the shell prompt continues error message


> Correct.  Providing help on valid values is exactly what
> error_append_hint() is for.
> 
> >                       Maybe Markus has an opinion on the best way to
> > word this error message.  
> 
> Yes: "Parameter 'src' expects an integer between 0 and 127"
> 
> Referring to an erroneous key=value by value is not nice.  What if the
> value occurs in multiple places, and is valid in at least one?  key is
> there, it's unique[*], so use it.
> 
> 
> [*] Except in the few places that use repeated keys to form lists.  Ugh.

  reply	other threads:[~2018-05-16 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 14:48 [Qemu-devel] [PATCH v2] numa: clarify error message when node index is out of range in -numa dist, Igor Mammedov
2018-05-15 15:26 ` Andrew Jones
2018-05-15 15:50   ` [Qemu-devel] [PATCH v3] " Igor Mammedov
2018-05-15 16:47   ` [Qemu-devel] [PATCH v2] " Eric Blake
2018-05-15 17:37     ` Markus Armbruster
2018-05-16 14:32       ` Igor Mammedov [this message]
2018-05-16 14:46         ` Eric Blake

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=20180516163234.79a6e692@redhat.com \
    --to=imammedo@redhat.com \
    --cc=armbru@redhat.com \
    --cc=drjones@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@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).