From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Omar Khan <okhan-e94Sedi4moU@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: paravirtualization structure
Date: Mon, 19 Feb 2007 17:24:23 +0200 [thread overview]
Message-ID: <45D9C127.9050201@qumranet.com> (raw)
In-Reply-To: <loom.20070219T155153-393-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
Omar Khan wrote:
> hi,
>
> I have a couple of kvm/kernel newbie questions:
>
> 1. What is the sequence of events for a paravirtualization hypercall? I
> understand how VMX architecture works, but how does the paravirt fit in? When we
> make a paravirt sys call we avoid a VMexit, but which address space does the
> call go to?
>
The hypercall sequence does not avoid a vmexit. The guest issues a
vmcall instruction, which is trapped and processed by the host.
> 2. Is the paravirtualization code included in the 2.6.20 kernel (if so where
> is it) or do we still need to apply the patch for it?
>
>
>
The paravirt code is not present in 2.6.20. You can download it using
the instructions in http://kvm.qumranet.com/kvmwiki/Code.
--
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
next prev parent reply other threads:[~2007-02-19 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 15:17 paravirtualization structure Omar Khan
[not found] ` <loom.20070219T155153-393-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-19 15:24 ` Avi Kivity [this message]
2007-02-19 20:29 ` Omar Khan
[not found] ` <loom.20070219T211655-267-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-19 21:18 ` Dor Laor
2007-02-20 0:47 ` Omar Khan
[not found] ` <loom.20070220T011441-39-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-20 7:14 ` Avi Kivity
2007-02-20 8:18 ` Arjan van de Ven
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=45D9C127.9050201@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=okhan-e94Sedi4moU@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