From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Glauber de Oliveira Costa <gcosta@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] split memory allocation
Date: Mon, 15 Sep 2008 11:00:29 -0500 [thread overview]
Message-ID: <48CE869D.4050003@codemonkey.ws> (raw)
In-Reply-To: <1221493762-6447-1-git-send-email-glommer@redhat.com>
Glauber Costa wrote:
> Right now, kvm keeps the memory allocation split, so we can
> handle different areas in different ways. This schema works with qemu
> too, so it appears to be the common ground.
>
> This patch proposes using this common ground for everyone, by spliting
> raw qemu.
>
Applied. Thanks.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-09-15 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 15:49 [Qemu-devel] [PATCH] split memory allocation Glauber Costa
2008-09-15 16:00 ` Anthony Liguori [this message]
2008-09-15 16:11 ` Glauber Costa
-- strict thread matches above, loose matches on Subject: below --
2008-09-12 13:18 Glauber Costa
2008-09-11 13:42 Glauber Costa
2008-09-11 14:18 ` Aurelien Jarno
2008-09-11 14:35 ` Anthony Liguori
2008-09-11 14:42 ` Glauber Costa
2008-09-11 15:28 ` Avi Kivity
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=48CE869D.4050003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gcosta@redhat.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 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).