kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: kvm/queue still ahead of kvm/next
Date: Mon, 19 Aug 2013 11:26:08 +0200	[thread overview]
Message-ID: <5211E4B0.2020808@redhat.com> (raw)
In-Reply-To: <CAOaxAcYJhOH-x8davobK4N96OfUG0McK4REqt+LsxwM_3NWXtg@mail.gmail.com>

Il 19/08/2013 06:36, Kashyap Chamarthy ha scritto:
> On Sat, Aug 10, 2013 at 12:56 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> >
>> > Hi all,
>> >
>> > I'm seeing some breakage of shadow-on-shadow and shadow-on-EPT nested
>> > VMX.  Until I can track more precisely whether it is a regression, and
>> > on which hosts I can reproduce it, I'm going to leave the patches out of
>> > kvm/next.
>> >
>> > The good news is that nested EPT works pretty well. :)
> 
> Paolo/others, I'm trying to test nEPT, so I'm trying to start this way:
> 
>    $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git
>    $ git branch --all
>    $ git checkout remotes/origin/queue
> 
> Compile, and proceed.
> 
> Or would you suggest to use
> 
>   http://git.kiszka.org/?p=kvm-kmod.git;a=blob;f=README
> 
> to test latest stuff?

If you prefer not to build your own kernel, kvm-kmod works too.
However, please build it with the latest 3.10.x kernel to make the
environment as similar as possible to what you'd get with kvm.git.

Paolo

  reply	other threads:[~2013-08-19  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 19:26 kvm/queue still ahead of kvm/next Paolo Bonzini
2013-08-19  4:36 ` Kashyap Chamarthy
2013-08-19  9:26   ` Paolo Bonzini [this message]
2013-08-19  9:42     ` Kashyap Chamarthy
2013-08-19  9:45       ` Kashyap Chamarthy
2013-08-20 16:06 ` Paolo Bonzini

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=5211E4B0.2020808@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kashyap.cv@gmail.com \
    --cc=kvm@vger.kernel.org \
    /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).