public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sukanto Ghosh <sukanto@cse.iitb.ac.in>
To: avi@qumranet.com
Cc: kvm@vger.kernel.org
Subject: Re: Scheduling of VCPUs and allocation of Guest Physical Memory
Date: Mon, 16 Jun 2008 19:53:26 +0530	[thread overview]
Message-ID: <4856775E.4050601@cse.iitb.ac.in> (raw)
In-Reply-To: <484D5808.9010907@qumranet.com>


>> But what about the interrupts that need to be delivered immediately 
>> and while the VM is executing (assume interrupts are enabled in the 
>> guest). Is any kind of signal-based mechanism employed to force a 
>> VM-exit ?
>>
>
> Sending a signal to a task that is executing guest code will force it 
> to exit to userspace immediately.  The in-kernel interrupt controller 
> emulation also forces guest exits by sending inter-processor interrupts.
>
>
I saw that KVM has guest SMP support upto 4 VCPUs. Are these VCPUs 
modelled as threads of 'the process representing the VM' ?

If it is, then, when a signal is sent to the that process by the QEMU 
process, shouldn't all of the VCPUs (for that VM) exit to the userspace ?

Who does this management of delivering the interrupt to the VCPU for 
which it is intended for ? And, how ?


Also, while going through the KVM source, I found mention of opaque at 
many places. What does 'opaque' refer to ? What is an opaque data ?



Thanks and Regards,
Sukanto


  reply	other threads:[~2008-06-16 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  7:29 Scheduling of VCPUs and allocation of Guest Physical Memory Sukanto Ghosh
2008-06-05 12:54 ` Anthony Liguori
2008-06-06 14:22   ` Sukanto Ghosh
2008-06-06 14:40     ` Anthony Liguori
2008-06-09 11:10       ` Sukanto Ghosh
2008-06-09 16:19         ` Avi Kivity
2008-06-16 14:23           ` Sukanto Ghosh [this message]
2008-06-18 14:12             ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4856775E.4050601@cse.iitb.ac.in \
    --to=sukanto@cse.iitb.ac.in \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox