From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vitaly Kuznetsov Subject: Re: [PATCH v5 4/9] xen: introduce XEN_DOMCTL_devour Date: Tue, 13 Jan 2015 17:17:22 +0100 Message-ID: <87oaq2d59p.fsf@vitty.brq.redhat.com> References: <1418305541-5135-1-git-send-email-vkuznets@redhat.com> <1418305541-5135-5-git-send-email-vkuznets@redhat.com> <1421157237.19103.61.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YB4A6-00016M-Nm for xen-devel@lists.xenproject.org; Tue, 13 Jan 2015 16:17:46 +0000 In-Reply-To: <1421157237.19103.61.camel@citrix.com> (Ian Campbell's message of "Tue, 13 Jan 2015 13:53:57 +0000") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Jan Beulich Cc: Wei Liu , Andrew Jones , Julien Grall , Keir Fraser , Stefano Stabellini , Ian Jackson , Tim Deegan , Olaf Hering , David Vrabel , Andrew Cooper , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org Ian Campbell writes: > On Thu, 2014-12-11 at 14:45 +0100, Vitaly Kuznetsov wrote: >> + gmfn = mfn_to_gmfn(d, mfn); > > (I haven't thought about it super hard, but I'm taking it as given that > this approach to kexec is going to be needed for ARM too, since that > seems likely) > > mfn_to_gmfn is going to be a bit pricey on ARM, we don't have an m2p to > refer to, I'm not sure what we would do instead, walking the p2m looking > for mfns surely won't be a good idea! Can we form a 'temporary m2p' table by walking p2m once? Our domain is dying and mappings don't change. > > An alternative approach to this might be to walk the guest p2m (with > appropriate continuations) and move each domheap page (this would also > help us preserve super page mappings). It would also have the advantage > of not needing additional stages in the destroy path and state in struct > domain etc, since all the action would be constrained to the one > hypercall. Something like that (but not exactly) was in my RFC/WIPv2 series: http://lists.xen.org/archives/html/xen-devel/2014-09/msg03624.html The drawback of such approach is the necessity of copying all mapped more than once pages (granted pages, qemu-mapped pages, ...) or at least providing blank pages instead of them. Jan, may I also explicitly ask your opinion? -- Vitaly