Displaying 4 results from an estimated 4 matches for "max_evtchn".
Did you mean:
max_evtchns
2006 Oct 04
0
[PATCH,RFC 6/17] 32-on-64 shared info handling
...setup_guest(struct
* Required to do this once per domain
* TODO: add a seperate function to do these.
*/
- memset(&d->shared_info->evtchn_mask[0], 0xff,
- sizeof(d->shared_info->evtchn_mask));
+ memset(shared_info_addr(d, evtchn_mask), 0xff, MAX_EVTCHNS(d) / 8);
}
Index: 2006-10-04/xen/arch/x86/hvm/vmx/vmx.c
===================================================================
--- 2006-10-04.orig/xen/arch/x86/hvm/vmx/vmx.c 2006-10-04 08:49:29.000000000 +0200
+++ 2006-10-04/xen/arch/x86/hvm/vmx/vmx.c 2006-10-04 15:11:03.000000000 +0200
@@ -119,...
2007 Jan 04
21
[PATCH] make balloon driver not return pages which are in [xen_start_info->nr_pages, max_pfn] on ia64
make balloon driver not return pages which are in
[xen_start_info->nr_pages, max_pfn] on ia64.
On ia64 memory might be assigned sparsely. In that case
xen_start_info->nr_pages and max_pfn doesn''t match while pages which are in
[xen_start_info->nr_pages, max_pfn] are used.
--
yamahata
_______________________________________________
Xen-devel mailing list
2006 Mar 10
12
[PATCH] Add SCHEDOP_block_on
...+}
+
+/*
+ * Block the currently-executing domain without enabling interrupts, for a
+ * particular evtchn. Whilst we check for a particular evtchn, /any/ event
+ * will wake us up again.
+ */
+static long do_block_on(unsigned long evtchn)
+{
+ struct vcpu *v = current;
+
+ if ( evtchn >= MAX_EVTCHNS )
+ return -EINVAL;
+
+ set_bit(_VCPUF_blocked, &v->vcpu_flags);
+
+ /* Check for event /after/ blocking: avoids wakeup waiting race. */
+ if ( evtchn_pending(v->domain->shared_info, evtchn) )
{
clear_bit(_VCPUF_blocked, &v->vcpu_flags);
}...
2012 Jan 31
26
[PATCH 00/10] FLASK updates: MSI interrupts, cleanups
This patch set adds XSM security labels to useful debugging output
locations, and fixes some assumptions that all interrupts behaved like
GSI interrupts (which had useful non-dynamic IDs). It also cleans up the
policy build process and adds an example of how to use the user field in
the security context.
Debug output:
[PATCH 01/10] xsm: Add security labels to event-channel dump
[PATCH 02/10] xsm: