linux-kernel - Re: [PATCH 02/21] PCI: Add API to track PCI devices preserved across Live Update

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: <aS_OQoYKmFBaOHSx@wunner.de>
Date: Wed, 3 Dec 2025 06:44:34 +0100
From: Lukas Wunner <lukas@...ner.de>
To: Chris Li <chrisl@...nel.org>
Cc: Jason Gunthorpe <jgg@...dia.com>, David Matlack <dmatlack@...gle.com>,
	Pasha Tatashin <pasha.tatashin@...een.com>,
	Alex Williamson <alex@...zbot.org>,
	Adithya Jayachandran <ajayachandra@...dia.com>,
	Alex Mastro <amastro@...com>, Alistair Popple <apopple@...dia.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	David Rientjes <rientjes@...gle.com>,
	Jacob Pan <jacob.pan@...ux.microsoft.com>,
	Josh Hilke <jrhilke@...gle.com>, Kevin Tian <kevin.tian@...el.com>,
	kvm@...r.kernel.org, Leon Romanovsky <leonro@...dia.com>,
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
	linux-pci@...r.kernel.org, Mike Rapoport <rppt@...nel.org>,
	Parav Pandit <parav@...dia.com>,
	Philipp Stanner <pstanner@...hat.com>,
	Pratyush Yadav <pratyush@...nel.org>,
	Saeed Mahameed <saeedm@...dia.com>,
	Samiullah Khawaja <skhawaja@...gle.com>,
	Shuah Khan <shuah@...nel.org>, Tomita Moeko <tomitamoeko@...il.com>,
	Vipin Sharma <vipinsh@...gle.com>, William Tu <witu@...dia.com>,
	Yi Liu <yi.l.liu@...el.com>, Yunxiang Li <Yunxiang.Li@....com>,
	Zhu Yanjun <yanjun.zhu@...ux.dev>,
	Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Subject: Re: [PATCH 02/21] PCI: Add API to track PCI devices preserved across
 Live Update

On Tue, Dec 02, 2025 at 08:36:53PM +0400, Chris Li wrote:
> On Tue, Dec 2, 2025 at 6:59 PM Jason Gunthorpe <jgg@...dia.com> wrote:
> > The device is active
> > during KHO, you CAN NOT do any resource reassignment, not bus numbers,
> > not mmio. It must be fully disabled.
> 
> I agree with Jason. The bus number is used in the low level hardware
> to do the DMA transfer. The bus number can not change for a device
> during livedupate with pending DMA transfer. The BDF MUST remain the
> same as the liveupdate with DMA transfer requirement.

Thank you both for the explanation.

> Another point is that, on the same machine it can have multiple PCI
> host bridges. Each PCI host bridge bus number is acquired from the
> ACPI table walk. I am not aware of any way to get the slot number of
> the PCI host bridge. Lukas, do you know how to get the PCI host bridge
> slot number to form a path?

Host bridges are identified by the segment number.  On ACPI-based systems,
it's retrieved by acpi_pci_root_add() through invocation of the _SEG method.

Thanks,

Lukas