From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34711)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1an02M-0005yg-6w
	for qemu-devel@nongnu.org; Mon, 04 Apr 2016 04:39:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1an02I-0005j6-AH
	for qemu-devel@nongnu.org; Mon, 04 Apr 2016 04:39:06 -0400
Received: from mx1.redhat.com ([209.132.183.28]:38963)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1an02I-0005j2-4W
	for qemu-devel@nongnu.org; Mon, 04 Apr 2016 04:39:02 -0400
Date: Mon, 4 Apr 2016 11:38:58 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20160404113838-mutt-send-email-mst@redhat.com>
References: <1458817415-29247-1-git-send-email-pbonzini@redhat.com>
	<1458817415-29247-3-git-send-email-pbonzini@redhat.com>
	<20160403164839-mutt-send-email-mst@redhat.com>
	<57021FC0.6050102@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57021FC0.6050102@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] memory: hide mr->ram_addr from
	qemu_get_ram_ptr users
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: arei.gonglei@huawei.com, famz@redhat.com, qemu-devel@nongnu.org

On Mon, Apr 04, 2016 at 10:03:12AM +0200, Paolo Bonzini wrote:
> 
> 
> On 03/04/2016 15:49, Michael S. Tsirkin wrote:
> > I agree but I think we need a better name for this function.
> > qemu_ram_offset_to_ptr?
> 
> What about qemu_map_ram_ptr?
> 
> Paolo

OK but this seems to imply there's also an unmap operation?

> > Will also serve to make sure backporting patches across this
> > API change does not cause issues.