Liav A 1f9d3a3523 Kernel/PCI: Hold a reference to DeviceIdentifier in the Device class ... There are now 2 separate classes for almost the same object type: - EnumerableDeviceIdentifier, which is used in the enumeration code for all PCI host controller classes. This is allowed to be moved and copied, as it doesn't support ref-counting. - DeviceIdentifier, which inherits from EnumerableDeviceIdentifier. This class uses ref-counting, and is not allowed to be copied. It has a spinlock member in its structure to allow safely executing complicated IO sequences on a PCI device and its space configuration. There's a static method that allows a quick conversion from EnumerableDeviceIdentifier to DeviceIdentifier while creating a NonnullRefPtr out of it. The reason for doing this is for the sake of integrity and reliablity of the system in 2 places: - Ensure that "complicated" tasks that rely on manipulating PCI device registers are done in a safe manner. For example, determining a PCI BAR space size requires multiple read and writes to the same register, and if another CPU tries to do something else with our selected register, then the result will be a catastrophe. - Allow the PCI API to have a united form around a shared object which actually holds much more data than the PCI::Address structure. This is fundamental if we want to do certain types of optimizations, and be able to support more features of the PCI bus in the foreseeable future. This patch already has several implications: - All PCI::Device(s) hold a reference to a DeviceIdentifier structure being given originally from the PCI::Access singleton. This means that all instances of DeviceIdentifier structures are located in one place, and all references are pointing to that location. This ensures that locking the operation spinlock will take effect in all the appropriate places. - We no longer support adding PCI host controllers and then immediately allow for enumerating it with a lambda function. It was found that this method is extremely broken and too much complicated to work reliably with the new paradigm being introduced in this patch. This means that for Volume Management Devices (Intel VMD devices), we simply first enumerate the PCI bus for such devices in the storage code, and if we find a device, we attach it in the PCI::Access method which will scan for devices behind that bridge and will add new DeviceIdentifier(s) objects to its internal Vector. Afterwards, we just continue as usual with scanning for actual storage controllers, so we will find a corresponding NVMe controllers if there were any behind that VMD bridge.		2023-01-26 23:04:26 +01:00
..
HostController.cpp	Kernel/PCI: Hold a reference to DeviceIdentifier in the Device class	2023-01-26 23:04:26 +01:00
HostController.h	Kernel/PCI: Hold a reference to DeviceIdentifier in the Device class	2023-01-26 23:04:26 +01:00
MemoryBackedHostBridge.cpp	Kernel: Split the SysFS core files into smaller components	2022-11-08 02:54:48 -07:00
MemoryBackedHostBridge.h	Kernel: Split the SysFS core files into smaller components	2022-11-08 02:54:48 -07:00
VolumeManagementDevice.cpp	Kernel/PCI: Hold a reference to DeviceIdentifier in the Device class	2023-01-26 23:04:26 +01:00
VolumeManagementDevice.h	Kernel: Turn lock ranks into template parameters	2023-01-02 18:15:27 -05:00