From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [patch] kvm: make cr3 loading more robust Date: Thu, 4 Jan 2007 10:06:55 +0100 Message-ID: <20070104090655.GA20798@elte.hu> References: <20070103021057.GA11316@elte.hu> <459B695C.5090004@qumranet.com> <20070103115911.GA2786@elte.hu> <459B9C5C.9060008@qumranet.com> <20070103122114.GD2786@elte.hu> <459BA194.8070305@qumranet.com> <20070103123253.GA8822@elte.hu> <20070103133714.GA20638@elte.hu> <20070103134417.GA22055@elte.hu> <459CC1BC.3070308@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel Return-path: To: Avi Kivity Content-Disposition: inline In-Reply-To: <459CC1BC.3070308-atKUWr5tajBWk0Htik3J/w@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 * Avi Kivity wrote: > The guest needs to cooperate, but it can do so using the native memory > hotlpug mechanisms (whatever they are). [...] as far a Linux guest goes, there's no such thing at the moment, at least in the mainline kernel. Most of the difficulties with RAM-unplug is on the guest OS side - i agree with you that doing it on the host side is easy. (because the host side does not really 'use' any of the guest's "RAM".) Ingo ------------------------------------------------------------------------- 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