From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqhN0-0006hI-EU for qemu-devel@nongnu.org; Tue, 18 Nov 2014 06:55:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqhMt-00084Y-90 for qemu-devel@nongnu.org; Tue, 18 Nov 2014 06:54:54 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqhMt-00084T-24 for qemu-devel@nongnu.org; Tue, 18 Nov 2014 06:54:47 -0500 Date: Tue, 18 Nov 2014 13:54:41 +0200 From: "Michael S. Tsirkin" Message-ID: <20141118115441.GA21969@redhat.com> References: <1416254843-16859-1-git-send-email-mst@redhat.com> <1416254843-16859-5-git-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH 4/5] memory: interface to allocate device ram List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paolo Bonzini , Juan Quintela , QEMU Developers , "Dr. David Alan Gilbert" On Mon, Nov 17, 2014 at 08:21:00PM +0000, Peter Maydell wrote: > On 17 November 2014 20:08, Michael S. Tsirkin wrote: > > Add API to allocate on-device RAM. > > This looks just like regular RAM from migration POV, > > but has two special properties internally: > > - it is never exposed to guest > > If it's not exposed to the guest why is it a MemoryRegion? > Those are pretty much the definition of regions of memory > we expose to the guest (via one address space or another)... > > -- PMM Mostly for migration: we are using page migration machinery to migrate this memory early rather than as part of device state after VM is stopped. -- MST