From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Scott Wood <scottwood@freescale.com>,
Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] kvm: ppc: booke206: use MMU API
Date: Mon, 20 Jun 2011 11:03:46 +0300 [thread overview]
Message-ID: <4DFEFEE2.3000806@redhat.com> (raw)
In-Reply-To: <4DFEF992.7010601@siemens.com>
On 06/20/2011 10:41 AM, Jan Kiszka wrote:
>
> > Those hopefully shouldn't be required anymore soon - when Jan's patches make it upstream. Jan, how's progress on that front?
>
> I can only forward this question: Avi, what are the plans for
> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/73917?
Will apply once all comments are addressed.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-20 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 20:38 [Qemu-devel] [PATCH 0/3] ppc: booke206: KVM MMU API and info tlb Scott Wood
2011-06-17 20:39 ` [Qemu-devel] [PATCH 1/3] kvm: ppc: booke206: use MMU API Scott Wood
2011-06-17 23:28 ` Alexander Graf
2011-06-18 16:13 ` Richard Henderson
2011-06-18 16:44 ` Alexander Graf
2011-06-20 7:41 ` Jan Kiszka
2011-06-20 8:03 ` Avi Kivity [this message]
2011-06-20 8:47 ` Jan Kiszka
2011-06-20 9:02 ` Avi Kivity
2011-06-17 20:39 ` [Qemu-devel] [PATCH 2/3] ppc: booke206: use MAV=2.0 TSIZE definition, fix 4G pages Scott Wood
2011-06-17 20:39 ` [Qemu-devel] [PATCH 3/3] ppc: booke206: add "info tlb" support Scott Wood
2011-06-17 23:39 ` Alexander Graf
2011-07-06 16:38 ` [Qemu-devel] [PATCH 0/3] ppc: booke206: KVM MMU API and info tlb Alexander Graf
2011-07-06 16:45 ` Scott Wood
2011-07-06 23:16 ` Scott Wood
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=4DFEFEE2.3000806@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=scottwood@freescale.com \
/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).