[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [PATCH RFC V4 10/14] Introduce qemu_ram_ptr_unlock.

From: Gerd Hoffmann
Subject: Re: [Qemu-devel] Re: [PATCH RFC V4 10/14] Introduce qemu_ram_ptr_unlock.
Date: Wed, 29 Sep 2010 09:38:02 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100827 Red Hat/3.1.3-1.el6 Thunderbird/3.1.3

On 09/28/10 17:14, Anthony Liguori wrote:
On 09/28/2010 10:01 AM, address@hidden wrote:
From: Anthony PERARD<address@hidden>

This function allows to unlock a ram_ptr give by qemu_get_ram_ptr. After
a call to qemu_ram_ptr_unlock, the pointer may be unmap from QEMU when
used with Xen.

Signed-off-by: Anthony PERARD<address@hidden>

Why isn't hooking cpu_physical_memory_{map,unmap}() not enough? That's
really the intention of the API.

I think quite a bunch of stuff stops working then because it doesn't properly use the map/unmap API ...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]