2008-08-20 07:49:59 +04:00
# include <linux/interrupt.h>
2008-07-10 22:16:40 +04:00
# include <linux/dmar.h>
2008-07-10 22:16:43 +04:00
# include <linux/spinlock.h>
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 11:04:11 +03:00
# include <linux/slab.h>
2008-07-10 22:16:43 +04:00
# include <linux/jiffies.h>
2009-08-04 23:07:08 +04:00
# include <linux/hpet.h>
2008-07-10 22:16:43 +04:00
# include <linux/pci.h>
2008-07-10 22:16:44 +04:00
# include <linux/irq.h>
2013-12-03 04:49:16 +04:00
# include <linux/intel-iommu.h>
# include <linux/acpi.h>
2008-07-10 22:16:40 +04:00
# include <asm/io_apic.h>
2008-12-13 00:14:18 +03:00
# include <asm/smp.h>
2009-01-07 19:08:59 +03:00
# include <asm/cpu.h>
2012-03-30 22:47:08 +04:00
# include <asm/irq_remapping.h>
2009-05-22 20:41:15 +04:00
# include <asm/pci-direct.h>
2012-03-30 22:47:05 +04:00
# include <asm/msidef.h>
2008-07-10 22:16:40 +04:00
2012-03-30 22:47:08 +04:00
# include "irq_remapping.h"
2012-03-30 22:47:00 +04:00
2012-03-30 22:46:59 +04:00
struct ioapic_scope {
struct intel_iommu * iommu ;
unsigned int id ;
unsigned int bus ; /* PCI bus number */
unsigned int devfn ; /* PCI devfn number */
} ;
struct hpet_scope {
struct intel_iommu * iommu ;
u8 id ;
unsigned int bus ;
unsigned int devfn ;
} ;
# define IR_X2APIC_MODE(mode) (mode ? (1 << 11) : 0)
2015-01-07 10:31:37 +03:00
# define IRTE_DEST(dest) ((eim_mode) ? dest : dest << 8)
2012-03-30 22:46:59 +04:00
2015-01-07 10:31:37 +03:00
static int __read_mostly eim_mode ;
2008-07-10 22:16:40 +04:00
static struct ioapic_scope ir_ioapic [ MAX_IO_APICS ] ;
2009-08-04 23:07:08 +04:00
static struct hpet_scope ir_hpet [ MAX_HPET_TBS ] ;
2010-07-20 22:06:49 +04:00
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
/*
* Lock ordering :
* - > dmar_global_lock
* - > irq_2_ir_lock
* - > qi - > q_lock
* - > iommu - > register_lock
* Note :
* intel_irq_remap_ops . { supported , prepare , enable , disable , reenable } are called
* in single - threaded environment with interrupt disabled , so no need to tabke
* the dmar_global_lock .
*/
2011-07-19 18:28:19 +04:00
static DEFINE_RAW_SPINLOCK ( irq_2_ir_lock ) ;
2010-10-10 14:34:27 +04:00
2014-01-06 10:18:16 +04:00
static int __init parse_ioapics_under_ir ( void ) ;
2008-08-20 07:50:21 +04:00
static struct irq_2_iommu * irq_2_iommu ( unsigned int irq )
{
2014-10-27 11:12:09 +03:00
struct irq_cfg * cfg = irq_cfg ( irq ) ;
2010-10-10 14:29:27 +04:00
return cfg ? & cfg - > irq_2_iommu : NULL ;
2008-12-06 05:58:31 +03:00
}
2013-12-18 10:34:27 +04:00
static int get_irte ( int irq , struct irte * entry )
2008-07-10 22:16:44 +04:00
{
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2010-10-10 14:34:27 +04:00
int index ;
2008-07-10 22:16:44 +04:00
2010-10-10 14:34:27 +04:00
if ( ! entry | | ! irq_iommu )
2008-07-10 22:16:44 +04:00
return - 1 ;
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
2014-07-23 20:13:26 +04:00
if ( unlikely ( ! irq_iommu - > iommu ) ) {
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
return - 1 ;
}
2008-08-20 07:50:21 +04:00
index = irq_iommu - > irte_index + irq_iommu - > sub_handle ;
* entry = * ( irq_iommu - > iommu - > ir_table - > base + index ) ;
2008-07-10 22:16:44 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
return 0 ;
}
2012-03-30 22:47:06 +04:00
static int alloc_irte ( struct intel_iommu * iommu , int irq , u16 count )
2008-07-10 22:16:44 +04:00
{
struct ir_table * table = iommu - > ir_table ;
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2014-10-27 11:12:09 +03:00
struct irq_cfg * cfg = irq_cfg ( irq ) ;
2008-07-10 22:16:44 +04:00
unsigned int mask = 0 ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2014-01-09 09:32:36 +04:00
int index ;
2008-07-10 22:16:44 +04:00
2010-10-10 14:34:27 +04:00
if ( ! count | | ! irq_iommu )
2008-08-20 07:50:21 +04:00
return - 1 ;
2008-07-10 22:16:44 +04:00
if ( count > 1 ) {
count = __roundup_pow_of_two ( count ) ;
mask = ilog2 ( count ) ;
}
if ( mask > ecap_max_handle_mask ( iommu - > ecap ) ) {
printk ( KERN_ERR
" Requested mask %x exceeds the max invalidation handle "
" mask value %Lx \n " , mask ,
ecap_max_handle_mask ( iommu - > ecap ) ) ;
return - 1 ;
}
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2014-01-06 10:18:08 +04:00
index = bitmap_find_free_region ( table - > bitmap ,
INTR_REMAP_TABLE_ENTRIES , mask ) ;
if ( index < 0 ) {
pr_warn ( " IR%d: can't allocate an IRTE \n " , iommu - > seq_id ) ;
} else {
cfg - > remapped = 1 ;
irq_iommu - > iommu = iommu ;
irq_iommu - > irte_index = index ;
irq_iommu - > sub_handle = 0 ;
irq_iommu - > irte_mask = mask ;
}
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
return index ;
}
2009-01-04 11:28:52 +03:00
static int qi_flush_iec ( struct intel_iommu * iommu , int index , int mask )
2008-07-10 22:16:44 +04:00
{
struct qi_desc desc ;
desc . low = QI_IEC_IIDEX ( index ) | QI_IEC_TYPE | QI_IEC_IM ( mask )
| QI_IEC_SELECTIVE ;
desc . high = 0 ;
2009-01-04 11:28:52 +03:00
return qi_submit_sync ( & desc , iommu ) ;
2008-07-10 22:16:44 +04:00
}
2012-03-30 22:47:06 +04:00
static int map_irq_to_irte_handle ( int irq , u16 * sub_handle )
2008-07-10 22:16:44 +04:00
{
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2010-10-10 14:34:27 +04:00
int index ;
2008-07-10 22:16:44 +04:00
2010-10-10 14:34:27 +04:00
if ( ! irq_iommu )
2008-07-10 22:16:44 +04:00
return - 1 ;
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2008-08-20 07:50:21 +04:00
* sub_handle = irq_iommu - > sub_handle ;
index = irq_iommu - > irte_index ;
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
return index ;
}
2012-03-30 22:47:06 +04:00
static int set_irte_irq ( int irq , struct intel_iommu * iommu , u16 index , u16 subhandle )
2008-07-10 22:16:44 +04:00
{
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2014-10-27 11:12:09 +03:00
struct irq_cfg * cfg = irq_cfg ( irq ) ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2008-08-20 07:50:21 +04:00
2010-10-10 14:34:27 +04:00
if ( ! irq_iommu )
2008-12-06 05:58:31 +03:00
return - 1 ;
2010-10-10 14:34:27 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2008-12-06 05:58:31 +03:00
2012-09-26 14:44:45 +04:00
cfg - > remapped = 1 ;
2008-08-20 07:50:21 +04:00
irq_iommu - > iommu = iommu ;
irq_iommu - > irte_index = index ;
irq_iommu - > sub_handle = subhandle ;
irq_iommu - > irte_mask = 0 ;
2008-07-10 22:16:44 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
return 0 ;
}
2012-03-30 22:47:06 +04:00
static int modify_irte ( int irq , struct irte * irte_modified )
2008-07-10 22:16:44 +04:00
{
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2008-07-10 22:16:44 +04:00
struct intel_iommu * iommu ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2010-10-10 14:34:27 +04:00
struct irte * irte ;
int rc , index ;
2008-07-10 22:16:44 +04:00
2010-10-10 14:34:27 +04:00
if ( ! irq_iommu )
2008-07-10 22:16:44 +04:00
return - 1 ;
2010-10-10 14:34:27 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
2008-08-20 07:50:21 +04:00
iommu = irq_iommu - > iommu ;
2008-07-10 22:16:44 +04:00
2008-08-20 07:50:21 +04:00
index = irq_iommu - > irte_index + irq_iommu - > sub_handle ;
2008-07-10 22:16:44 +04:00
irte = & iommu - > ir_table - > base [ index ] ;
2010-08-06 22:02:31 +04:00
set_64bit ( & irte - > low , irte_modified - > low ) ;
set_64bit ( & irte - > high , irte_modified - > high ) ;
2008-07-10 22:16:44 +04:00
__iommu_flush_cache ( iommu , irte , sizeof ( * irte ) ) ;
2009-01-04 11:28:52 +03:00
rc = qi_flush_iec ( iommu , index , 0 ) ;
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2009-01-04 11:28:52 +03:00
return rc ;
2008-07-10 22:16:44 +04:00
}
2012-03-30 22:47:06 +04:00
static struct intel_iommu * map_hpet_to_ir ( u8 hpet_id )
2009-08-04 23:07:08 +04:00
{
int i ;
for ( i = 0 ; i < MAX_HPET_TBS ; i + + )
2014-11-09 17:48:00 +03:00
if ( ir_hpet [ i ] . id = = hpet_id & & ir_hpet [ i ] . iommu )
2009-08-04 23:07:08 +04:00
return ir_hpet [ i ] . iommu ;
return NULL ;
}
2012-03-30 22:47:06 +04:00
static struct intel_iommu * map_ioapic_to_ir ( int apic )
x64, x2apic/intr-remap: IO-APIC support for interrupt-remapping
IO-APIC support in the presence of interrupt-remapping infrastructure.
IO-APIC RTE will be programmed with interrupt-remapping table entry(IRTE)
index and the IRTE will contain information about the vector, cpu destination,
trigger mode etc, which traditionally was present in the IO-APIC RTE.
Introduce a new irq_chip for cleaner irq migration (in the process
context as opposed to the current irq migration in the context of an interrupt.
interrupt-remapping infrastructure will help us achieve this cleanly).
For edge triggered, irq migration is a simple atomic update(of vector
and cpu destination) of IRTE and flush the hardware cache.
For level triggered, we need to modify the io-apic RTE aswell with the update
vector information, along with modifying IRTE with vector and cpu destination.
So irq migration for level triggered is little bit more complex compared to
edge triggered migration. But the good news is, we use the same algorithm
for level triggered migration as we have today, only difference being,
we now initiate the irq migration from process context instead of the
interrupt context.
In future, when we do a directed EOI (combined with cpu EOI broadcast
suppression) to the IO-APIC, level triggered irq migration will also be
as simple as edge triggered migration and we can do the irq migration
with a simple atomic update to IO-APIC RTE.
TBD: some tests/changes needed in the presence of fixup_irqs() for
level triggered irq migration.
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: akpm@linux-foundation.org
Cc: arjan@linux.intel.com
Cc: andi@firstfloor.org
Cc: ebiederm@xmission.com
Cc: jbarnes@virtuousgeek.org
Cc: steiner@sgi.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-10 22:16:56 +04:00
{
int i ;
for ( i = 0 ; i < MAX_IO_APICS ; i + + )
2014-11-09 17:48:00 +03:00
if ( ir_ioapic [ i ] . id = = apic & & ir_ioapic [ i ] . iommu )
x64, x2apic/intr-remap: IO-APIC support for interrupt-remapping
IO-APIC support in the presence of interrupt-remapping infrastructure.
IO-APIC RTE will be programmed with interrupt-remapping table entry(IRTE)
index and the IRTE will contain information about the vector, cpu destination,
trigger mode etc, which traditionally was present in the IO-APIC RTE.
Introduce a new irq_chip for cleaner irq migration (in the process
context as opposed to the current irq migration in the context of an interrupt.
interrupt-remapping infrastructure will help us achieve this cleanly).
For edge triggered, irq migration is a simple atomic update(of vector
and cpu destination) of IRTE and flush the hardware cache.
For level triggered, we need to modify the io-apic RTE aswell with the update
vector information, along with modifying IRTE with vector and cpu destination.
So irq migration for level triggered is little bit more complex compared to
edge triggered migration. But the good news is, we use the same algorithm
for level triggered migration as we have today, only difference being,
we now initiate the irq migration from process context instead of the
interrupt context.
In future, when we do a directed EOI (combined with cpu EOI broadcast
suppression) to the IO-APIC, level triggered irq migration will also be
as simple as edge triggered migration and we can do the irq migration
with a simple atomic update to IO-APIC RTE.
TBD: some tests/changes needed in the presence of fixup_irqs() for
level triggered irq migration.
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: akpm@linux-foundation.org
Cc: arjan@linux.intel.com
Cc: andi@firstfloor.org
Cc: ebiederm@xmission.com
Cc: jbarnes@virtuousgeek.org
Cc: steiner@sgi.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-10 22:16:56 +04:00
return ir_ioapic [ i ] . iommu ;
return NULL ;
}
2012-03-30 22:47:06 +04:00
static struct intel_iommu * map_dev_to_ir ( struct pci_dev * dev )
2008-07-10 22:16:57 +04:00
{
struct dmar_drhd_unit * drhd ;
drhd = dmar_find_matched_drhd_unit ( dev ) ;
if ( ! drhd )
return NULL ;
return drhd - > iommu ;
}
2009-05-22 20:41:14 +04:00
static int clear_entries ( struct irq_2_iommu * irq_iommu )
{
struct irte * start , * entry , * end ;
struct intel_iommu * iommu ;
int index ;
if ( irq_iommu - > sub_handle )
return 0 ;
iommu = irq_iommu - > iommu ;
index = irq_iommu - > irte_index + irq_iommu - > sub_handle ;
start = iommu - > ir_table - > base + index ;
end = start + ( 1 < < irq_iommu - > irte_mask ) ;
for ( entry = start ; entry < end ; entry + + ) {
2010-08-06 22:02:31 +04:00
set_64bit ( & entry - > low , 0 ) ;
set_64bit ( & entry - > high , 0 ) ;
2009-05-22 20:41:14 +04:00
}
2014-01-06 10:18:08 +04:00
bitmap_release_region ( iommu - > ir_table - > bitmap , index ,
irq_iommu - > irte_mask ) ;
2009-05-22 20:41:14 +04:00
return qi_flush_iec ( iommu , index , irq_iommu - > irte_mask ) ;
}
2012-03-30 22:47:04 +04:00
static int free_irte ( int irq )
2008-07-10 22:16:44 +04:00
{
2010-10-10 14:34:27 +04:00
struct irq_2_iommu * irq_iommu = irq_2_iommu ( irq ) ;
2009-03-17 03:04:53 +03:00
unsigned long flags ;
2010-10-10 14:34:27 +04:00
int rc ;
2008-07-10 22:16:44 +04:00
2010-10-10 14:34:27 +04:00
if ( ! irq_iommu )
2008-07-10 22:16:44 +04:00
return - 1 ;
2010-10-10 14:34:27 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_lock_irqsave ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
2009-05-22 20:41:14 +04:00
rc = clear_entries ( irq_iommu ) ;
2008-07-10 22:16:44 +04:00
2008-08-20 07:50:21 +04:00
irq_iommu - > iommu = NULL ;
irq_iommu - > irte_index = 0 ;
irq_iommu - > sub_handle = 0 ;
irq_iommu - > irte_mask = 0 ;
2008-07-10 22:16:44 +04:00
2011-07-19 18:28:19 +04:00
raw_spin_unlock_irqrestore ( & irq_2_ir_lock , flags ) ;
2008-07-10 22:16:44 +04:00
2009-01-04 11:28:52 +03:00
return rc ;
2008-07-10 22:16:44 +04:00
}
2009-05-22 20:41:15 +04:00
/*
* source validation type
*/
# define SVT_NO_VERIFY 0x0 /* no verification is required */
2011-03-31 05:57:33 +04:00
# define SVT_VERIFY_SID_SQ 0x1 /* verify using SID and SQ fields */
2009-05-22 20:41:15 +04:00
# define SVT_VERIFY_BUS 0x2 /* verify bus of request-id */
/*
* source - id qualifier
*/
# define SQ_ALL_16 0x0 /* verify all 16 bits of request-id */
# define SQ_13_IGNORE_1 0x1 / * verify most significant 13 bits, ignore
* the third least significant bit
*/
# define SQ_13_IGNORE_2 0x2 / * verify most significant 13 bits, ignore
* the second and third least significant bits
*/
# define SQ_13_IGNORE_3 0x3 / * verify most significant 13 bits, ignore
* the least three significant bits
*/
/*
* set SVT , SQ and SID fields of irte to verify
* source ids of interrupt requests
*/
static void set_irte_sid ( struct irte * irte , unsigned int svt ,
unsigned int sq , unsigned int sid )
{
2010-07-20 22:06:49 +04:00
if ( disable_sourceid_checking )
svt = SVT_NO_VERIFY ;
2009-05-22 20:41:15 +04:00
irte - > svt = svt ;
irte - > sq = sq ;
irte - > sid = sid ;
}
2012-03-30 22:47:06 +04:00
static int set_ioapic_sid ( struct irte * irte , int apic )
2009-05-22 20:41:15 +04:00
{
int i ;
u16 sid = 0 ;
if ( ! irte )
return - 1 ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
2009-05-22 20:41:15 +04:00
for ( i = 0 ; i < MAX_IO_APICS ; i + + ) {
2014-11-09 17:48:00 +03:00
if ( ir_ioapic [ i ] . iommu & & ir_ioapic [ i ] . id = = apic ) {
2009-05-22 20:41:15 +04:00
sid = ( ir_ioapic [ i ] . bus < < 8 ) | ir_ioapic [ i ] . devfn ;
break ;
}
}
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
up_read ( & dmar_global_lock ) ;
2009-05-22 20:41:15 +04:00
if ( sid = = 0 ) {
pr_warning ( " Failed to set source-id of IOAPIC (%d) \n " , apic ) ;
return - 1 ;
}
2014-01-06 10:18:17 +04:00
set_irte_sid ( irte , SVT_VERIFY_SID_SQ , SQ_ALL_16 , sid ) ;
2009-05-22 20:41:15 +04:00
return 0 ;
}
2012-03-30 22:47:06 +04:00
static int set_hpet_sid ( struct irte * irte , u8 id )
2009-08-04 23:07:08 +04:00
{
int i ;
u16 sid = 0 ;
if ( ! irte )
return - 1 ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
2009-08-04 23:07:08 +04:00
for ( i = 0 ; i < MAX_HPET_TBS ; i + + ) {
2014-11-09 17:48:00 +03:00
if ( ir_hpet [ i ] . iommu & & ir_hpet [ i ] . id = = id ) {
2009-08-04 23:07:08 +04:00
sid = ( ir_hpet [ i ] . bus < < 8 ) | ir_hpet [ i ] . devfn ;
break ;
}
}
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
up_read ( & dmar_global_lock ) ;
2009-08-04 23:07:08 +04:00
if ( sid = = 0 ) {
pr_warning ( " Failed to set source-id of HPET block (%d) \n " , id ) ;
return - 1 ;
}
/*
* Should really use SQ_ALL_16 . Some platforms are broken .
* While we figure out the right quirks for these broken platforms , use
* SQ_13_IGNORE_3 for now .
*/
set_irte_sid ( irte , SVT_VERIFY_SID_SQ , SQ_13_IGNORE_3 , sid ) ;
return 0 ;
}
2014-07-03 19:51:43 +04:00
struct set_msi_sid_data {
struct pci_dev * pdev ;
u16 alias ;
} ;
static int set_msi_sid_cb ( struct pci_dev * pdev , u16 alias , void * opaque )
{
struct set_msi_sid_data * data = opaque ;
data - > pdev = pdev ;
data - > alias = alias ;
return 0 ;
}
2012-03-30 22:47:06 +04:00
static int set_msi_sid ( struct irte * irte , struct pci_dev * dev )
2009-05-22 20:41:15 +04:00
{
2014-07-03 19:51:43 +04:00
struct set_msi_sid_data data ;
2009-05-22 20:41:15 +04:00
if ( ! irte | | ! dev )
return - 1 ;
2014-07-03 19:51:43 +04:00
pci_for_each_dma_alias ( dev , set_msi_sid_cb , & data ) ;
2009-05-22 20:41:15 +04:00
2014-07-03 19:51:43 +04:00
/*
* DMA alias provides us with a PCI device and alias . The only case
* where the it will return an alias on a different bus than the
* device is the case of a PCIe - to - PCI bridge , where the alias is for
* the subordinate bus . In this case we can only verify the bus .
*
* If the alias device is on a different bus than our source device
* then we have a topology based alias , use it .
*
* Otherwise , the alias is for a device DMA quirk and we cannot
* assume that MSI uses the same requester ID . Therefore use the
* original device .
*/
if ( PCI_BUS_NUM ( data . alias ) ! = data . pdev - > bus - > number )
set_irte_sid ( irte , SVT_VERIFY_BUS , SQ_ALL_16 ,
PCI_DEVID ( PCI_BUS_NUM ( data . alias ) ,
dev - > bus - > number ) ) ;
else if ( data . pdev - > bus - > number ! = dev - > bus - > number )
set_irte_sid ( irte , SVT_VERIFY_SID_SQ , SQ_ALL_16 , data . alias ) ;
else
set_irte_sid ( irte , SVT_VERIFY_SID_SQ , SQ_ALL_16 ,
PCI_DEVID ( dev - > bus - > number , dev - > devfn ) ) ;
2009-05-22 20:41:15 +04:00
return 0 ;
}
2012-03-30 22:47:07 +04:00
static void iommu_set_irq_remapping ( struct intel_iommu * iommu , int mode )
2008-07-10 22:16:43 +04:00
{
u64 addr ;
2009-05-10 23:30:58 +04:00
u32 sts ;
2008-07-10 22:16:43 +04:00
unsigned long flags ;
addr = virt_to_phys ( ( void * ) iommu - > ir_table - > base ) ;
2011-07-19 18:19:51 +04:00
raw_spin_lock_irqsave ( & iommu - > register_lock , flags ) ;
2008-07-10 22:16:43 +04:00
dmar_writeq ( iommu - > reg + DMAR_IRTA_REG ,
( addr ) | IR_X2APIC_MODE ( mode ) | INTR_REMAP_TABLE_REG_SIZE ) ;
/* Set interrupt-remapping table pointer */
2014-08-11 15:13:25 +04:00
writel ( iommu - > gcmd | DMA_GCMD_SIRTP , iommu - > reg + DMAR_GCMD_REG ) ;
2008-07-10 22:16:43 +04:00
IOMMU_WAIT_OP ( iommu , DMAR_GSTS_REG ,
readl , ( sts & DMA_GSTS_IRTPS ) , sts ) ;
2011-07-19 18:19:51 +04:00
raw_spin_unlock_irqrestore ( & iommu - > register_lock , flags ) ;
2008-07-10 22:16:43 +04:00
/*
* global invalidation of interrupt entry cache before enabling
* interrupt - remapping .
*/
qi_global_iec ( iommu ) ;
2011-07-19 18:19:51 +04:00
raw_spin_lock_irqsave ( & iommu - > register_lock , flags ) ;
2008-07-10 22:16:43 +04:00
/* Enable interrupt-remapping */
iommu - > gcmd | = DMA_GCMD_IRE ;
2013-02-02 02:57:43 +04:00
iommu - > gcmd & = ~ DMA_GCMD_CFI ; /* Block compatibility-format MSIs */
2009-05-10 23:30:58 +04:00
writel ( iommu - > gcmd , iommu - > reg + DMAR_GCMD_REG ) ;
2008-07-10 22:16:43 +04:00
IOMMU_WAIT_OP ( iommu , DMAR_GSTS_REG ,
readl , ( sts & DMA_GSTS_IRES ) , sts ) ;
2013-02-02 02:57:43 +04:00
/*
* With CFI clear in the Global Command register , we should be
* protected from dangerous ( i . e . compatibility ) interrupts
* regardless of x2apic status . Check just to be sure .
*/
if ( sts & DMA_GSTS_CFIS )
WARN ( 1 , KERN_WARNING
" Compatibility-format IRQs enabled despite intr remapping; \n "
" you are vulnerable to IRQ injection. \n " ) ;
2011-07-19 18:19:51 +04:00
raw_spin_unlock_irqrestore ( & iommu - > register_lock , flags ) ;
2008-07-10 22:16:43 +04:00
}
2014-11-09 17:48:00 +03:00
static int intel_setup_irq_remapping ( struct intel_iommu * iommu )
2008-07-10 22:16:43 +04:00
{
struct ir_table * ir_table ;
struct page * pages ;
2014-01-06 10:18:08 +04:00
unsigned long * bitmap ;
2008-07-10 22:16:43 +04:00
2014-11-09 17:48:00 +03:00
if ( iommu - > ir_table )
return 0 ;
2008-07-10 22:16:43 +04:00
2015-01-07 10:31:30 +03:00
ir_table = kzalloc ( sizeof ( struct ir_table ) , GFP_KERNEL ) ;
2014-11-09 17:48:00 +03:00
if ( ! ir_table )
2008-07-10 22:16:43 +04:00
return - ENOMEM ;
2015-01-07 10:31:30 +03:00
pages = alloc_pages_node ( iommu - > node , GFP_KERNEL | __GFP_ZERO ,
2009-10-02 22:01:23 +04:00
INTR_REMAP_PAGE_ORDER ) ;
2008-07-10 22:16:43 +04:00
if ( ! pages ) {
2014-01-06 10:18:08 +04:00
pr_err ( " IR%d: failed to allocate pages of order %d \n " ,
iommu - > seq_id , INTR_REMAP_PAGE_ORDER ) ;
2014-11-09 17:48:00 +03:00
goto out_free_table ;
2008-07-10 22:16:43 +04:00
}
2014-01-06 10:18:08 +04:00
bitmap = kcalloc ( BITS_TO_LONGS ( INTR_REMAP_TABLE_ENTRIES ) ,
sizeof ( long ) , GFP_ATOMIC ) ;
if ( bitmap = = NULL ) {
pr_err ( " IR%d: failed to allocate bitmap \n " , iommu - > seq_id ) ;
2014-11-09 17:48:00 +03:00
goto out_free_pages ;
2014-01-06 10:18:08 +04:00
}
2008-07-10 22:16:43 +04:00
ir_table - > base = page_address ( pages ) ;
2014-01-06 10:18:08 +04:00
ir_table - > bitmap = bitmap ;
2014-11-09 17:48:00 +03:00
iommu - > ir_table = ir_table ;
2008-07-10 22:16:43 +04:00
return 0 ;
2014-11-09 17:48:00 +03:00
out_free_pages :
__free_pages ( pages , INTR_REMAP_PAGE_ORDER ) ;
out_free_table :
kfree ( ir_table ) ;
return - ENOMEM ;
}
static void intel_teardown_irq_remapping ( struct intel_iommu * iommu )
{
if ( iommu & & iommu - > ir_table ) {
free_pages ( ( unsigned long ) iommu - > ir_table - > base ,
INTR_REMAP_PAGE_ORDER ) ;
kfree ( iommu - > ir_table - > bitmap ) ;
kfree ( iommu - > ir_table ) ;
iommu - > ir_table = NULL ;
}
2008-07-10 22:16:43 +04:00
}
2009-03-17 03:04:56 +03:00
/*
* Disable Interrupt Remapping .
*/
2012-03-30 22:47:07 +04:00
static void iommu_disable_irq_remapping ( struct intel_iommu * iommu )
2009-03-17 03:04:56 +03:00
{
unsigned long flags ;
u32 sts ;
if ( ! ecap_ir_support ( iommu - > ecap ) )
return ;
2009-03-28 00:22:44 +03:00
/*
* global invalidation of interrupt entry cache before disabling
* interrupt - remapping .
*/
qi_global_iec ( iommu ) ;
2011-07-19 18:19:51 +04:00
raw_spin_lock_irqsave ( & iommu - > register_lock , flags ) ;
2009-03-17 03:04:56 +03:00
sts = dmar_readq ( iommu - > reg + DMAR_GSTS_REG ) ;
if ( ! ( sts & DMA_GSTS_IRES ) )
goto end ;
iommu - > gcmd & = ~ DMA_GCMD_IRE ;
writel ( iommu - > gcmd , iommu - > reg + DMAR_GCMD_REG ) ;
IOMMU_WAIT_OP ( iommu , DMAR_GSTS_REG ,
readl , ! ( sts & DMA_GSTS_IRES ) , sts ) ;
end :
2011-07-19 18:19:51 +04:00
raw_spin_unlock_irqrestore ( & iommu - > register_lock , flags ) ;
2009-03-17 03:04:56 +03:00
}
2011-08-24 04:05:18 +04:00
static int __init dmar_x2apic_optout ( void )
{
struct acpi_table_dmar * dmar ;
dmar = ( struct acpi_table_dmar * ) dmar_tbl ;
if ( ! dmar | | no_x2apic_optout )
return 0 ;
return dmar - > flags & DMAR_X2APIC_OPT_OUT ;
}
2015-01-07 10:31:29 +03:00
static void __init intel_cleanup_irq_remapping ( void )
{
struct dmar_drhd_unit * drhd ;
struct intel_iommu * iommu ;
for_each_iommu ( iommu , drhd ) {
if ( ecap_ir_support ( iommu - > ecap ) ) {
iommu_disable_irq_remapping ( iommu ) ;
intel_teardown_irq_remapping ( iommu ) ;
}
}
if ( x2apic_supported ( ) )
pr_warn ( " Failed to enable irq remapping. You are vulnerable to irq-injection attacks. \n " ) ;
}
static int __init intel_prepare_irq_remapping ( void )
2008-07-10 22:16:43 +04:00
{
struct dmar_drhd_unit * drhd ;
2014-01-06 10:18:18 +04:00
struct intel_iommu * iommu ;
2008-07-10 22:16:43 +04:00
2015-01-07 10:31:35 +03:00
if ( irq_remap_broken ) {
printk ( KERN_WARNING
" This system BIOS has enabled interrupt remapping \n "
" on a chipset that contains an erratum making that \n "
" feature unstable. To maintain system stability \n "
" interrupt remapping is being disabled. Please \n "
" contact your BIOS vendor for an update \n " ) ;
add_taint ( TAINT_FIRMWARE_WORKAROUND , LOCKDEP_STILL_OK ) ;
return - ENODEV ;
}
2015-01-07 10:31:29 +03:00
if ( dmar_table_init ( ) < 0 )
2015-01-07 10:31:35 +03:00
return - ENODEV ;
if ( ! dmar_ir_support ( ) )
return - ENODEV ;
2013-02-02 02:57:43 +04:00
2009-09-07 18:58:07 +04:00
if ( parse_ioapics_under_ir ( ) ! = 1 ) {
2015-01-07 10:31:29 +03:00
printk ( KERN_INFO " Not enabling interrupt remapping \n " ) ;
2013-02-02 02:57:43 +04:00
goto error ;
2009-09-07 18:58:07 +04:00
}
2015-01-07 10:31:36 +03:00
/* First make sure all IOMMUs support IRQ remapping */
2015-01-07 10:31:35 +03:00
for_each_iommu ( iommu , drhd )
2015-01-07 10:31:36 +03:00
if ( ! ecap_ir_support ( iommu - > ecap ) )
goto error ;
/* Do the allocations early */
for_each_iommu ( iommu , drhd )
if ( intel_setup_irq_remapping ( iommu ) )
2015-01-07 10:31:29 +03:00
goto error ;
2015-01-07 10:31:36 +03:00
2015-01-07 10:31:29 +03:00
return 0 ;
2015-01-07 10:31:35 +03:00
2015-01-07 10:31:29 +03:00
error :
intel_cleanup_irq_remapping ( ) ;
2015-01-07 10:31:35 +03:00
return - ENODEV ;
2015-01-07 10:31:29 +03:00
}
static int __init intel_enable_irq_remapping ( void )
{
struct dmar_drhd_unit * drhd ;
struct intel_iommu * iommu ;
2015-02-06 12:59:53 +03:00
bool setup = false ;
2015-01-07 10:31:29 +03:00
int eim = 0 ;
if ( x2apic_supported ( ) ) {
2011-08-24 04:05:18 +04:00
eim = ! dmar_x2apic_optout ( ) ;
2013-02-02 02:57:43 +04:00
if ( ! eim )
2015-02-22 00:07:27 +03:00
pr_info ( " x2apic is disabled because BIOS sets x2apic opt out bit. You can use 'intremap=no_x2apic_optout' to override the BIOS setting. \n " ) ;
2011-08-24 04:05:18 +04:00
}
2014-01-06 10:18:18 +04:00
for_each_iommu ( iommu , drhd ) {
2009-04-04 13:21:26 +04:00
/*
* If the queued invalidation is already initialized ,
* shouldn ' t disable it .
*/
if ( iommu - > qi )
continue ;
2009-03-17 03:04:57 +03:00
/*
* Clear previous faults .
*/
dmar_fault ( - 1 , iommu ) ;
/*
* Disable intr remapping and queued invalidation , if already
* enabled prior to OS handover .
*/
2012-03-30 22:47:07 +04:00
iommu_disable_irq_remapping ( iommu ) ;
2009-03-17 03:04:57 +03:00
dmar_disable_qi ( iommu ) ;
}
2008-07-10 22:16:43 +04:00
/*
* check for the Interrupt - remapping support
*/
2015-01-07 10:31:36 +03:00
for_each_iommu ( iommu , drhd )
2008-07-10 22:16:43 +04:00
if ( eim & & ! ecap_eim_support ( iommu - > ecap ) ) {
printk ( KERN_INFO " DRHD %Lx: EIM not supported by DRHD, "
" ecap %Lx \n " , drhd - > reg_base_addr , iommu - > ecap ) ;
2015-01-07 10:31:37 +03:00
eim = 0 ;
2008-07-10 22:16:43 +04:00
}
2015-01-07 10:31:37 +03:00
eim_mode = eim ;
if ( eim )
pr_info ( " Queued invalidation will be enabled to support x2apic and Intr-remapping. \n " ) ;
2008-07-10 22:16:43 +04:00
/*
* Enable queued invalidation for all the DRHD ' s .
*/
2014-01-06 10:18:18 +04:00
for_each_iommu ( iommu , drhd ) {
int ret = dmar_enable_qi ( iommu ) ;
2008-07-10 22:16:43 +04:00
if ( ret ) {
printk ( KERN_ERR " DRHD %Lx: failed to enable queued, "
" invalidation, ecap %Lx, ret %d \n " ,
drhd - > reg_base_addr , iommu - > ecap , ret ) ;
2013-02-02 02:57:43 +04:00
goto error ;
2008-07-10 22:16:43 +04:00
}
}
/*
* Setup Interrupt - remapping for all the DRHD ' s now .
*/
2014-01-06 10:18:18 +04:00
for_each_iommu ( iommu , drhd ) {
2014-11-09 17:48:00 +03:00
iommu_set_irq_remapping ( iommu , eim ) ;
2015-02-06 12:59:53 +03:00
setup = true ;
2008-07-10 22:16:43 +04:00
}
if ( ! setup )
goto error ;
2012-03-30 22:47:07 +04:00
irq_remapping_enabled = 1 ;
2012-09-26 14:44:36 +04:00
/*
* VT - d has a different layout for IO - APIC entries when
* interrupt remapping is enabled . So it needs a special routine
* to print IO - APIC entries for debugging purposes too .
*/
x86_io_apic_ops . print_entries = intel_ir_io_apic_print_entries ;
2011-08-24 04:05:18 +04:00
pr_info ( " Enabled IRQ remapping in %s mode \n " , eim ? " x2apic " : " xapic " ) ;
2008-07-10 22:16:43 +04:00
2011-08-24 04:05:18 +04:00
return eim ? IRQ_REMAP_X2APIC_MODE : IRQ_REMAP_XAPIC_MODE ;
2008-07-10 22:16:43 +04:00
error :
2015-01-07 10:31:29 +03:00
intel_cleanup_irq_remapping ( ) ;
2008-07-10 22:16:43 +04:00
return - 1 ;
}
2008-07-10 22:16:40 +04:00
2014-11-09 17:48:00 +03:00
static int ir_parse_one_hpet_scope ( struct acpi_dmar_device_scope * scope ,
struct intel_iommu * iommu ,
struct acpi_dmar_hardware_unit * drhd )
2009-08-04 23:07:08 +04:00
{
struct acpi_dmar_pci_path * path ;
u8 bus ;
2014-11-09 17:48:00 +03:00
int count , free = - 1 ;
2009-08-04 23:07:08 +04:00
bus = scope - > bus ;
path = ( struct acpi_dmar_pci_path * ) ( scope + 1 ) ;
count = ( scope - > length - sizeof ( struct acpi_dmar_device_scope ) )
/ sizeof ( struct acpi_dmar_pci_path ) ;
while ( - - count > 0 ) {
/*
* Access PCI directly due to the PCI
* subsystem isn ' t initialized yet .
*/
2013-10-31 05:30:22 +04:00
bus = read_pci_config_byte ( bus , path - > device , path - > function ,
2009-08-04 23:07:08 +04:00
PCI_SECONDARY_BUS ) ;
path + + ;
}
2014-11-09 17:48:00 +03:00
for ( count = 0 ; count < MAX_HPET_TBS ; count + + ) {
if ( ir_hpet [ count ] . iommu = = iommu & &
ir_hpet [ count ] . id = = scope - > enumeration_id )
return 0 ;
else if ( ir_hpet [ count ] . iommu = = NULL & & free = = - 1 )
free = count ;
}
if ( free = = - 1 ) {
pr_warn ( " Exceeded Max HPET blocks \n " ) ;
return - ENOSPC ;
}
ir_hpet [ free ] . iommu = iommu ;
ir_hpet [ free ] . id = scope - > enumeration_id ;
ir_hpet [ free ] . bus = bus ;
ir_hpet [ free ] . devfn = PCI_DEVFN ( path - > device , path - > function ) ;
pr_info ( " HPET id %d under DRHD base 0x%Lx \n " ,
scope - > enumeration_id , drhd - > address ) ;
return 0 ;
2009-08-04 23:07:08 +04:00
}
2014-11-09 17:48:00 +03:00
static int ir_parse_one_ioapic_scope ( struct acpi_dmar_device_scope * scope ,
struct intel_iommu * iommu ,
struct acpi_dmar_hardware_unit * drhd )
2009-05-22 20:41:15 +04:00
{
struct acpi_dmar_pci_path * path ;
u8 bus ;
2014-11-09 17:48:00 +03:00
int count , free = - 1 ;
2009-05-22 20:41:15 +04:00
bus = scope - > bus ;
path = ( struct acpi_dmar_pci_path * ) ( scope + 1 ) ;
count = ( scope - > length - sizeof ( struct acpi_dmar_device_scope ) )
/ sizeof ( struct acpi_dmar_pci_path ) ;
while ( - - count > 0 ) {
/*
* Access PCI directly due to the PCI
* subsystem isn ' t initialized yet .
*/
2013-10-31 05:30:22 +04:00
bus = read_pci_config_byte ( bus , path - > device , path - > function ,
2009-05-22 20:41:15 +04:00
PCI_SECONDARY_BUS ) ;
path + + ;
}
2014-11-09 17:48:00 +03:00
for ( count = 0 ; count < MAX_IO_APICS ; count + + ) {
if ( ir_ioapic [ count ] . iommu = = iommu & &
ir_ioapic [ count ] . id = = scope - > enumeration_id )
return 0 ;
else if ( ir_ioapic [ count ] . iommu = = NULL & & free = = - 1 )
free = count ;
}
if ( free = = - 1 ) {
pr_warn ( " Exceeded Max IO APICS \n " ) ;
return - ENOSPC ;
}
ir_ioapic [ free ] . bus = bus ;
ir_ioapic [ free ] . devfn = PCI_DEVFN ( path - > device , path - > function ) ;
ir_ioapic [ free ] . iommu = iommu ;
ir_ioapic [ free ] . id = scope - > enumeration_id ;
pr_info ( " IOAPIC id %d under DRHD base 0x%Lx IOMMU %d \n " ,
scope - > enumeration_id , drhd - > address , iommu - > seq_id ) ;
return 0 ;
2009-05-22 20:41:15 +04:00
}
2009-08-04 23:07:08 +04:00
static int ir_parse_ioapic_hpet_scope ( struct acpi_dmar_header * header ,
struct intel_iommu * iommu )
2008-07-10 22:16:40 +04:00
{
2014-11-09 17:48:00 +03:00
int ret = 0 ;
2008-07-10 22:16:40 +04:00
struct acpi_dmar_hardware_unit * drhd ;
struct acpi_dmar_device_scope * scope ;
void * start , * end ;
drhd = ( struct acpi_dmar_hardware_unit * ) header ;
start = ( void * ) ( drhd + 1 ) ;
end = ( ( void * ) drhd ) + header - > length ;
2014-11-09 17:48:00 +03:00
while ( start < end & & ret = = 0 ) {
2008-07-10 22:16:40 +04:00
scope = start ;
2014-11-09 17:48:00 +03:00
if ( scope - > entry_type = = ACPI_DMAR_SCOPE_TYPE_IOAPIC )
ret = ir_parse_one_ioapic_scope ( scope , iommu , drhd ) ;
else if ( scope - > entry_type = = ACPI_DMAR_SCOPE_TYPE_HPET )
ret = ir_parse_one_hpet_scope ( scope , iommu , drhd ) ;
start + = scope - > length ;
}
2008-07-10 22:16:40 +04:00
2014-11-09 17:48:00 +03:00
return ret ;
}
2009-08-04 23:07:08 +04:00
2014-11-09 17:48:00 +03:00
static void ir_remove_ioapic_hpet_scope ( struct intel_iommu * iommu )
{
int i ;
2009-08-04 23:07:08 +04:00
2014-11-09 17:48:00 +03:00
for ( i = 0 ; i < MAX_HPET_TBS ; i + + )
if ( ir_hpet [ i ] . iommu = = iommu )
ir_hpet [ i ] . iommu = NULL ;
2008-07-10 22:16:40 +04:00
2014-11-09 17:48:00 +03:00
for ( i = 0 ; i < MAX_IO_APICS ; i + + )
if ( ir_ioapic [ i ] . iommu = = iommu )
ir_ioapic [ i ] . iommu = NULL ;
2008-07-10 22:16:40 +04:00
}
/*
* Finds the assocaition between IOAPIC ' s and its Interrupt - remapping
* hardware unit .
*/
2014-01-06 10:18:16 +04:00
static int __init parse_ioapics_under_ir ( void )
2008-07-10 22:16:40 +04:00
{
struct dmar_drhd_unit * drhd ;
2014-01-06 10:18:18 +04:00
struct intel_iommu * iommu ;
2015-02-06 12:59:53 +03:00
bool ir_supported = false ;
2012-08-08 17:27:03 +04:00
int ioapic_idx ;
2008-07-10 22:16:40 +04:00
2014-01-06 10:18:18 +04:00
for_each_iommu ( iommu , drhd )
2008-07-10 22:16:40 +04:00
if ( ecap_ir_support ( iommu - > ecap ) ) {
2009-08-04 23:07:08 +04:00
if ( ir_parse_ioapic_hpet_scope ( drhd - > hdr , iommu ) )
2008-07-10 22:16:40 +04:00
return - 1 ;
2015-02-06 12:59:53 +03:00
ir_supported = true ;
2008-07-10 22:16:40 +04:00
}
2012-08-08 17:27:03 +04:00
if ( ! ir_supported )
return 0 ;
for ( ioapic_idx = 0 ; ioapic_idx < nr_ioapics ; ioapic_idx + + ) {
int ioapic_id = mpc_ioapic_id ( ioapic_idx ) ;
if ( ! map_ioapic_to_ir ( ioapic_id ) ) {
pr_err ( FW_BUG " ioapic %d has no mapping iommu, "
" interrupt remapping will be disabled \n " ,
ioapic_id ) ;
return - 1 ;
}
2008-07-10 22:16:40 +04:00
}
2012-08-08 17:27:03 +04:00
return 1 ;
2008-07-10 22:16:40 +04:00
}
2009-03-28 00:22:44 +03:00
2013-12-18 10:34:27 +04:00
static int __init ir_dev_scope_init ( void )
2011-08-24 04:05:19 +04:00
{
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
int ret ;
2012-03-30 22:47:07 +04:00
if ( ! irq_remapping_enabled )
2011-08-24 04:05:19 +04:00
return 0 ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_write ( & dmar_global_lock ) ;
ret = dmar_dev_scope_init ( ) ;
up_write ( & dmar_global_lock ) ;
return ret ;
2011-08-24 04:05:19 +04:00
}
rootfs_initcall ( ir_dev_scope_init ) ;
2012-03-30 22:47:07 +04:00
static void disable_irq_remapping ( void )
2009-03-28 00:22:44 +03:00
{
struct dmar_drhd_unit * drhd ;
struct intel_iommu * iommu = NULL ;
/*
* Disable Interrupt - remapping for all the DRHD ' s now .
*/
for_each_iommu ( iommu , drhd ) {
if ( ! ecap_ir_support ( iommu - > ecap ) )
continue ;
2012-03-30 22:47:07 +04:00
iommu_disable_irq_remapping ( iommu ) ;
2009-03-28 00:22:44 +03:00
}
}
2012-03-30 22:47:07 +04:00
static int reenable_irq_remapping ( int eim )
2009-03-28 00:22:44 +03:00
{
struct dmar_drhd_unit * drhd ;
2015-02-06 12:59:53 +03:00
bool setup = false ;
2009-03-28 00:22:44 +03:00
struct intel_iommu * iommu = NULL ;
for_each_iommu ( iommu , drhd )
if ( iommu - > qi )
dmar_reenable_qi ( iommu ) ;
/*
* Setup Interrupt - remapping for all the DRHD ' s now .
*/
for_each_iommu ( iommu , drhd ) {
if ( ! ecap_ir_support ( iommu - > ecap ) )
continue ;
/* Set up interrupt remapping for iommu.*/
2012-03-30 22:47:07 +04:00
iommu_set_irq_remapping ( iommu , eim ) ;
2015-02-06 12:59:53 +03:00
setup = true ;
2009-03-28 00:22:44 +03:00
}
if ( ! setup )
goto error ;
return 0 ;
error :
/*
* handle error condition gracefully here !
*/
return - 1 ;
}
2012-03-30 22:47:02 +04:00
static void prepare_irte ( struct irte * irte , int vector ,
unsigned int dest )
{
memset ( irte , 0 , sizeof ( * irte ) ) ;
irte - > present = 1 ;
irte - > dst_mode = apic - > irq_dest_mode ;
/*
* Trigger mode in the IRTE will always be edge , and for IO - APIC , the
* actual level or edge trigger will be setup in the IO - APIC
* RTE . This will help simplify level triggered irq migration .
* For more details , see the comments ( in io_apic . c ) explainig IO - APIC
* irq migration in the presence of interrupt - remapping .
*/
irte - > trigger_mode = 0 ;
irte - > dlvry_mode = apic - > irq_delivery_mode ;
irte - > vector = vector ;
irte - > dest_id = IRTE_DEST ( dest ) ;
irte - > redir_hint = 1 ;
}
static int intel_setup_ioapic_entry ( int irq ,
struct IO_APIC_route_entry * route_entry ,
unsigned int destination , int vector ,
struct io_apic_irq_attr * attr )
{
int ioapic_id = mpc_ioapic_id ( attr - > ioapic ) ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
struct intel_iommu * iommu ;
2012-03-30 22:47:02 +04:00
struct IR_IO_APIC_route_entry * entry ;
struct irte irte ;
int index ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
iommu = map_ioapic_to_ir ( ioapic_id ) ;
2012-03-30 22:47:02 +04:00
if ( ! iommu ) {
pr_warn ( " No mapping iommu for ioapic %d \n " , ioapic_id ) ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
index = - ENODEV ;
} else {
index = alloc_irte ( iommu , irq , 1 ) ;
if ( index < 0 ) {
pr_warn ( " Failed to allocate IRTE for ioapic %d \n " ,
ioapic_id ) ;
index = - ENOMEM ;
}
2012-03-30 22:47:02 +04:00
}
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
up_read ( & dmar_global_lock ) ;
if ( index < 0 )
return index ;
2012-03-30 22:47:02 +04:00
prepare_irte ( & irte , vector , destination ) ;
/* Set source-id of interrupt request */
set_ioapic_sid ( & irte , ioapic_id ) ;
modify_irte ( irq , & irte ) ;
apic_printk ( APIC_VERBOSE , KERN_DEBUG " IOAPIC[%d]: "
" Set IRTE entry (P:%d FPD:%d Dst_Mode:%d "
" Redir_hint:%d Trig_Mode:%d Dlvry_Mode:%X "
" Avail:%X Vector:%02X Dest:%08X "
" SID:%04X SQ:%X SVT:%X) \n " ,
attr - > ioapic , irte . present , irte . fpd , irte . dst_mode ,
irte . redir_hint , irte . trigger_mode , irte . dlvry_mode ,
irte . avail , irte . vector , irte . dest_id ,
irte . sid , irte . sq , irte . svt ) ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
entry = ( struct IR_IO_APIC_route_entry * ) route_entry ;
2012-03-30 22:47:02 +04:00
memset ( entry , 0 , sizeof ( * entry ) ) ;
entry - > index2 = ( index > > 15 ) & 0x1 ;
entry - > zero = 0 ;
entry - > format = 1 ;
entry - > index = ( index & 0x7fff ) ;
/*
* IO - APIC RTE will be configured with virtual vector .
* irq handler will do the explicit EOI to the io - apic .
*/
entry - > vector = attr - > ioapic_pin ;
entry - > mask = 0 ; /* enable IRQ */
entry - > trigger = attr - > trigger ;
entry - > polarity = attr - > polarity ;
/* Mask level triggered irqs.
* Use IRQ_DELAYED_DISABLE for edge triggered irqs .
*/
if ( attr - > trigger )
entry - > mask = 1 ;
return 0 ;
}
2012-03-30 22:47:03 +04:00
/*
* Migrate the IO - APIC irq in the presence of intr - remapping .
*
* For both level and edge triggered , irq migration is a simple atomic
* update ( of vector and cpu destination ) of IRTE and flush the hardware cache .
*
* For level triggered , we eliminate the io - apic RTE modification ( with the
* updated vector information ) , by using a virtual vector ( io - apic pin number ) .
* Real vector that is used for interrupting cpu will be coming from
* the interrupt - remapping table entry .
*
* As the migration is a simple atomic update of IRTE , the same mechanism
* is used to migrate MSI irq ' s in the presence of interrupt - remapping .
*/
static int
intel_ioapic_set_affinity ( struct irq_data * data , const struct cpumask * mask ,
bool force )
{
2014-10-27 11:12:09 +03:00
struct irq_cfg * cfg = irqd_cfg ( data ) ;
2012-03-30 22:47:03 +04:00
unsigned int dest , irq = data - > irq ;
struct irte irte ;
2012-06-07 17:15:59 +04:00
int err ;
2012-03-30 22:47:03 +04:00
2012-06-15 05:28:49 +04:00
if ( ! config_enabled ( CONFIG_SMP ) )
return - EINVAL ;
2012-03-30 22:47:03 +04:00
if ( ! cpumask_intersects ( mask , cpu_online_mask ) )
return - EINVAL ;
if ( get_irte ( irq , & irte ) )
return - EBUSY ;
2012-06-07 17:15:59 +04:00
err = assign_irq_vector ( irq , cfg , mask ) ;
if ( err )
return err ;
2012-03-30 22:47:03 +04:00
2012-06-07 17:15:59 +04:00
err = apic - > cpu_mask_to_apicid_and ( cfg - > domain , mask , & dest ) ;
if ( err ) {
2012-06-12 20:26:33 +04:00
if ( assign_irq_vector ( irq , cfg , data - > affinity ) )
2012-06-07 17:15:59 +04:00
pr_err ( " Failed to recover vector for irq %d \n " , irq ) ;
return err ;
}
2012-03-30 22:47:03 +04:00
irte . vector = cfg - > vector ;
irte . dest_id = IRTE_DEST ( dest ) ;
/*
* Atomically updates the IRTE with the new destination , vector
* and flushes the interrupt entry cache .
*/
modify_irte ( irq , & irte ) ;
/*
* After this point , all the interrupts will start arriving
* at the new destination . So , time to cleanup the previous
* vector allocation .
*/
if ( cfg - > move_in_progress )
send_cleanup_vector ( cfg ) ;
cpumask_copy ( data - > affinity , mask ) ;
return 0 ;
}
2012-03-30 22:47:02 +04:00
2012-03-30 22:47:05 +04:00
static void intel_compose_msi_msg ( struct pci_dev * pdev ,
unsigned int irq , unsigned int dest ,
struct msi_msg * msg , u8 hpet_id )
{
struct irq_cfg * cfg ;
struct irte irte ;
2012-05-08 11:08:54 +04:00
u16 sub_handle = 0 ;
2012-03-30 22:47:05 +04:00
int ir_index ;
2014-10-27 11:12:09 +03:00
cfg = irq_cfg ( irq ) ;
2012-03-30 22:47:05 +04:00
ir_index = map_irq_to_irte_handle ( irq , & sub_handle ) ;
BUG_ON ( ir_index = = - 1 ) ;
prepare_irte ( & irte , cfg - > vector , dest ) ;
/* Set source-id of interrupt request */
if ( pdev )
set_msi_sid ( & irte , pdev ) ;
else
set_hpet_sid ( & irte , hpet_id ) ;
modify_irte ( irq , & irte ) ;
msg - > address_hi = MSI_ADDR_BASE_HI ;
msg - > data = sub_handle ;
msg - > address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
MSI_ADDR_IR_SHV |
MSI_ADDR_IR_INDEX1 ( ir_index ) |
MSI_ADDR_IR_INDEX2 ( ir_index ) ;
}
/*
* Map the PCI dev to the corresponding remapping hardware unit
* and allocate ' nvec ' consecutive interrupt - remapping table entries
* in it .
*/
static int intel_msi_alloc_irq ( struct pci_dev * dev , int irq , int nvec )
{
struct intel_iommu * iommu ;
int index ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
2012-03-30 22:47:05 +04:00
iommu = map_dev_to_ir ( dev ) ;
if ( ! iommu ) {
printk ( KERN_ERR
" Unable to map PCI %s to iommu \n " , pci_name ( dev ) ) ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
index = - ENOENT ;
} else {
index = alloc_irte ( iommu , irq , nvec ) ;
if ( index < 0 ) {
printk ( KERN_ERR
" Unable to allocate %d IRTE for PCI %s \n " ,
nvec , pci_name ( dev ) ) ;
index = - ENOSPC ;
}
2012-03-30 22:47:05 +04:00
}
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
up_read ( & dmar_global_lock ) ;
2012-03-30 22:47:05 +04:00
return index ;
}
static int intel_msi_setup_irq ( struct pci_dev * pdev , unsigned int irq ,
int index , int sub_handle )
{
struct intel_iommu * iommu ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
int ret = - ENOENT ;
2012-03-30 22:47:05 +04:00
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
2012-03-30 22:47:05 +04:00
iommu = map_dev_to_ir ( pdev ) ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
if ( iommu ) {
/*
* setup the mapping between the irq and the IRTE
* base index , the sub_handle pointing to the
* appropriate interrupt remap table entry .
*/
set_irte_irq ( irq , iommu , index , sub_handle ) ;
ret = 0 ;
}
up_read ( & dmar_global_lock ) ;
2012-03-30 22:47:05 +04:00
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
return ret ;
2012-03-30 22:47:05 +04:00
}
2014-09-17 13:32:19 +04:00
static int intel_alloc_hpet_msi ( unsigned int irq , unsigned int id )
2012-03-30 22:47:05 +04:00
{
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
int ret = - 1 ;
struct intel_iommu * iommu ;
2012-03-30 22:47:05 +04:00
int index ;
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
down_read ( & dmar_global_lock ) ;
iommu = map_hpet_to_ir ( id ) ;
if ( iommu ) {
index = alloc_irte ( iommu , irq , 1 ) ;
if ( index > = 0 )
ret = 0 ;
}
up_read ( & dmar_global_lock ) ;
2012-03-30 22:47:05 +04:00
iommu/vt-d: Introduce a rwsem to protect global data structures
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event happens.
So a global rwsem solution is adopted for balance between simplicity
and performance.
For interrupt remapping driver, function intel_irq_remapping_supported(),
dmar_table_init(), intel_enable_irq_remapping(), disable_irq_remapping(),
reenable_irq_remapping() and enable_drhd_fault_handling() etc
are called during booting, suspending and resuming with interrupt
disabled, so no need to take the global lock.
For interrupt remapping entry allocation, the locking model is:
down_read(&dmar_global_lock);
/* Find corresponding iommu */
iommu = map_hpet_to_ir(id);
if (iommu)
/*
* Allocate remapping entry and mark entry busy,
* the IOMMU won't be hot-removed until the
* allocated entry has been released.
*/
index = alloc_irte(iommu, irq, 1);
up_read(&dmar_global_lock);
For DMA remmaping driver, we only uses the dmar_global_lock rwsem to
protect functions which are only called in process context. For any
function which may be called in interrupt context, we will use RCU
to protect them in following patches.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
2014-02-19 10:07:33 +04:00
return ret ;
2012-03-30 22:47:05 +04:00
}
2012-03-30 22:47:00 +04:00
struct irq_remap_ops intel_irq_remap_ops = {
2015-01-07 10:31:29 +03:00
. prepare = intel_prepare_irq_remapping ,
2012-03-30 22:47:07 +04:00
. enable = intel_enable_irq_remapping ,
. disable = disable_irq_remapping ,
. reenable = reenable_irq_remapping ,
2012-03-30 22:47:01 +04:00
. enable_faulting = enable_drhd_fault_handling ,
2012-03-30 22:47:02 +04:00
. setup_ioapic_entry = intel_setup_ioapic_entry ,
2012-03-30 22:47:03 +04:00
. set_affinity = intel_ioapic_set_affinity ,
2012-03-30 22:47:04 +04:00
. free_irq = free_irte ,
2012-03-30 22:47:05 +04:00
. compose_msi_msg = intel_compose_msi_msg ,
. msi_alloc_irq = intel_msi_alloc_irq ,
. msi_setup_irq = intel_msi_setup_irq ,
2014-09-17 13:32:19 +04:00
. alloc_hpet_msi = intel_alloc_hpet_msi ,
2012-03-30 22:47:00 +04:00
} ;
2014-11-09 17:47:58 +03:00
2014-11-09 17:48:00 +03:00
/*
* Support of Interrupt Remapping Unit Hotplug
*/
static int dmar_ir_add ( struct dmar_drhd_unit * dmaru , struct intel_iommu * iommu )
{
int ret ;
int eim = x2apic_enabled ( ) ;
if ( eim & & ! ecap_eim_support ( iommu - > ecap ) ) {
pr_info ( " DRHD %Lx: EIM not supported by DRHD, ecap %Lx \n " ,
iommu - > reg_phys , iommu - > ecap ) ;
return - ENODEV ;
}
if ( ir_parse_ioapic_hpet_scope ( dmaru - > hdr , iommu ) ) {
pr_warn ( " DRHD %Lx: failed to parse managed IOAPIC/HPET \n " ,
iommu - > reg_phys ) ;
return - ENODEV ;
}
/* TODO: check all IOAPICs are covered by IOMMU */
/* Setup Interrupt-remapping now. */
ret = intel_setup_irq_remapping ( iommu ) ;
if ( ret ) {
pr_err ( " DRHD %Lx: failed to allocate resource \n " ,
iommu - > reg_phys ) ;
ir_remove_ioapic_hpet_scope ( iommu ) ;
return ret ;
}
if ( ! iommu - > qi ) {
/* Clear previous faults. */
dmar_fault ( - 1 , iommu ) ;
iommu_disable_irq_remapping ( iommu ) ;
dmar_disable_qi ( iommu ) ;
}
/* Enable queued invalidation */
ret = dmar_enable_qi ( iommu ) ;
if ( ! ret ) {
iommu_set_irq_remapping ( iommu , eim ) ;
} else {
pr_err ( " DRHD %Lx: failed to enable queued invalidation, ecap %Lx, ret %d \n " ,
iommu - > reg_phys , iommu - > ecap , ret ) ;
intel_teardown_irq_remapping ( iommu ) ;
ir_remove_ioapic_hpet_scope ( iommu ) ;
}
return ret ;
}
2014-11-09 17:47:58 +03:00
int dmar_ir_hotplug ( struct dmar_drhd_unit * dmaru , bool insert )
{
2014-11-09 17:48:00 +03:00
int ret = 0 ;
struct intel_iommu * iommu = dmaru - > iommu ;
if ( ! irq_remapping_enabled )
return 0 ;
if ( iommu = = NULL )
return - EINVAL ;
if ( ! ecap_ir_support ( iommu - > ecap ) )
return 0 ;
if ( insert ) {
if ( ! iommu - > ir_table )
ret = dmar_ir_add ( dmaru , iommu ) ;
} else {
if ( iommu - > ir_table ) {
if ( ! bitmap_empty ( iommu - > ir_table - > bitmap ,
INTR_REMAP_TABLE_ENTRIES ) ) {
ret = - EBUSY ;
} else {
iommu_disable_irq_remapping ( iommu ) ;
intel_teardown_irq_remapping ( iommu ) ;
ir_remove_ioapic_hpet_scope ( iommu ) ;
}
}
}
return ret ;
2014-11-09 17:47:58 +03:00
}