public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm-devel <kvm@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM fixes for 2.6.26-rc7
Date: Wed, 25 Jun 2008 00:05:06 +0300	[thread overview]
Message-ID: <48616182.9030902@qumranet.com> (raw)

Linus, please pull from the repo and branch at:

  git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git 
kvm-updates-2.6.26

to receive kvm updates for 2.6.26-rc7.  The patches fix host oopses,
guest interrupt loss, and total kvm clock borkage.

Since one of the goals of kvm clock was to be binary compatible with the Xen
clock, the patchset moves the Xen time code to common code and makes kvm 
reuse it.
This fixes both the ABI and correctness issues.  Jeremy has acked the Xen
changes.

Avi Kivity (3):
      KVM: MMU: Fix oops on guest userspace access to guest pagetable
      KVM: ioapic: fix lost interrupt when changing a device's irq
      KVM: VMX: Fix host msr corruption with preemption enabled

Gerd Hoffmann (5):
      x86: Add structs and functions for paravirt clocksource
      x86: Make xen use the paravirt clocksource structs and functions
      KVM: Make kvm host use the paravirt clocksource structs
      x86: KVM guest: Use the paravirt clocksource structs and functions
      KVM: Remove now unused structs from kvm_para.h

Marcelo Tosatti (4):
      KVM: Fix race between timer migration and vcpu migration
      KVM: close timer injection race window in __vcpu_run
      KVM: MMU: Fix rmap_write_protect() hugepage iteration bug
      KVM: MMU: large page update_pte issue with non-PAE 32-bit guests 
(resend)

 arch/x86/Kconfig              |    5 ++
 arch/x86/kernel/Makefile      |    1 +
 arch/x86/kernel/kvmclock.c    |   89 ++++++++++----------------
 arch/x86/kernel/pvclock.c     |  141 
+++++++++++++++++++++++++++++++++++++++++
 arch/x86/kvm/i8254.c          |    9 ++-
 arch/x86/kvm/lapic.c          |    1 +
 arch/x86/kvm/mmu.c            |   19 +++---
 arch/x86/kvm/vmx.c            |   19 +++---
 arch/x86/kvm/x86.c            |   91 +++++++++++++++++++-------
 arch/x86/xen/Kconfig          |    1 +
 arch/x86/xen/time.c           |  132 
++++-----------------------------------
 include/asm-x86/kvm_host.h    |    4 +-
 include/asm-x86/kvm_para.h    |   18 -----
 include/asm-x86/pvclock-abi.h |   42 ++++++++++++
 include/asm-x86/pvclock.h     |   13 ++++
 include/linux/kvm_host.h      |    1 +
 include/xen/interface/xen.h   |    7 +-
 virt/kvm/ioapic.c             |   31 +++------
 18 files changed, 358 insertions(+), 266 deletions(-)
 create mode 100644 arch/x86/kernel/pvclock.c
 create mode 100644 include/asm-x86/pvclock-abi.h
 create mode 100644 include/asm-x86/pvclock.h

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


             reply	other threads:[~2008-06-24 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 21:05 Avi Kivity [this message]
2008-06-25  1:12 ` [GIT PULL] KVM fixes for 2.6.26-rc7 Linus Torvalds
2008-06-25  7:08   ` Avi Kivity
2008-06-25 16:13 ` Bernd Schubert
2008-06-27  5:18 ` Jeremy Fitzhardinge
2008-06-28  4:02   ` Avi Kivity

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=48616182.9030902@qumranet.com \
    --to=avi@qumranet.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