qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Lukáš Doktor" <ldoktor@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Janosch Frank" <frankja@linux.ibm.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	"Halil Pasic" <pasic@linux.ibm.com>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH v3 1/1] vl/s390x: fixup ram sizes for compat machines
Date: Thu, 2 Apr 2020 14:05:36 +0200	[thread overview]
Message-ID: <20200402140536.1b9e7c41@redhat.com> (raw)
In-Reply-To: <e3dfecd4-2905-dc8b-92e7-2194a52ea9ea@de.ibm.com>

On Thu, 2 Apr 2020 13:42:22 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 02.04.20 13:39, Igor Mammedov wrote:
> [...]
> >>>     
> >>>> +                    "MB to match machine restrictions. Consider updating "
> >>>> +                    "the guest definition.i\n", sz / MiB, newsz / MiB);      
> >>>
> >>> also it might be better to use size_to_str() to format numbers    
> >>
> >> The text explicitly talks about 'MB'... not sure if it would be
> >> confusing if the user specified MB and ended up with GB or so in this
> >> message.  
> > 
> > MB can be dropped, since it still might not match what user specified with -m
> > it could be specified in b/kb/mb/gb over there
> > 
> > so I'd drop MB and print value size_to_str() returns
> > (it will add appropriate suffix if I'm not mistaken)
> >   
> 
> The return value of size_to_str must be freed. Arent we going overboard for such
> a message?

yep, one can use g_autofree for it.
on upside one doesn't have to bother with picking proper format string
which is far from trivial in case type mutates depending on host.

> 



  reply	other threads:[~2020-04-02 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 12:37 [PATCH v3 1/1] vl/s390x: fixup ram sizes for compat machines Christian Borntraeger
2020-04-01 12:46 ` Christian Borntraeger
2020-04-01 13:14 ` David Hildenbrand
2020-04-02  9:22   ` Cornelia Huck
2020-04-02  9:25     ` Christian Borntraeger
2020-04-02 10:27       ` Cornelia Huck
2020-04-02 10:32         ` Christian Borntraeger
2020-04-01 16:34 ` Igor Mammedov
2020-04-02  9:27   ` Cornelia Huck
2020-04-02  9:39     ` Christian Borntraeger
2020-04-02  9:43       ` Cornelia Huck
2020-04-02 11:25       ` Cornelia Huck
2020-04-02 11:32         ` Christian Borntraeger
2020-04-02 11:39     ` Igor Mammedov
2020-04-02 11:42       ` Christian Borntraeger
2020-04-02 12:05         ` Igor Mammedov [this message]
2020-04-02 12:09           ` Christian Borntraeger
2020-04-02 12:35             ` Christian Borntraeger
2020-04-02 14:18               ` Cornelia Huck
2020-04-02 15:01               ` Igor Mammedov
2020-04-02 17:48                 ` Peter Xu
2020-04-02 15:16 ` Cornelia Huck

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=20200402140536.1b9e7c41@redhat.com \
    --to=imammedo@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=ldoktor@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.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).