[Xen-devel] [PATCH] x86/apicv: move posted_intr_vector handler to pi_notification_interrupt

["Xuquan (Quan Xu)" <xuquan8@xxxxxxxxxx>]

>From e101539e18625cb70dfaee58ae7e73aa5df7b8a9 Mon Sep 17 00:00:00 2001
From: Quan Xu <xuquan8@xxxxxxxxxx>
Date: Fri, 24 Feb 2017 08:43:16 +0800
Subject: [PATCH] x86/apicv: move posted_intr_vector handler to
 pi_notification_interrupt

event_check_interrupt is likely used in pair with original delivery logic.
Now since delivery path is changed, we should move to pi_notification_interrupt
always.

Signed-off-by: Quan Xu <xuquan8@xxxxxxxxxx>
---
 xen/arch/x86/hvm/vmx/vmx.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
index 61925cf..1b026fa 100644
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -2279,13 +2279,9 @@ const struct hvm_function_table * __init start_vmx(void)

     if ( cpu_has_vmx_posted_intr_processing )
     {
+        alloc_direct_apic_vector(&posted_intr_vector, 
pi_notification_interrupt);
         if ( iommu_intpost )
-        {
-            alloc_direct_apic_vector(&posted_intr_vector, 
pi_notification_interrupt);
             alloc_direct_apic_vector(&pi_wakeup_vector, pi_wakeup_interrupt);
-        }
-        else
-            alloc_direct_apic_vector(&posted_intr_vector, 
event_check_interrupt);
     }
     else
     {
--
1.8.3.1

Attachment: 0001-x86-apicv-move-posted_intr_vector-handler-to-pi_noti.patch
Description: 0001-x86-apicv-move-posted_intr_vector-handler-to-pi_noti.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel