From: Avi Kivity <avi@redhat.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Chris Wright <chrisw@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Nadav Har'El" <nyh@math.technion.ac.il>,
"Dong, Eddie" <eddie.dong@intel.com>,
Sheng Yang <sheng@linux.intel.com>
Subject: Re: KVM call agenda for Sept 21
Date: Tue, 21 Sep 2010 13:48:35 +0200 [thread overview]
Message-ID: <4C989B93.5060201@redhat.com> (raw)
In-Reply-To: <54B2EB610B7F1340BB6A0D4CA04A4F10B3B6BEAC@orsmsx505.amr.corp.intel.com>
On 09/21/2010 05:37 AM, Nakajima, Jun wrote:
> Avi Kivity wrote on Mon, 20 Sep 2010 at 09:50:55:
>
> > On 09/20/2010 06:44 PM, Chris Wright wrote:
> >> Please send in any agenda items you are interested in covering.
> >>
> > nested vmx: the resurrection. Nice to see it progressing again, but
> > there's still a lot of ground to cover. Perhaps we can involve Intel to
> > speed things up?
> >
> Hi, Avi
>
> What are you looking for?
>
>
Help in getting the patchset in. Reviewing is always appreciated (while
it tends to increase the time, the result is usually better). If we can
find a way to share the work, even better.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2010-09-21 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 16:44 KVM call agenda for Sept 21 Chris Wright
2010-09-20 16:50 ` Avi Kivity
2010-09-20 19:15 ` Michael S. Tsirkin
2010-09-20 19:30 ` Anthony Liguori
2010-09-21 3:37 ` Nakajima, Jun
2010-09-21 11:48 ` Avi Kivity [this message]
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=4C989B93.5060201@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nyh@math.technion.ac.il \
--cc=qemu-devel@nongnu.org \
--cc=sheng@linux.intel.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