Messages in this thread | | | Date | Mon, 11 Oct 2021 20:08:54 +0200 | From | Borislav Petkov <> | Subject | Re: [PATCH v3 1/3] x86/amd_nb: Add support for northbridges on Aldebaran |
| |
On Mon, Oct 11, 2021 at 07:56:34PM +0530, Chatradhi, Naveen Krishna wrote: > Aldebaran is an AMD GPU name, code submitted [PATCH 000/159] Aldebaran > support (lists.freedesktop.org) > <https://lists.freedesktop.org/archives/amd-gfx/2021-February/059694.html> > is a part of the DRM framework
A short explanation in your patchset would be very helpful so that a reader can know what it is and search the net further, if more info is needed.
> Aldebaran GPU might be a later variant of gfx9 and are connected to the CPU > sockets via custom xGMI links. > > I could not find any family number associated with the GPUs. The DRM driver > code uses it as follows and > > does not expose the value to other frameworks in Linux. > > +#define CHIP_ALDEBARAN 25 > > in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdkfd/cwsr_trap_handler_gfx9.asm
Aha, so Aldebaran is the chip name. And how are those PCI IDs named in the documentation? Aldebaran data fabric PCI functions or so?
> The roots_per_misc count is different for the CPU nodes and GPU nodes. We > tried to address > > your comment without introducing pci_dev_id arrays for GPU roots, misc and > links. But, introducing > > GPU ID arrays looks cleaner, let me submit the revised code and we can > revisit this point.
Ok, but as I said above, what those devices are, means nothing to the amd_nb code because that simply enumerates PCI IDs when those things were simply northbridges.
If the GPU PCI IDs do not fit easily into the scheme then maybe the scheme has become inadeqate... we'll see...
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
| |