From: Sean Christopherson <seanjc@google.com>
To: Hou Wenlong <houwenlong.hwl@antgroup.com>
Cc: kvm@vger.kernel.org, David Matlack <dmatlack@google.com>
Subject: Re: [PATCH v3 0/6] KVM: x86/mmu: Fix wrong usages of range-based tlb flushing
Date: Fri, 7 Oct 2022 16:26:02 +0000 [thread overview]
Message-ID: <Y0BTGmuFCoiopUmR@google.com> (raw)
In-Reply-To: <cover.1663929851.git.houwenlong.hwl@antgroup.com>
On Fri, Sep 23, 2022, Hou Wenlong wrote:
> Hou Wenlong (6):
> KVM: x86/mmu: Fix wrong gfn range of tlb flushing in
> validate_direct_spte()
Only functional feedback from me is to move patch 1 and never introduce
kvm_flush_remote_tlbs_direct_sp()[*].
Stylistically, please wrap changelogs at ~75 chars, several of the changelogs
wrap at ~60, which is too aggressive/narrow.
Other than that, looks good.
[*] https://lore.kernel.org/all/YzSz1bFwD1XQ%2F%2FyY@google.com
prev parent reply other threads:[~2022-10-07 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 10:52 [PATCH v3 0/6] KVM: x86/mmu: Fix wrong usages of range-based tlb flushing Hou Wenlong
2022-09-23 10:52 ` [PATCH v3 1/6] KVM: x86/mmu: Fix wrong gfn range of tlb flushing in validate_direct_spte() Hou Wenlong
2022-09-28 20:51 ` Sean Christopherson
2022-09-23 10:52 ` [PATCH v3 2/6] KVM: x86/mmu: Move round_gfn_for_level() helper into mmu_internal.h Hou Wenlong
2022-09-23 10:52 ` [PATCH v3 3/6] KVM: x86/mmu: Fix wrong gfn range of tlb flushing in kvm_set_pte_rmapp() Hou Wenlong
2022-09-23 10:52 ` [PATCH v3 4/6] KVM: x86/mmu: Reduce gfn range of tlb flushing in tdp_mmu_map_handle_target_level() Hou Wenlong
2022-09-23 10:52 ` [PATCH v3 5/6] KVM: x86/mmu: Fix wrong start gfn of tlb flushing with range Hou Wenlong
2022-09-23 10:52 ` [PATCH v3 6/6] KVM: x86/mmu: Cleanup range-based flushing for given page Hou Wenlong
2022-10-07 16:26 ` Sean Christopherson [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=Y0BTGmuFCoiopUmR@google.com \
--to=seanjc@google.com \
--cc=dmatlack@google.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=kvm@vger.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.