From: Avi Kivity <avi@redhat.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: nyh@math.technion.ac.il, Gleb Natapov <gleb@redhat.com>,
Andy Whitcroft <apw@canonical.com>,
kvm@vger.kernel.org
Subject: Re: Nested kvm_intel broken on pre 3.3 hosts
Date: Thu, 09 Aug 2012 12:34:15 +0300 [thread overview]
Message-ID: <50238417.6080300@redhat.com> (raw)
In-Reply-To: <50236329.2040509@canonical.com>
On 08/09/2012 10:13 AM, Stefan Bader wrote:
> Avi, was the last version of the patch (only adding the flag to the nested MSRs)
> good for submitting to stable from your point of view?
>
Yes, it is correct. I forwarded it to stable, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-08-09 9:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 11:29 Nested kvm_intel broken on pre 3.3 hosts Stefan Bader
2012-08-01 13:39 ` Gleb Natapov
2012-08-01 14:08 ` Avi Kivity
2012-08-01 14:26 ` Stefan Bader
2012-08-01 14:29 ` Avi Kivity
2012-08-01 15:07 ` Nadav Har'El
2012-08-01 15:10 ` Gleb Natapov
2012-08-01 15:11 ` Avi Kivity
2012-08-02 15:19 ` Stefan Bader
2012-08-02 15:19 ` [PATCH 1/7] KVM: Move cpuid code to new file Stefan Bader
2012-08-02 15:19 ` [PATCH 2/7] KVM: expose latest Intel cpu new features (BMI1/BMI2/FMA/AVX2) to guest Stefan Bader
2012-08-02 15:19 ` [PATCH 3/7] KVM: Expose kvm_lapic_local_deliver() Stefan Bader
2012-08-02 15:19 ` [PATCH 4/7] KVM: Expose a version 2 architectural PMU to a guests Stefan Bader
2012-08-02 15:19 ` [PATCH 5/7] KVM: Add generic RDPMC support Stefan Bader
2012-08-02 15:19 ` [PATCH 6/7] KVM: SVM: Intercept RDPMC Stefan Bader
2012-08-02 15:19 ` [PATCH 7/7] KVM: VMX: " Stefan Bader
2012-08-02 15:26 ` Nested kvm_intel broken on pre 3.3 hosts Avi Kivity
2012-08-03 10:55 ` (unknown), Stefan Bader
2012-08-03 10:57 ` Nested kvm_intel broken on pre 3.3 hosts Stefan Bader
2012-08-05 9:18 ` Avi Kivity
2012-08-06 14:40 ` Stefan Bader
2012-08-09 7:13 ` Stefan Bader
2012-08-09 9:34 ` 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=50238417.6080300@redhat.com \
--to=avi@redhat.com \
--cc=apw@canonical.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nyh@math.technion.ac.il \
--cc=stefan.bader@canonical.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;
as well as URLs for NNTP newsgroup(s).