From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm-devel <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM updates for Linux 3.0-rc3
Date: Sun, 19 Jun 2011 21:21:53 +0300 [thread overview]
Message-ID: <4DFE3E41.4040602@redhat.com> (raw)
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.0
to receive several (fairly serious) KVM fixes: kvmclock was broken due
to bad asm constraints, live migration & vga tracking instantiated large
ptes instead of small ones, and the guest cr3 was corrupted in some
scenarios.
Borislav Petkov (1):
KVM: MMU: Fix build warnings in walk_addr_generic()
Marcelo Tosatti (1):
KVM: VMX: do not overwrite uptodate vcpu->arch.cr3 on KVM_SET_SREGS
Steve (1):
KVM: MMU: fix opposite condition in mapping_level_dirty_bitmap
Zachary Amsden (1):
KVM: Fix register corruption in pvclock_scale_delta
arch/x86/include/asm/pvclock.h | 9 +++++++--
arch/x86/kvm/mmu.c | 2 +-
arch/x86/kvm/paging_tmpl.h | 2 +-
arch/x86/kvm/vmx.c | 3 ++-
4 files changed, 11 insertions(+), 5 deletions(-)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
reply other threads:[~2011-06-19 18:22 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=4DFE3E41.4040602@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