From: Joerg Roedel <joerg.roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 0/5] Another set of Nested SVM fixes and cleanups
Date: Wed, 16 Sep 2009 16:18:58 +0200 [thread overview]
Message-ID: <20090916141858.GH8480@amd.com> (raw)
In-Reply-To: <4AB0F013.8050608@redhat.com>
On Wed, Sep 16, 2009 at 05:02:59PM +0300, Avi Kivity wrote:
> On 09/16/2009 04:24 PM, Joerg Roedel wrote:
> >Hi,
> >
> >this series of patches contain another set of cleanups and an important fix to
> >the Nested SVM code. These patches make the TSC handling code for SVM aware of
> >a nested guest. This fixes the TSC running backwards on guest and nested guest.
> >The backwards running TSC resulted in stalled guests when kvm-clock was
> >enabled. Please consider to apply.
> >
>
> Looks good. 3, 4 needed for 2.6.32-rc as well, yes?
Yes, would be good since these two are real bugfixes. Probably also
relevant for -stable.
Joerg
next prev parent reply other threads:[~2009-09-16 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 13:24 [PATCH 0/5] Another set of Nested SVM fixes and cleanups Joerg Roedel
2009-09-16 13:24 ` [PATCH 1/5] KVM: SVM: reorganize svm_interrupt_allowed Joerg Roedel
2009-09-16 13:24 ` [PATCH 2/5] KVM: SVM: don't copy exit_int_info on nested vmrun Joerg Roedel
2009-09-16 13:24 ` [PATCH 3/5] KVM: SVM: Fix tsc offset adjustment when running nested Joerg Roedel
2009-09-16 13:24 ` [PATCH 4/5] KVM: SVM: Handle tsc in svm_get_msr/svm_set_msr correctly Joerg Roedel
2009-09-16 13:24 ` [PATCH 5/5] KVM: SVM: Remove remaining occurences of rdtscll Joerg Roedel
2009-09-16 14:02 ` [PATCH 0/5] Another set of Nested SVM fixes and cleanups Avi Kivity
2009-09-16 14:18 ` Joerg Roedel [this message]
2009-09-18 6:53 ` 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=20090916141858.GH8480@amd.com \
--to=joerg.roedel@amd.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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).