From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/2] Minimal RAM API support
Date: Wed, 15 Dec 2010 17:23:22 +0000
Message-ID: <201012151723.32164.paul@codesourcery.com>
References: <20101213212059.2472.17879.stgit@s20.home> <20101213212430.2472.23807.stgit@s20.home>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc: Alex Williamson <alex.williamson@redhat.com>,
	anthony@codemonkey.ws, blauwirbel@gmail.com, kvm@vger.kernel.org
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([38.113.113.100]:51880 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751246Ab0LORXr (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 15 Dec 2010 12:23:47 -0500
In-Reply-To: <20101213212430.2472.23807.stgit@s20.home>
Sender: kvm-owner@vger.kernel.org
List-ID: <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