diff options
| author | Damien Le Moal <dlemoal@kernel.org> | 2025-05-09 08:25:02 +0900 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-06-04 14:45:09 +0200 |
| commit | e411fb62f9474e8186acbca1b8e0188aa3da411d (patch) | |
| tree | 56abc0ae505ab4b9fa51471ec5d3e696ca3e4467 /tools/perf/scripts/python | |
| parent | bde2474dbff89e7a7532f08c230f14374d3dcfbe (diff) | |
nvmet: pci-epf: cleanup nvmet_pci_epf_raise_irq()
[ Upstream commit 4236e600bf902202214aa6277e84c4738c56f762 ]
There is no point in taking the controller irq_lock and calling
nvmet_pci_epf_should_raise_irq() for a completion queue which does not
have IRQ enabled (NVMET_PCI_EPF_Q_IRQ_ENABLED flag is not set).
Move the test for the NVMET_PCI_EPF_Q_IRQ_ENABLED flag out of
nvmet_pci_epf_should_raise_irq() to the top of nvmet_pci_epf_raise_irq()
to return early when no IRQ should be raised.
Also, use dev_err_ratelimited() to avoid a message storm under load when
raising IRQs is failing.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <cassel@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
