Andreas Kling 2c72d495a3 Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage ... I believe this to be safe, as the main thing that LockRefPtr provides over RefPtr is safe copying from a shared LockRefPtr instance. I've inspected the uses of RefPtr<PhysicalPage> and it seems they're all guarded by external locking. Some of it is less obvious, but this is an area where we're making continuous headway.		2022-08-24 18:35:41 +02:00
..
Controller.cpp	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
Controller.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
Definitions.h	Kernel/Storage: Move ATA device signature definitions to a general file	2022-07-19 11:07:34 +01:00
InterruptHandler.cpp	Kernel/Storage: Move AHCI and IDE code into new subdirectories	2022-07-19 11:07:34 +01:00
InterruptHandler.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
Port.cpp	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
Port.h	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00