All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] More fixes for nested svm
Date: Sun, 25 Apr 2010 11:39:33 +0300	[thread overview]
Message-ID: <4BD3FFC5.5030107@redhat.com> (raw)
In-Reply-To: <1271932394-13968-1-git-send-email-joerg.roedel@amd.com>

On 04/22/2010 01:33 PM, Joerg Roedel wrote:
> Hi Avi, Marcelo,
>
> here is another set of nested svm fixes. They fix NMI code to make UP Hyper-V
> root domain booting. The patches also add better handling for nested entry
> failures and mce intercepts.
> Also in this patchset are the fixes for the supported cpuid reporting for svm
> features. These patches were taken from the nested-npt patchset and slightly
> modified. These patches are also marked for -stable backporting.
> The probably most important fix is about exception reinjection. This didn't
> work reliably before and is fixed with the patch in this series now. This fix
> also touches common x86 code but that should be ok because it could be reused
> by nested-vmx later.
> Please review and give comments (or apply ;-).
>
>    

All applied, thanks.

Regarding stable, it should be easy to backport the patches to 
2.6.34-rc6, but for 2.6.33 and earlier, it's murky.  And we certainly 
don't have the means to test them.

So please prepare _tested_ patchsets (git is fine) for 2.6.3[432].  I 
suggest you hold off for 2.6.3[32] until their next release, since there 
are a lot of kvm patches in review for them.  In general patches should 
be prepared against kvm.git kvm-updates/2.6.foo; we'll keep them up to 
date against stable.

Longer term, we need kvm-autotest support for nsvm, and unit tests in 
qemu-kvm/kvm/user/test.

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


      parent reply	other threads:[~2010-04-25  8:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 10:33 [PATCH 0/8] More fixes for nested svm Joerg Roedel
2010-04-22 10:33 ` [PATCH 1/8] KVM: SVM: Fix nested nmi handling Joerg Roedel
2010-04-23 13:46   ` Alexander Graf
2010-04-23 14:13     ` Joerg Roedel
2010-04-23 14:19       ` Alexander Graf
2010-04-23 14:22         ` Joerg Roedel
2010-04-23 14:24           ` Alexander Graf
2010-04-23 14:31             ` Joerg Roedel
2010-04-23 14:42               ` Alexander Graf
2010-04-23 14:51                 ` Joerg Roedel
2010-04-23 19:18                   ` Alexander Graf
2010-04-22 10:33 ` [PATCH 2/8] KVM: SVM: Make sure rip is synced to vmcb before nested vmexit Joerg Roedel
2010-04-22 10:33 ` [PATCH 3/8] KVM: SVM: Sync cr0 and cr3 to kvm state before nested handling Joerg Roedel
2010-04-23 13:50   ` Alexander Graf
2010-04-23 14:17     ` Joerg Roedel
2010-04-23 14:20       ` Alexander Graf
2010-04-22 10:33 ` [PATCH 4/8] KVM: SVM: Propagate nested entry failure into guest hypervisor Joerg Roedel
2010-04-23 13:50   ` Alexander Graf
2010-04-22 10:33 ` [PATCH 5/8] KVM: X86: Add callback to let modules decide over some supported cpuid bits Joerg Roedel
2010-04-23 13:52   ` Alexander Graf
2010-04-23 13:59     ` Avi Kivity
2010-04-22 10:33 ` [PATCH 6/8] KVM: SVM: Report emulated SVM features to userspace Joerg Roedel
2010-04-23 13:55   ` Alexander Graf
2010-04-23 14:21     ` Joerg Roedel
2010-04-22 10:33 ` [PATCH 7/8] KVM: x86: Allow marking an exception as reinjected Joerg Roedel
2010-04-23 13:57   ` Alexander Graf
2010-04-23 14:27     ` Joerg Roedel
2010-04-23 14:41       ` Alexander Graf
2010-04-22 10:33 ` [PATCH 8/8] KVM: SVM: Handle MCE intercepts always on host level Joerg Roedel
2010-04-23 13:58   ` Alexander Graf
2010-04-23 14:28     ` Joerg Roedel
2010-04-22 11:04 ` [PATCH 0/8] More fixes for nested svm Avi Kivity
2010-04-23 13:47   ` Alexander Graf
2010-04-23 19:18   ` Alexander Graf
2010-04-23 13:43 ` Alexander Graf
2010-04-25  8:39 ` 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=4BD3FFC5.5030107@redhat.com \
    --to=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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 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.