public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Nadav Har'El" <nyh@math.technion.ac.il>
Cc: Chris Wright <chrisw@redhat.com>, kvm@vger.kernel.org
Subject: Re: KVM call minutes for Nov 30
Date: Wed, 01 Dec 2010 12:28:59 +0200	[thread overview]
Message-ID: <4CF6236B.4080308@redhat.com> (raw)
In-Reply-To: <20101201092730.GB29486@fermat.math.technion.ac.il>

On 12/01/2010 11:27 AM, Nadav Har'El wrote:
> I really want to get nested VMX into KVM, and I'm already doing whatever I
> can to make this a reality. But unfortunately, I am not yet a seasoned KVM or
> VMX expert (I'm trying to become one...), and it wasn't I who wrote the
> original nested VMX code, so every new issue and every new feature that I am
> asked to fix is new to me, and takes me considerable time to learn, debug,
> and fix.
>
> I hope to continue working on nested VMX, next year as well, but IBM's (my
> employer's) plans for next year are not yet set in stone. In any case, I
> firmly believe that the nested VMX feature will be better, and be available
> more quickly, if I am not the only person working on it. I will be very happy
> if somebody reading this wants to work on this with me. This is the main
> reason why I wanted to put nested VMX in the main tree (even before it is
> 100% bug-free and feature-complete), because that would make it much easier
> for more people to try this feature, and hopefully to help me fix problems
> which bother them.

I am reluctant to lower the bar on entry.  Things like SMP and host EPT 
support are really basic IMO.  Good integration into KVM is also important.

If you would like to get more people participating, I suggest publishing 
a git tree.  People can then post patches against the tree, which you 
can merge into the relevant commits.  It would also get more testing 
done by interested parties.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-12-01 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 15:53 KVM call minutes for Nov 30 Chris Wright
2010-11-30 15:59 ` Anthony Liguori
2010-12-01  9:27 ` Nadav Har'El
2010-12-01 10:28   ` Avi Kivity [this message]
2010-12-06 19:39   ` Nadav Har'El
2010-12-07  8:34     ` Avi Kivity
2010-12-07 12:49       ` Nadav Har'El
2010-12-07 13:10         ` Avi Kivity

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=4CF6236B.4080308@redhat.com \
    --to=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nyh@math.technion.ac.il \
    /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