All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM updates for 3.0-rc2
Date: Mon, 06 Jun 2011 17:31:05 +0300	[thread overview]
Message-ID: <4DECE4A9.4030505@redhat.com> (raw)

Linus, please pull from

   ssh://master.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.0

to receive a few KVM fixes for -rc2.  In particular, guest in/out 
instructions have been faulting when they shouldn't have.


Heiko Carstens (1):
       KVM: add missing void __user * cast to access_ok() call

Marcelo Tosatti (1):
       KVM: x86: use proper port value when checking io instruction 
permission

Mike Waychison (1):
       KVM: Initialize kvm before registering the mmu notifier

  arch/x86/kvm/emulate.c |   82 
+++++++++++++++++++++++++++--------------------
  virt/kvm/kvm_main.c    |   15 +++++---
  2 files changed, 56 insertions(+), 41 deletions(-)

-- 
error compiling committee.c: too many arguments to function


                 reply	other threads:[~2011-06-06 14:31 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=4DECE4A9.4030505@redhat.com \
    --to=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 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.