[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains
From: |
Cédric Le Goater |
Subject: |
Re: [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains |
Date: |
Thu, 28 Jan 2021 18:20:26 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
On 1/28/21 6:13 PM, Cédric Le Goater wrote:
> On 1/28/21 6:05 PM, Daniel Henrique Barboza wrote:
>>
>>
>> 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.
>
> I was also seeing the issue on KVM and I am still seeing it with
> this patchset. It's gone on TCG however.
ooups, sorry. All good on KVM also !
Tested-by: Cédric Le Goater <clg@kaod.org>
We can now safely use for_each_node() in the kernel.
Thanks Daniel,
C.
- [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains, Daniel Henrique Barboza, 2021/01/28
- [PATCH 1/3] spapr: move spapr_machine_using_legacy_numa() to spapr_numa.c, Daniel Henrique Barboza, 2021/01/28
- [PATCH 3/3] spapr_numa.c: fix ibm, max-associativity-domains calculation, Daniel Henrique Barboza, 2021/01/28
- [PATCH 2/3] spapr_numa.c: create spapr_numa_initial_nvgpu_NUMA_id() helper, Daniel Henrique Barboza, 2021/01/28
- Re: [PATCH 0/3] spapr, spapr_numa: fix max-associativity-domains, Greg Kurz, 2021/01/28