From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=48051 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PSv4x-0007dS-GW for qemu-devel@nongnu.org; Wed, 15 Dec 2010 12:23:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PSv4w-0005Id-8d for qemu-devel@nongnu.org; Wed, 15 Dec 2010 12:23:51 -0500 Received: from mail.codesourcery.com ([38.113.113.100]:37530) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PSv4v-0005I7-TN for qemu-devel@nongnu.org; Wed, 15 Dec 2010 12:23:50 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH v4 1/2] Minimal RAM API support Date: Wed, 15 Dec 2010 17:23:22 +0000 References: <20101213212059.2472.17879.stgit@s20.home> <20101213212430.2472.23807.stgit@s20.home> In-Reply-To: <20101213212430.2472.23807.stgit@s20.home> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201012151723.32164.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: blauwirbel@gmail.com, Alex Williamson , kvm@vger.kernel.org > This adds a minimum chunk of Anthony's RAM API support so that we > can identify actual VM RAM versus all the other things that make > use of qemu_ram_alloc. Why do we care? How are you defining "actual VM RAM"? Surely the whole point of qemu_ram_alloc is to allocate a chunk of memory that can be mapped into the guest physical address space, so all uses of qemu_ram_alloc should be using this API. Paul