From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
david@gibson.dropbear.id.au
Subject: Re: [PATCH] spapr_numa.c: fixes in spapr_numa_FORM2_write_rtas_tables()
Date: Wed, 22 Sep 2021 14:35:18 +0200 [thread overview]
Message-ID: <1429cd8b-508f-2ec8-310a-65dd173d2a68@redhat.com> (raw)
In-Reply-To: <20210922135250.31a2d4d4@bahia.huguette>
On 9/22/21 13:52, Greg Kurz wrote:
> On Wed, 22 Sep 2021 13:17:32 +0200
> Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
>> On 9/21/21 21:43, Daniel Henrique Barboza wrote:
>>> This patch has a handful of modifications for the recent added
>>> FORM2 support:
>>>
>>> - there is no particular reason for both 'lookup_index_table' and
>>> 'distance_table' to be allocated in the heap, since their sizes are
>>> known right at the start of the function. Use static allocation in
>>> them to spare a couple of g_new0() calls;
>>>
>>> - to not allocate more than the necessary size in 'distance_table'. At
>>> this moment the array is oversized due to allocating uint32_t for all
>>> elements, when most of them fits in an uint8_t;
>>>
>>> - create a NUMA_LOCAL_DISTANCE macro to avoid hardcoding the local
>>> distance value.
>>>
>>> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>>> ---
>>> hw/ppc/spapr_numa.c | 35 +++++++++++++++++++----------------
>>> 1 file changed, 19 insertions(+), 16 deletions(-)
>>> /*
>>> * Retrieves max_dist_ref_points of the current NUMA affinity.
>>> */
>>> @@ -500,17 +503,21 @@ static void spapr_numa_FORM2_write_rtas_tables(SpaprMachineState *spapr,
>>> MachineState *ms = MACHINE(spapr);
>>> NodeInfo *numa_info = ms->numa_state->nodes;
>>> int nb_numa_nodes = ms->numa_state->num_nodes;
>>> + /* Lookup index table has an extra uint32_t with its length */
>>> + uint32_t lookup_index_table[nb_numa_nodes + 1];
>>> int distance_table_entries = nb_numa_nodes * nb_numa_nodes;
>>> - g_autofree uint32_t *lookup_index_table = NULL;
>>> - g_autofree uint32_t *distance_table = NULL;
>>> - int src, dst, i, distance_table_size;
>>> - uint8_t *node_distances;
>>
>> This should have be of ptrdiff_t type.
>>
>
> Why ? I don't see pointer subtraction in the code.
Oops, you are right.
prev parent reply other threads:[~2021-09-22 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 19:43 [PATCH] spapr_numa.c: fixes in spapr_numa_FORM2_write_rtas_tables() Daniel Henrique Barboza
2021-09-22 3:08 ` David Gibson
2021-09-22 8:26 ` Greg Kurz
2021-09-22 9:51 ` BALATON Zoltan
2021-09-22 11:00 ` Daniel Henrique Barboza
2021-09-22 11:10 ` BALATON Zoltan
2021-09-22 11:17 ` Philippe Mathieu-Daudé
2021-09-22 11:50 ` Daniel Henrique Barboza
2021-09-22 11:52 ` Greg Kurz
2021-09-22 12:35 ` Philippe Mathieu-Daudé [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=1429cd8b-508f-2ec8-310a-65dd173d2a68@redhat.com \
--to=philmd@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--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).