Displaying 2 results from an estimated 2 matches for "msix_post_handler".
2013 Nov 22
10
[PATCH v4] x86: properly handle MSI-X unmask operation from guests
...h | 1 +
4 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
index deb7b92..6c83c25 100644
--- a/xen/arch/x86/hvm/io.c
+++ b/xen/arch/x86/hvm/io.c
@@ -297,6 +297,9 @@ void hvm_io_assist(ioreq_t *p)
break;
}
+ if ( msix_post_handler(curr) )
+ gdprintk(XENLOG_ERR, "msix_post_handler error\n");
+
if ( p->state == STATE_IOREQ_NONE )
vcpu_end_shutdown_deferral(curr);
}
diff --git a/xen/arch/x86/hvm/vmsi.c b/xen/arch/x86/hvm/vmsi.c
index 4826b4a..2cdd0dc 100644
--- a/xen/arch/x86/hvm/vmsi.c
+++ b/...
2013 Nov 26
6
[PATCH v5] x86: properly handle MSI-X unmask operation from guests
...v4:Some changes related to coding style according to Andrew Cooper''s comments
v5:Some changes according to Jan''s comments, including
a) remove "valid" field, use "ctrl_address" itself to judge if there is a valid
pending msix unmask operation
b) Call msix_post_handler() when (p->state == STATE_IOREQ_NONE), which
means it gets executed only upon completion of I/O
From de586050612f2fbe6fbb46065c2a84069c52009e Mon Sep 17 00:00:00 2001
From: Feng Wu <feng.wu@intel.com>
Date: Wed, 13 Nov 2013 21:43:48 -0500
Subject: [PATCH v5] x86: properly handle MSI...