From: Juan Quintela <quintela@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
KVM list <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Memory API code review
Date: Thu, 15 Sep 2011 10:13:38 +0200 [thread overview]
Message-ID: <m3vcsu8bpp.fsf@neno.neno> (raw)
In-Reply-To: <4E70C343.1030605@redhat.com> (Avi Kivity's message of "Wed, 14 Sep 2011 18:07:47 +0300")
Avi Kivity <avi@redhat.com> wrote:
> I would like to carry out an online code review of the memory API so
> that more people are familiar with the internals, and perhaps even to
> catch some bugs or deficiency. I'd like to use the next kvm
> conference call slot for this (Tuesday 1400 UTC) since many people
> already have it reserved in the schedule.
>
> It would be great if people from the wider qemu community be present,
> rather than the usual "x86 is everything" crowd (+Jan) that usually
> participates in the kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?
I think so.
Later, Juan.
> We'll also need a way to disseminate a few slides and an editor
> session for showing the code. We have an elluminate account that can
> be used for this, but usually this has a 50% failure rate on Linux.
> Anthony, perhaps we can set up a view-only vnc reflector on qemu.org?
next prev parent reply other threads:[~2011-09-15 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 15:07 [Qemu-devel] Memory API code review Avi Kivity
2011-09-14 15:27 ` Anthony Liguori
2011-09-14 18:27 ` Chris Wright
2011-09-15 8:13 ` Juan Quintela [this message]
2011-09-19 9:27 ` Peter Maydell
2011-09-20 13:50 ` 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=m3vcsu8bpp.fsf@neno.neno \
--to=quintela@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).