From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Greg Kurz <groug@kaod.org>
Cc: clg@kaod.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains
Date: Thu, 28 Jan 2021 14:05:26 -0300 [thread overview]
Message-ID: <6057fa92-e554-edfb-c6a7-4d0d318dd52d@gmail.com> (raw)
In-Reply-To: <20210128170318.1e164823@bahia.lan>
On 1/28/21 1:03 PM, Greg Kurz wrote:
> On Thu, 28 Jan 2021 12:17:28 -0300
> Daniel Henrique Barboza <danielhb413@gmail.com> wrote:
>
>> Hi,
>>
>> Patches 02 and 03 contain fixes for a problem Cedric found out when
>> booting TCG guests with multiple NUMA nodes. See patch 03 commit
>> message for more info.
>>
>
> This paragraph mentions "TCG guests", but I see nothing that is
> specific to TCG in these patches... so I expect the problem to
> also exists with KVM, right ?
Yeah. I mentioned TCG because this is the use case Cedric reproduced
the bug with, but I myself had no problems reproducing it with
accel=kvm as well.
DHB
>
>> First patch is an unrelated cleanup I did while investigating.
>>
>> Daniel Henrique Barboza (3):
>> spapr: move spapr_machine_using_legacy_numa() to spapr_numa.c
>> spapr_numa.c: create spapr_numa_initial_nvgpu_NUMA_id() helper
>> spapr_numa.c: fix ibm,max-associativity-domains calculation
>>
>> hw/ppc/spapr.c | 21 ++------------------
>> hw/ppc/spapr_numa.c | 39 ++++++++++++++++++++++++++++++++++++-
>> include/hw/ppc/spapr.h | 1 -
>> include/hw/ppc/spapr_numa.h | 1 +
>> 4 files changed, 41 insertions(+), 21 deletions(-)
>>
>
next prev parent reply other threads:[~2021-01-28 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 15:17 [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains Daniel Henrique Barboza
2021-01-28 15:17 ` [PATCH 1/3] spapr: move spapr_machine_using_legacy_numa() to spapr_numa.c Daniel Henrique Barboza
2021-01-28 16:03 ` Greg Kurz
2021-01-28 23:56 ` David Gibson
2021-01-28 15:17 ` [PATCH 2/3] spapr_numa.c: create spapr_numa_initial_nvgpu_NUMA_id() helper Daniel Henrique Barboza
2021-01-28 15:50 ` Greg Kurz
2021-01-28 15:17 ` [PATCH 3/3] spapr_numa.c: fix ibm, max-associativity-domains calculation Daniel Henrique Barboza
2021-01-28 16:21 ` [PATCH 3/3] spapr_numa.c: fix ibm,max-associativity-domains calculation Greg Kurz
2021-01-28 16:03 ` [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains Greg Kurz
2021-01-28 17:05 ` Daniel Henrique Barboza [this message]
2021-01-28 17:13 ` Cédric Le Goater
2021-01-28 17:20 ` Cédric Le Goater
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=6057fa92-e554-edfb-c6a7-4d0d318dd52d@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--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).