2018-01-27 02:45:16 +09:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2005-04-17 07:20:36 +09:00
|
|
|
/*
|
2018-03-10 07:36:33 +09:00
|
|
|
* PCI Message Signaled Interrupt (MSI)
|
2005-04-17 07:20:36 +09:00
|
|
|
*
|
|
|
|
* Copyright (C) 2003-2004 Intel
|
|
|
|
* Copyright (C) Tom Long Nguyen (tom.l.nguyen@intel.com)
|
2016-07-12 18:20:17 +09:00
|
|
|
* Copyright (C) 2016 Christoph Hellwig.
|
2005-04-17 07:20:36 +09:00
|
|
|
*/
|
2006-10-04 18:16:41 +09:00
|
|
|
#include <linux/err.h>
|
2011-05-27 22:37:25 +09:00
|
|
|
#include <linux/export.h>
|
2021-12-07 07:27:44 +09:00
|
|
|
#include <linux/irq.h>
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-12-07 07:27:47 +09:00
|
|
|
#include "../pci.h"
|
2021-12-07 07:27:52 +09:00
|
|
|
#include "msi.h"
|
2005-04-17 07:20:36 +09:00
|
|
|
|
|
|
|
static int pci_msi_enable = 1;
|
2014-10-27 11:44:36 +09:00
|
|
|
int pci_msi_ignore_mask;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static noinline void pci_msi_update_mask(struct msi_desc *desc, u32 clear, u32 set)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
2021-12-07 07:27:56 +09:00
|
|
|
raw_spinlock_t *lock = &to_pci_dev(desc->dev)->msi_lock;
|
2021-07-30 06:51:47 +09:00
|
|
|
unsigned long flags;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-12-07 07:27:39 +09:00
|
|
|
if (!desc->pci.msi_attrib.can_mask)
|
2021-11-04 08:27:29 +09:00
|
|
|
return;
|
|
|
|
|
2021-07-30 06:51:47 +09:00
|
|
|
raw_spin_lock_irqsave(lock, flags);
|
2021-12-07 07:27:39 +09:00
|
|
|
desc->pci.msi_mask &= ~clear;
|
|
|
|
desc->pci.msi_mask |= set;
|
|
|
|
pci_write_config_dword(msi_desc_to_pci_dev(desc), desc->pci.mask_pos,
|
|
|
|
desc->pci.msi_mask);
|
2021-07-30 06:51:47 +09:00
|
|
|
raw_spin_unlock_irqrestore(lock, flags);
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
}
|
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static inline void pci_msi_mask(struct msi_desc *desc, u32 mask)
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
{
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msi_update_mask(desc, 0, mask);
|
2009-03-17 21:54:09 +09:00
|
|
|
}
|
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static inline void pci_msi_unmask(struct msi_desc *desc, u32 mask)
|
2016-07-12 18:20:14 +09:00
|
|
|
{
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msi_update_mask(desc, mask, 0);
|
|
|
|
}
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2021-07-30 06:51:58 +09:00
|
|
|
static inline void __iomem *pci_msix_desc_addr(struct msi_desc *desc)
|
|
|
|
{
|
2021-12-11 07:19:18 +09:00
|
|
|
return desc->pci.mask_base + desc->msi_index * PCI_MSIX_ENTRY_SIZE;
|
2016-07-12 18:20:14 +09:00
|
|
|
}
|
|
|
|
|
2009-03-17 21:54:09 +09:00
|
|
|
/*
|
2021-08-10 04:08:56 +09:00
|
|
|
* This internal function does not flush PCI writes to the device. All
|
|
|
|
* users must ensure that they read from the device before either assuming
|
|
|
|
* that the device state is up to date, or returning out of this file.
|
|
|
|
* It does not affect the msi_desc::msix_ctrl cache either. Use with care!
|
2009-03-17 21:54:09 +09:00
|
|
|
*/
|
2021-08-10 04:08:56 +09:00
|
|
|
static void pci_msix_write_vector_ctrl(struct msi_desc *desc, u32 ctrl)
|
2009-03-17 21:54:09 +09:00
|
|
|
{
|
2021-08-10 04:08:56 +09:00
|
|
|
void __iomem *desc_addr = pci_msix_desc_addr(desc);
|
2014-10-27 11:44:36 +09:00
|
|
|
|
2021-12-07 07:27:39 +09:00
|
|
|
if (desc->pci.msi_attrib.can_mask)
|
2021-11-04 08:27:29 +09:00
|
|
|
writel(ctrl, desc_addr + PCI_MSIX_ENTRY_VECTOR_CTRL);
|
2021-08-10 04:08:56 +09:00
|
|
|
}
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static inline void pci_msix_mask(struct msi_desc *desc)
|
|
|
|
{
|
2021-12-07 07:27:39 +09:00
|
|
|
desc->pci.msix_ctrl |= PCI_MSIX_ENTRY_CTRL_MASKBIT;
|
|
|
|
pci_msix_write_vector_ctrl(desc, desc->pci.msix_ctrl);
|
2021-08-10 04:08:56 +09:00
|
|
|
/* Flush write to device */
|
2021-12-07 07:27:39 +09:00
|
|
|
readl(desc->pci.mask_base);
|
2021-08-10 04:08:56 +09:00
|
|
|
}
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static inline void pci_msix_unmask(struct msi_desc *desc)
|
|
|
|
{
|
2021-12-07 07:27:39 +09:00
|
|
|
desc->pci.msix_ctrl &= ~PCI_MSIX_ENTRY_CTRL_MASKBIT;
|
|
|
|
pci_msix_write_vector_ctrl(desc, desc->pci.msix_ctrl);
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
}
|
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static void __pci_msi_mask_desc(struct msi_desc *desc, u32 mask)
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
{
|
2021-12-07 07:27:39 +09:00
|
|
|
if (desc->pci.msi_attrib.is_msix)
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msix_mask(desc);
|
2021-11-04 08:27:29 +09:00
|
|
|
else
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msi_mask(desc, mask);
|
2009-03-17 21:54:09 +09:00
|
|
|
}
|
2009-03-17 21:54:06 +09:00
|
|
|
|
2021-08-10 04:08:56 +09:00
|
|
|
static void __pci_msi_unmask_desc(struct msi_desc *desc, u32 mask)
|
2009-03-17 21:54:09 +09:00
|
|
|
{
|
2021-12-07 07:27:39 +09:00
|
|
|
if (desc->pci.msi_attrib.is_msix)
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msix_unmask(desc);
|
2021-11-04 08:27:29 +09:00
|
|
|
else
|
2021-08-10 04:08:56 +09:00
|
|
|
pci_msi_unmask(desc, mask);
|
2009-03-17 21:54:09 +09:00
|
|
|
}
|
|
|
|
|
2014-11-23 19:55:58 +09:00
|
|
|
/**
|
2019-05-30 22:05:58 +09:00
|
|
|
* pci_msi_mask_irq - Generic IRQ chip callback to mask PCI/MSI interrupts
|
2014-11-23 19:55:58 +09:00
|
|
|
* @data: pointer to irqdata associated to that interrupt
|
|
|
|
*/
|
|
|
|
void pci_msi_mask_irq(struct irq_data *data)
|
2009-03-17 21:54:09 +09:00
|
|
|
{
|
2021-07-30 06:51:58 +09:00
|
|
|
struct msi_desc *desc = irq_data_get_msi_desc(data);
|
|
|
|
|
|
|
|
__pci_msi_mask_desc(desc, BIT(data->irq - desc->irq));
|
2009-03-17 21:54:09 +09:00
|
|
|
}
|
2015-12-11 02:52:59 +09:00
|
|
|
EXPORT_SYMBOL_GPL(pci_msi_mask_irq);
|
2009-03-17 21:54:09 +09:00
|
|
|
|
2014-11-23 19:55:58 +09:00
|
|
|
/**
|
2019-05-30 22:05:58 +09:00
|
|
|
* pci_msi_unmask_irq - Generic IRQ chip callback to unmask PCI/MSI interrupts
|
2014-11-23 19:55:58 +09:00
|
|
|
* @data: pointer to irqdata associated to that interrupt
|
|
|
|
*/
|
|
|
|
void pci_msi_unmask_irq(struct irq_data *data)
|
2009-03-17 21:54:09 +09:00
|
|
|
{
|
2021-07-30 06:51:58 +09:00
|
|
|
struct msi_desc *desc = irq_data_get_msi_desc(data);
|
|
|
|
|
|
|
|
__pci_msi_unmask_desc(desc, BIT(data->irq - desc->irq));
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
2015-12-11 02:52:59 +09:00
|
|
|
EXPORT_SYMBOL_GPL(pci_msi_unmask_irq);
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2014-11-10 00:10:33 +09:00
|
|
|
void __pci_read_msi_msg(struct msi_desc *entry, struct msi_msg *msg)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
2015-07-09 17:00:43 +09:00
|
|
|
struct pci_dev *dev = msi_desc_to_pci_dev(entry);
|
|
|
|
|
|
|
|
BUG_ON(dev->current_state != PCI_D0);
|
2010-07-23 22:56:28 +09:00
|
|
|
|
2021-12-07 07:27:39 +09:00
|
|
|
if (entry->pci.msi_attrib.is_msix) {
|
2016-07-12 18:20:14 +09:00
|
|
|
void __iomem *base = pci_msix_desc_addr(entry);
|
2010-07-23 22:56:28 +09:00
|
|
|
|
2021-12-07 07:27:39 +09:00
|
|
|
if (WARN_ON_ONCE(entry->pci.msi_attrib.is_virtual))
|
2019-05-24 07:30:51 +09:00
|
|
|
return;
|
|
|
|
|
2010-07-23 22:56:28 +09:00
|
|
|
msg->address_lo = readl(base + PCI_MSIX_ENTRY_LOWER_ADDR);
|
|
|
|
msg->address_hi = readl(base + PCI_MSIX_ENTRY_UPPER_ADDR);
|
|
|
|
msg->data = readl(base + PCI_MSIX_ENTRY_DATA);
|
|
|
|
} else {
|
2013-04-18 08:34:36 +09:00
|
|
|
int pos = dev->msi_cap;
|
2010-07-23 22:56:28 +09:00
|
|
|
u16 data;
|
|
|
|
|
2013-04-18 08:39:57 +09:00
|
|
|
pci_read_config_dword(dev, pos + PCI_MSI_ADDRESS_LO,
|
|
|
|
&msg->address_lo);
|
2021-12-07 07:27:39 +09:00
|
|
|
if (entry->pci.msi_attrib.is_64) {
|
2013-04-18 08:39:57 +09:00
|
|
|
pci_read_config_dword(dev, pos + PCI_MSI_ADDRESS_HI,
|
|
|
|
&msg->address_hi);
|
2013-04-18 08:41:13 +09:00
|
|
|
pci_read_config_word(dev, pos + PCI_MSI_DATA_64, &data);
|
2010-07-23 22:56:28 +09:00
|
|
|
} else {
|
|
|
|
msg->address_hi = 0;
|
2013-04-18 08:41:13 +09:00
|
|
|
pci_read_config_word(dev, pos + PCI_MSI_DATA_32, &data);
|
2010-07-23 22:56:28 +09:00
|
|
|
}
|
|
|
|
msg->data = data;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-11-10 00:10:34 +09:00
|
|
|
void __pci_write_msi_msg(struct msi_desc *entry, struct msi_msg *msg)
|
2008-12-06 11:58:34 +09:00
|
|
|
{
|
2015-07-09 17:00:43 +09:00
|
|
|
struct pci_dev *dev = msi_desc_to_pci_dev(entry);
|
|
|
|
|
2017-03-30 12:49:11 +09:00
|
|
|
if (dev->current_state != PCI_D0 || pci_dev_is_disconnected(dev)) {
|
2010-06-18 04:16:36 +09:00
|
|
|
/* Don't touch the hardware now */
|
2021-12-07 07:27:39 +09:00
|
|
|
} else if (entry->pci.msi_attrib.is_msix) {
|
2016-07-12 18:20:14 +09:00
|
|
|
void __iomem *base = pci_msix_desc_addr(entry);
|
2021-12-07 07:27:39 +09:00
|
|
|
u32 ctrl = entry->pci.msix_ctrl;
|
2021-07-30 06:51:58 +09:00
|
|
|
bool unmasked = !(ctrl & PCI_MSIX_ENTRY_CTRL_MASKBIT);
|
2009-03-17 21:54:06 +09:00
|
|
|
|
2021-12-07 07:27:39 +09:00
|
|
|
if (entry->pci.msi_attrib.is_virtual)
|
2019-05-24 07:30:51 +09:00
|
|
|
goto skip;
|
|
|
|
|
2021-07-30 06:51:42 +09:00
|
|
|
/*
|
|
|
|
* The specification mandates that the entry is masked
|
|
|
|
* when the message is modified:
|
|
|
|
*
|
|
|
|
* "If software changes the Address or Data value of an
|
|
|
|
* entry while the entry is unmasked, the result is
|
|
|
|
* undefined."
|
|
|
|
*/
|
|
|
|
if (unmasked)
|
2021-07-30 06:51:58 +09:00
|
|
|
pci_msix_write_vector_ctrl(entry, ctrl | PCI_MSIX_ENTRY_CTRL_MASKBIT);
|
2021-07-30 06:51:42 +09:00
|
|
|
|
2009-06-23 17:40:04 +09:00
|
|
|
writel(msg->address_lo, base + PCI_MSIX_ENTRY_LOWER_ADDR);
|
|
|
|
writel(msg->address_hi, base + PCI_MSIX_ENTRY_UPPER_ADDR);
|
|
|
|
writel(msg->data, base + PCI_MSIX_ENTRY_DATA);
|
2021-07-30 06:51:42 +09:00
|
|
|
|
|
|
|
if (unmasked)
|
2021-07-30 06:51:58 +09:00
|
|
|
pci_msix_write_vector_ctrl(entry, ctrl);
|
2021-07-30 06:51:43 +09:00
|
|
|
|
|
|
|
/* Ensure that the writes are visible in the device */
|
|
|
|
readl(base + PCI_MSIX_ENTRY_DATA);
|
2009-03-17 21:54:06 +09:00
|
|
|
} else {
|
2013-04-18 08:34:36 +09:00
|
|
|
int pos = dev->msi_cap;
|
2009-03-17 21:54:10 +09:00
|
|
|
u16 msgctl;
|
|
|
|
|
2013-04-18 08:38:32 +09:00
|
|
|
pci_read_config_word(dev, pos + PCI_MSI_FLAGS, &msgctl);
|
2009-03-17 21:54:10 +09:00
|
|
|
msgctl &= ~PCI_MSI_FLAGS_QSIZE;
|
2021-12-07 07:27:39 +09:00
|
|
|
msgctl |= entry->pci.msi_attrib.multiple << 4;
|
2013-04-18 08:38:32 +09:00
|
|
|
pci_write_config_word(dev, pos + PCI_MSI_FLAGS, msgctl);
|
2006-10-04 18:16:33 +09:00
|
|
|
|
2013-04-18 08:39:57 +09:00
|
|
|
pci_write_config_dword(dev, pos + PCI_MSI_ADDRESS_LO,
|
|
|
|
msg->address_lo);
|
2021-12-07 07:27:39 +09:00
|
|
|
if (entry->pci.msi_attrib.is_64) {
|
2013-04-18 08:39:57 +09:00
|
|
|
pci_write_config_dword(dev, pos + PCI_MSI_ADDRESS_HI,
|
|
|
|
msg->address_hi);
|
2013-04-18 08:41:13 +09:00
|
|
|
pci_write_config_word(dev, pos + PCI_MSI_DATA_64,
|
|
|
|
msg->data);
|
2006-10-04 18:16:33 +09:00
|
|
|
} else {
|
2013-04-18 08:41:13 +09:00
|
|
|
pci_write_config_word(dev, pos + PCI_MSI_DATA_32,
|
|
|
|
msg->data);
|
2006-10-04 18:16:33 +09:00
|
|
|
}
|
2021-07-30 06:51:43 +09:00
|
|
|
/* Ensure that the writes are visible in the device */
|
|
|
|
pci_read_config_word(dev, pos + PCI_MSI_FLAGS, &msgctl);
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
2019-05-24 07:30:51 +09:00
|
|
|
|
|
|
|
skip:
|
2007-03-09 05:04:57 +09:00
|
|
|
entry->msg = *msg;
|
2019-05-24 07:30:51 +09:00
|
|
|
|
|
|
|
if (entry->write_msi_msg)
|
|
|
|
entry->write_msi_msg(entry, entry->write_msi_msg_data);
|
|
|
|
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
2006-10-04 18:16:33 +09:00
|
|
|
|
2014-11-10 00:10:34 +09:00
|
|
|
void pci_write_msi_msg(unsigned int irq, struct msi_msg *msg)
|
2008-12-06 11:58:34 +09:00
|
|
|
{
|
2011-03-29 00:49:12 +09:00
|
|
|
struct msi_desc *entry = irq_get_msi_desc(irq);
|
2008-12-06 11:58:34 +09:00
|
|
|
|
2014-11-10 00:10:34 +09:00
|
|
|
__pci_write_msi_msg(entry, msg);
|
2008-12-06 11:58:34 +09:00
|
|
|
}
|
2014-11-10 00:10:34 +09:00
|
|
|
EXPORT_SYMBOL_GPL(pci_write_msi_msg);
|
2008-12-06 11:58:34 +09:00
|
|
|
|
2009-08-06 11:32:51 +09:00
|
|
|
static void free_msi_irqs(struct pci_dev *dev)
|
|
|
|
{
|
2014-11-15 23:24:07 +09:00
|
|
|
pci_msi_teardown_msi_irqs(dev);
|
2009-08-06 11:32:51 +09:00
|
|
|
|
2021-12-07 07:27:54 +09:00
|
|
|
if (dev->msix_base) {
|
|
|
|
iounmap(dev->msix_base);
|
|
|
|
dev->msix_base = NULL;
|
|
|
|
}
|
2009-08-06 11:32:51 +09:00
|
|
|
}
|
2007-01-18 13:50:05 +09:00
|
|
|
|
2007-10-25 17:16:30 +09:00
|
|
|
static void pci_intx_for_msi(struct pci_dev *dev, int enable)
|
|
|
|
{
|
|
|
|
if (!(dev->dev_flags & PCI_DEV_FLAGS_MSI_INTX_DISABLE_BUG))
|
|
|
|
pci_intx(dev, enable);
|
|
|
|
}
|
|
|
|
|
2020-12-04 03:51:09 +09:00
|
|
|
static void pci_msi_set_enable(struct pci_dev *dev, int enable)
|
|
|
|
{
|
|
|
|
u16 control;
|
|
|
|
|
|
|
|
pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &control);
|
|
|
|
control &= ~PCI_MSI_FLAGS_ENABLE;
|
|
|
|
if (enable)
|
|
|
|
control |= PCI_MSI_FLAGS_ENABLE;
|
|
|
|
pci_write_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, control);
|
|
|
|
}
|
|
|
|
|
2021-12-07 07:27:42 +09:00
|
|
|
/*
|
|
|
|
* Architecture override returns true when the PCI MSI message should be
|
|
|
|
* written by the generic restore function.
|
|
|
|
*/
|
|
|
|
bool __weak arch_restore_msi_irqs(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2007-01-25 17:34:08 +09:00
|
|
|
static void __pci_restore_msi_state(struct pci_dev *dev)
|
2006-02-08 18:11:38 +09:00
|
|
|
{
|
2007-03-09 05:04:57 +09:00
|
|
|
struct msi_desc *entry;
|
2021-12-07 07:27:42 +09:00
|
|
|
u16 control;
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2007-03-05 17:30:10 +09:00
|
|
|
if (!dev->msi_enabled)
|
|
|
|
return;
|
|
|
|
|
2011-03-29 00:49:12 +09:00
|
|
|
entry = irq_get_msi_desc(dev->irq);
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 0);
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msi_set_enable(dev, 0);
|
2021-12-07 07:27:42 +09:00
|
|
|
if (arch_restore_msi_irqs(dev))
|
|
|
|
__pci_write_msi_msg(entry, &entry->msg);
|
2007-03-09 05:04:57 +09:00
|
|
|
|
2013-04-18 08:34:36 +09:00
|
|
|
pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &control);
|
2021-07-30 06:51:58 +09:00
|
|
|
pci_msi_update_mask(entry, 0, 0);
|
2008-08-08 00:52:37 +09:00
|
|
|
control &= ~PCI_MSI_FLAGS_QSIZE;
|
2021-12-07 07:27:39 +09:00
|
|
|
control |= (entry->pci.msi_attrib.multiple << 4) | PCI_MSI_FLAGS_ENABLE;
|
2013-04-18 08:34:36 +09:00
|
|
|
pci_write_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, control);
|
2007-01-25 17:34:08 +09:00
|
|
|
}
|
|
|
|
|
2020-12-04 03:51:09 +09:00
|
|
|
static void pci_msix_clear_and_set_ctrl(struct pci_dev *dev, u16 clear, u16 set)
|
|
|
|
{
|
|
|
|
u16 ctrl;
|
|
|
|
|
|
|
|
pci_read_config_word(dev, dev->msix_cap + PCI_MSIX_FLAGS, &ctrl);
|
|
|
|
ctrl &= ~clear;
|
|
|
|
ctrl |= set;
|
|
|
|
pci_write_config_word(dev, dev->msix_cap + PCI_MSIX_FLAGS, ctrl);
|
|
|
|
}
|
|
|
|
|
2007-01-25 17:34:08 +09:00
|
|
|
static void __pci_restore_msix_state(struct pci_dev *dev)
|
2006-02-08 18:11:38 +09:00
|
|
|
{
|
|
|
|
struct msi_desc *entry;
|
2021-12-07 07:27:42 +09:00
|
|
|
bool write_msg;
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2007-01-29 04:42:52 +09:00
|
|
|
if (!dev->msix_enabled)
|
|
|
|
return;
|
|
|
|
|
2006-02-08 18:11:38 +09:00
|
|
|
/* route the table */
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 0);
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msix_clear_and_set_ctrl(dev, 0,
|
2014-06-19 17:29:53 +09:00
|
|
|
PCI_MSIX_FLAGS_ENABLE | PCI_MSIX_FLAGS_MASKALL);
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2021-12-07 07:27:42 +09:00
|
|
|
write_msg = arch_restore_msi_irqs(dev);
|
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_lock_descs(&dev->dev);
|
2021-12-07 07:51:18 +09:00
|
|
|
msi_for_each_desc(entry, &dev->dev, MSI_DESC_ALL) {
|
2021-12-07 07:27:42 +09:00
|
|
|
if (write_msg)
|
|
|
|
__pci_write_msi_msg(entry, &entry->msg);
|
2021-12-07 07:27:39 +09:00
|
|
|
pci_msix_write_vector_ctrl(entry, entry->pci.msix_ctrl);
|
2021-12-07 07:27:42 +09:00
|
|
|
}
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_unlock_descs(&dev->dev);
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msix_clear_and_set_ctrl(dev, PCI_MSIX_FLAGS_MASKALL, 0);
|
2006-02-08 18:11:38 +09:00
|
|
|
}
|
2007-01-25 17:34:08 +09:00
|
|
|
|
|
|
|
void pci_restore_msi_state(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
__pci_restore_msi_state(dev);
|
|
|
|
__pci_restore_msix_state(dev);
|
|
|
|
}
|
2007-11-08 06:43:59 +09:00
|
|
|
EXPORT_SYMBOL_GPL(pci_restore_msi_state);
|
2006-02-08 18:11:38 +09:00
|
|
|
|
2021-12-16 02:16:44 +09:00
|
|
|
static void pcim_msi_release(void *pcidev)
|
|
|
|
{
|
|
|
|
struct pci_dev *dev = pcidev;
|
|
|
|
|
|
|
|
dev->is_msi_managed = false;
|
|
|
|
pci_free_irq_vectors(dev);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Needs to be separate from pcim_release to prevent an ordering problem
|
|
|
|
* vs. msi_device_data_release() in the MSI core code.
|
|
|
|
*/
|
|
|
|
static int pcim_setup_msi_release(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!pci_is_managed(dev) || dev->is_msi_managed)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
ret = devm_add_action(&dev->dev, pcim_msi_release, dev);
|
|
|
|
if (!ret)
|
|
|
|
dev->is_msi_managed = true;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2021-12-16 02:19:49 +09:00
|
|
|
/*
|
|
|
|
* Ordering vs. devres: msi device data has to be installed first so that
|
|
|
|
* pcim_msi_release() is invoked before it on device release.
|
|
|
|
*/
|
|
|
|
static int pci_setup_msi_context(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
int ret = msi_setup_device_data(&dev->dev);
|
|
|
|
|
|
|
|
if (!ret)
|
|
|
|
ret = pcim_setup_msi_release(dev);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
static int msi_setup_msi_desc(struct pci_dev *dev, int nvec,
|
|
|
|
struct irq_affinity_desc *masks)
|
2014-07-08 11:07:23 +09:00
|
|
|
{
|
2021-12-07 07:51:15 +09:00
|
|
|
struct msi_desc desc;
|
2016-09-14 23:18:49 +09:00
|
|
|
u16 control;
|
|
|
|
|
2014-07-08 11:07:23 +09:00
|
|
|
/* MSI Entry Initialization */
|
2021-12-07 07:51:15 +09:00
|
|
|
memset(&desc, 0, sizeof(desc));
|
2014-07-08 11:07:23 +09:00
|
|
|
|
|
|
|
pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &control);
|
2021-11-05 03:01:29 +09:00
|
|
|
/* Lies, damned lies, and MSIs */
|
|
|
|
if (dev->dev_flags & PCI_DEV_FLAGS_HAS_MSI_MASKING)
|
|
|
|
control |= PCI_MSI_FLAGS_MASKBIT;
|
2021-12-07 07:51:15 +09:00
|
|
|
/* Respect XEN's mask disabling */
|
|
|
|
if (pci_msi_ignore_mask)
|
|
|
|
control &= ~PCI_MSI_FLAGS_MASKBIT;
|
2014-07-08 11:07:23 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
desc.nvec_used = nvec;
|
|
|
|
desc.pci.msi_attrib.is_64 = !!(control & PCI_MSI_FLAGS_64BIT);
|
|
|
|
desc.pci.msi_attrib.can_mask = !!(control & PCI_MSI_FLAGS_MASKBIT);
|
|
|
|
desc.pci.msi_attrib.default_irq = dev->irq;
|
|
|
|
desc.pci.msi_attrib.multi_cap = (control & PCI_MSI_FLAGS_QMASK) >> 1;
|
|
|
|
desc.pci.msi_attrib.multiple = ilog2(__roundup_pow_of_two(nvec));
|
|
|
|
desc.affinity = masks;
|
2014-07-08 11:07:23 +09:00
|
|
|
|
|
|
|
if (control & PCI_MSI_FLAGS_64BIT)
|
2021-12-07 07:51:15 +09:00
|
|
|
desc.pci.mask_pos = dev->msi_cap + PCI_MSI_MASK_64;
|
2014-07-08 11:07:23 +09:00
|
|
|
else
|
2021-12-07 07:51:15 +09:00
|
|
|
desc.pci.mask_pos = dev->msi_cap + PCI_MSI_MASK_32;
|
2014-07-08 11:07:23 +09:00
|
|
|
|
|
|
|
/* Save the initial mask status */
|
2021-12-07 07:51:15 +09:00
|
|
|
if (desc.pci.msi_attrib.can_mask)
|
|
|
|
pci_read_config_dword(dev, desc.pci.mask_pos, &desc.pci.msi_mask);
|
2014-07-08 11:07:23 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
return msi_add_msi_desc(&dev->dev, &desc);
|
2014-07-08 11:07:23 +09:00
|
|
|
}
|
|
|
|
|
2014-10-03 14:13:24 +09:00
|
|
|
static int msi_verify_entries(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
struct msi_desc *entry;
|
|
|
|
|
2021-07-30 06:51:52 +09:00
|
|
|
if (!dev->no_64bit_msi)
|
|
|
|
return 0;
|
|
|
|
|
2021-12-07 07:51:18 +09:00
|
|
|
msi_for_each_desc(entry, &dev->dev, MSI_DESC_ALL) {
|
2021-07-30 06:51:52 +09:00
|
|
|
if (entry->msg.address_hi) {
|
2020-12-04 03:51:10 +09:00
|
|
|
pci_err(dev, "arch assigned 64-bit MSI address %#x%08x but device only supports 32 bits\n",
|
|
|
|
entry->msg.address_hi, entry->msg.address_lo);
|
2021-12-07 07:51:18 +09:00
|
|
|
break;
|
2020-12-04 03:51:10 +09:00
|
|
|
}
|
2014-10-03 14:13:24 +09:00
|
|
|
}
|
2021-12-07 07:51:18 +09:00
|
|
|
return !entry ? 0 : -EIO;
|
2014-10-03 14:13:24 +09:00
|
|
|
}
|
|
|
|
|
2005-04-17 07:20:36 +09:00
|
|
|
/**
|
|
|
|
* msi_capability_init - configure device's MSI capability structure
|
|
|
|
* @dev: pointer to the pci_dev data structure of MSI device function
|
2009-03-17 21:54:10 +09:00
|
|
|
* @nvec: number of interrupts to allocate
|
2019-05-30 22:05:58 +09:00
|
|
|
* @affd: description of automatic IRQ affinity assignments (may be %NULL)
|
2005-04-17 07:20:36 +09:00
|
|
|
*
|
2009-03-17 21:54:10 +09:00
|
|
|
* Setup the MSI capability structure of the device with the requested
|
|
|
|
* number of interrupts. A return value of zero indicates the successful
|
2019-05-30 22:05:58 +09:00
|
|
|
* setup of an entry with the new MSI IRQ. A negative return value indicates
|
2009-03-17 21:54:10 +09:00
|
|
|
* an error, and a positive return value indicates the number of interrupts
|
|
|
|
* which could have been allocated.
|
|
|
|
*/
|
2016-11-09 10:15:04 +09:00
|
|
|
static int msi_capability_init(struct pci_dev *dev, int nvec,
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
struct irq_affinity *affd)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
2021-12-07 07:51:13 +09:00
|
|
|
struct irq_affinity_desc *masks = NULL;
|
2005-04-17 07:20:36 +09:00
|
|
|
struct msi_desc *entry;
|
2013-04-05 01:54:32 +09:00
|
|
|
int ret;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-12-11 07:18:44 +09:00
|
|
|
/*
|
|
|
|
* Disable MSI during setup in the hardware, but mark it enabled
|
|
|
|
* so that setup code can evaluate it.
|
|
|
|
*/
|
|
|
|
pci_msi_set_enable(dev, 0);
|
|
|
|
dev->msi_enabled = 1;
|
2009-06-16 21:31:45 +09:00
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
if (affd)
|
|
|
|
masks = irq_create_affinity_masks(nvec, affd);
|
|
|
|
|
|
|
|
msi_lock_descs(&dev->dev);
|
2021-12-07 07:51:15 +09:00
|
|
|
ret = msi_setup_msi_desc(dev, nvec, masks);
|
|
|
|
if (ret)
|
2021-12-11 07:18:44 +09:00
|
|
|
goto fail;
|
2006-10-04 18:16:41 +09:00
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* All MSIs are unmasked by default; mask them all */
|
2021-12-07 07:51:18 +09:00
|
|
|
entry = msi_first_desc(&dev->dev, MSI_DESC_ALL);
|
2021-07-30 06:51:58 +09:00
|
|
|
pci_msi_mask(entry, msi_multi_mask(entry));
|
2009-03-17 21:54:09 +09:00
|
|
|
|
2005-04-17 07:20:36 +09:00
|
|
|
/* Configure MSI capability structure */
|
2014-11-15 23:24:07 +09:00
|
|
|
ret = pci_msi_setup_msi_irqs(dev, nvec, PCI_CAP_ID_MSI);
|
2021-07-30 06:51:54 +09:00
|
|
|
if (ret)
|
|
|
|
goto err;
|
2007-01-29 04:56:37 +09:00
|
|
|
|
2014-10-03 14:13:24 +09:00
|
|
|
ret = msi_verify_entries(dev);
|
2021-07-30 06:51:54 +09:00
|
|
|
if (ret)
|
|
|
|
goto err;
|
2014-10-03 14:13:24 +09:00
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* Set MSI enabled bits */
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 0);
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msi_set_enable(dev, 1);
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2015-07-31 04:00:08 +09:00
|
|
|
pcibios_free_irq(dev);
|
2007-04-18 18:39:21 +09:00
|
|
|
dev->irq = entry->irq;
|
2021-12-07 07:51:13 +09:00
|
|
|
goto unlock;
|
2021-07-30 06:51:54 +09:00
|
|
|
|
|
|
|
err:
|
2021-07-30 06:51:58 +09:00
|
|
|
pci_msi_unmask(entry, msi_multi_mask(entry));
|
2021-07-30 06:51:54 +09:00
|
|
|
free_msi_irqs(dev);
|
2021-12-11 07:18:44 +09:00
|
|
|
fail:
|
|
|
|
dev->msi_enabled = 0;
|
2021-12-07 07:51:13 +09:00
|
|
|
unlock:
|
|
|
|
msi_unlock_descs(&dev->dev);
|
|
|
|
kfree(masks);
|
2021-07-30 06:51:54 +09:00
|
|
|
return ret;
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
|
|
|
|
2021-10-13 10:41:36 +09:00
|
|
|
static void __iomem *msix_map_region(struct pci_dev *dev,
|
|
|
|
unsigned int nr_entries)
|
2009-08-06 11:34:34 +09:00
|
|
|
{
|
2010-06-17 10:42:44 +09:00
|
|
|
resource_size_t phys_addr;
|
2009-08-06 11:34:34 +09:00
|
|
|
u32 table_offset;
|
PCI: Fail MSI-X mappings if there's no space assigned to MSI-X BAR
Unlike MSI, which is configured via registers in the MSI capability in
Configuration Space, MSI-X is configured via tables in Memory Space.
These MSI-X tables are mapped by a device BAR, and if no Memory Space
has been assigned to the BAR, MSI-X cannot be used.
Fail MSI-X setup if no space has been assigned for the BAR.
Previously, we ioremapped the MSI-X table even if the resource hadn't been
assigned. In this case, the resource address is undefined (and is often
zero), which may lead to warnings or oopses in this path:
pci_enable_msix
msix_capability_init
msix_map_region
ioremap_nocache
The PCI core sets resource flags to zero when it can't assign space for the
resource (see reset_resource()). There are also some cases where it sets
the IORESOURCE_UNSET flag, e.g., pci_reassigndev_resource_alignment(),
pci_assign_resource(), etc. So we must check for both cases.
[bhelgaas: changelog]
Reported-by: Zhang Jukuo <zhangjukuo@huawei.com>
Tested-by: Zhang Jukuo <zhangjukuo@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2015-01-28 10:52:17 +09:00
|
|
|
unsigned long flags;
|
2009-08-06 11:34:34 +09:00
|
|
|
u8 bir;
|
|
|
|
|
2013-04-18 08:43:40 +09:00
|
|
|
pci_read_config_dword(dev, dev->msix_cap + PCI_MSIX_TABLE,
|
|
|
|
&table_offset);
|
2013-04-18 09:10:07 +09:00
|
|
|
bir = (u8)(table_offset & PCI_MSIX_TABLE_BIR);
|
PCI: Fail MSI-X mappings if there's no space assigned to MSI-X BAR
Unlike MSI, which is configured via registers in the MSI capability in
Configuration Space, MSI-X is configured via tables in Memory Space.
These MSI-X tables are mapped by a device BAR, and if no Memory Space
has been assigned to the BAR, MSI-X cannot be used.
Fail MSI-X setup if no space has been assigned for the BAR.
Previously, we ioremapped the MSI-X table even if the resource hadn't been
assigned. In this case, the resource address is undefined (and is often
zero), which may lead to warnings or oopses in this path:
pci_enable_msix
msix_capability_init
msix_map_region
ioremap_nocache
The PCI core sets resource flags to zero when it can't assign space for the
resource (see reset_resource()). There are also some cases where it sets
the IORESOURCE_UNSET flag, e.g., pci_reassigndev_resource_alignment(),
pci_assign_resource(), etc. So we must check for both cases.
[bhelgaas: changelog]
Reported-by: Zhang Jukuo <zhangjukuo@huawei.com>
Tested-by: Zhang Jukuo <zhangjukuo@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2015-01-28 10:52:17 +09:00
|
|
|
flags = pci_resource_flags(dev, bir);
|
|
|
|
if (!flags || (flags & IORESOURCE_UNSET))
|
|
|
|
return NULL;
|
|
|
|
|
2013-04-18 09:10:07 +09:00
|
|
|
table_offset &= PCI_MSIX_TABLE_OFFSET;
|
2009-08-06 11:34:34 +09:00
|
|
|
phys_addr = pci_resource_start(dev, bir) + table_offset;
|
|
|
|
|
2020-01-06 17:43:50 +09:00
|
|
|
return ioremap(phys_addr, nr_entries * PCI_MSIX_ENTRY_SIZE);
|
2009-08-06 11:34:34 +09:00
|
|
|
}
|
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
static int msix_setup_msi_descs(struct pci_dev *dev, void __iomem *base,
|
|
|
|
struct msix_entry *entries, int nvec,
|
|
|
|
struct irq_affinity_desc *masks)
|
2009-08-06 11:35:48 +09:00
|
|
|
{
|
2021-12-07 07:51:15 +09:00
|
|
|
int ret = 0, i, vec_count = pci_msix_vec_count(dev);
|
2021-12-07 07:51:13 +09:00
|
|
|
struct irq_affinity_desc *curmsk;
|
2021-12-07 07:51:15 +09:00
|
|
|
struct msi_desc desc;
|
2021-07-30 06:51:41 +09:00
|
|
|
void __iomem *addr;
|
2016-07-12 18:20:18 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
memset(&desc, 0, sizeof(desc));
|
2021-07-30 06:51:41 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
desc.nvec_used = 1;
|
|
|
|
desc.pci.msi_attrib.is_msix = 1;
|
|
|
|
desc.pci.msi_attrib.is_64 = 1;
|
|
|
|
desc.pci.msi_attrib.default_irq = dev->irq;
|
|
|
|
desc.pci.mask_base = base;
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
for (i = 0, curmsk = masks; i < nvec; i++, curmsk++) {
|
|
|
|
desc.msi_index = entries ? entries[i].entry : i;
|
|
|
|
desc.affinity = masks ? curmsk : NULL;
|
|
|
|
desc.pci.msi_attrib.is_virtual = desc.msi_index >= vec_count;
|
|
|
|
desc.pci.msi_attrib.can_mask = !pci_msi_ignore_mask &&
|
|
|
|
!desc.pci.msi_attrib.is_virtual;
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2022-02-14 19:07:47 +09:00
|
|
|
if (desc.pci.msi_attrib.can_mask) {
|
2021-12-07 07:51:15 +09:00
|
|
|
addr = pci_msix_desc_addr(&desc);
|
|
|
|
desc.pci.msix_ctrl = readl(addr + PCI_MSIX_ENTRY_VECTOR_CTRL);
|
2021-07-30 06:51:55 +09:00
|
|
|
}
|
2021-07-30 06:51:41 +09:00
|
|
|
|
2021-12-07 07:51:15 +09:00
|
|
|
ret = msi_add_msi_desc(&dev->dev, &desc);
|
|
|
|
if (ret)
|
|
|
|
break;
|
2009-08-06 11:35:48 +09:00
|
|
|
}
|
2021-12-07 07:51:15 +09:00
|
|
|
return ret;
|
2009-08-06 11:35:48 +09:00
|
|
|
}
|
|
|
|
|
2021-07-30 06:51:41 +09:00
|
|
|
static void msix_update_entries(struct pci_dev *dev, struct msix_entry *entries)
|
2009-08-06 11:35:10 +09:00
|
|
|
{
|
2021-12-07 07:51:18 +09:00
|
|
|
struct msi_desc *desc;
|
2009-08-06 11:35:10 +09:00
|
|
|
|
2021-12-07 07:27:46 +09:00
|
|
|
if (entries) {
|
2021-12-07 07:51:18 +09:00
|
|
|
msi_for_each_desc(desc, &dev->dev, MSI_DESC_ALL) {
|
|
|
|
entries->vector = desc->irq;
|
2021-07-30 06:51:41 +09:00
|
|
|
entries++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2021-07-30 06:51:41 +09:00
|
|
|
static void msix_mask_all(void __iomem *base, int tsize)
|
|
|
|
{
|
|
|
|
u32 ctrl = PCI_MSIX_ENTRY_CTRL_MASKBIT;
|
|
|
|
int i;
|
2019-05-24 07:30:51 +09:00
|
|
|
|
2021-08-27 02:03:42 +09:00
|
|
|
if (pci_msi_ignore_mask)
|
|
|
|
return;
|
|
|
|
|
2021-07-30 06:51:41 +09:00
|
|
|
for (i = 0; i < tsize; i++, base += PCI_MSIX_ENTRY_SIZE)
|
|
|
|
writel(ctrl, base + PCI_MSIX_ENTRY_VECTOR_CTRL);
|
2009-08-06 11:35:10 +09:00
|
|
|
}
|
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
static int msix_setup_interrupts(struct pci_dev *dev, void __iomem *base,
|
|
|
|
struct msix_entry *entries, int nvec,
|
|
|
|
struct irq_affinity *affd)
|
|
|
|
{
|
|
|
|
struct irq_affinity_desc *masks = NULL;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (affd)
|
|
|
|
masks = irq_create_affinity_masks(nvec, affd);
|
|
|
|
|
|
|
|
msi_lock_descs(&dev->dev);
|
2021-12-07 07:51:15 +09:00
|
|
|
ret = msix_setup_msi_descs(dev, base, entries, nvec, masks);
|
2021-12-07 07:51:13 +09:00
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
ret = pci_msi_setup_msi_irqs(dev, nvec, PCI_CAP_ID_MSIX);
|
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
/* Check if all MSI entries honor device restrictions */
|
|
|
|
ret = msi_verify_entries(dev);
|
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
msix_update_entries(dev, entries);
|
|
|
|
goto out_unlock;
|
|
|
|
|
|
|
|
out_free:
|
|
|
|
free_msi_irqs(dev);
|
|
|
|
out_unlock:
|
|
|
|
msi_unlock_descs(&dev->dev);
|
|
|
|
kfree(masks);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2005-04-17 07:20:36 +09:00
|
|
|
/**
|
|
|
|
* msix_capability_init - configure device's MSI-X capability
|
|
|
|
* @dev: pointer to the pci_dev data structure of MSI-X device function
|
2005-10-24 03:57:38 +09:00
|
|
|
* @entries: pointer to an array of struct msix_entry entries
|
|
|
|
* @nvec: number of @entries
|
2019-05-30 22:05:58 +09:00
|
|
|
* @affd: Optional pointer to enable automatic affinity assignment
|
2005-04-17 07:20:36 +09:00
|
|
|
*
|
2005-05-04 09:38:30 +09:00
|
|
|
* Setup the MSI-X capability structure of device function with a
|
2019-05-30 22:05:58 +09:00
|
|
|
* single MSI-X IRQ. A return of zero indicates the successful setup of
|
|
|
|
* requested MSI-X entries with allocated IRQs or non-zero for otherwise.
|
2005-04-17 07:20:36 +09:00
|
|
|
**/
|
2016-09-14 23:18:49 +09:00
|
|
|
static int msix_capability_init(struct pci_dev *dev, struct msix_entry *entries,
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
int nvec, struct irq_affinity *affd)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
|
|
|
void __iomem *base;
|
2021-07-30 06:51:41 +09:00
|
|
|
int ret, tsize;
|
|
|
|
u16 control;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-07-30 06:51:40 +09:00
|
|
|
/*
|
|
|
|
* Some devices require MSI-X to be enabled before the MSI-X
|
|
|
|
* registers can be accessed. Mask all the vectors to prevent
|
|
|
|
* interrupts coming in before they're fully set up.
|
|
|
|
*/
|
|
|
|
pci_msix_clear_and_set_ctrl(dev, 0, PCI_MSIX_FLAGS_MASKALL |
|
|
|
|
PCI_MSIX_FLAGS_ENABLE);
|
2009-06-19 11:15:59 +09:00
|
|
|
|
2021-12-11 07:18:44 +09:00
|
|
|
/* Mark it enabled so setup functions can query it */
|
|
|
|
dev->msix_enabled = 1;
|
|
|
|
|
2014-06-19 17:29:53 +09:00
|
|
|
pci_read_config_word(dev, dev->msix_cap + PCI_MSIX_FLAGS, &control);
|
2005-04-17 07:20:36 +09:00
|
|
|
/* Request & Map MSI-X table region */
|
2021-07-30 06:51:41 +09:00
|
|
|
tsize = msix_table_size(control);
|
|
|
|
base = msix_map_region(dev, tsize);
|
2021-07-30 06:51:40 +09:00
|
|
|
if (!base) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto out_disable;
|
|
|
|
}
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2021-12-07 07:27:54 +09:00
|
|
|
dev->msix_base = base;
|
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
ret = msix_setup_interrupts(dev, base, entries, nvec, affd);
|
2009-08-06 11:35:48 +09:00
|
|
|
if (ret)
|
2021-12-07 07:51:13 +09:00
|
|
|
goto out_disable;
|
2009-06-19 11:15:59 +09:00
|
|
|
|
2021-12-11 07:18:44 +09:00
|
|
|
/* Disable INTX */
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 0);
|
2021-12-14 20:49:32 +09:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Ensure that all table entries are masked to prevent
|
|
|
|
* stale entries from firing in a crash kernel.
|
|
|
|
*
|
|
|
|
* Done late to deal with a broken Marvell NVME device
|
|
|
|
* which takes the MSI-X mask bits into account even
|
|
|
|
* when MSI-X is disabled, which prevents MSI delivery.
|
|
|
|
*/
|
|
|
|
msix_mask_all(base, tsize);
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msix_clear_and_set_ctrl(dev, PCI_MSIX_FLAGS_MASKALL, 0);
|
2009-05-08 22:13:33 +09:00
|
|
|
|
2015-07-31 04:00:08 +09:00
|
|
|
pcibios_free_irq(dev);
|
2005-04-17 07:20:36 +09:00
|
|
|
return 0;
|
2009-08-06 11:33:39 +09:00
|
|
|
|
2021-07-30 06:51:40 +09:00
|
|
|
out_disable:
|
2021-12-11 07:18:44 +09:00
|
|
|
dev->msix_enabled = 0;
|
2021-12-14 20:42:14 +09:00
|
|
|
pci_msix_clear_and_set_ctrl(dev, PCI_MSIX_FLAGS_MASKALL | PCI_MSIX_FLAGS_ENABLE, 0);
|
2021-07-30 06:51:40 +09:00
|
|
|
|
2009-08-06 11:33:39 +09:00
|
|
|
return ret;
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
|
|
|
|
2006-08-31 14:55:07 +09:00
|
|
|
/**
|
2014-09-24 03:45:58 +09:00
|
|
|
* pci_msi_supported - check whether MSI may be enabled on a device
|
2006-08-31 14:55:07 +09:00
|
|
|
* @dev: pointer to the pci_dev data structure of MSI device function
|
2019-05-30 22:05:58 +09:00
|
|
|
* @nvec: how many MSIs have been requested?
|
2006-08-31 14:55:07 +09:00
|
|
|
*
|
2013-11-15 03:28:18 +09:00
|
|
|
* Look at global flags, the device itself, and its parent buses
|
2007-04-05 16:19:07 +09:00
|
|
|
* to determine if MSI/-X are supported for the device. If MSI/-X is
|
2014-09-24 03:45:58 +09:00
|
|
|
* supported return 1, else return 0.
|
2006-08-31 14:55:07 +09:00
|
|
|
**/
|
2014-09-24 03:45:58 +09:00
|
|
|
static int pci_msi_supported(struct pci_dev *dev, int nvec)
|
2006-08-31 14:55:07 +09:00
|
|
|
{
|
|
|
|
struct pci_bus *bus;
|
|
|
|
|
2006-10-05 17:24:31 +09:00
|
|
|
/* MSI must be globally enabled and supported by the device */
|
2014-09-24 05:25:11 +09:00
|
|
|
if (!pci_msi_enable)
|
2014-09-24 03:45:58 +09:00
|
|
|
return 0;
|
2014-09-24 05:25:11 +09:00
|
|
|
|
2019-10-15 06:17:05 +09:00
|
|
|
if (!dev || dev->no_msi)
|
2014-09-24 03:45:58 +09:00
|
|
|
return 0;
|
2006-08-31 14:55:07 +09:00
|
|
|
|
2007-04-05 16:19:12 +09:00
|
|
|
/*
|
|
|
|
* You can't ask to have 0 or less MSIs configured.
|
|
|
|
* a) it's stupid ..
|
|
|
|
* b) the list manipulation code assumes nvec >= 1.
|
|
|
|
*/
|
|
|
|
if (nvec < 1)
|
2014-09-24 03:45:58 +09:00
|
|
|
return 0;
|
2007-04-05 16:19:12 +09:00
|
|
|
|
2009-08-10 10:14:15 +09:00
|
|
|
/*
|
|
|
|
* Any bridge which does NOT route MSI transactions from its
|
|
|
|
* secondary bus to its primary bus must set NO_MSI flag on
|
2006-10-05 17:24:31 +09:00
|
|
|
* the secondary pci_bus.
|
2021-03-31 00:11:44 +09:00
|
|
|
*
|
|
|
|
* The NO_MSI flag can either be set directly by:
|
|
|
|
* - arch-specific PCI host bus controller drivers (deprecated)
|
|
|
|
* - quirks for specific PCI bridges
|
|
|
|
*
|
|
|
|
* or indirectly by platform-specific PCI host bridge drivers by
|
|
|
|
* advertising the 'msi_domain' property, which results in
|
|
|
|
* the NO_MSI flag when no MSI domain is found for this bridge
|
|
|
|
* at probe time.
|
2006-10-05 17:24:31 +09:00
|
|
|
*/
|
2006-08-31 14:55:07 +09:00
|
|
|
for (bus = dev->bus; bus; bus = bus->parent)
|
|
|
|
if (bus->bus_flags & PCI_BUS_FLAGS_NO_MSI)
|
2014-09-24 03:45:58 +09:00
|
|
|
return 0;
|
2006-08-31 14:55:07 +09:00
|
|
|
|
2014-09-24 03:45:58 +09:00
|
|
|
return 1;
|
2006-08-31 14:55:07 +09:00
|
|
|
}
|
|
|
|
|
2013-12-30 16:28:13 +09:00
|
|
|
/**
|
|
|
|
* pci_msi_vec_count - Return the number of MSI vectors a device can send
|
|
|
|
* @dev: device to report about
|
|
|
|
*
|
|
|
|
* This function returns the number of MSI vectors a device requested via
|
|
|
|
* Multiple Message Capable register. It returns a negative errno if the
|
|
|
|
* device is not capable sending MSI interrupts. Otherwise, the call succeeds
|
|
|
|
* and returns a power of two, up to a maximum of 2^5 (32), according to the
|
|
|
|
* MSI specification.
|
|
|
|
**/
|
|
|
|
int pci_msi_vec_count(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
u16 msgctl;
|
|
|
|
|
|
|
|
if (!dev->msi_cap)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &msgctl);
|
|
|
|
ret = 1 << ((msgctl & PCI_MSI_FLAGS_QMASK) >> 1);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(pci_msi_vec_count);
|
|
|
|
|
2017-03-10 06:45:14 +09:00
|
|
|
static void pci_msi_shutdown(struct pci_dev *dev)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
2009-03-17 21:54:09 +09:00
|
|
|
struct msi_desc *desc;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2007-03-22 19:51:39 +09:00
|
|
|
if (!pci_msi_enable || !dev || !dev->msi_enabled)
|
2007-01-29 04:42:52 +09:00
|
|
|
return;
|
|
|
|
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msi_set_enable(dev, 0);
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 1);
|
2007-03-05 17:30:10 +09:00
|
|
|
dev->msi_enabled = 0;
|
2006-10-04 18:16:31 +09:00
|
|
|
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
/* Return the device with MSI unmasked as initial states */
|
2021-12-07 07:51:18 +09:00
|
|
|
desc = msi_first_desc(&dev->dev, MSI_DESC_ALL);
|
|
|
|
if (!WARN_ON_ONCE(!desc))
|
|
|
|
pci_msi_unmask(desc, msi_multi_mask(desc));
|
2007-03-22 19:51:27 +09:00
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* Restore dev->irq to its default pin-assertion IRQ */
|
2021-12-07 07:27:39 +09:00
|
|
|
dev->irq = desc->pci.msi_attrib.default_irq;
|
2015-07-31 04:00:08 +09:00
|
|
|
pcibios_alloc_irq(dev);
|
2008-04-24 06:58:09 +09:00
|
|
|
}
|
2009-03-17 21:54:06 +09:00
|
|
|
|
2009-08-10 10:14:15 +09:00
|
|
|
void pci_disable_msi(struct pci_dev *dev)
|
2008-04-24 06:58:09 +09:00
|
|
|
{
|
|
|
|
if (!pci_msi_enable || !dev || !dev->msi_enabled)
|
|
|
|
return;
|
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_lock_descs(&dev->dev);
|
2008-04-24 06:58:09 +09:00
|
|
|
pci_msi_shutdown(dev);
|
2009-08-06 11:32:51 +09:00
|
|
|
free_msi_irqs(dev);
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_unlock_descs(&dev->dev);
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
2007-03-22 19:51:34 +09:00
|
|
|
EXPORT_SYMBOL(pci_disable_msi);
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2009-01-24 08:21:14 +09:00
|
|
|
/**
|
2013-12-30 16:28:15 +09:00
|
|
|
* pci_msix_vec_count - return the number of device's MSI-X table entries
|
2009-01-24 08:21:14 +09:00
|
|
|
* @dev: pointer to the pci_dev data structure of MSI-X device function
|
2013-12-30 16:28:15 +09:00
|
|
|
* This function returns the number of device's MSI-X table entries and
|
|
|
|
* therefore the number of MSI-X vectors device is capable of sending.
|
|
|
|
* It returns a negative errno if the device is not capable of sending MSI-X
|
|
|
|
* interrupts.
|
|
|
|
**/
|
|
|
|
int pci_msix_vec_count(struct pci_dev *dev)
|
2009-01-24 08:21:14 +09:00
|
|
|
{
|
|
|
|
u16 control;
|
|
|
|
|
2013-04-05 01:54:33 +09:00
|
|
|
if (!dev->msix_cap)
|
2013-12-30 16:28:15 +09:00
|
|
|
return -EINVAL;
|
2009-01-24 08:21:14 +09:00
|
|
|
|
2013-04-18 08:38:32 +09:00
|
|
|
pci_read_config_word(dev, dev->msix_cap + PCI_MSIX_FLAGS, &control);
|
2013-04-18 08:44:48 +09:00
|
|
|
return msix_table_size(control);
|
2009-01-24 08:21:14 +09:00
|
|
|
}
|
2013-12-30 16:28:15 +09:00
|
|
|
EXPORT_SYMBOL(pci_msix_vec_count);
|
2009-01-24 08:21:14 +09:00
|
|
|
|
2016-09-14 23:18:49 +09:00
|
|
|
static int __pci_enable_msix(struct pci_dev *dev, struct msix_entry *entries,
|
2019-05-24 07:30:51 +09:00
|
|
|
int nvec, struct irq_affinity *affd, int flags)
|
2005-04-17 07:20:36 +09:00
|
|
|
{
|
2014-09-24 05:38:28 +09:00
|
|
|
int nr_entries;
|
2007-01-29 04:42:52 +09:00
|
|
|
int i, j;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2019-10-15 06:17:05 +09:00
|
|
|
if (!pci_msi_supported(dev, nvec) || dev->current_state != PCI_D0)
|
2014-09-24 03:45:58 +09:00
|
|
|
return -EINVAL;
|
2007-04-05 16:19:08 +09:00
|
|
|
|
2013-12-30 16:28:15 +09:00
|
|
|
nr_entries = pci_msix_vec_count(dev);
|
|
|
|
if (nr_entries < 0)
|
|
|
|
return nr_entries;
|
2019-05-24 07:30:51 +09:00
|
|
|
if (nvec > nr_entries && !(flags & PCI_IRQ_VIRTUAL))
|
2009-05-07 17:28:41 +09:00
|
|
|
return nr_entries;
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2016-07-12 18:20:16 +09:00
|
|
|
if (entries) {
|
|
|
|
/* Check for any invalid entries */
|
|
|
|
for (i = 0; i < nvec; i++) {
|
|
|
|
if (entries[i].entry >= nr_entries)
|
|
|
|
return -EINVAL; /* invalid entry */
|
|
|
|
for (j = i + 1; j < nvec; j++) {
|
|
|
|
if (entries[i].entry == entries[j].entry)
|
|
|
|
return -EINVAL; /* duplicate entry */
|
|
|
|
}
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
|
|
|
}
|
2006-10-04 18:16:31 +09:00
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* Check whether driver already requested for MSI IRQ */
|
2009-08-10 10:14:15 +09:00
|
|
|
if (dev->msi_enabled) {
|
2018-01-19 03:55:24 +09:00
|
|
|
pci_info(dev, "can't enable MSI-X (MSI IRQ already assigned)\n");
|
2005-04-17 07:20:36 +09:00
|
|
|
return -EINVAL;
|
|
|
|
}
|
2016-11-09 10:15:04 +09:00
|
|
|
return msix_capability_init(dev, entries, nvec, affd);
|
2016-09-14 23:18:49 +09:00
|
|
|
}
|
|
|
|
|
2017-03-10 06:45:14 +09:00
|
|
|
static void pci_msix_shutdown(struct pci_dev *dev)
|
2007-03-22 19:51:33 +09:00
|
|
|
{
|
2021-12-07 07:51:18 +09:00
|
|
|
struct msi_desc *desc;
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
|
2007-03-22 19:51:39 +09:00
|
|
|
if (!pci_msi_enable || !dev || !dev->msix_enabled)
|
2007-01-29 04:42:52 +09:00
|
|
|
return;
|
|
|
|
|
2017-03-30 12:49:11 +09:00
|
|
|
if (pci_dev_is_disconnected(dev)) {
|
|
|
|
dev->msix_enabled = 0;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
/* Return the device with MSI-X masked as initial states */
|
2021-12-07 07:51:18 +09:00
|
|
|
msi_for_each_desc(desc, &dev->dev, MSI_DESC_ALL)
|
|
|
|
pci_msix_mask(desc);
|
PCI MSI: Fix restoration of MSI/MSI-X mask states in suspend/resume
There are 2 problems on mask states in suspend/resume.
[1]:
It is better to restore the mask states of MSI/MSI-X to initial states
(MSI is unmasked, MSI-X is masked) when we release the device.
The pci_msi_shutdown() does the restoration of mask states for MSI,
while the msi_free_irqs() does it for MSI-X. In other words, in the
"disable" path both of MSI and MSI-X are handled, but in the "shutdown"
path only MSI is handled.
MSI:
pci_disable_msi()
=> pci_msi_shutdown()
[ mask states for MSI restored ]
=> msi_set_enable(dev, pos, 0);
=> msi_free_irqs()
MSI-X:
pci_disable_msix()
=> pci_msix_shutdown()
=> msix_set_enable(dev, 0);
=> msix_free_all_irqs
=> msi_free_irqs()
[ mask states for MSI-X restored ]
This patch moves the masking for MSI-X from msi_free_irqs() to
pci_msix_shutdown().
This change has some positive side effects:
- It prevents OS from touching mask states before reading preserved
bits in the register, which can be happen if msi_free_irqs() is
called from error path in msix_capability_init().
- It also prevents touching the register after turning off MSI-X in
"disable" path, which can be a problem on some devices.
[2]:
We have cache of the mask state in msi_desc, which is automatically
updated when msi/msix_mask_irq() is called. This cached states are
used for the resume.
But since what need to be restored in the resume is the states before
the shutdown on the suspend, calling msi/msix_mask_irq() from
pci_msi/msix_shutdown() is not appropriate.
This patch introduces __msi/msix_mask_irq() that do mask as same
as msi/msix_mask_irq() but does not update cached state, for use
in pci_msi/msix_shutdown().
[updated: get rid of msi/msix_mask_irq_nocache() (proposed by Matthew Wilcox)]
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-06-24 12:08:09 +09:00
|
|
|
|
2015-05-07 23:52:21 +09:00
|
|
|
pci_msix_clear_and_set_ctrl(dev, PCI_MSIX_FLAGS_ENABLE, 0);
|
2007-10-25 17:16:30 +09:00
|
|
|
pci_intx_for_msi(dev, 1);
|
2007-03-05 17:30:10 +09:00
|
|
|
dev->msix_enabled = 0;
|
2015-07-31 04:00:08 +09:00
|
|
|
pcibios_alloc_irq(dev);
|
2008-04-24 06:58:09 +09:00
|
|
|
}
|
2009-08-06 11:31:27 +09:00
|
|
|
|
2009-08-10 10:14:15 +09:00
|
|
|
void pci_disable_msix(struct pci_dev *dev)
|
2008-04-24 06:58:09 +09:00
|
|
|
{
|
|
|
|
if (!pci_msi_enable || !dev || !dev->msix_enabled)
|
|
|
|
return;
|
|
|
|
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_lock_descs(&dev->dev);
|
2008-04-24 06:58:09 +09:00
|
|
|
pci_msix_shutdown(dev);
|
2009-08-06 11:32:51 +09:00
|
|
|
free_msi_irqs(dev);
|
2021-12-07 07:51:13 +09:00
|
|
|
msi_unlock_descs(&dev->dev);
|
2005-04-17 07:20:36 +09:00
|
|
|
}
|
2007-03-22 19:51:34 +09:00
|
|
|
EXPORT_SYMBOL(pci_disable_msix);
|
2005-04-17 07:20:36 +09:00
|
|
|
|
2016-07-12 18:20:18 +09:00
|
|
|
static int __pci_enable_msi_range(struct pci_dev *dev, int minvec, int maxvec,
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
struct irq_affinity *affd)
|
2013-12-30 16:28:16 +09:00
|
|
|
{
|
2014-04-14 22:28:35 +09:00
|
|
|
int nvec;
|
2013-12-30 16:28:16 +09:00
|
|
|
int rc;
|
|
|
|
|
2019-10-15 06:17:05 +09:00
|
|
|
if (!pci_msi_supported(dev, minvec) || dev->current_state != PCI_D0)
|
2014-09-24 03:45:58 +09:00
|
|
|
return -EINVAL;
|
2014-04-14 22:28:35 +09:00
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* Check whether driver already requested MSI-X IRQs */
|
2014-04-14 22:28:35 +09:00
|
|
|
if (dev->msix_enabled) {
|
2018-01-19 03:55:24 +09:00
|
|
|
pci_info(dev, "can't enable MSI (MSI-X already enabled)\n");
|
2014-04-14 22:28:35 +09:00
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2013-12-30 16:28:16 +09:00
|
|
|
if (maxvec < minvec)
|
|
|
|
return -ERANGE;
|
|
|
|
|
2018-09-24 23:00:41 +09:00
|
|
|
if (WARN_ON_ONCE(dev->msi_enabled))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2014-04-14 22:28:35 +09:00
|
|
|
nvec = pci_msi_vec_count(dev);
|
|
|
|
if (nvec < 0)
|
|
|
|
return nvec;
|
2016-07-12 18:20:18 +09:00
|
|
|
if (nvec < minvec)
|
2016-12-01 11:15:04 +09:00
|
|
|
return -ENOSPC;
|
2016-07-12 18:20:18 +09:00
|
|
|
|
|
|
|
if (nvec > maxvec)
|
2014-04-14 22:28:35 +09:00
|
|
|
nvec = maxvec;
|
|
|
|
|
2021-12-16 02:19:49 +09:00
|
|
|
rc = pci_setup_msi_context(dev);
|
2021-12-16 02:16:44 +09:00
|
|
|
if (rc)
|
|
|
|
return rc;
|
|
|
|
|
2016-07-12 18:20:18 +09:00
|
|
|
for (;;) {
|
2016-11-09 10:15:04 +09:00
|
|
|
if (affd) {
|
2017-05-19 02:47:47 +09:00
|
|
|
nvec = irq_calc_affinity_vectors(minvec, nvec, affd);
|
2016-07-12 18:20:18 +09:00
|
|
|
if (nvec < minvec)
|
|
|
|
return -ENOSPC;
|
|
|
|
}
|
|
|
|
|
2016-11-09 10:15:04 +09:00
|
|
|
rc = msi_capability_init(dev, nvec, affd);
|
2016-07-12 18:20:18 +09:00
|
|
|
if (rc == 0)
|
|
|
|
return nvec;
|
|
|
|
|
|
|
|
if (rc < 0)
|
2013-12-30 16:28:16 +09:00
|
|
|
return rc;
|
2016-07-12 18:20:18 +09:00
|
|
|
if (rc < minvec)
|
|
|
|
return -ENOSPC;
|
|
|
|
|
|
|
|
nvec = rc;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-01-10 05:37:40 +09:00
|
|
|
/* deprecated, don't use */
|
|
|
|
int pci_enable_msi(struct pci_dev *dev)
|
2016-07-12 18:20:18 +09:00
|
|
|
{
|
2017-01-10 05:37:40 +09:00
|
|
|
int rc = __pci_enable_msi_range(dev, 1, 1, NULL);
|
|
|
|
if (rc < 0)
|
|
|
|
return rc;
|
|
|
|
return 0;
|
2016-07-12 18:20:18 +09:00
|
|
|
}
|
2017-01-10 05:37:40 +09:00
|
|
|
EXPORT_SYMBOL(pci_enable_msi);
|
2016-07-12 18:20:18 +09:00
|
|
|
|
|
|
|
static int __pci_enable_msix_range(struct pci_dev *dev,
|
2016-11-09 10:15:04 +09:00
|
|
|
struct msix_entry *entries, int minvec,
|
2019-05-24 07:30:51 +09:00
|
|
|
int maxvec, struct irq_affinity *affd,
|
|
|
|
int flags)
|
2016-07-12 18:20:18 +09:00
|
|
|
{
|
2016-09-14 23:18:49 +09:00
|
|
|
int rc, nvec = maxvec;
|
2016-07-12 18:20:18 +09:00
|
|
|
|
|
|
|
if (maxvec < minvec)
|
|
|
|
return -ERANGE;
|
|
|
|
|
2018-09-24 23:00:41 +09:00
|
|
|
if (WARN_ON_ONCE(dev->msix_enabled))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2021-12-16 02:19:49 +09:00
|
|
|
rc = pci_setup_msi_context(dev);
|
2021-12-16 02:16:44 +09:00
|
|
|
if (rc)
|
|
|
|
return rc;
|
|
|
|
|
2016-07-12 18:20:18 +09:00
|
|
|
for (;;) {
|
2016-11-09 10:15:04 +09:00
|
|
|
if (affd) {
|
2017-05-19 02:47:47 +09:00
|
|
|
nvec = irq_calc_affinity_vectors(minvec, nvec, affd);
|
2016-07-12 18:20:18 +09:00
|
|
|
if (nvec < minvec)
|
2013-12-30 16:28:16 +09:00
|
|
|
return -ENOSPC;
|
|
|
|
}
|
|
|
|
|
2019-05-24 07:30:51 +09:00
|
|
|
rc = __pci_enable_msix(dev, entries, nvec, affd, flags);
|
2016-07-12 18:20:18 +09:00
|
|
|
if (rc == 0)
|
|
|
|
return nvec;
|
|
|
|
|
|
|
|
if (rc < 0)
|
|
|
|
return rc;
|
|
|
|
if (rc < minvec)
|
|
|
|
return -ENOSPC;
|
|
|
|
|
|
|
|
nvec = rc;
|
|
|
|
}
|
2013-12-30 16:28:16 +09:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* pci_enable_msix_range - configure device's MSI-X capability structure
|
|
|
|
* @dev: pointer to the pci_dev data structure of MSI-X device function
|
|
|
|
* @entries: pointer to an array of MSI-X entries
|
2019-05-30 22:05:58 +09:00
|
|
|
* @minvec: minimum number of MSI-X IRQs requested
|
|
|
|
* @maxvec: maximum number of MSI-X IRQs requested
|
2013-12-30 16:28:16 +09:00
|
|
|
*
|
|
|
|
* Setup the MSI-X capability structure of device function with a maximum
|
|
|
|
* possible number of interrupts in the range between @minvec and @maxvec
|
|
|
|
* upon its software driver call to request for MSI-X mode enabled on its
|
|
|
|
* hardware device function. It returns a negative errno if an error occurs.
|
|
|
|
* If it succeeds, it returns the actual number of interrupts allocated and
|
|
|
|
* indicates the successful configuration of MSI-X capability structure
|
|
|
|
* with new allocated MSI-X interrupts.
|
|
|
|
**/
|
|
|
|
int pci_enable_msix_range(struct pci_dev *dev, struct msix_entry *entries,
|
2016-07-12 18:20:18 +09:00
|
|
|
int minvec, int maxvec)
|
2013-12-30 16:28:16 +09:00
|
|
|
{
|
2019-05-24 07:30:51 +09:00
|
|
|
return __pci_enable_msix_range(dev, entries, minvec, maxvec, NULL, 0);
|
2013-12-30 16:28:16 +09:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(pci_enable_msix_range);
|
2014-11-11 22:02:18 +09:00
|
|
|
|
2016-07-12 18:20:17 +09:00
|
|
|
/**
|
2016-11-09 10:15:05 +09:00
|
|
|
* pci_alloc_irq_vectors_affinity - allocate multiple IRQs for a device
|
2016-07-12 18:20:17 +09:00
|
|
|
* @dev: PCI device to operate on
|
|
|
|
* @min_vecs: minimum number of vectors required (must be >= 1)
|
|
|
|
* @max_vecs: maximum (desired) number of vectors
|
|
|
|
* @flags: flags or quirks for the allocation
|
2016-11-09 10:15:05 +09:00
|
|
|
* @affd: optional description of the affinity requirements
|
2016-07-12 18:20:17 +09:00
|
|
|
*
|
|
|
|
* Allocate up to @max_vecs interrupt vectors for @dev, using MSI-X or MSI
|
|
|
|
* vectors if available, and fall back to a single legacy vector
|
|
|
|
* if neither is available. Return the number of vectors allocated,
|
|
|
|
* (which might be smaller than @max_vecs) if successful, or a negative
|
|
|
|
* error code on error. If less than @min_vecs interrupt vectors are
|
|
|
|
* available for @dev the function will fail with -ENOSPC.
|
|
|
|
*
|
|
|
|
* To get the Linux IRQ number used for a vector that can be passed to
|
|
|
|
* request_irq() use the pci_irq_vector() helper.
|
|
|
|
*/
|
2016-11-09 10:15:05 +09:00
|
|
|
int pci_alloc_irq_vectors_affinity(struct pci_dev *dev, unsigned int min_vecs,
|
|
|
|
unsigned int max_vecs, unsigned int flags,
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
struct irq_affinity *affd)
|
2016-07-12 18:20:17 +09:00
|
|
|
{
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
struct irq_affinity msi_default_affd = {0};
|
2020-06-16 16:33:16 +09:00
|
|
|
int nvecs = -ENOSPC;
|
2016-07-12 18:20:17 +09:00
|
|
|
|
2016-11-09 10:15:05 +09:00
|
|
|
if (flags & PCI_IRQ_AFFINITY) {
|
|
|
|
if (!affd)
|
|
|
|
affd = &msi_default_affd;
|
|
|
|
} else {
|
|
|
|
if (WARN_ON(affd))
|
|
|
|
affd = NULL;
|
|
|
|
}
|
2016-11-09 10:15:04 +09:00
|
|
|
|
2016-08-11 23:11:04 +09:00
|
|
|
if (flags & PCI_IRQ_MSIX) {
|
2020-06-16 16:33:16 +09:00
|
|
|
nvecs = __pci_enable_msix_range(dev, NULL, min_vecs, max_vecs,
|
|
|
|
affd, flags);
|
|
|
|
if (nvecs > 0)
|
|
|
|
return nvecs;
|
2016-07-12 18:20:17 +09:00
|
|
|
}
|
|
|
|
|
2016-08-11 23:11:04 +09:00
|
|
|
if (flags & PCI_IRQ_MSI) {
|
2020-06-16 16:33:16 +09:00
|
|
|
nvecs = __pci_enable_msi_range(dev, min_vecs, max_vecs, affd);
|
|
|
|
if (nvecs > 0)
|
|
|
|
return nvecs;
|
2016-07-12 18:20:17 +09:00
|
|
|
}
|
|
|
|
|
2019-05-30 22:05:58 +09:00
|
|
|
/* use legacy IRQ if allowed */
|
2017-02-01 22:41:42 +09:00
|
|
|
if (flags & PCI_IRQ_LEGACY) {
|
|
|
|
if (min_vecs == 1 && dev->irq) {
|
genirq/affinity: Add new callback for (re)calculating interrupt sets
The interrupt affinity spreading mechanism supports to spread out
affinities for one or more interrupt sets. A interrupt set contains one or
more interrupts. Each set is mapped to a specific functionality of a
device, e.g. general I/O queues and read I/O queus of multiqueue block
devices.
The number of interrupts per set is defined by the driver. It depends on
the total number of available interrupts for the device, which is
determined by the PCI capabilites and the availability of underlying CPU
resources, and the number of queues which the device provides and the
driver wants to instantiate.
The driver passes initial configuration for the interrupt allocation via a
pointer to struct irq_affinity.
Right now the allocation mechanism is complex as it requires to have a loop
in the driver to determine the maximum number of interrupts which are
provided by the PCI capabilities and the underlying CPU resources. This
loop would have to be replicated in every driver which wants to utilize
this mechanism. That's unwanted code duplication and error prone.
In order to move this into generic facilities it is required to have a
mechanism, which allows the recalculation of the interrupt sets and their
size, in the core code. As the core code does not have any knowledge about the
underlying device, a driver specific callback is required in struct
irq_affinity, which can be invoked by the core code. The callback gets the
number of available interupts as an argument, so the driver can calculate the
corresponding number and size of interrupt sets.
At the moment the struct irq_affinity pointer which is handed in from the
driver and passed through to several core functions is marked 'const', but for
the callback to be able to modify the data in the struct it's required to
remove the 'const' qualifier.
Add the optional callback to struct irq_affinity, which allows drivers to
recalculate the number and size of interrupt sets and remove the 'const'
qualifier.
For simple invocations, which do not supply a callback, a default callback
is installed, which just sets nr_sets to 1 and transfers the number of
spreadable vectors to the set_size array at index 0.
This is for now guarded by a check for nr_sets != 0 to keep the NVME driver
working until it is converted to the callback mechanism.
To make sure that the driver configuration is correct under all circumstances
the callback is invoked even when there are no interrupts for queues left,
i.e. the pre/post requirements already exhaust the numner of available
interrupts.
At the PCI layer irq_create_affinity_masks() has to be invoked even for the
case where the legacy interrupt is used. That ensures that the callback is
invoked and the device driver can adjust to that situation.
[ tglx: Fixed the simple case (no sets required). Moved the sanity check
for nr_sets after the invocation of the callback so it catches
broken drivers. Fixed the kernel doc comments for struct
irq_affinity and de-'This patch'-ed the changelog ]
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Cc: linux-pci@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com>
Link: https://lkml.kernel.org/r/20190216172228.512444498@linutronix.de
2019-02-17 02:13:09 +09:00
|
|
|
/*
|
|
|
|
* Invoke the affinity spreading logic to ensure that
|
|
|
|
* the device driver can adjust queue configuration
|
|
|
|
* for the single interrupt case.
|
|
|
|
*/
|
|
|
|
if (affd)
|
|
|
|
irq_create_affinity_masks(1, affd);
|
2017-02-01 22:41:42 +09:00
|
|
|
pci_intx(dev, 1);
|
|
|
|
return 1;
|
|
|
|
}
|
2016-08-11 23:11:05 +09:00
|
|
|
}
|
|
|
|
|
2020-06-16 16:33:16 +09:00
|
|
|
return nvecs;
|
2016-07-12 18:20:17 +09:00
|
|
|
}
|
2016-11-09 10:15:05 +09:00
|
|
|
EXPORT_SYMBOL(pci_alloc_irq_vectors_affinity);
|
2016-07-12 18:20:17 +09:00
|
|
|
|
|
|
|
/**
|
|
|
|
* pci_free_irq_vectors - free previously allocated IRQs for a device
|
|
|
|
* @dev: PCI device to operate on
|
|
|
|
*
|
|
|
|
* Undoes the allocations and enabling in pci_alloc_irq_vectors().
|
|
|
|
*/
|
|
|
|
void pci_free_irq_vectors(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
pci_disable_msix(dev);
|
|
|
|
pci_disable_msi(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(pci_free_irq_vectors);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* pci_irq_vector - return Linux IRQ number of a device vector
|
2021-12-07 07:27:26 +09:00
|
|
|
* @dev: PCI device to operate on
|
|
|
|
* @nr: Interrupt vector index (0-based)
|
|
|
|
*
|
|
|
|
* @nr has the following meanings depending on the interrupt mode:
|
|
|
|
* MSI-X: The index in the MSI-X vector table
|
|
|
|
* MSI: The index of the enabled MSI vectors
|
|
|
|
* INTx: Must be 0
|
|
|
|
*
|
|
|
|
* Return: The Linux interrupt number or -EINVAl if @nr is out of range.
|
2016-07-12 18:20:17 +09:00
|
|
|
*/
|
|
|
|
int pci_irq_vector(struct pci_dev *dev, unsigned int nr)
|
|
|
|
{
|
2021-12-11 07:19:25 +09:00
|
|
|
unsigned int irq;
|
2016-07-12 18:20:17 +09:00
|
|
|
|
2021-12-11 07:19:25 +09:00
|
|
|
if (!dev->msi_enabled && !dev->msix_enabled)
|
|
|
|
return !nr ? dev->irq : -EINVAL;
|
2016-07-12 18:20:17 +09:00
|
|
|
|
2021-12-11 07:19:25 +09:00
|
|
|
irq = msi_get_virq(&dev->dev, nr);
|
|
|
|
return irq ? irq : -EINVAL;
|
2016-07-12 18:20:17 +09:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(pci_irq_vector);
|
|
|
|
|
2016-09-14 23:18:51 +09:00
|
|
|
/**
|
2019-05-30 22:05:58 +09:00
|
|
|
* pci_irq_get_affinity - return the affinity of a particular MSI vector
|
2016-09-14 23:18:51 +09:00
|
|
|
* @dev: PCI device to operate on
|
|
|
|
* @nr: device-relative interrupt vector index (0-based).
|
2021-12-07 07:27:26 +09:00
|
|
|
*
|
|
|
|
* @nr has the following meanings depending on the interrupt mode:
|
|
|
|
* MSI-X: The index in the MSI-X vector table
|
|
|
|
* MSI: The index of the enabled MSI vectors
|
|
|
|
* INTx: Must be 0
|
|
|
|
*
|
|
|
|
* Return: A cpumask pointer or NULL if @nr is out of range
|
2016-09-14 23:18:51 +09:00
|
|
|
*/
|
|
|
|
const struct cpumask *pci_irq_get_affinity(struct pci_dev *dev, int nr)
|
|
|
|
{
|
2021-12-18 19:25:14 +09:00
|
|
|
int idx, irq = pci_irq_vector(dev, nr);
|
2021-12-11 07:19:26 +09:00
|
|
|
struct msi_desc *desc;
|
2016-09-14 23:18:51 +09:00
|
|
|
|
2021-12-11 07:19:26 +09:00
|
|
|
if (WARN_ON_ONCE(irq <= 0))
|
2016-09-14 23:18:51 +09:00
|
|
|
return NULL;
|
|
|
|
|
2021-12-11 07:19:26 +09:00
|
|
|
desc = irq_get_msi_desc(irq);
|
|
|
|
/* Non-MSI does not have the information handy */
|
|
|
|
if (!desc)
|
2016-09-14 23:18:51 +09:00
|
|
|
return cpu_possible_mask;
|
2021-12-11 07:19:26 +09:00
|
|
|
|
2022-02-01 06:02:46 +09:00
|
|
|
/* MSI[X] interrupts can be allocated without affinity descriptor */
|
|
|
|
if (!desc->affinity)
|
2021-12-11 07:19:26 +09:00
|
|
|
return NULL;
|
2021-12-18 19:25:14 +09:00
|
|
|
|
|
|
|
/*
|
|
|
|
* MSI has a mask array in the descriptor.
|
|
|
|
* MSI-X has a single mask.
|
|
|
|
*/
|
|
|
|
idx = dev->msi_enabled ? nr : 0;
|
|
|
|
return &desc->affinity[idx].mask;
|
2016-09-14 23:18:51 +09:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(pci_irq_get_affinity);
|
|
|
|
|
2015-07-09 17:00:45 +09:00
|
|
|
struct pci_dev *msi_desc_to_pci_dev(struct msi_desc *desc)
|
|
|
|
{
|
|
|
|
return to_pci_dev(desc->dev);
|
|
|
|
}
|
2015-12-11 02:52:59 +09:00
|
|
|
EXPORT_SYMBOL(msi_desc_to_pci_dev);
|
2015-07-09 17:00:45 +09:00
|
|
|
|
2021-12-07 07:27:52 +09:00
|
|
|
void pci_no_msi(void)
|
2015-10-02 22:43:06 +09:00
|
|
|
{
|
2021-12-07 07:27:52 +09:00
|
|
|
pci_msi_enable = 0;
|
2015-10-02 22:43:06 +09:00
|
|
|
}
|
2020-08-26 20:16:53 +09:00
|
|
|
|
|
|
|
/**
|
2021-12-07 07:27:52 +09:00
|
|
|
* pci_msi_enabled - is MSI enabled?
|
2020-08-26 20:16:53 +09:00
|
|
|
*
|
2021-12-07 07:27:52 +09:00
|
|
|
* Returns true if MSI has not been disabled by the command-line option
|
|
|
|
* pci=nomsi.
|
|
|
|
**/
|
|
|
|
int pci_msi_enabled(void)
|
2020-08-26 20:16:53 +09:00
|
|
|
{
|
2021-12-07 07:27:52 +09:00
|
|
|
return pci_msi_enable;
|
2020-08-26 20:16:53 +09:00
|
|
|
}
|
2021-12-07 07:27:52 +09:00
|
|
|
EXPORT_SYMBOL(pci_msi_enabled);
|