kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call for agenda for 2013-10-01
Date: Tue, 24 Sep 2013 16:09:56 +0200	[thread overview]
Message-ID: <87vc1qqpjf.fsf@elfo.elfo> (raw)


Hi

Please, send any topic that you are interested in covering.

Last week I forgot to send the call for topics.  We still have a topic there.

Thanks, Juan.

Agenda so far:
- Talk about qemu reverse executing (1st description was done this week)
  How to handle IO when we want to do reverse execution.
  How this relate to Kemari needs?
  And to icount changes?

Call details:

10:00 AM to 11:00 AM EDT
Every two weeks

If you need phone number details,  contact me privately.

             reply	other threads:[~2013-09-24 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 14:09 Juan Quintela [this message]
2013-09-27  9:57 ` KVM call for agenda for 2013-10-01 Frederic Konrad
2013-09-30  5:17 ` Michael S. Tsirkin
2013-09-30  8:53 ` Orit Wasserman
2013-10-01  7:20   ` Frederic Konrad

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=87vc1qqpjf.fsf@elfo.elfo \
    --to=quintela@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;
as well as URLs for NNTP newsgroup(s).