From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch] kvm: make cr3 loading more robust Date: Wed, 03 Jan 2007 15:14:45 +0200 Message-ID: <459BAC45.9090202@qumranet.com> References: <20070103021057.GA11316@elte.hu> <459B695C.5090004@qumranet.com> <20070103115230.GB937@elte.hu> <459B9AC7.6020506@qumranet.com> <20070103121301.GC2786@elte.hu> <459BA0B4.20804@qumranet.com> <20070103122814.GA7350@elte.hu> <20070103124020.GA9738@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel Return-path: To: Ingo Molnar In-Reply-To: <20070103124020.GA9738-X9Un+BFzKDI@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 Ingo Molnar wrote: > * Ingo Molnar wrote: > > >>> The kvm goals do not include cycle accurate emulation. [...] >>> >> yes. That's why i'm suggesting to kill the VM in such a scenario. A >> cr3 value is only valid if it points to real RAM. >> > > and if it ever causes real incompatibility it should be easy to address > it by returning a per-vcpu (or per-vm) special memory slot in > gfn_to_memslot(), for invalid memory, instead of the current NULL, > right? > Yes. A read-only memory slot may have other uses too (for ROMs). -- 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