From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sh8E0-0004F5-TE for qemu-devel@nongnu.org; Tue, 19 Jun 2012 19:52:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sh8Dz-00071O-6s for qemu-devel@nongnu.org; Tue, 19 Jun 2012 19:52:44 -0400 Received: from gate.crashing.org ([63.228.1.57]:59920) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sh8Dy-00071D-Tx for qemu-devel@nongnu.org; Tue, 19 Jun 2012 19:52:43 -0400 Message-ID: <1340149958.28143.53.camel@pasglop> From: Benjamin Herrenschmidt Date: Wed, 20 Jun 2012 09:52:38 +1000 In-Reply-To: <894DCBE1-CD2E-46DC-91FA-FD127C326004@suse.de> References: <1339239192.24838.84.camel@pasglop> <1339241642.24838.92.camel@pasglop> <5DD2FF44-F27E-49C4-AF2C-2EF95341DF6E@suse.de> <87lijjjqk5.fsf@elfo.mitica> <1340137841.28143.34.camel@pasglop> <874nq6kj3m.fsf@elfo.mitica> <1340146833.28143.50.camel@pasglop> <87y5nij3r6.fsf@elfo.mitica> <1340148512.28143.52.camel@pasglop> <894DCBE1-CD2E-46DC-91FA-FD127C326004@suse.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] vm state save/restore question List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "qemu-devel@nongnu.org Developers" , quintela@redhat.com On Wed, 2012-06-20 at 01:30 +0200, Alexander Graf wrote: > > We support the paravirtualized -M pseries in full emu as well, in which > > case the hashed page table is handled by qemu itself who implements the > > H_ENTER & co hypercalls. So it's very similar, except that qemu doesn't > > have to ask the kernel to get a snapshot :-) > > > > So I can flush out the storage format and two stage process inside qemu, > > and then bother with the kvm/kernel interface. > > > > Normal "bare metal" operation in qemu (or even KVM "PR") doesn't require > > this as in that case the hash table is just a normal part of the guest > > memory, it's only an issue when doing paravirtualized guest such as > > pseries (aka PAPR). > > IIRC we still allocate it outside of normal guest memory, so you don't get the migration for free :). You haven't ready my post properly :-) Cheers, Ben.