search for: do_grant_table_op

...(XEN) Xen call trace: (XEN) [<ffff83000010f240>] get_page+0x107/0x1b4 (XEN) [<ffff83000010f10a>] get_page_and_type+0x21/0x50 (XEN) [<ffff8300001116c4>] __gnttab_copy+0x3f5/0x5b4 (XEN) [<ffff830000111971>] gnttab_copy+0xee/0x1c4 (XEN) [<ffff830000111dbd>] do_grant_table_op+0x376/0x3bc (XEN) [<ffff8300001b83e2>] syscall_enter+0xa2/0xfc (XEN) (XEN) Guest stack trace from rbp=ffff830000ff3cf8: (XEN) ???????????????? <G><2>grant_table.c:990:d0 do_grant_table_op: domain 0, cmd 5, count 1 (XEN) /export/build/schuster/xvm-gate/xen.hg/xen/include/asm/...

...); 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 me advice once again. > I was not able to find an appropriate common header. In which header > do you defin...

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, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

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

...vmx_assist: 224 0xffff8300001134a8 populate_physmap: 216 0xffff8300001137d3 populate_physmap: 216 0xffff83000012a742 guest_console_write: 216 0xffff83000012a8de guest_console_write: 216 0xffff83000011009a do_grant_table_op: 208 0xffff8300001343e1 arch_set_info_guest: 208 0xffff83000014d382 do_set_gdt: 208 0xffff830000160c67 alloc_shadow_page: 208 0xffff83000017f103 alloc_shadow_page: 208 0xffff8300001c11c6 construct_default...

...make[2]: *** [memory.o] Error 1 make[2]: *** Waiting for unfinished jobs.... multicall.c: In function `do_multicall'': multicall.c:43: error: can''t find a register in class `BREG'' while reloading `asm'' make[2]: *** [multicall.o] Error 1 grant_table.c: In function `do_grant_table_op'': /var/tmp/portage/xen-3.0.2/work/xen-3.0.2/xen/include/asm/mm.h:206: error: can''t find a register in class `BREG'' while reloading `asm'' /var/tmp/portage/xen-3.0.2/work/xen-3.0.2/xen/include/asm/mm.h:206: error: can''t find a register in class `BREG'&...

...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 do_ni_hypercall /* 30 : callbackop */ + .long do_ni_hypercall /* xen...

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it