From: Junaid Shahid <junaids@google.com>
To: kvm@vger.kernel.org
Cc: andreslc@google.com, pfeiner@google.com, pbonzini@redhat.com,
guangrong.xiao@linux.intel.com
Subject: [PATCH 0/5] Followup patches for lockless access tracking
Date: Wed, 21 Dec 2016 20:29:27 -0800 [thread overview]
Message-ID: <1482380972-25573-1-git-send-email-junaids@google.com> (raw)
This series includes a few followup patches implementing some of the code review feedback from the lockless access tracking patch series.
Junaid Shahid (5):
kvm: x86: mmu: Rename EPT_VIOLATION_READ/WRITE/INSTR constants
kvm: x86: mmu: Set SPTE_SPECIAL_MASK within mmu.c
kvm: x86: mmu: Move pgtbl walk inside retry loop in fast_page_fault
kvm: x86: mmu: Update comment in mark_spte_for_access_track
kvm: x86: mmu: Verify that restored PTE has needed perms in fast page
fault
arch/x86/include/asm/vmx.h | 12 ++--
arch/x86/kvm/mmu.c | 153 ++++++++++++++++++++++++---------------------
arch/x86/kvm/vmx.c | 12 ++--
arch/x86/kvm/x86.c | 3 -
4 files changed, 93 insertions(+), 87 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-12-22 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 4:29 Junaid Shahid [this message]
2016-12-22 4:29 ` [PATCH 1/5] kvm: x86: mmu: Rename EPT_VIOLATION_READ/WRITE/INSTR constants Junaid Shahid
2016-12-22 4:29 ` [PATCH 2/5] kvm: x86: mmu: Set SPTE_SPECIAL_MASK within mmu.c Junaid Shahid
2016-12-22 4:29 ` [PATCH 3/5] kvm: x86: mmu: Move pgtbl walk inside retry loop in fast_page_fault Junaid Shahid
2016-12-22 4:29 ` [PATCH 4/5] kvm: x86: mmu: Update comment in mark_spte_for_access_track Junaid Shahid
2016-12-22 4:29 ` [PATCH 5/5] kvm: x86: mmu: Verify that restored PTE has needed perms in fast page fault Junaid Shahid
2017-01-25 11:49 ` Paolo Bonzini
2017-01-25 20:05 ` Junaid Shahid
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=1482380972-25573-1-git-send-email-junaids@google.com \
--to=junaids@google.com \
--cc=andreslc@google.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pfeiner@google.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