From: Laurent Vivier <laurent@vivier.eu>
To: Greg Kurz <groug@kaod.org>, Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] numa: Add missing \n to error message
Date: Tue, 12 Nov 2019 10:34:39 +0100 [thread overview]
Message-ID: <89950cbb-c788-36d7-8987-9e64a5591169@vivier.eu> (raw)
In-Reply-To: <157304440026.351774.14607704217028190097.stgit@bahia.lan>
Le 06/11/2019 à 13:46, Greg Kurz a écrit :
> If memory allocation fails when using -mem-path, QEMU is supposed to print
> out a message to indicate that fallback to anonymous RAM is deprecated. This
> is done with error_printf() which does output buffering. As a consequence,
> the message is only printed at the next flush, eg. when quiting QEMU, and
> it also lacks a trailing newline:
>
> qemu-system-ppc64: unable to map backing store for guest RAM: Cannot allocate memory
> qemu-system-ppc64: warning: falling back to regular RAM allocation
> QEMU 4.1.50 monitor - type 'help' for more information
> (qemu) q
> This is deprecated. Make sure that -mem-path specified path has sufficient resources to allocate -m specified RAM amountgreg@boss02:~/Work/qemu/qemu-spapr$
>
> Add the missing \n to fix both issues.
>
> Fixes: cb79224b7e4b "deprecate -mem-path fallback to anonymous RAM"
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> hw/core/numa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/core/numa.c b/hw/core/numa.c
> index 038c96d4abc6..e3332a984f7c 100644
> --- a/hw/core/numa.c
> +++ b/hw/core/numa.c
> @@ -503,7 +503,7 @@ static void allocate_system_memory_nonnuma(MemoryRegion *mr, Object *owner,
> warn_report("falling back to regular RAM allocation");
> error_printf("This is deprecated. Make sure that -mem-path "
> " specified path has sufficient resources to allocate"
> - " -m specified RAM amount");
> + " -m specified RAM amount\n");
> /* Legacy behavior: if allocation failed, fall back to
> * regular RAM allocation.
> */
>
>
Applied to my trivial-patches branch.
Thanks,
Laurent
prev parent reply other threads:[~2019-11-12 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:46 [PATCH] numa: Add missing \n to error message Greg Kurz
2019-11-06 12:55 ` Greg Kurz
2019-11-06 13:01 ` Laurent Vivier
2019-11-06 14:12 ` Greg Kurz
2019-11-06 14:20 ` Laurent Vivier
2019-11-06 14:35 ` Philippe Mathieu-Daudé
2019-11-06 16:55 ` Markus Armbruster
2019-11-06 17:04 ` Laurent Vivier
2019-11-12 9:34 ` Laurent Vivier [this message]
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=89950cbb-c788-36d7-8987-9e64a5591169@vivier.eu \
--to=laurent@vivier.eu \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=marcel@redhat.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 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).