From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: tarski <tarski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: guest threads
Date: Thu, 22 Mar 2007 13:54:43 +0200 [thread overview]
Message-ID: <46026E83.2000204@qumranet.com> (raw)
In-Reply-To: <loom.20070322T113842-266-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
tarski wrote:
> hello everyone,
>
> I was just wondering how KVM schedules multiple Virtual machines (guest
> operating systems) running on top of it? If a thread/process blocks on a guest
> os does KVM block the whole virtual machine or are other threads/processes
> running on that particular guest given a chance to run?
>
>
kvm is not aware of threads and processes within guests.
kvm (actually, the Linux scheduler) will deschedule a guest if one of
these two conditions occur:
- if the guest executes the 'hlt' instruction (typically when it has no
processes to run)
- using normal Linux process preemption rules (timeslice expires, higher
priority thread becomes runnable, etc.)
so it's quite possible for multiple guest threads or processes to run
within a single host timeslice.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-22 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 10:48 guest threads tarski
[not found] ` <loom.20070322T113842-266-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-03-22 11:48 ` Dor Laor
2007-03-22 11:54 ` Avi Kivity [this message]
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=46026E83.2000204@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tarski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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