qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
	qemu-devel@nongnu.org, Stefano.Stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] Re: [PATCH RFC V4 10/14] Introduce qemu_ram_ptr_unlock.
Date: Wed, 29 Sep 2010 09:38:02 +0200	[thread overview]
Message-ID: <4CA2ECDA.5080309@redhat.com> (raw)
In-Reply-To: <4CA2064A.7020701@codemonkey.ws>

On 09/28/10 17:14, Anthony Liguori wrote:
> On 09/28/2010 10:01 AM, anthony.perard@citrix.com wrote:
>> From: Anthony PERARD<anthony.perard@citrix.com>
>>
>> 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<anthony.perard@citrix.com>
>
> 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 ...

cheers,
   Gerd

  parent reply	other threads:[~2010-09-29  7:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 15:01 [Qemu-devel] [PATCH RFC V4 00/14] xen device model support anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 01/14] xen: Replace some tab-indents with spaces (clean-up) anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 02/14] xen: Support new libxc calls from xen unstable anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 03/14] xen: Add xen_machine_fv anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 04/14] Introduce -accel command option anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 05/14] xen: Add xen in -accel option anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 06/14] xen: Add the Xen platform pci device anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 07/14] piix_pci: Introduces Xen specific call for irq anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 08/14] xen: add a 8259 Interrupt Controller anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 09/14] xen: Introduce the Xen mapcache anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 10/14] Introduce qemu_ram_ptr_unlock anthony.perard
2010-09-28 15:14   ` [Qemu-devel] " Anthony Liguori
2010-09-28 15:25     ` Stefano Stabellini
2010-09-28 16:01       ` Anthony Liguori
2010-09-28 18:04         ` Stefano Stabellini
2010-09-29  7:38     ` Gerd Hoffmann [this message]
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 11/14] vl.c: Introduce getter for shutdown_requested and reset_requested anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 12/14] xen: Initialize event channels and io rings anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 13/14] xen: Set running state in xenstore anthony.perard
2010-09-28 15:01 ` [Qemu-devel] [PATCH RFC V4 14/14] xen: Add a Xen specific ACPI Implementation to target-xen anthony.perard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA2ECDA.5080309@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).