From: Alex Williamson <alex.williamson@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws,
blauwirbel@gmail.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v4 1/2] Minimal RAM API support
Date: Wed, 15 Dec 2010 12:11:35 -0700 [thread overview]
Message-ID: <1292440295.2862.50.camel@x201> (raw)
In-Reply-To: <201012151723.32164.paul@codesourcery.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v4 1/2] Minimal RAM API support
Date: Wed, 15 Dec 2010 12:11:35 -0700 [thread overview]
Message-ID: <1292440295.2862.50.camel@x201> (raw)
In-Reply-To: <201012151723.32164.paul@codesourcery.com>
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
next prev parent reply other threads:[~2010-12-15 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 21:24 [PATCH v4 0/2] Minimal RAM API support Alex Williamson
2010-12-13 21:24 ` [Qemu-devel] " Alex Williamson
2010-12-13 21:24 ` [PATCH v4 1/2] " Alex Williamson
2010-12-13 21:24 ` [Qemu-devel] " Alex Williamson
2010-12-15 17:23 ` Paul Brook
2010-12-15 17:23 ` Paul Brook
2010-12-15 19:11 ` Alex Williamson [this message]
2010-12-15 19:11 ` Alex Williamson
2010-12-15 19:34 ` Anthony Liguori
2010-12-15 19:34 ` Anthony Liguori
2010-12-13 21:24 ` [PATCH v4 2/2] RAM API: Make use of it for x86 PC Alex Williamson
2010-12-13 21:24 ` [Qemu-devel] " Alex Williamson
2010-12-14 9:18 ` Avi Kivity
2010-12-14 9:18 ` [Qemu-devel] " Avi Kivity
2010-12-14 15:16 ` Alex Williamson
2010-12-14 15:16 ` [Qemu-devel] " Alex Williamson
2010-12-14 15:18 ` Anthony Liguori
2010-12-14 15:18 ` [Qemu-devel] " Anthony Liguori
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=1292440295.2862.50.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.