mirror of
https://github.com/RGBCube/serenity
synced 2025-05-20 16:35:07 +00:00
2c72d495a3
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.
24 lines
881 B
C++
24 lines
881 B
C++
/*
|
|
* Copyright (c) 2022, Pankaj R <pankydev8@gmail.com>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <Kernel/Storage/NVMe/NVMeQueue.h>
|
|
|
|
namespace Kernel {
|
|
|
|
class NVMeInterruptQueue : public NVMeQueue
|
|
, public IRQHandler {
|
|
public:
|
|
NVMeInterruptQueue(NonnullOwnPtr<Memory::Region> rw_dma_region, Memory::PhysicalPage const& rw_dma_page, u16 qid, u8 irq, u32 q_depth, OwnPtr<Memory::Region> cq_dma_region, NonnullRefPtrVector<Memory::PhysicalPage> cq_dma_page, OwnPtr<Memory::Region> sq_dma_region, NonnullRefPtrVector<Memory::PhysicalPage> sq_dma_page, Memory::TypedMapping<volatile DoorbellRegister> db_regs);
|
|
void submit_sqe(NVMeSubmission& submission) override;
|
|
virtual ~NVMeInterruptQueue() override {};
|
|
|
|
private:
|
|
virtual void complete_current_request(u16 status) override;
|
|
bool handle_irq(RegisterState const&) override;
|
|
};
|
|
}
|