From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM paravirtualization on non-VMX/SVM CPUs? Date: Mon, 19 Mar 2007 18:50:34 +0200 Message-ID: <45FEBF5A.3070004@qumranet.com> References: <45FEBC41.6060802@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Tomasz Chmielewski Return-path: In-Reply-To: <45FEBC41.6060802-Nem3ZqsbT/g@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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