From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
balbir@linux.vnet.ibm.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, Dave Hansen <haveblue@linux.vnet.ibm.com>
Subject: Re: KVM call agenda for June 15
Date: Tue, 15 Jun 2010 15:33:19 +0200 [thread overview]
Message-ID: <m3iq5k774w.fsf@trasno.mitica> (raw)
In-Reply-To: <4C17799B.20105@codemonkey.ws> (Anthony Liguori's message of "Tue, 15 Jun 2010 08:01:15 -0500")
Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 06/15/2010 12:48 AM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>>
>
> - Page cache controls (Balbir/Dave)
- Migration Subsections
Just sent a possible implementation code to the list (too late for a big
examination, but I would like to know if anybody has any comments about
it).
Later, Juan.
next prev parent reply other threads:[~2010-06-15 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 5:48 KVM call agenda for June 15 Chris Wright
2010-06-15 13:01 ` Anthony Liguori
2010-06-15 13:33 ` Juan Quintela [this message]
2010-06-15 14:18 ` 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=m3iq5k774w.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=balbir@linux.vnet.ibm.com \
--cc=chrisw@redhat.com \
--cc=haveblue@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--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