On Tue, 26 Aug 2025 at 20:33, Edgar E. Iglesias <edgar.igles...@gmail.com> wrote: > > On Fri, Aug 22, 2025 at 05:15:48PM +0200, Luc Michel wrote: > > From: Francisco Iglesias <francisco.igles...@xilinx.com> > > > > Introduce a 'first-cpu-index' property for specifying the first QEMU CPU > > connected to the GICv3. This makes it possible to have multiple instances > > of the GICv3 connected to different CPU clusters. > > > > For KVM, mark this property has unsupported. It probably does not make > > much sense as it is intented to be used to model non-SMP systems. > > > > Signed-off-by: Luc Michel <luc.mic...@amd.com> > > Signed-off-by: Francisco Iglesias <francisco.igles...@amd.com> > > Peter, were you looking at solving this with links to CPU's for the next > GIC? Perhaps we should do the same here? > > I'm also fine with this patch as simple way of solving this problem.
Yeah, links to CPUs is my plan for GICv5. We don't currently support having an array of link properties, so you need this patch: https://lore.kernel.org/qemu-devel/20250606140327.1289993-1-peter.mayd...@linaro.org/ which provides the macro for declaring the property array and some functions for setting it up in the board/SoC code (and a sketch in the commit message of how to do it). If you want to have a go at doing it that way, feel free; but I'm happy with doing what this patch does, since it's what we already did for GICv2. We can always come back and do the refactoring later. thanks -- PMM
