[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YYl0l+XV/QRZieGY@zn.tnic>
Date: Mon, 8 Nov 2021 20:03:51 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Chatradhi, Naveen Krishna" <nchatrad@....com>
Cc: linux-edac@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, mingo@...hat.com, mchehab@...nel.org,
yazen.ghannam@....com, Muralidhara M K <muralimk@....com>
Subject: Re: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on
Aldebaran
On Mon, Nov 08, 2021 at 10:23:49PM +0530, Chatradhi, Naveen Krishna wrote:
> Northbridges on CPUs and GPUs can be described using the elements in the
> above structure.
If you're going to describe *northbridges*, then your struct cannot be called
system_topology...
> I thought organizing the data in a structure would simplify the
> initialization of cpus and gpus.
Ehh, did you even read my mail where I tried to explain that sprinkling
if (gpu)
this
else
that
all over amd_cache_northbridges() is not proper design?
;-\
> I will modify the patch to enumerate gpu northbridge info only if there are
>
> gpu nodes with pci_device to access the node_map registers.
Why would you do that? What's the advantage?
How about you answer my questions first so that we agree on the design
first before you go and do things?
Hmm.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists