From: Marcelo Tosatti <mtosatti@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: [GIT PULL] KVM fixes for 3.6-rc2
Date: Fri, 3 Aug 2012 15:15:24 -0300 [thread overview]
Message-ID: <20120803181524.GA19680@amt.cnet> (raw)
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
To receive the following KVM _bug fixes_:
- Fix DS/ES segment register corruption on x86_32.
- Fix kvmclock wallclock migration offset.
- Fix PIT interrupt ACK vs system reset logic bug.
Avi Kivity (1):
KVM: VMX: Fix ds/es corruption on i386 with preemption
Bruce Rogers (1):
KVM: x86: apply kvmclock offset to guest wall clock time
Gleb Natapov (1):
KVM: PIC: call ack notifiers for irqs that are dropped form irr
arch/x86/kvm/i8259.c | 17 +++++++++++++++++
arch/x86/kvm/vmx.c | 20 +++++++++++++-------
arch/x86/kvm/x86.c | 4 ++++
3 files changed, 34 insertions(+), 7 deletions(-)
reply other threads:[~2012-08-03 18:16 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=20120803181524.GA19680@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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