[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] From virtio_kick until VM-exit?

From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] From virtio_kick until VM-exit?
Date: Sat, 30 Jul 2016 09:35:58 +0100

On Fri, Jul 29, 2016 at 9:00 PM, Charls D. Chap <address@hidden> wrote:

Please use Reply-All when responding to a mailing list thread.  This
keeps the mailing list (address@hidden) in the CC list so your
replies are sent to the mailing list too.  This way the discussion
stays public on the mailing list and others can participate.

> I've read again and again the code. Please let me ask you one last question.
> the question is, where is the VMEXIT and VMENTRY code.
> If i have this, i can answer the following that bother me:
> 1)
> What is a VMEXIT, what mechanism? is it an interrupt? Same for VMENTRY
> Where does the VMENTRY return? In an interrupt handler?
> 2)
> Which are the parameters of vmetry and vmexit
> does each vcpu has a specific VPID or does it change in every RESUME
> 3)
> What is a hypercall? A pair of VMEXIT-VMENTRY? or is it oneway (does it ever
> return?) Or there are many types of hypercalls
> 4)
> When we do vmexit, Is it another context? I am mean, does the stack changes?
> What is the guest stack? Each vcpu has one stack?

Please look at the Intel Software Developer's Manuals and read about
VMX instructions:


Once you have an overview you'll understand the semantics and be able
to grep for the relevant code in the kvm kernel module.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]