qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Pankaj Gupta" <pankaj.gupta@cloud.ionos.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Li Zhang" <li.zhang@cloud.ionos.com>
Subject: Re: [PATCH] physmem: improve ram size error messages
Date: Fri, 6 Nov 2020 14:58:25 +0100	[thread overview]
Message-ID: <CAM9Jb+izw67vqXQ-tOCuNugJeBUREopYuh0XHw5QZvKXP278fw@mail.gmail.com> (raw)
In-Reply-To: <20201022111302.8105-1-pankaj.gupta.linux@gmail.com>

Ping

>  Ram size mismatch condition logs below message.
>
>    "Length mismatch: pc.ram: 0x80000000 in != 0x180000000: Invalid argument"
>
>  This patch improves the readability of error messages.
>  Removed the superflous "in" and changed "Length" to "Size".
>
> Signed-off-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
> Reported-by: Li Zhang <li.zhang@cloud.ionos.com>
> ---
>  softmmu/physmem.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/softmmu/physmem.c b/softmmu/physmem.c
> index e319fb2a1e..8da184f4a6 100644
> --- a/softmmu/physmem.c
> +++ b/softmmu/physmem.c
> @@ -1756,15 +1756,15 @@ int qemu_ram_resize(RAMBlock *block, ram_addr_t newsize, Error **errp)
>
>      if (!(block->flags & RAM_RESIZEABLE)) {
>          error_setg_errno(errp, EINVAL,
> -                         "Length mismatch: %s: 0x" RAM_ADDR_FMT
> -                         " in != 0x" RAM_ADDR_FMT, block->idstr,
> +                         "Size mismatch: %s: 0x" RAM_ADDR_FMT
> +                         " != 0x" RAM_ADDR_FMT, block->idstr,
>                           newsize, block->used_length);
>          return -EINVAL;
>      }
>
>      if (block->max_length < newsize) {
>          error_setg_errno(errp, EINVAL,
> -                         "Length too large: %s: 0x" RAM_ADDR_FMT
> +                         "Size too large: %s: 0x" RAM_ADDR_FMT
>                           " > 0x" RAM_ADDR_FMT, block->idstr,
>                           newsize, block->max_length);
>          return -EINVAL;
> --
> 2.20.1
>


  reply	other threads:[~2020-11-06 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 11:13 [PATCH] physmem: improve ram size error messages Pankaj Gupta
2020-11-06 13:58 ` Pankaj Gupta [this message]
2020-11-09 14:18 ` Philippe Mathieu-Daudé
2020-11-09 14:24 ` Paolo Bonzini

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=CAM9Jb+izw67vqXQ-tOCuNugJeBUREopYuh0XHw5QZvKXP278fw@mail.gmail.com \
    --to=pankaj.gupta.linux@gmail.com \
    --cc=li.zhang@cloud.ionos.com \
    --cc=pankaj.gupta@cloud.ionos.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@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).