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
..
NVMeController.cpp	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMeController.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
NVMeDefinitions.h	Kernel: Add polling support to NVMe	2022-02-02 18:26:59 +01:00
NVMeInterruptQueue.cpp	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMeInterruptQueue.h	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMeNameSpace.cpp	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
NVMeNameSpace.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
NVMePollQueue.cpp	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMePollQueue.h	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMeQueue.cpp	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMeQueue.h	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00