From: Serhii Popovych <spopovyc@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH for 3.1] spapr: Fix ibm, max-associativity-domains property number of nodes
Date: Mon, 19 Nov 2018 18:18:04 +0200 [thread overview]
Message-ID: <13c0668b-6a38-6fad-c80d-4465fda88cb9@redhat.com> (raw)
In-Reply-To: <6ff0a235-0136-63b6-dd6a-cd78f656ca0e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3462 bytes --]
Laurent Vivier wrote:
> On 19/11/2018 14:27, Greg Kurz wrote:
>> On Mon, 19 Nov 2018 08:09:38 -0500
>> Serhii Popovych <spopovyc@redhat.com> wrote:
>>
>>> Laurent Vivier reported off by one with maximum number of NUMA nodes
>>> provided by qemu-kvm being less by one than required according to
>>> description of "ibm,max-associativity-domains" property in LoPAPR.
>>>
>>> It appears that I incorrectly treated LoPAPR description of this
>>> property assuming it provides last valid domain (NUMA node here)
>>> instead of maximum number of domains.
>>>
>>> ### Before hot-add
>>>
>>> (qemu) info numa
>>> 3 nodes
>>> node 0 cpus: 0
>>> node 0 size: 0 MB
>>> node 0 plugged: 0 MB
>>> node 1 cpus:
>>> node 1 size: 1024 MB
>>> node 1 plugged: 0 MB
>>> node 2 cpus:
>>> node 2 size: 0 MB
>>> node 2 plugged: 0 MB
>>>
>>> $ numactl -H
>>> available: 2 nodes (0-1)
>>> node 0 cpus: 0
>>> node 0 size: 0 MB
>>> node 0 free: 0 MB
>>> node 1 cpus:
>>> node 1 size: 999 MB
>>> node 1 free: 658 MB
>>> node distances:
>>> node 0 1
>>> 0: 10 40
>>> 1: 40 10
>>>
>>> ### Hot-add
>>>
>>> (qemu) object_add memory-backend-ram,id=mem0,size=1G
>>> (qemu) device_add pc-dimm,id=dimm1,memdev=mem0,node=2
>>> (qemu) [ 87.704898] pseries-hotplug-mem: Attempting to hot-add 4 ...
>>> <there is no "Initmem setup node 2 [mem 0xHEX-0xHEX]">
>>> [ 87.705128] lpar: Attempting to resize HPT to shift 21
>>> ... <HPT resize messages>
>>>
>>> ### After hot-add
>>>
>>> (qemu) info numa
>>> 3 nodes
>>> node 0 cpus: 0
>>> node 0 size: 0 MB
>>> node 0 plugged: 0 MB
>>> node 1 cpus:
>>> node 1 size: 1024 MB
>>> node 1 plugged: 0 MB
>>> node 2 cpus:
>>> node 2 size: 1024 MB
>>> node 2 plugged: 1024 MB
>>>
>>> $ numactl -H
>>> available: 2 nodes (0-1)
>>> ^^^^^^^^^^^^^^^^^^^^^^^^
>>> Still only two nodes (and memory hot-added to node 0 below)
>>> node 0 cpus: 0
>>> node 0 size: 1024 MB
>>> node 0 free: 1021 MB
>>> node 1 cpus:
>>> node 1 size: 999 MB
>>> node 1 free: 658 MB
>>> node distances:
>>> node 0 1
>>> 0: 10 40
>>> 1: 40 10
>>>
>>> After fix applied numactl(8) reports 3 nodes available and memory
>>> plugged into node 2 as expected.
>>>
>>> Fixes: da9f80fbad21 ("spapr: Add ibm,max-associativity-domains property")
>>> Reported-by: Laurent Vivier <lvivier@redhat.com>
>>> Signed-off-by: Serhii Popovych <spopovyc@redhat.com>
>>> ---
>>> hw/ppc/spapr.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>>> index 7afd1a1..843ae6c 100644
>>> --- a/hw/ppc/spapr.c
>>> +++ b/hw/ppc/spapr.c
>>> @@ -1033,7 +1033,7 @@ static void spapr_dt_rtas(sPAPRMachineState *spapr, void *fdt)
>>> cpu_to_be32(0),
>>> cpu_to_be32(0),
>>> cpu_to_be32(0),
>>> - cpu_to_be32(nb_numa_nodes ? nb_numa_nodes - 1 : 0),
>>> + cpu_to_be32(nb_numa_nodes ? nb_numa_nodes : 0),
>>
>> Maybe simply cpu_to_be32(nb_numa_nodes) ?
>
> I agree the "? : " is not needed.
>
> With "cpu_to_be32(nb_numa_nodes)":
>
Agree, ?: was relevant only to catch -1 case when running guest w/o NUMA
config. Will send v2. Thanks for quick review.
> Reviewed-by: Laurent Vivier <lvivier@redhat.com>
>
> Thanks,
> Laurent
>
--
Thanks,
Serhii
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-11-19 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 13:09 [Qemu-devel] [PATCH for 3.1] spapr: Fix ibm, max-associativity-domains property number of nodes Serhii Popovych
2018-11-19 13:27 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-11-19 13:30 ` Laurent Vivier
2018-11-19 16:18 ` Serhii Popovych [this message]
2018-11-19 13:48 ` Laurent Vivier
2018-11-19 16:59 ` Greg Kurz
2018-11-20 18:58 ` Serhii Popovych
2018-11-21 13:58 ` Greg Kurz
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=13c0668b-6a38-6fad-c80d-4465fda88cb9@redhat.com \
--to=spopovyc@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).