From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Tomasz Chmielewski <mangoo-Nem3ZqsbT/g@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM paravirtualization on non-VMX/SVM CPUs?
Date: Mon, 19 Mar 2007 18:50:34 +0200 [thread overview]
Message-ID: <45FEBF5A.3070004@qumranet.com> (raw)
In-Reply-To: <45FEBC41.6060802-Nem3ZqsbT/g@public.gmane.org>
Tomasz Chmielewski wrote:
> In January, Ingo Molnar announced "KVM paravirtualization for Linux"[1].
>
> The announcement mentions "support for the hardware cr3-cache feature of
> Intel-VMX CPUs" and "i only tested this on 32-bit VMX".
>
> Because of this, I'm not sure how to understand it:
>
> 1) KVM paravirtualization means that it will be possible to use KVM on
> non-VMX/SVM CPUs (much like Xen)?
>
No. That is possible (and kqemu demonstrates it can be done), but it is
not implemented and to my knowledge no one is working on it.
> 2) KVM paravirtualization means paravirtualized drivers only (net, disk
> etc.), but it will still run only on VMX/SVM-capable CPUs?
>
>
>
Yes. In addition, it enables platform-level optimization (like the cr3
cache).
--
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-19 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 16:37 KVM paravirtualization on non-VMX/SVM CPUs? Tomasz Chmielewski
[not found] ` <45FEBC41.6060802-Nem3ZqsbT/g@public.gmane.org>
2007-03-19 16:42 ` Hugo Mills
2007-03-19 16:50 ` 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=45FEBF5A.3070004@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mangoo-Nem3ZqsbT/g@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.