Re: KVM architecture docs

[Avi Kivity <avi@qumranet.com>]

Zhao Forrest wrote:
>> http://ols.108.redhat.com/2007/Reprints/kivity-Reprint.pdf
>>
>>     
> Hi Avi,
>
> I have a question about KVM architecture after reading your paper.
> It reads:
> ......
> At the kernel level, the kernel causes the hardware
> to enter guest mode. If the processor exits guest
> mode due to an event such as an external interrupt
> or a shadow page table fault, the kernel performs
> the necessary handling and resumes guest execution.
> If the exit reason is due to an I/O instruction
> or a signal queued to the process, then the kernel
> exits to userspace.
> ......
> After reading your paper my understanding of KVM architecture is that
> for a particular VM the user mode(QEMU), kernel mode and guest mode share
> the same process context from host linux kernel's point of view, right?
>   

Correct.  Virtual machine == process, virtual cpu == thread.

> If this is the case, see the below example:
> 1 physical NIC interrupt is received on physical CPU 0 and host kernel
> determines that this is a network packet targeted to the emulated NIC
> for a VM
> 2 at the same time this VM is running in guest mode on physical CPU 1
> My question is: at this time can host kernel *actively* interrupt VM
> and make it run in user mode to handle the incoming network data
> packet in QEMU? Or host kernel has to wait for
> VM(because of external interrupt or shadow page table fault or I/O
> instruction) to quit guest mode and wait for VM to voluntarily detect
> that incoming network packet is pending and switch to user space?
>   

The incoming packet is processed by the host ethernet stack; it is 
forwarded to the bridge, which forwards it to the tap.  When the tap 
queues the packet, it sends a signal to qemu (since the tap file 
descriptor has a signal associated).  When the kernel delivers the 
signal, it notices the qemu thread is running on cpu 1, so it sends an 
inter-processor interrupt to cpu 1.  The interrupt causes the processor 
to leave guest mode and exit to the hypervisor, which notices that a 
signal is pending, so it exits to qemu which dequeues the packet and 
notifies the guest (if necessary) by injecting an interrupt.

Note that most of this path (including the IPI) is regular Linux code, 
not kvm related, and would happen for any other application in the same way.

> A further question is, how a VM detect the incoming pending network
> packet? In kernel space or in user space?
>   

Are you talking about the host or guest?  If the host, the packet is 
received by the kernel, and further processing is done in userspace.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/