From: Paolo Bonzini <pbonzini@redhat.com>
To: Tianyu Lan <lantianyu1986@gmail.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Lan Tianyu <Tianyu.Lan@microsoft.com>,
Radim Krcmar <rkrcmar@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
bp@alien8.de, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
kvm <kvm@vger.kernel.org>,
"linux-kernel@vger kernel org" <linux-kernel@vger.kernel.org>,
michael.h.kelley@microsoft.com, kys@microsoft.com,
vkuznets@redhat.com, linux@armlinux.org.uk
Subject: Re: [PATCH 11/11] KVM/MMU: Flush tlb in the kvm_age_rmapp()
Date: Tue, 8 Jan 2019 12:52:25 +0100 [thread overview]
Message-ID: <de1d7197-9063-846c-770a-1a28686a545d@redhat.com> (raw)
In-Reply-To: <CAOLK0pxrdWZ6RAJROw0cyfexjZnKqSsCrm-jUD=wUHWvWV47kQ@mail.gmail.com>
On 08/01/19 04:42, Tianyu Lan wrote:
> From my understanding, this means to move the flush in the
> kvm_mmu_notifier_clear_flush_young()
> to kvm_age_hva() and do flush in kvm_age_hva() when young is >0 and "flush"
> parameter is true, right?
Yes.
Paolo
prev parent reply other threads:[~2019-01-08 11:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 8:53 [PATCH 00/11] X86/KVM/Hyper-V: Add HV ept tlb range list flush support in KVM lantianyu1986
2019-01-04 8:53 ` [PATCH 1/11] X86/Hyper-V: Add parameter offset for hyperv_fill_flush_guest_mapping_list() lantianyu1986
2019-01-04 8:53 ` [PATCH 2/11] KVM/VMX: Fill range list in kvm_fill_hv_flush_list_func() lantianyu1986
2019-01-04 8:53 ` [PATCH 3/11] KVM: Add spte's point in the struct kvm_mmu_page lantianyu1986
2019-01-07 16:34 ` Paolo Bonzini
2019-01-04 8:53 ` [PATCH 4/11] KVM/MMU: Introduce tlb flush with range list lantianyu1986
2019-01-07 16:39 ` Paolo Bonzini
2019-01-04 8:53 ` [PATCH 5/11] KVM/MMU: Flush tlb directly in the kvm_mmu_slot_gfn_write_protect() lantianyu1986
2019-01-04 8:54 ` [PATCH 6/11] KVM/MMU: Flush tlb with range list in sync_page() lantianyu1986
[not found] ` <20190104163035.GC11288@linux.intel.com>
2019-01-07 5:13 ` Tianyu Lan
2019-01-07 16:07 ` Paolo Bonzini
2019-01-04 8:54 ` [PATCH 7/11] KVM: Remove redundant check in the kvm_get_dirty_log_protect() lantianyu1986
[not found] ` <20190104155036.GA11288@linux.intel.com>
2019-01-04 21:27 ` Sean Christopherson
2019-01-07 16:20 ` Paolo Bonzini
2019-01-04 8:54 ` [PATCH 8/11] KVM: Make kvm_arch_mmu_enable_log_dirty_pt_masked() return value lantianyu1986
2019-01-04 8:54 ` [PATCH 9/11] KVM/MMU: Flush tlb in the kvm_mmu_write_protect_pt_masked() lantianyu1986
2019-01-07 16:26 ` Paolo Bonzini
2019-01-10 9:06 ` Tianyu Lan
2019-01-04 8:54 ` [PATCH 10/11] KVM: Add flush parameter for kvm_age_hva() lantianyu1986
2019-01-04 8:54 ` [PATCH 11/11] KVM/MMU: Flush tlb in the kvm_age_rmapp() lantianyu1986
[not found] ` <20190104161235.GB11288@linux.intel.com>
2019-01-07 3:42 ` Tianyu Lan
2019-01-07 16:31 ` Paolo Bonzini
2019-01-08 3:42 ` Tianyu Lan
2019-01-08 11:52 ` Paolo Bonzini [this message]
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=de1d7197-9063-846c-770a-1a28686a545d@redhat.com \
--to=pbonzini@redhat.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=lantianyu1986@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael.h.kelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®