search for: do_xen_version

hi, my friends: Currently, i am studying the way of hypercall's implementation. i have already known the flow of hypercall's execuation, and i decided to add a new hypercall into the Xen. first, i want to know the detail of one hypercall function, for example, "do_xen_version", but i can not find the location of definition of "do_xen_version". who can help me? i have get some resualts as follows: [root@vt-0 xen-3.1.0-src]# find ./ -name "*.*" | xargs grep "do_xen_version" ./xen/include/xen/hypercall.h:do_xen_version( Binary file ./xe...

hi, my friends: recently, i am reading the source codes about hypercall. First, i study a simple hypercall, for example, the "do_xen_version". In "xen-3.1.0-src\xen\common\kernel.c", the definition of "do_xen_version" is: DO(xen_version) (int cmd, XEN_GUEST_HANDLE(void) arg) { .... } according to the " #define DO(fn) long do_##fn ", the expanded form is "do_xen_version (...)". then, in th...

...s. We could either uninline some of these functions, or try gcc -O2 or gcc -Os. Ian, Keir, which of these approaches do you prefer? Currently the top stack users are: $ objdump -dS xen-syms | ./checkstack.pl x86_64 0xffff8300001c7c47 find_unisys_acpi_oem_table: 1296 0xffff83000011182e do_xen_version: 1280 0xffff83000015bc3e x86_emulate_memop: 1264 0xffff8300001adbaa vmx_world_save: 1040 0xffff8300001aeac5 vmx_world_save: 1040 0xffff830000106800 do_dom0_op: 968 0xffff8300001080cf do_dom0_op...

...e do_* functions are at least: extern long do_ni_hypercall(void); extern long do_dom0_op(dom0_op_t *u_dom0_op); extern long do_memory_op(int cmd, void *arg); extern long do_multicall(multicall_entry_t *call_list, unsigned int nr_calls); extern long do_event_channel_op(evtchn_op_t *uop); extern long do_xen_version(int cmd, void *arg); extern long do_console_io(int cmd, int count, char *buffer); extern long do_grant_table_op(unsigned int cmd, void *uop, unsigned int count); Thanks, Tristan. Le Jeudi 26 Janvier 2006 05:33, Masaki Kanno a écrit : > Hi, Tristan > > Thank you for advice. Please give m...

...est1/xen-unstable/xen/common/kernel.c:84: undefined reference to `__stack_chk_fail'' /home/test1/xen-unstable/xen/common/kernel.c:84: relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `__stack_chk_fail'' /home/test1/xen-unstable/xen/common/built_in.o: In function `do_xen_version'': /home/test1/xen-unstable/xen/common/kernel.c:230: undefined reference to `__stack_chk_fail'' /home/test1/xen-unstable/xen/common/kernel.c:230: relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `__stack_chk_fail'' /home/test1/xen-unstable/xen/common/buil...

...+ .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 + .long do_console_io + .long do_physdev_op + .long do_grant_table_op /* 20 */ + .long do_vm_assist + .long do_ni_hypercall + .long do_restore_trap_frame + .long do_vcpu_op + .long do_ni_hypercall /* 25 */ + .long do_mmuext_op + .long do_ni_hypercall + .long do_nmi_op + .long do_sched_op + .long d...

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