All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Li Zhang <lizhang@suse.de>
Cc: eduardo@habkost.net, wangyanan55@huawei.com, f4bug@amsat.org,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] numa: check mem or memdev in numa configuration
Date: Thu, 17 Feb 2022 11:25:39 +0100	[thread overview]
Message-ID: <20220217112539.43ddd55f@redhat.com> (raw)
In-Reply-To: <65f05997-dd2b-c30d-5c95-8e832f21afa0@suse.de>

On Thu, 17 Feb 2022 10:38:32 +0100
Li Zhang <lizhang@suse.de> wrote:

> On 2/17/22 10:10 AM, Igor Mammedov wrote:
> > On Wed, 16 Feb 2022 17:36:13 +0100
> > Li Zhang <lizhang@suse.de> wrote:
> >   
> >> If there is no mem or memdev in numa configuration, it always
> >> reports the error as the following:
> >>
> >> total memory for NUMA nodes (0x0) should equal RAM size (0x100000000)
> >>
> >> This error is confusing and the reason is that total memory of numa nodes
> >> is always 0 if there is no mem or memdev in numa configuration.
> >> So it's better to check mem or memdev in numa configuration.
> >>
> >> Signed-off-by: Li Zhang <lizhang@suse.de>
> >> ---
> >>   hw/core/numa.c | 5 +++++
> >>   1 file changed, 5 insertions(+)
> >>
> >> diff --git a/hw/core/numa.c b/hw/core/numa.c
> >> index 1aa05dcf42..11cbec51eb 100644
> >> --- a/hw/core/numa.c
> >> +++ b/hw/core/numa.c
> >> @@ -132,6 +132,11 @@ static void parse_numa_node(MachineState *ms, NumaNodeOptions *node,
> >>   
> >>       have_memdevs = have_memdevs ? : node->has_memdev;
> >>       have_mem = have_mem ? : node->has_mem;
> >> +    if (!node->has_memdev && !node->has_mem) {
> >> +        error_setg(errp, "numa configuration should use mem= or memdev= ");
> >> +        return;
> >> +    }  
> > 
> > Wouldn't this breaks memory less numa nodes?  
> 
> Yes, you are right. It will break it if there more numa nodes
> than memory, and the numa nodes have no memory backends specified.
> 
> Is it allowed for users to specify more numa nodes than memory?
yep, I think we support it at least for one of the targets
(but I don't remember which one(s))

> 
> > 
> > I'd rather add/rephrase to original error message that memory
> > should be specified explicitly for desired numa nodes.
> > And I'd not mention 'mem=' since
> >    docs/about/removed-features.rst:``-numa node,mem=...`` (removed in 5.1)  
> 
> Thanks for your suggestions, I will rephrase it.
> 
> >   
> >> +
> >>       if ((node->has_mem && have_memdevs) || (node->has_memdev && have_mem)) {
> >>           error_setg(errp, "numa configuration should use either mem= or memdev=,"
> >>                      "mixing both is not allowed");  
> >   
> 



  reply	other threads:[~2022-02-17 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:36 [PATCH 1/1] numa: check mem or memdev in numa configuration Li Zhang
2022-02-17  9:10 ` Igor Mammedov
2022-02-17  9:38   ` Li Zhang
2022-02-17 10:25     ` Igor Mammedov [this message]
2022-02-17 11:06       ` Li Zhang
2022-02-17 12:24       ` Li Zhang
2022-02-17 13:33         ` Igor Mammedov
2022-02-17 15:22           ` Li Zhang

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=20220217112539.43ddd55f@redhat.com \
    --to=imammedo@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=f4bug@amsat.org \
    --cc=lizhang@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyanan55@huawei.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 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.