diff options
author | 2025-05-09 08:25:02 +0900 | |
---|---|---|
committer | 2025-05-13 07:57:11 +0200 | |
commit | 4236e600bf902202214aa6277e84c4738c56f762 (patch) | |
tree | 2c1fb43ab42ae5d0572703ab7c2f3ead446aca40 /scripts/lib/kdoc/kdoc_parser.py | |
parent | nvmet: pci-epf: do not fall back to using INTX if not supported (diff) | |
download | linux-rng-4236e600bf902202214aa6277e84c4738c56f762.tar.xz linux-rng-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 <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <cassel@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions