From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: [GIT PULL] KVM updates fot 2.6.37-rc6
Date: Fri, 17 Dec 2010 17:17:53 +0200 [thread overview]
Message-ID: <4D0B7F21.3000103@redhat.com> (raw)
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.37
to get a few KVM fixes for 2.6.37-rc6. Two of the fixes are for forward
compatibility with Bulldozer processors, one is a live migration fix,
and one an ordinary preemption counter leak fix.
Andre Przywara (1):
KVM: enlarge number of possible CPUID leaves
Avi Kivity (1):
KVM: Fix preemption counter leak in kvm_timer_init()
Joerg Roedel (1):
KVM: SVM: Do not report xsave in supported cpuid
Sheng Yang (1):
KVM: Fix OSXSAVE after migration
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/svm.c | 4 ++++
arch/x86/kvm/vmx.c | 5 -----
arch/x86/kvm/x86.c | 11 +++++------
arch/x86/kvm/x86.h | 5 +++++
5 files changed, 15 insertions(+), 12 deletions(-)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
reply other threads:[~2010-12-17 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D0B7F21.3000103@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=torvalds@linux-foundation.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