Re: [PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte()

On Tue, Mar 06, 2018 at 05:39:41PM -0500, Jagannathan Raman wrote: > It was noticed that the IRTE configured for guest OS kernel > was over-written while the guest was running. As a result, > vt-d Posted Interrupts configured for the guest are not being > delivered directly, and instead bounces off

Re: [PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte()

> On Apr 4, 2018, at 2:06 PM, Jag Raman wrote: > > > > On 3/6/2018 5:39 PM, Jagannathan Raman wrote: >> It was noticed that the IRTE configured for guest OS kernel >> was over-written while the guest was running. As a result, >> vt-d Posted Interrupts configured for the guest are not being >>

Re: [PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte()

On 3/6/2018 5:39 PM, Jagannathan Raman wrote: It was noticed that the IRTE configured for guest OS kernel was over-written while the guest was running. As a result, vt-d Posted Interrupts configured for the guest are not being delivered directly, and instead bounces off the host. Every interrup

[PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte()

It was noticed that the IRTE configured for guest OS kernel was over-written while the guest was running. As a result, vt-d Posted Interrupts configured for the guest are not being delivered directly, and instead bounces off the host. Every interrupt delivery takes a VM Exit. It was noticed that t