Add VT-d Posted-Interrupts support - IOMMU part
v7 cover Add VT-d Posted-Interrupts support - IOMMU part
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt. With VT-d Posted-Interrupts enabled, external interrupts from direct-assigned devices can be delivered to guests without VMM intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in the following URL:
http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html
This series was part of http://thread.gmane.org/gmane.linux.kernel.iommu/7708. To make things clear, send out IOMMU part here.
This patch-set is based on the lastest x86/apic branch of tip tree.
Divide the whole series which contain multiple components into three parts:
- Prerequisite changes to irq subsystem (already merged in tip tree x86/apic branch)
- IOMMU part (in this series)
- KVM and VFIO parts (will send out this part once the first two parts are accepted)
v6->v7:
* Add an static inline helper function set_irq_posting_cap() to set the PI capability.
* Add some comments for the new member "ir_data->irte_pi_entry".
v5->v6:
* Extend 'struct irte' for VT-d Posted-Interrupts, combine remapped and posted mode into one irte structure.
v4->v5:
* Abstract modify_irte() to accept two format of irte.
v3->v4:
* Change capability to a int variant flags instead of a function call.
* Add hotplug case for VT-d PI.
Feng Wu (7):
iommu: Add new member capability to struct irq_remap_ops iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip iommu, x86: No need to migrating irq for VT-d Posted-Interrupts iommu, x86: Add cap_pi_support() to detect VT-d PI capability iommu, x86: Setup Posted-Interrupts capability for Intel iommu iommu, x86: define irq_remapping_cap()
iommu, x86: Properly handler PI for IOMMU hotplug
Thomas Gleixner (1):
iommu: dmar: Extend struct irte for VT-d Posted-Interrupts
arch/x86/include/asm/irq_remapping.h | 11 +++++ drivers/iommu/intel_irq_remapping.c | 84 +++++++++++++++++++++++++++++++++++- drivers/iommu/irq_remapping.c | 11 +++++ drivers/iommu/irq_remapping.h | 6 +++ include/linux/dmar.h | 70 +++++++++++++++++++++++------- include/linux/intel-iommu.h | 1 + 6 files changed, 167 insertions(+), 16 deletions(-)
Signature · 1 line
2.1.0
PATCH v7 1/8 iommu: Add new member capability to struct irq_remap_ops
This patch adds a new member capability to struct irq_remap_ops, this new function ops can be used to check whether some features are supported, such as VT-d Posted-Interrupts.
--- arch/x86/include/asm/irq_remapping.h | 4 ++++ drivers/iommu/irq_remapping.h | 3 +++ 2 files changed, 7 insertions(+)
arch/x86/include/asm/irq_remapping.h +4 -0
@@ -31,6 +31,10 @@ struct irq_alloc_info;#ifdef CONFIG_IRQ_REMAP +enum irq_remap_cap { +IRQ_POSTING_CAP =0 , +}; +extern void set_irq_remapping_broken (void );extern int irq_remapping_prepare (void );extern int irq_remapping_enable (void );
drivers/iommu/irq_remapping.h +3 -0
@@ -35,6 +35,9 @@ extern int no_x2apic_optout;extern int irq_remapping_enabled;struct irq_remap_ops { +/* The supported capabilities */ +int capability; +/* Initializes hardware and makes it ready for remapping interrupts */ int (*prepare)(void );
Signature · 1 line
2.1.0
PATCH v7 2/8 iommu: dmar: Extend struct irte for VT-d Posted-Interrupts
In reply to Feng WuFrom: Thomas Gleixner <[email protected]>
The IRTE (Interrupt Remapping Table Entry) is either an entry for remapped or for posted interrupts. The hardware distiguishes between remapped and posted entries by bit 15 in the low 64 bit of the IRTE. If cleared the entry is remapped, if set it's posted.
The entries have common fields and dependent on the posted bit fields with different meanings.
Extend struct irte to handle the differences between remap and posted mode by having three structs in the unions:
- Shared
- Remapped
- Posted
--- include/linux/dmar.h | 70 +++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 55 insertions(+), 15 deletions(-)
include/linux/dmar.h +55 -15
@@ -185,33 +185,73 @@ static inline int dmar_device_remove(void *handle)struct irte {union { +/* Shared between remapped and posted mode*/ struct { -__u64 present :1 , - fpd :1 , - dst_mode :1 , - redir_hint :1 , - trigger_mode :1 , - dlvry_mode :3 , - avail :4 , - __reserved_1 :4 , - vector :8 , - __reserved_2 :8 , - dest_id :32 ; +__u64 present :1 ,/* 0 */ + fpd :1 ,/* 1 */ + __res0 :6 ,/* 2 - 6 */ + avail :4 ,/* 8 - 11 */ + __res1 :3 ,/* 12 - 14 */ + pst :1 ,/* 15 */ + vector :8 ,/* 16 - 23 */ + __res2 :40 ;/* 24 - 63 */ + }; + +/* Remapped mode */ +struct { +__u64 r_present :1 ,/* 0 */ + r_fpd :1 ,/* 1 */ + dst_mode :1 ,/* 2 */ + redir_hint :1 ,/* 3 */ + trigger_mode :1 ,/* 4 */ + dlvry_mode :3 ,/* 5 - 7 */ + r_avail :4 ,/* 8 - 11 */ + r_res0 :4 ,/* 12 - 15 */ + r_vector :8 ,/* 16 - 23 */ + r_res1 :8 ,/* 24 - 31 */ + dest_id :32 ;/* 32 - 63 */ + }; + +/* Posted mode */ +struct { +__u64 p_present :1 ,/* 0 */ + p_fpd :1 ,/* 1 */ + p_res0 :6 ,/* 2 - 7 */ + p_avail :4 ,/* 8 - 11 */ + p_res1 :2 ,/* 12 - 13 */ + p_urgent :1 ,/* 14 */ + p_pst :1 ,/* 15 */ + p_vector :8 ,/* 16 - 23 */ + p_res2 :14 ,/* 24 - 37 */ + pda_l :26 ;/* 38 - 63 */ };__u64 low; };union { +/* Shared between remapped and posted mode*/ struct { -__u64 sid :16 , - sq :2 , - svt :2 , - __reserved_3 :44 ; +__u64 sid :16 ,/* 64 - 79 */ + sq :2 ,/* 80 - 81 */ + svt :2 ,/* 82 - 83 */ + __res3 :44 ;/* 84 - 127 */ + }; + +/* Posted mode*/ +struct { +__u64 p_sid :16 ,/* 64 - 79 */ + p_sq :2 ,/* 80 - 81 */ + p_svt :2 ,/* 82 - 83 */ + p_res3 :12 ,/* 84 - 95 */ + pda_h :32 ;/* 96 - 127 */ };__u64 high; }; }; +#define PDA_LOW_BIT 26 +#define PDA_HIGH_BIT 32 +enum {IRQ_REMAP_XAPIC_MODE ,IRQ_REMAP_X2APIC_MODE ,
Signature · 1 line
2.1.0
PATCH v7 3/8 iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip
In reply to Feng WuImplement irq_set_vcpu_affinity for intel_ir_chip.
--- arch/x86/include/asm/irq_remapping.h | 5 ++++ drivers/iommu/intel_irq_remapping.c | 46 ++++++++++++++++++++++++++++++++++++ 2 files changed, 51 insertions(+)
arch/x86/include/asm/irq_remapping.h +5 -0
@@ -57,6 +57,11 @@ static inline struct irq_domain *arch_get_ir_parent_domain(void) return x86_vector_domain; } +struct vcpu_data { +u64 pi_desc_addr;/* Physical address of PI Descriptor */ +u32 vector;/* Guest vector of the interrupt */ +}; +#else /* CONFIG_IRQ_REMAP */ static inline void set_irq_remapping_broken (void ) { }
drivers/iommu/intel_irq_remapping.c +46 -0
62 lines not on this page · raw message
Signature · 1 line
2.1.0
PATCH v7 4/8 iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
In reply to Feng WuWe don't need to migrate the irqs for VT-d Posted-Interrupts here. When 'pst' is set in IRTE, the associated irq will be posted to guests instead of interrupt remapping. The destination of the interrupt is set in Posted-Interrupts Descriptor, and the migration happens during vCPU scheduling.
However, we still update the cached irte here, which can be used when changing back to remapping mode.
--- drivers/iommu/intel_irq_remapping.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/iommu/intel_irq_remapping.c +4 -1
@@ -994,7 +994,10 @@ intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask,*/ irte->vector = cfg->vector; irte->dest_id =IRTE_DEST (cfg->dest_apicid); -modify_irte (&ir_data->irq_2_iommu, irte); + +/* We don't need to modify irte if the interrupt is for posting. */ +if (irte->pst !=1 ) +modify_irte (&ir_data->irq_2_iommu, irte);/* * After this point, all the interrupts will start arriving
Signature · 1 line
2.1.0
Re: [v7 4/8] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
Quoted 21 lines · Feng Wu
We don't need to migrate the irqs for VT-d Posted-Interrupts here. When 'pst' is set in IRTE, the associated irq will be posted to guests instead of interrupt remapping. The destination of the interrupt is set in Posted-Interrupts Descriptor, and the migration happens during vCPU scheduling.
However, we still update the cached irte here, which can be used when changing back to remapping mode.
Signed-off-by Feng Wu <[email protected]>Acked-by David Woodhouse <[email protected]>--- drivers/iommu/intel_irq_remapping.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/iommu/intel_irq_remapping.c +0
-0
drivers/iommu/intel_irq_remapping.c intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask, · line 1000
Quoted 8 lines
drivers/iommu/intel_irq_remapping.c +4
-1@@ -994,7 +994,10 @@ intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask,*/ irte->vector = cfg->vector; irte->dest_id =IRTE_DEST (cfg->dest_apicid); -modify_irte (&ir_data->irq_2_iommu, irte); + +/* We don't need to modify irte if the interrupt is for posting. */ +if (irte->pst !=1 ) +modify_irte (&ir_data->irq_2_iommu, irte);
I don't think this is correct. ir_data->irte_entry contains the non posted version, which has pst == 0.
You need some other way to store whether you are in posted mode or not.
Thanks,
tglx
RE: [v7 4/8] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
Quoted 48 lines
-----Original Message-----
From: Thomas Gleixner [mailto:[email protected]]
Sent: Monday, May 25, 2015 4:38 PM
To: Wu, Feng
Cc: [email protected]; [email protected]; jiang.liu-VuQAYsv1563Yd54FQh9/[email protected]; iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; [email protected]
Subject: Re: [v7 4/8] iommu, x86: No need to migrating irq for VT-d
Posted-InterruptsQuoted 9 lines · Feng Wu
We don't need to migrate the irqs for VT-d Posted-Interrupts here. When 'pst' is set in IRTE, the associated irq will be posted to guests instead of interrupt remapping. The destination of the interrupt is set in Posted-Interrupts Descriptor, and the migration happens during vCPU scheduling.
However, we still update the cached irte here, which can be used when changing back to remapping mode.
Review
Quoted 8 lines
Signed-off-by Feng Wu <[email protected]>Acked-by David Woodhouse <[email protected]>--- drivers/iommu/intel_irq_remapping.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)(quoted diff) +0
-0
b/drivers/iommu/intel_irq_remapping.cdrivers/iommu/intel_irq_remapping.c intel_ir_set_affinity(struct irq_data *data, const
Quoted 4 lines
index 1955b09..646f4cf 100644
drivers/iommu/intel_irq_remapping.c +0
-0@@ -994,7 +994,10 @@ intel_ir_set_affinity(struct irq_data *data, conststruct cpumask *mask,
drivers/iommu/intel_irq_remapping.c intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask, · line 1000
Quoted 8 lines
drivers/iommu/intel_irq_remapping.c +4
-1*/ irte->vector = cfg->vector; irte->dest_id =IRTE_DEST (cfg->dest_apicid); -modify_irte (&ir_data->irq_2_iommu, irte); + +/* We don't need to modify irte if the interrupt is for posting. */ +if (irte->pst !=1 ) +modify_irte (&ir_data->irq_2_iommu, irte);I don't think this is correct.
ir_data->irte_entrycontains the non posted version, which has pst == 0.
Quoted 2 lines
You need some other way to store whether you are in posted mode or not.
Yes, seems this is incorrect. Thank you for pointing this out. After more thinking about this, I think I can do it this way:
#1. Check the 'pst' field in hardware
#2. If 'pst' is 1, we don't update the IRTE in hardware.
However, the question is the check and update operations should be protected by the same spinlock ' irq_2_ir_lock ', otherwise, race condition may happen.
Based on the above idea, I have two solutions for this, do you think which one is better or you have other better suggestions? It is highly appreciated if you can give comments about them!
Solution 1:
Introduction a new function test_and_modify_irte() which is called by intel_ir_set_affinity in place of the original modify_irte().
Here is the changes:
+static int test_and_modify_irte(struct irq_2_iommu *irq_iommu,
+ struct irte *irte_modified)
+{
+ struct intel_iommu *iommu; + unsigned long flags; + struct irte *irte; + int rc, index;
+
+ if (!irq_iommu)
+ return -1;
+
+ raw_spin_lock_irqsave(&irq_2_ir_lock, flags);
+
+ iommu = irq_iommu->iommu;
+
+ index = irq_iommu->irte_index + irq_iommu->sub_handle;
+ irte = &iommu->ir_table->base[index];
+
+ if (irte->pst)
+ goto unlock;
+
+ set_64bit(&irte->low, irte_modified->low); + set_64bit(&irte->high, irte_modified->high); + __iommu_flush_cache(iommu, irte, sizeof(*irte));
+
+ rc = qi_flush_iec(iommu, index, 0);
+unlock:
+ raw_spin_unlock_irqrestore(&irq_2_ir_lock, flags);
+
+ return rc;
+}
+
Soluation 2:
Instead of introducing a new function, add a flag in the original modify_irte() function to indicate that whether we need to check and return before updating the real hardware, add pass 1 to return_on_pst in intel_ir_set_affinity() Here is the changes:
static int modify_irte(struct irq_2_iommu *irq_iommu,
- struct irte *irte_modified)
+ struct irte *irte_modified
+ bool return_on_pst)
{
struct intel_iommu *iommu;
unsigned long flags;
@@ -140,11 +173,15 @@ static int modify_irte(struct irq_2_iommu *irq_iommu,
index = irq_iommu->irte_index + irq_iommu->sub_handle;
irte = &iommu->ir_table->base[index];+ if (return_on_pst && irte->pst)
+ goto unlock;
+
set_64bit(&irte->low, irte_modified->low);
set_64bit(&irte->high, irte_modified->high);
__iommu_flush_cache(iommu, irte, sizeof(*irte));
rc = qi_flush_iec(iommu, index, 0);
+unlock:
raw_spin_unlock_irqrestore(&irq_2_ir_lock, flags);
return rc;Thanks,
Feng
Quoted 4 lines
Thanks,
tglx
RE: [v7 4/8] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
Quoted 12 lines · Feng
Quoted 11 lines · Feng Wu
drivers/iommu/intel_irq_remapping.c intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask, · line 1000
Quoted 4 lines
drivers/iommu/intel_irq_remapping.c +4
-0+ +/* We don't need to modify irte if the interrupt is for posting. */ +if (irte->pst !=1 ) +modify_irte (&ir_data->irq_2_iommu, irte);I don't think this is correct.
ir_data->irte_entrycontains the non posted version, which has pst == 0.You need some other way to store whether you are in posted mode or not.
Quoted 7 lines
Yes, seems this is incorrect. Thank you for pointing this out. After more thinking about this, I think I can do it this way:
#1. Check the 'pst' field in hardware
#2. If 'pst' is 1, we don't update the IRTE in hardware.However, the question is the check and update operations should be protected by the same spinlock '
irq_2_ir_lock', otherwise, race condition may happen.
Why?
set_affinity() and vcpu_set_affinity() are serialized via irq_desc->lock. And vcpu_set_affinity() is the only way to switch from and to posted mode.
So all you need is a field in intel_irq_data which captures whether posted is enabled or not.
Thanks,
tglx
RE: [v7 4/8] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
Quoted 30 lines
-----Original Message-----
From: Thomas Gleixner [mailto:[email protected]]
Sent: Tuesday, May 26, 2015 6:00 PM
To: Wu, Feng
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: RE: [v7 4/8] iommu, x86: No need to migrating irq for VT-d Posted-InterruptsQuoted 12 lines · Feng
Quoted 11 lines · Feng Wu
drivers/iommu/intel_irq_remapping.c intel_ir_set_affinity(struct irq_data *data, const struct cpumask *mask, · line 1000
Quoted 4 lines
drivers/iommu/intel_irq_remapping.c +4
-0+ +/* We don't need to modify irte if the interrupt is for posting. */ +if (irte->pst !=1 ) +modify_irte (&ir_data->irq_2_iommu, irte);I don't think this is correct.
ir_data->irte_entrycontains the non posted version, which has pst == 0.You need some other way to store whether you are in posted mode or not.
Quoted 6 lines
Yes, seems this is incorrect. Thank you for pointing this out. After more thinking about this, I think I can do it this way:
#1. Check the 'pst' field in hardware
#2. If 'pst' is 1, we don't update the IRTE in hardware.However, the question is the check and update operations should be
Quoted 8 lines
protected
Quoted 1 line
by the same spinlock '
irq_2_ir_lock', otherwise, race condition may happen.Why?
set_affinity()andvcpu_set_affinity()are serialized viairq_desc->lock. Andvcpu_set_affinity()is the only way to switch from and to posted mode.
Oh, Yes, I didn't notice that they are both protected by that lock. In that case, I can just add a filed like you mentioned below. Thanks for the comments!
Thanks,
Feng
Quoted 7 lines
So all you need is a field in
intel_irq_datawhich captures whether posted is enabled or not.Thanks,
tglx
PATCH v7 5/8 iommu, x86: Add cap_pi_support() to detect VT-d PI capability
In reply to Feng WuAdd helper function to detect VT-d Posted-Interrupts capability.
--- include/linux/intel-iommu.h | 1 + 1 file changed, 1 insertion(+)
include/linux/intel-iommu.h +1 -0
@@ -87,6 +87,7 @@ static inline void dmar_writeq(void __iomem *addr, u64 val)/* * Decoding Capability Register */ +#define cap_pi_support (c) (((c) >> 59) & 1)#define cap_read_drain (c) (((c) >> 55) & 1)#define cap_write_drain (c) (((c) >> 54) & 1)#define cap_max_amask_val (c) (((c) >> 48) & 0x3f)
Signature · 1 line
2.1.0
PATCH v7 6/8 iommu, x86: Setup Posted-Interrupts capability for Intel iommu
In reply to Feng WuSet Posted-Interrupts capability for Intel iommu when IR is enabled, clear it when IR is disabled.
--- drivers/iommu/intel_irq_remapping.c | 30 ++++++++++++++++++++++++++++++ drivers/iommu/irq_remapping.c | 2 ++ drivers/iommu/irq_remapping.h | 3 +++ 3 files changed, 35 insertions(+)
drivers/iommu/intel_irq_remapping.c +30 -0
@@ -572,6 +572,26 @@ error:return -ENODEV ; } +/* +* Set Posted-Interrupts capability. +*/ +static inline void set_irq_posting_cap (void ) +{ +struct dmar_drhd_unit *drhd; +struct intel_iommu *iommu; + +if (!disable_irq_post) { + intel_irq_remap_ops.capability |=1 <<IRQ_POSTING_CAP ; + +for_each_iommu (iommu, drhd) +if (!cap_pi_support (iommu->cap)) { + intel_irq_remap_ops.capability &= + ~(1 <<IRQ_POSTING_CAP ); +break ; + } + } +} +static int __init intel_enable_irq_remapping (void ) {struct dmar_drhd_unit *drhd;
@@ -647,6 +667,8 @@ static int __init intel_enable_irq_remapping(void) irq_remapping_enabled =1 ; +set_irq_posting_cap (); +pr_info ("Enabled IRQ remapping in %s mode\n" , eim ?"x2apic" :"xapic" );return eim ?IRQ_REMAP_X2APIC_MODE :IRQ_REMAP_XAPIC_MODE ;
@@ -847,6 +869,12 @@ static void disable_irq_remapping(void)iommu_disable_irq_remapping (iommu); } + +/* +* Clear Posted-Interrupts capability. +*/ +if (!disable_irq_post) + intel_irq_remap_ops.capability &= ~(1 <<IRQ_POSTING_CAP ); }static int reenable_irq_remapping (int eim)
@@ -874,6 +902,8 @@ static int reenable_irq_remapping(int eim)if (!setup) goto error; +set_irq_posting_cap (); +return 0 ; error:
drivers/iommu/irq_remapping.c +2 -0
@@ -22,6 +22,8 @@ int irq_remap_broken;int disable_sourceid_checking;int no_x2apic_optout; +int disable_irq_post =1 ; +static int disable_irq_remap;static struct irq_remap_ops *remap_ops;
drivers/iommu/irq_remapping.h +3 -0
@@ -34,6 +34,8 @@ extern int disable_sourceid_checking;extern int no_x2apic_optout;extern int irq_remapping_enabled; +extern int disable_irq_post; +struct irq_remap_ops {/* The supported capabilities */ int capability;
@@ -69,6 +71,7 @@ extern void ir_ack_apic_edge(struct irq_data *data);#define irq_remapping_enabled 0#define irq_remap_broken 0 +#define disable_irq_post 1#endif /* CONFIG_IRQ_REMAP */
Signature · 1 line
2.1.0
PATCH v7 7/8 iommu, x86: define irq_remapping_cap()
In reply to Feng WuThis patch adds a new interface irq_remapping_cap() to detect whether irq remapping supports new features, such as VT-d Posted-Interrupts. We export this function out, so that KVM code can check this and use this mechanism properly.
--- arch/x86/include/asm/irq_remapping.h | 2 ++ drivers/iommu/irq_remapping.c | 9 +++++++++ 2 files changed, 11 insertions(+)
arch/x86/include/asm/irq_remapping.h +2 -0
@@ -35,6 +35,7 @@ enum irq_remap_cap { IRQ_POSTING_CAP = 0, }; +extern bool irq_remapping_cap (enum irq_remap_cap cap);extern void set_irq_remapping_broken (void );extern int irq_remapping_prepare (void );extern int irq_remapping_enable (void );
@@ -64,6 +65,7 @@ struct vcpu_data {#else /* CONFIG_IRQ_REMAP */ +static bool irq_remapping_cap (enum irq_remap_cap cap) {return 0 ; }static inline void set_irq_remapping_broken (void ) { }static inline int irq_remapping_prepare (void ) {return -ENODEV ; }static inline int irq_remapping_enable (void ) {return -ENODEV ; }
drivers/iommu/irq_remapping.c +9 -0
@@ -81,6 +81,15 @@ void set_irq_remapping_broken(void) irq_remap_broken =1 ; } +bool irq_remapping_cap (enum irq_remap_cap cap) +{ +if (!remap_ops || disable_irq_post) +return 0 ; + +return (remap_ops->capability & (1 << cap)); +} +EXPORT_SYMBOL_GPL (irq_remapping_cap); +int __init irq_remapping_prepare (void ) {if (disable_irq_remap)
Signature · 1 line
2.1.0
PATCH v7 8/8 iommu, x86: Properly handler PI for IOMMU hotplug
In reply to Feng WuReturn error when inserting a new IOMMU which doesn't support PI if PI is currently in use.
--- drivers/iommu/intel_irq_remapping.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/iommu/intel_irq_remapping.c +3 -0
@@ -1354,6 +1354,9 @@ int dmar_ir_hotplug(struct dmar_drhd_unit *dmaru, bool insert)return -EINVAL ;if (!ecap_ir_support (iommu->ecap))return 0 ; +if (irq_remapping_cap (IRQ_POSTING_CAP ) && + !cap_pi_support (iommu->cap)) +return -EBUSY ;if (insert) {if (!iommu->ir_table)
Signature · 1 line
2.1.0