From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/2] Minimal RAM API support
Date: Wed, 15 Dec 2010 12:11:35 -0700
Message-ID: <1292440295.2862.50.camel@x201>
References: <20101213212059.2472.17879.stgit@s20.home>
	 <20101213212430.2472.23807.stgit@s20.home>
	 <201012151723.32164.paul@codesourcery.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws, blauwirbel@gmail.com,
	kvm@vger.kernel.org
To: Paul Brook <paul@codesourcery.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:14460 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754849Ab0LOTLv (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 15 Dec 2010 14:11:51 -0500
In-Reply-To: <201012151723.32164.paul@codesourcery.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, 2010-12-15 at 17:23 +0000, Paul Brook wrote:
> > 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.

http://wiki.qemu.org/Features/RamAPI