From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9 v3] KVM: Nested SVM fixes and tracepoint conversion
Date: Mon, 12 Oct 2009 11:26:02 +0200 [thread overview]
Message-ID: <4AD2F62A.5010704@redhat.com> (raw)
In-Reply-To: <1255097313-23267-1-git-send-email-joerg.roedel@amd.com>
On 10/09/2009 04:08 PM, Joerg Roedel wrote:
> Hi Avi, Marcelo,
>
> this series of patches contains bugfixes for the Nested SVM code and the
> conversion of Nested SVM debugging to tracepoints. The fixes are:
>
> 1) A patch Alex already sent (1/9) but which was not yet
> applied. It fixes a lost event_inj problem when we emulate a
> vmrun and a vmexit without entering the guest in the
> meantime.
>
> 2) The patch 2/9 fixes a schedule() while atomic bug in the
> Nested SVM code. The KVM interrupt injection code runs with
> preemtion and interrupts disabled. But the
> enable_irq_window() function from SVM may emulate a #vmexit.
> This emulation might sleep which causes the schedule() while
> atomic() bug.
>
> These fixes (patches 1 and 2) should also be considered for -stable
> backporting. The patches 3 to 8 convert the old printk based debugging
> for Nested SVM to tracepoints. Patch 9 removes the nsvm_printk code.
> Please review and/or consider to apply these changes.
>
Looks good to me.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-12 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 14:08 [PATCH 0/9 v3] KVM: Nested SVM fixes and tracepoint conversion Joerg Roedel
2009-10-09 14:08 ` [PATCH 1/9] KVM: SVM: Notify nested hypervisor of lost event injections Joerg Roedel
2009-10-09 14:08 ` [PATCH 2/9] KVM: SVM: Move INTR vmexit out of atomic code Joerg Roedel
2009-10-09 14:08 ` [PATCH 3/9] KVM: SVM: Add tracepoint for nested vmrun Joerg Roedel
2009-10-09 14:08 ` [PATCH 4/9] KVM: SVM: Add tracepoint for nested #vmexit Joerg Roedel
2009-10-09 14:08 ` [PATCH 5/9] KVM: SVM: Add tracepoint for injected #vmexit Joerg Roedel
2009-10-09 14:08 ` [PATCH 6/9] KVM: SVM: Add tracepoint for #vmexit because intr pending Joerg Roedel
2009-10-09 14:08 ` [PATCH 7/9] KVM: SVM: Add tracepoint for invlpga instruction Joerg Roedel
2009-10-09 14:08 ` [PATCH 8/9] KVM: SVM: Add tracepoint for skinit instruction Joerg Roedel
2009-10-09 14:08 ` [PATCH 9/9] KVM: SVM: Remove nsvm_printk debugging code Joerg Roedel
2009-10-12 9:26 ` Avi Kivity [this message]
2009-10-12 18:37 ` [PATCH 0/9 v3] KVM: Nested SVM fixes and tracepoint conversion 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=4AD2F62A.5010704@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox