From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Serious issues with xenpaging Date: Fri, 7 Mar 2014 16:54:09 +0100 Message-ID: <20140307155409.GA10037@aepfle.de> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> <20140307154339.GA10945@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20140307154339.GA10945@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Fri, Mar 07, Konrad Rzeszutek Wilk wrote: > In the context of http://wiki.xenproject.org/wiki/GSoc_2014#Lazy_restore_using_memory_paging > should that be removed then? As the dependency of it would be to first 'un-bitrot' it and that > might take more than the original GSoC problem statement describes?? While its a good idea, it can HVM only at this point because PV doesnt do paging. So its real work to get this done. Olaf