kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: [GIT PULL] kvm/page_track changes for i915 KVMGT
Date: Wed,  9 Nov 2016 15:25:19 +0100	[thread overview]
Message-ID: <1478701519-13533-1-git-send-email-pbonzini@redhat.com> (raw)

Daniel,

The following changes since commit d9092f52d7e61dd1557f2db2400ddb430e85937e:

  kvm: x86: Check memopp before dereference (CVE-2016-8630) (2016-11-02 21:31:53 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-kvmgt

for you to fetch changes up to 871b7ef2a1850d0b435c8b324bf4a5d391adde3f:

  kvm/page_track: export symbols for external usage (2016-11-04 12:13:20 +0100)

----------------------------------------------------------------
The three KVM patches that KVMGT needs.

----------------------------------------------------------------
Jike Song (2):
      kvm/page_track: call notifiers with kvm_page_track_notifier_node
      kvm/page_track: export symbols for external usage

Xiaoguang Chen (1):
      KVM: x86: add track_flush_slot page track notifier

 arch/x86/include/asm/kvm_page_track.h | 14 +++++++++++++-
 arch/x86/kvm/mmu.c                    | 11 ++++++++++-
 arch/x86/kvm/page_track.c             | 31 ++++++++++++++++++++++++++++++-
 arch/x86/kvm/x86.c                    |  2 +-
 4 files changed, 54 insertions(+), 4 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-11-09 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 14:25 Paolo Bonzini [this message]
2016-11-09 15:15 ` [GIT PULL] kvm/page_track changes for i915 KVMGT Daniel Vetter
2016-11-09 15:16   ` Paolo Bonzini

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=1478701519-13533-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).