All of lore.kernel.org
 help / color / mirror / Atom feed
From: lantianyu1986@gmail.com
To: unlisted-recipients:; (no To-header on input)
Cc: Lan Tianyu <Tianyu.Lan@microsoft.com>,
	pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	michael.h.kelley@microsoft.com, kys@microsoft.com,
	vkuznets@redhat.com, linux@armlinux.org.uk
Subject: [PATCH V3 9/10] KVM/MMU: Use tlb range flush in the kvm_age_hva()
Date: Fri, 22 Feb 2019 23:06:36 +0800	[thread overview]
Message-ID: <20190222150637.2337-10-Tianyu.Lan@microsoft.com> (raw)
In-Reply-To: <20190222150637.2337-1-Tianyu.Lan@microsoft.com>

From: Lan Tianyu <Tianyu.Lan@microsoft.com>

This patch is to use tlb range flush in the kvm_age_hva().
If range flush is not available, kvm_flush_remote_tlbs_with_address()
will call kvm_flush_remote_tlbs().

Signed-off-by: Lan Tianyu <Tianyu.Lan@microsoft.com>
---
 arch/x86/kvm/mmu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 295833dafc59..2e13aac28293 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -1994,7 +1994,7 @@ int kvm_age_hva(struct kvm *kvm, unsigned long start, unsigned long end,
 	int young = kvm_handle_hva_range(kvm, start, end, 0, kvm_age_rmapp);
 
 	if (flush && young > 0)
-		kvm_flush_remote_tlbs(kvm);
+		kvm_flush_remote_tlbs_with_address(kvm, start, end - start + 1);
 
 	return young;
 }
-- 
2.14.4


  parent reply	other threads:[~2019-02-22 15:08 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 15:06 [PATCH V3 00/10] X86/KVM/Hyper-V: Add HV ept tlb range list flush support in KVM lantianyu1986
2019-02-22 15:06 ` lantianyu1986
2019-02-22 15:06 ` lantianyu1986
2019-02-22 15:06 ` lantianyu1986
2019-02-22 15:06 ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 1/10] X86/Hyper-V: Add parameter offset for hyperv_fill_flush_guest_mapping_list() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 17:08   ` Stephen Hemminger
2019-02-22 17:08     ` Stephen Hemminger
2019-02-22 17:08     ` Stephen Hemminger
2019-02-22 17:08     ` Stephen Hemminger
2019-02-22 17:08     ` Stephen Hemminger
2019-02-26 13:00     ` Tianyu Lan
2019-02-26 13:00       ` Tianyu Lan
2019-02-26 13:00       ` Tianyu Lan
2019-02-26 13:00       ` Tianyu Lan
2019-02-26 13:00       ` Tianyu Lan
2019-02-26 14:09   ` [Update PATCH " lantianyu1986
2019-02-22 15:06 ` [PATCH V3 2/10] KVM/VMX: Fill range list in kvm_fill_hv_flush_list_func() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 3/10] KVM/MMU: Introduce tlb flush with range list lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 4/10] KVM/MMU: Use range flush in sync_page() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 5/10] KVM/MMU: Flush tlb directly in the kvm_mmu_slot_gfn_write_protect() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 6/10] KVM: Add kvm_get_memslot() to get memslot via slot id lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 7/10] KVM: Use tlb range flush in the kvm_vm_ioctl_get/clear_dirty_log() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` [PATCH V3 8/10] KVM: Add flush parameter for kvm_age_hva() lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06   ` lantianyu1986
2019-02-22 15:06 ` lantianyu1986 [this message]
2019-02-22 15:06 ` [PATCH V3 10/10] KVM/MMU: Add last_level flag in the struct mmu_spte_page lantianyu1986
2019-02-22 18:25 ` [PATCH V3 00/10] X86/KVM/Hyper-V: Add HV ept tlb range list flush support in KVM Paolo Bonzini
2019-02-22 18:25   ` Paolo Bonzini
2019-02-22 18:25   ` Paolo Bonzini
2019-02-22 18:25   ` Paolo Bonzini
2019-02-23 14:37   ` Tianyu Lan
2019-02-23 14:37     ` Tianyu Lan
2019-02-23 14:37     ` Tianyu Lan
2019-02-23 14:37     ` Tianyu Lan
2019-02-23 14:37     ` Tianyu Lan
2019-02-26 14:21 ` [Update PATCH V3 2/10] KVM/VMX: Fill range list in kvm_fill_hv_flush_list_func() lantianyu1986

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=20190222150637.2337-10-Tianyu.Lan@microsoft.com \
    --to=lantianyu1986@gmail.com \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.h.kelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --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 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.