|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [win-pv-devel] [PATCH] Don't call DbgPrint (or variants) from an event channel callback
Windows debug primitives will IPI so it's not a good idea to use them
from within an interrupt handler which may get called at HIGH_LEVEL.
Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
---
src/xeniface/ioctl_evtchn.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/xeniface/ioctl_evtchn.c b/src/xeniface/ioctl_evtchn.c
index 5fb8bec..b9b0e27 100644
--- a/src/xeniface/ioctl_evtchn.c
+++ b/src/xeniface/ioctl_evtchn.c
@@ -84,10 +84,7 @@ EvtchnInterruptHandler(
KeGetCurrentProcessorNumberEx(&ProcNumber);
ProcIndex = KeGetProcessorIndexFromNumber(&ProcNumber);
- if (!KeInsertQueueDpc(&Context->Dpc, NULL, NULL)) {
- XenIfaceDebugPrint(TRACE, "NOT INSERTED: Context %p, Port %lu, FO %p,
Cpu %lu\n",
- Context, Context->LocalPort, Context->FileObject,
ProcIndex);
- }
+ (VOID) KeInsertQueueDpc(&Context->Dpc, NULL, NULL);
return TRUE;
}
--
2.5.3
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |