From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for June 8
Date: Tue, 08 Jun 2010 09:53:13 +0200 [thread overview]
Message-ID: <m3iq5uyn86.fsf@trasno.mitica> (raw)
In-Reply-To: <4C0D75AF.7050502@codemonkey.ws> (Anthony Liguori's message of "Mon, 07 Jun 2010 17:41:51 -0500")
Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 06/07/2010 05:26 PM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>>
>> If we have a lack of agenda items I'll cancel the week's call.
>>
>>
>
> - Accelerating counters (aka moving PIT to userspace, keeping HPET in
> userspace)
> - Live migration + hotplug
- migration events? any news about this or async migrate command?
- migration subsections. I have some initial code that I expect to push
before the call.
Later, Juan.
next prev parent reply other threads:[~2010-06-08 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 22:26 KVM call agenda for June 8 Chris Wright
2010-06-07 22:41 ` Anthony Liguori
2010-06-08 7:53 ` Juan Quintela [this message]
2010-06-08 8:50 ` Avi Kivity
2010-06-08 10:07 ` 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=m3iq5uyn86.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.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