Re: [PATCH v4 0/2] Fix RISC-V's arch-topology reporting

From: Atish Patra <atishp@atishpatra.org>
To: Conor Dooley <Conor.Dooley@microchip.com>
Cc: "will@kernel.org" <will@kernel.org>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Palmer Dabbelt" <palmer@rivosinc.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Sudeep Holla" <sudeep.holla@arm.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Daire McNamara" <Daire.McNamara@microchip.com>,
	"Niklas Cassel" <niklas.cassel@wdc.com>,
	"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Zong Li" <zong.li@sifive.com>,
	"Emil Renner Berhing" <kernel@esmil.dk>,
	"Jonas Hahnfeld" <hahnjo@hahnjo.de>,
	"Guo Ren" <guoren@kernel.org>, "Anup Patel" <anup@brainfault.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
	"Rob Herring" <robh@kernel.org>, "Marc Zyngier" <maz@kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Brice Goglin" <Brice.Goglin@inria.fr>
Subject: Re: [PATCH v4 0/2] Fix RISC-V's arch-topology reporting
Date: Tue, 26 Jul 2022 01:12:28 -0700	[thread overview]
Message-ID: <CAOnJCUJh0vU8-tK31-A44h+VNHZA2_R6GayNjFg-7Daa6efbag@mail.gmail.com> (raw)
In-Reply-To: <28e38506-8fce-9000-c211-199a7aa69910@microchip.com>

On Mon, Jul 25, 2022 at 2:20 AM <Conor.Dooley@microchip.com> wrote:
>
> On 25/07/2022 10:13, Will Deacon wrote:
> > On Sat, Jul 23, 2022 at 11:22:01AM +0000, Conor.Dooley@microchip.com wrote:
> >> On 15/07/2022 18:51, Conor Dooley wrote:
> >>
> >> Hey,
> >>
> >> Not got any feedback on the smpboot changes from the RISC-V side.
> >> I tested it on polarfire, the d1 (with both SMP & !SMP set iirc)
> >> & on the u540. It all looked good to me.
> >>
> >> I'd like to have this fixed for v5.20, but there isn't too much
> >> time left before the mw. Not too sure about the cross-tree changes,
> >> does it need an immutable branch or could it go through driver-core?
> >> Catalin suggested removing the CC stable from patch 1/2 & adding it
> >> as a dependency for the 2/2 patch - but obviously that's up to the
> >> committer to sort out.
> >
> > I'm finalising the arm64 queue today, so I don't really want to pull in
> > additional changes beyond critical fixes at this point, I'm afraid. I was
> > half-expecting a pull request from the riscv side last week but I didn't
> > see anything.
>
> Yeah, that's fair. It's late in the game for cross-tree messing.
> I know Palmer has been p busy recently.
>
> > FWIW, if there's still no movement by -rc1, then I'm happy to queue all
> > of this on its own branch in the arm64 tree for 5.21.
>
> Hopefully someone on the riscv side will have confirmed what I am doing
> is sane by then.
>
> >
> > Let me know.
>
> I will, thanks!

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.

Thanks for the fixes. I have tested this on Qemu(removing the topology
node) for the following configurations.
SMP, !SMP, NUMA (2 sockets)

FWIW,
Tested-by: Atish Patra <atishp@rivosinc.com>

-- 
Regards,
Atish

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv