* Scheduler/hypervisor traps, vm_event_vcpu_pause - some details on how they work?
@ 2016-03-14 6:51 Corneliu ZUZU
0 siblings, 0 replies; only message in thread
From: Corneliu ZUZU @ 2016-03-14 6:51 UTC (permalink / raw)
Cc: Tamas K Lengyel, Stefano Stabellini, Razvan Cojocaru, Jan Beulich
I'm trying to add a vm-event function that would execute just before a
vCPU resumes execution. To do this, I need to know precisely how and
when this happens.
I've been browsing the codebase to try and gain some insight on the
matter, but I still need some clarifications as parts of it are not so
Currently my understanding is that a vCPU can be entered in 3 ways:
1) The first entry, when the vCPU is first created. On ARM, the PC of
the vCPU is set to continue_new_vcpu.
Q1. How does this happen on X86?
2) After a hypervisor trap (X86 VMENTER/ARM ERET).
Q2. How does pausing of the current vCPU (vm_event_vcpu_pause)
work, specifically where does the context switch to another vCPU happen?
Is it reentered through the below mentioned scheduling functions?
Q3. Can we resume on another vCPU than the one that trapped if it
Q4. Can a hypervisor trap be interrupted by a scheduling operation?
3) Scheduler interrupt -> functions context_switch/continue_running.
Q5. Are these 3 the only ways a vCPU can be entered?
Thank you very much,
Xen-devel mailing list
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-03-14 6:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-14 6:51 Scheduler/hypervisor traps, vm_event_vcpu_pause - some details on how they work? Corneliu ZUZU
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).