From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:38863)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1R5a8R-0005B0-W9
	for qemu-devel@nongnu.org; Mon, 19 Sep 2011 05:27:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1R5a8Q-0001kE-V0
	for qemu-devel@nongnu.org; Mon, 19 Sep 2011 05:27:31 -0400
Received: from mail-pz0-f42.google.com ([209.85.210.42]:65268)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1R5a8Q-0001k4-QQ
	for qemu-devel@nongnu.org; Mon, 19 Sep 2011 05:27:30 -0400
Received: by pzk1 with SMTP id 1so10608026pzk.1
	for <qemu-devel@nongnu.org>; Mon, 19 Sep 2011 02:27:29 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4E70C343.1030605@redhat.com>
References: <4E70C343.1030605@redhat.com>
Date: Mon, 19 Sep 2011 10:27:29 +0100
Message-ID: <CAFEAcA8XeVO9_uwbGgHDA3sTkxWMjQG88mVRzP0ohLSoy9rd3w@mail.gmail.com>
From: Peter Maydell <peter.maydell@linaro.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Memory API code review
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, KVM list <kvm@vger.kernel.org>, Juan Quintela <quintela@redhat.com>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, Richard Henderson <rth@twiddle.net>

On 14 September 2011 16:07, 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 so=
me
> bugs or deficiency. =C2=A0I'd like to use the next kvm conference call sl=
ot 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, rat=
her
> than the usual "x86 is everything" crowd (+Jan) that usually participates=
 in
> the kvm weekly call.

I can dial in if that's useful -- are the dialin details available somewher=
e?

thanks
-- PMM