search for: do_sched_op

Keir, The patch below is necessary to get ia64 building on current xen-unstable.hg. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3983e4f1b054 xen/arch/ia64/Rules.mk --- a/xen/arch/ia64/Rules.mk Sun Mar 12 10:03:33 2006 +0100 +++ b/xen/arch/ia64/Rules.mk Mon Mar 13 09:36:01 2006 -0700 @@ -12,7 +12,7 @@ CPPFLAGS += -I$(BASEDIR)/include -I$(BA

...is initialized in hypercall_page_initialise(void *hypercall_page) at the time when control panel creates the domain. Later, domain can simply the corresponding entry to issue a hypercall. For the subroutine of the HYPERVISOR_xxx, usually it is do_xxx. For example, __HYPERVISOR_sched_op should be do_sched_op. For more information, please refer to hypercall_table in xen/arch/x86/x86_{32,64}/entry.S. Thanks Ke T S wrote: > Hi, > > Can someone let me know what exactly the array "hypercall_page " > contains? Are they function pointers? > > How do I know which functions are g...

...>vcpu_info->evtchn_pending_sel); smp_mb__after_clear_bit(); /* Event pending already? */ if ( test_bit(port, &d->shared_info->evtchn_pending[0]) ) + break; + if( v->vcpu_info->evtchn_upcall_pending ) break; do_sched_op(SCHEDOP_block, 0); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I am trying to release domU pages from page_list and xenpage_list after domU shutdown while retaining the rest of the domain information. To achieve this in __domain_finalise_shutdown i call domain_relinquish_resources. This is failing to release pages from page_list for type PGT_l2_page_tables and crashing dom0. To be specific, while testing on mini-os i saw that when

...context_saved + + .align 5 + .type hypercall_table, #object +ENTRY(hypercall_table) + .long do_set_trap_table /* 0 */ + .long do_mmu_update + .long do_ni_hypercall /* set_gdt */ + .long do_ni_hypercall /* stack_switch */ + .long do_set_callbacks + .long do_ni_hypercall /* fpu_switch */ + .long do_sched_op_compat + .long do_ni_hypercall + .long do_ni_hypercall + .long do_ni_hypercall + .long do_ni_hypercall /* 10 */ + .long do_ni_hypercall + .long do_memory_op + .long do_multicall + .long do_update_va_mapping + .long do_set_timer_op /* 15 */ + .long do_event_channel_op + .long do_xen_version + .l...

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of