From: <Conor.Dooley@microchip.com>
To: <atishp@atishpatra.org>
Cc: <will@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>,
<aou@eecs.berkeley.edu>, <sudeep.holla@arm.com>,
<catalin.marinas@arm.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <Daire.McNamara@microchip.com>,
<niklas.cassel@wdc.com>, <damien.lemoal@opensource.wdc.com>,
<geert@linux-m68k.org>, <zong.li@sifive.com>, <kernel@esmil.dk>,
<hahnjo@hahnjo.de>, <guoren@kernel.org>, <anup@brainfault.org>,
<heiko@sntech.de>, <philipp.tomsich@vrull.eu>, <robh@kernel.org>,
<maz@kernel.org>, <viresh.kumar@linaro.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <Brice.Goglin@inria.fr>
Subject: Re: [PATCH v4 0/2] Fix RISC-V's arch-topology reporting
Date: Tue, 26 Jul 2022 09:14:49 +0000 [thread overview]
Message-ID: <5cca96f1-2f30-b0bf-394f-5ee0a29eaf3c@microchip.com> (raw)
In-Reply-To: <CAOnJCUJh0vU8-tK31-A44h+VNHZA2_R6GayNjFg-7Daa6efbag@mail.gmail.com>
On 26/07/2022 09:12, Atish Patra wrote:
>
> Sorry for the delayed response here. I was planning to test the series
> last week itself
> but got dragged into something else and a qemu bug for NUMA.
No worries, thanks for testing/reviewing it.
>
> Thanks for the fixes. I have tested this on Qemu(removing the topology
> node) for the following configurations.
> SMP, !SMP, NUMA (2 sockets)
A NUMA test, great! I do need to get qemu set up properly..
>
> FWIW,
> Tested-by: Atish Patra <atishp@rivosinc.com>
Thanks,
Conor.
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <atishp@atishpatra.org>
Cc: <will@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>,
<aou@eecs.berkeley.edu>, <sudeep.holla@arm.com>,
<catalin.marinas@arm.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <Daire.McNamara@microchip.com>,
<niklas.cassel@wdc.com>, <damien.lemoal@opensource.wdc.com>,
<geert@linux-m68k.org>, <zong.li@sifive.com>, <kernel@esmil.dk>,
<hahnjo@hahnjo.de>, <guoren@kernel.org>, <anup@brainfault.org>,
<heiko@sntech.de>, <philipp.tomsich@vrull.eu>, <robh@kernel.org>,
<maz@kernel.org>, <viresh.kumar@linaro.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <Brice.Goglin@inria.fr>
Subject: Re: [PATCH v4 0/2] Fix RISC-V's arch-topology reporting
Date: Tue, 26 Jul 2022 09:14:49 +0000 [thread overview]
Message-ID: <5cca96f1-2f30-b0bf-394f-5ee0a29eaf3c@microchip.com> (raw)
In-Reply-To: <CAOnJCUJh0vU8-tK31-A44h+VNHZA2_R6GayNjFg-7Daa6efbag@mail.gmail.com>
On 26/07/2022 09:12, Atish Patra wrote:
>
> Sorry for the delayed response here. I was planning to test the series
> last week itself
> but got dragged into something else and a qemu bug for NUMA.
No worries, thanks for testing/reviewing it.
>
> Thanks for the fixes. I have tested this on Qemu(removing the topology
> node) for the following configurations.
> SMP, !SMP, NUMA (2 sockets)
A NUMA test, great! I do need to get qemu set up properly..
>
> FWIW,
> Tested-by: Atish Patra <atishp@rivosinc.com>
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <atishp@atishpatra.org>
Cc: <will@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>,
<aou@eecs.berkeley.edu>, <sudeep.holla@arm.com>,
<catalin.marinas@arm.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <Daire.McNamara@microchip.com>,
<niklas.cassel@wdc.com>, <damien.lemoal@opensource.wdc.com>,
<geert@linux-m68k.org>, <zong.li@sifive.com>, <kernel@esmil.dk>,
<hahnjo@hahnjo.de>, <guoren@kernel.org>, <anup@brainfault.org>,
<heiko@sntech.de>, <philipp.tomsich@vrull.eu>, <robh@kernel.org>,
<maz@kernel.org>, <viresh.kumar@linaro.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <Brice.Goglin@inria.fr>
Subject: Re: [PATCH v4 0/2] Fix RISC-V's arch-topology reporting
Date: Tue, 26 Jul 2022 09:14:49 +0000 [thread overview]
Message-ID: <5cca96f1-2f30-b0bf-394f-5ee0a29eaf3c@microchip.com> (raw)
In-Reply-To: <CAOnJCUJh0vU8-tK31-A44h+VNHZA2_R6GayNjFg-7Daa6efbag@mail.gmail.com>
On 26/07/2022 09:12, Atish Patra wrote:
>
> Sorry for the delayed response here. I was planning to test the series
> last week itself
> but got dragged into something else and a qemu bug for NUMA.
No worries, thanks for testing/reviewing it.
>
> Thanks for the fixes. I have tested this on Qemu(removing the topology
> node) for the following configurations.
> SMP, !SMP, NUMA (2 sockets)
A NUMA test, great! I do need to get qemu set up properly..
>
> FWIW,
> Tested-by: Atish Patra <atishp@rivosinc.com>
Thanks,
Conor.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-26 9:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 17:51 [PATCH v4 0/2] Fix RISC-V's arch-topology reporting Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-15 17:51 ` [PATCH v4 1/2] arm64: topology: move store_cpu_topology() to shared code Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-19 11:41 ` Catalin Marinas
2022-07-19 11:41 ` Catalin Marinas
2022-07-19 11:41 ` Catalin Marinas
2022-07-19 11:51 ` Conor.Dooley
2022-07-19 11:51 ` Conor.Dooley
2022-07-19 11:51 ` Conor.Dooley
2022-07-19 12:00 ` Catalin Marinas
2022-07-19 12:00 ` Catalin Marinas
2022-07-19 12:00 ` Catalin Marinas
2022-07-26 8:10 ` Atish Patra
2022-07-26 8:10 ` Atish Patra
2022-07-26 8:10 ` Atish Patra
2022-07-15 17:51 ` [PATCH v4 2/2] riscv: topology: fix default topology reporting Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-15 17:51 ` Conor Dooley
2022-07-26 8:24 ` Atish Patra
2022-07-26 8:24 ` Atish Patra
2022-07-26 8:24 ` Atish Patra
2022-07-16 13:35 ` [PATCH v4 0/2] Fix RISC-V's arch-topology reporting Conor.Dooley
2022-07-16 13:35 ` Conor.Dooley
2022-07-16 13:35 ` Conor.Dooley
2022-07-23 11:22 ` Conor.Dooley
2022-07-23 11:22 ` Conor.Dooley
2022-07-23 11:22 ` Conor.Dooley
2022-07-25 9:13 ` Will Deacon
2022-07-25 9:13 ` Will Deacon
2022-07-25 9:13 ` Will Deacon
2022-07-25 9:20 ` Conor.Dooley
2022-07-25 9:20 ` Conor.Dooley
2022-07-25 9:20 ` Conor.Dooley
2022-07-26 8:12 ` Atish Patra
2022-07-26 8:12 ` Atish Patra
2022-07-26 8:12 ` Atish Patra
2022-07-26 9:14 ` Conor.Dooley [this message]
2022-07-26 9:14 ` Conor.Dooley
2022-07-26 9:14 ` Conor.Dooley
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=5cca96f1-2f30-b0bf-394f-5ee0a29eaf3c@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Brice.Goglin@inria.fr \
--cc=Daire.McNamara@microchip.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=catalin.marinas@arm.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=hahnjo@hahnjo.de \
--cc=heiko@sntech.de \
--cc=kernel@esmil.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=zong.li@sifive.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.