diff options
| author | Damien Le Moal <[email protected]> | 2025-05-08 23:25:02 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2025-05-13 05:57:11 +0000 |
| commit | 4236e600bf902202214aa6277e84c4738c56f762 (patch) | |
| tree | 2c1fb43ab42ae5d0572703ab7c2f3ead446aca40 /rust/helpers/mutex.c | |
| parent | nvmet: pci-epf: do not fall back to using INTX if not supported (diff) | |
| download | kernel-4236e600bf902202214aa6277e84c4738c56f762.tar.gz kernel-4236e600bf902202214aa6277e84c4738c56f762.zip | |
nvmet: pci-epf: cleanup nvmet_pci_epf_raise_irq()
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 <[email protected]>
Reviewed-by: Niklas Cassel <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'rust/helpers/mutex.c')
0 files changed, 0 insertions, 0 deletions