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 Sept 21
Date: Sun, 26 Sep 2010 16:50:34 +0200 [thread overview]
Message-ID: <4C9F5DBA.3030208@redhat.com> (raw)
In-Reply-To: <20100926142817.GA14396@fermat.math.technion.ac.il>
On 09/26/2010 04:28 PM, Nadav Har'El wrote:
> > I'm worried about maintaining core vmx after nvmx is merged, not nvmx
> > itself. There are simply many more things to consider when making a change.
>
> Right, but how can we avoid this issue, assuming that you do want nvmx in?
We can't avoid it. We can mitigate it to some extent by structuring the
code correctly.
> May I ask how this effected nested SVM?
>
I kept breaking nsvm when making changes to core svm, and Joerg kept
fixing them.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-09-26 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 18:05 KVM call minutes for Sept 21 Chris Wright
2010-09-21 18:05 ` [Qemu-devel] " Chris Wright
2010-09-21 18:23 ` Anthony Liguori
2010-09-21 18:23 ` [Qemu-devel] " Anthony Liguori
2010-09-22 0:04 ` Nadav Har'El
2010-09-22 1:48 ` Chris Wright
2010-09-22 17:49 ` Nadav Har'El
2010-09-22 18:03 ` Anthony Liguori
2010-09-22 19:34 ` Joerg Roedel
2010-09-22 19:48 ` Joerg Roedel
2010-09-22 9:02 ` Gleb Natapov
2010-09-22 16:29 ` Nadav Har'El
2010-09-22 17:47 ` Gleb Natapov
2010-09-22 19:20 ` Joerg Roedel
2010-09-22 20:18 ` Gleb Natapov
2010-09-22 23:00 ` Nadav Har'El
2010-09-26 14:03 ` Avi Kivity
2010-09-26 20:25 ` Joerg Roedel
2010-09-27 8:36 ` Avi Kivity
2010-09-27 14:18 ` Gleb Natapov
2010-09-27 14:22 ` Avi Kivity
2010-09-26 13:27 ` Avi Kivity
2010-09-26 14:28 ` Nadav Har'El
2010-09-26 14:50 ` 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=4C9F5DBA.3030208@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.