All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] numa: Make deprecation warnings conditional on !qtest_enabled()
Date: Wed, 3 Jul 2019 09:49:50 +0200	[thread overview]
Message-ID: <20190703094950.56ea30cd@redhat.com> (raw)
In-Reply-To: <20190702215726.23661-1-ehabkost@redhat.com>

On Tue,  2 Jul 2019 18:57:26 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:

> This will help us avoid spurious warnings during "make check".
> 
> Note that this will silence the warnings generated by
> tests/numa-test, but not the ones generated by
> tests/bios-tables-test.  We still need to change
> tests/bios-tables-test to use "-numa ...,memdev=" to silence
> these warnings.
> 
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

> ---
>  numa.c | 15 ++++++++++-----
>  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/numa.c b/numa.c
> index 1824c4e049..4988f25cd4 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -35,6 +35,7 @@
>  #include "qapi/qapi-visit-misc.h"
>  #include "hw/boards.h"
>  #include "sysemu/hostmem.h"
> +#include "sysemu/qtest.h"
>  #include "hw/mem/pc-dimm.h"
>  #include "hw/mem/memory-device.h"
>  #include "qemu/option.h"
> @@ -117,8 +118,10 @@ static void parse_numa_node(MachineState *ms, NumaNodeOptions *node,
>  
>      if (node->has_mem) {
>          numa_info[nodenr].node_mem = node->mem;
> -        warn_report("Parameter -numa node,mem is deprecated,"
> -                    " use -numa node,memdev instead");
> +        if (!qtest_enabled()) {
> +            warn_report("Parameter -numa node,mem is deprecated,"
> +                        " use -numa node,memdev instead");
> +        }
>      }
>      if (node->has_memdev) {
>          Object *o;
> @@ -405,9 +408,11 @@ void numa_complete_configuration(MachineState *ms)
>          if (i == nb_numa_nodes) {
>              assert(mc->numa_auto_assign_ram);
>              mc->numa_auto_assign_ram(mc, numa_info, nb_numa_nodes, ram_size);
> -            warn_report("Default splitting of RAM between nodes is deprecated,"
> -                        " Use '-numa node,memdev' to explictly define RAM"
> -                        " allocation per node");
> +            if (!qtest_enabled()) {
> +                warn_report("Default splitting of RAM between nodes is deprecated,"
> +                            " Use '-numa node,memdev' to explictly define RAM"
> +                            " allocation per node");
> +            }
>          }
>  
>          numa_total = 0;



  reply	other threads:[~2019-07-03  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 21:57 [Qemu-devel] [PATCH] numa: Make deprecation warnings conditional on !qtest_enabled() Eduardo Habkost
2019-07-03  7:49 ` Igor Mammedov [this message]
2019-07-03 15:47 ` [Qemu-devel] [PATCH v2] tests: numa-test: use -numa memdev option instead of legacy 'mem' option Igor Mammedov
2019-07-03 19:37   ` Eduardo Habkost
2019-07-04  7:33     ` Igor Mammedov
2019-07-08 22:25       ` Eduardo Habkost
2019-07-09 14:51         ` Igor Mammedov
2019-07-03 19:57   ` no-reply

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=20190703094950.56ea30cd@redhat.com \
    --to=imammedo@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.