All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.34.1
Date: Wed, 07 Jul 2010 16:54:28 +0200	[thread overview]
Message-ID: <4C349524.8060309@siemens.com> (raw)

This is just an update for the current stable kvm-kmod version based on
2.6.34.1.

KVM changes since kvm-kmod-2.6.34:
 - Fix wallclock version writing race
 - MMU: Don't read pdptrs with mmu spinlock held in mmu_alloc_roots
 - VMX: enable VMXON check with SMX enabled (Intel TXT)
 - MMU: Segregate shadow pages with different cr0.wp
 - x86: Inject #GP with the right rip on efer writes
 - x86: Add missing locking to arch specific vcpu ioctls
 - x86: Check LMA bit before set_efer
 - x86: Add callback to let modules decide over some supported cpuid
   bits
 - x86: Don't allow lmsw to clear cr0.pe
 - SVM: Don't allow nested guest to VMMCALL into host
 - SVM: Report emulated SVM features to userspace
 - SVM: Fix wrong interrupt injection in enable_irq_windows
 - SVM: Don't sync nested cr8 to lapic and back
 - SVM: Fix nested msr intercept handling
 - SVM: Sync all control registers on nested vmexit
 - SVM: Fix schedule-while-atomic on nested exception handling
 - SVM: Don't use kmap_atomic in nested_svm_map

kvm-kmod changes:
 - expand relative kernel path

You can download this version from

http://downloads.sourceforge.net/project/kvm/kvm-kmod/2.6.34.1/kvm-kmod-2.6.34.1.tar.bz2


An update to kvm-kmod-2.6.32.16 will follow soon as well, but without
further announcement.

                 reply	other threads:[~2010-07-07 14:54 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=4C349524.8060309@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.