public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/8] Nested SVM unit tests
Date: Wed, 28 Jul 2010 14:53:59 +0300	[thread overview]
Message-ID: <4C501A57.4010808@redhat.com> (raw)
In-Reply-To: <20100728114029.GF26098@amd.com>

  On 07/28/2010 02:40 PM, Roedel, Joerg wrote:
> On Wed, Jul 28, 2010 at 06:18:19AM -0400, Avi Kivity wrote:
>> The following patchset adds a framework for nested SVM unit testing.  As
>> you may guess, future fixes and enhancements to nested SVM will require
>> matching tests.
> Cool stuff. I guess the third test failed (vmrun intercept check),
> should be easy to fix. This is generally a very useful thing.
>

Yes.

>> Currently, our nested SVM implementation has a 66.67% success rate using
>> these tests.
> Okay, thats the downside :-) Anyway, are KVM changes not realated to
> nested-svm required to pass these tests too?

Yes.  These tests are run as part of autotest (well, I forgot to update 
kvm/test/x86/unittests.cfg).  If something wants to be in 'master', it 
needs to pass these tests.  So it will be a good idea to add tests for 
things that are liable to break as part of normal code churn, e.g. event 
injection.

> How about fixes for race conditions? We had bugs in the past with lost
> interrupts in the L2 guest which only showed up under very special
> conditions that may be hard to reproduce directly. They may depend on an
> L1 interrupt becoming pending for example.
> (And I think we still have one bug in this area left which is not yet
>   root-caused)

The test framework supports smp, so you can have the second vcpu do 
nasty stuff.  The difficult part is when the failure depends on host 
state that is not visible to the guest.  Perhaps we can add test-only 
hypercalls that allow the guest to manipulate this state (drop shadows, 
etc.)

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2010-07-28 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 10:18 [PATCH 0/8] Nested SVM unit tests Avi Kivity
2010-07-28 10:18 ` [PATCH 1/8] test: move ARRAY_SIZE() to libcflat.h Avi Kivity
2010-07-28 10:18 ` [PATCH 2/8] test: move memset() to libcflat Avi Kivity
2010-07-28 10:18 ` [PATCH 3/8] test: add type bool Avi Kivity
2010-07-28 10:18 ` [PATCH 4/8] test: add processor register access functions Avi Kivity
2010-07-28 10:18 ` [PATCH 5/8] test: make use of new processor.h header Avi Kivity
2010-07-28 10:18 ` [PATCH 6/8] test: add svm definitions header Avi Kivity
2010-07-28 10:18 ` [PATCH 7/8] test: add msr " Avi Kivity
2010-07-28 10:18 ` [PATCH 8/8] test: add svm tests Avi Kivity
2010-07-28 11:40 ` [PATCH 0/8] Nested SVM unit tests Roedel, Joerg
2010-07-28 11:53   ` Avi Kivity [this message]
2010-07-28 12:39     ` Roedel, Joerg
2010-07-28 12:46       ` Avi Kivity
2010-07-29 16:55 ` Marcelo Tosatti

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=4C501A57.4010808@redhat.com \
    --to=avi@redhat.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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