Home
last modified time | relevance | path

Searched refs:hypercall (Results 1 – 6 of 6) sorted by relevance

/external/bcc/examples/tracing/
Dkvm_hypercall.txt1 Demonstrations of kvm_hypercall.py, showing eBPF/bcc based hypercall analysis
8 hypercall itself.
10 To test this, while the python script is run, induce a hypercall from a
32 This output shows a sequence of exit -> hypercall -> entry where the
/external/kernel-headers/original/uapi/linux/
Dkvm.h347 } hypercall; member
/external/arm-trusted-firmware/docs/components/
Dsecure-partition-manager.rst765 a pending interrupt number through an hypercall. The PVM injects
776 the interrupt number through an hypercall.
/external/bcc/
DREADME.md80 …call.py): Conditional static kernel tracepoints for KVM entry, exit and hypercall [Examples](examp…
/external/crosvm/kvm_sys/src/aarch64/
Dbindings.rs2629 pub hypercall: kvm_run__bindgen_ty_1__bindgen_ty_7,
3863 unsafe { &(*(::std::ptr::null::<kvm_run__bindgen_ty_1>())).hypercall as *const _ as usize }, in bindgen_test_layout_kvm_run__bindgen_ty_1()
3869 stringify!(hypercall) in bindgen_test_layout_kvm_run__bindgen_ty_1()
/external/crosvm/kvm_sys/src/x86/
Dbindings.rs5066 pub hypercall: kvm_run__bindgen_ty_1__bindgen_ty_7,
6300 unsafe { &(*(::std::ptr::null::<kvm_run__bindgen_ty_1>())).hypercall as *const _ as usize }, in bindgen_test_layout_kvm_run__bindgen_ty_1()
6306 stringify!(hypercall) in bindgen_test_layout_kvm_run__bindgen_ty_1()