search for: do_set_trap_t

Hello, I am a newbie at xen - I am trying to trace the complete execution of a trap. Specifically, I am trying to find out where the control transfer happens between a domU to dom0 when a trap occurs, and where the control switches back to domU after the trap is handled. I was wondering if there is some documentation on this or someone may be able to help me out. Thanks, Girish

...r4, [r2, #OFFSET_VCPU_DACR] + ldr r7, [r2, #OFFSET_VCPU_CONTEXTIDR] + + mcr p15, 0, r4, c3, c0, 0 + mcr p15, 0, r7, c13, c0, 1 + + add ip, r2, #OFFSET_VCPU_R4 + ldmia ip, {r4 - sl, fp, ip, sp, lr} + + b 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_n...

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