lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251021141500.GDaPeVZJ8MaPbtTYv_@fat_crate.local>
Date: Tue, 21 Oct 2025 16:15:00 +0200
From: Borislav Petkov <bp@...en8.de>
To: Yazen Ghannam <yazen.ghannam@....com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
	Mario Limonciello <mario.limonciello@....com>,
	Filip Barczyk <filip.barczyk@...o.net>
Subject: Re: [PATCH 1/2] x86/amd_node: Fix AMD root device caching

On Tue, Oct 21, 2025 at 09:37:45AM -0400, Yazen Ghannam wrote:
> It's correct that one of the root devices will be on bus 0x0. But that
> device will be part of AMD node 0. So we still need to pick a root
> device for the other, if any, AMD nodes in the system.
> 
> For example, a system with 2 AMD nodes could have this:
> Node 0 : 0x00 0x07 0x0e 0x15
> Node 1 : 0x1c 0x23 0x2a 0x31

Aha, so next question: isn't there a way to figure out which is the *first*
PCI bus of a AMD node? My gut feeling tells me there should be some info
somewhere which we can use...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ