From: Lan Tianyu <tianyu.lan@intel.com>
To: pbonzini@redhat.com, guangrong.xiao@linux.intel.com,
agraf@suse.com, benh@kernel.crashing.org, gleb@kernel.org,
hpa@zytor.com, kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mingo@redhat.com, mpe@ellerman.id.au, paulus@samba.org,
tglx@linutronix.de, x86@kernel.org
Cc: Lan Tianyu <tianyu.lan@intel.com>
Subject: [PATCH 0/7] KVM/X86/PPC: Clear up kvm mmu memory barriers and update related comments
Date: Sun, 13 Mar 2016 11:10:23 +0800 [thread overview]
Message-ID: <1457838631-26775-1-git-send-email-tianyu.lan@intel.com> (raw)
This series is to clear up kvm mmu memory barriers.
1) Remove redundant barrier (PATCH 1)
2) Replace origin barrier functions with preferrable ones (PATCH 2, 3, 5)
3) Fix unpaired barriers (PATCH 4)
4) Update or add barrier related comments (PATCH 6, 7)
Lan Tianyu (7):
KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()
KVM/x86: Replace smp_mb() with smp_store_mb/release() in the
walk_shadow_page_lockless_begin/end()
KVM: Replace smp_mb() with smp_mb_after_atomic() in the
kvm_make_all_cpus_request()
KVM/x86: Call smp_wmb() before increasing tlbs_dirty
KVM: Replace smp_mb() with smp_load_acquire() in the
kvm_flush_remote_tlbs()
KVM/x86: update the comment of memory barrier in the
vcpu_enter_guest()
KVM/PPC: update the comment of memory barrier in the
kvmppc_prepare_to_enter()
arch/powerpc/kvm/powerpc.c | 3 +++
arch/x86/kvm/mmu.c | 23 ++++++++++-------------
arch/x86/kvm/paging_tmpl.h | 11 +++++++++++
arch/x86/kvm/x86.c | 8 ++++++--
virt/kvm/kvm_main.c | 22 ++++++++++++++++++----
5 files changed, 48 insertions(+), 19 deletions(-)
--
1.8.4.rc0.1.g8f6a3e5.dirty
next reply other threads:[~2016-03-13 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 3:10 Lan Tianyu [this message]
2016-03-13 3:10 ` [PATCH 1/7] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page() Lan Tianyu
2016-03-13 3:10 ` [PATCH 2/7] KVM/x86: Replace smp_mb() with smp_store_mb/release() in the walk_shadow_page_lockless_begin/end() Lan Tianyu
2016-03-13 3:10 ` [PATCH 3/7] KVM: Replace smp_mb() with smp_mb_after_atomic() in the kvm_make_all_cpus_request() Lan Tianyu
2016-03-13 3:10 ` [PATCH 4/7] KVM/x86: Call smp_wmb() before increasing tlbs_dirty Lan Tianyu
2016-03-13 3:10 ` [PATCH 5/7] KVM: Replace smp_mb() with smp_load_acquire() in the kvm_flush_remote_tlbs() Lan Tianyu
2016-03-13 3:10 ` [PATCH 6/7] KVM/x86: update the comment of memory barrier in the vcpu_enter_guest() Lan Tianyu
2016-03-13 3:10 ` [PATCH 7/7] KVM/PPC: update the comment of memory barrier in the kvmppc_prepare_to_enter() Lan Tianyu
2016-03-14 13:03 ` [PATCH 0/7] KVM/X86/PPC: Clear up kvm mmu memory barriers and update related comments 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=1457838631-26775-1-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=agraf@suse.com \
--cc=benh@kernel.crashing.org \
--cc=gleb@kernel.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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).