From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, Gavin Shan <gshan@redhat.com>
Cc: will@kernel.org, linux-kernel@vger.kernel.org, shan.gavin@gmail.com
Subject: Re: [PATCH v2 0/3] KVM: arm64: Minor page fault handler improvement
Date: Wed, 7 Apr 2021 14:46:38 +0100 [thread overview]
Message-ID: <161780318317.1871386.15067995969870728434.b4-ty@kernel.org> (raw)
In-Reply-To: <20210316041126.81860-1-gshan@redhat.com>
On Tue, 16 Mar 2021 12:11:23 +0800, Gavin Shan wrote:
> The series includes several minior improvements to stage-2 page fault
> handler: PATCH[1/2] are cleaning up the code. PATCH[3] don't retrieve
> the memory slot again in the page fault handler to save a bit CPU cycles.
>
> Changelog
> =========
> v2:
> * Rebased to 5.12.rc3 and include r-bs from Keqian (Gavin)
> * Drop patch to fix IPA limit boundary issue (Keqian)
> * Comments on why we use __gfn_to_pfn_memslot() (Keqian)
>
> [...]
Applied to kvm-arm64/memslot-fixes, thanks!
[1/3] KVM: arm64: Hide kvm_mmu_wp_memory_region()
commit: eab62148478d339a37c7a6b37d34182ccf5056ad
[2/3] KVM: arm64: Use find_vma_intersection()
commit: c728fd4ce75e9c342ea96facc5a2fe5ddb976a67
[3/3] KVM: arm64: Don't retrieve memory slot again in page fault handler
commit: 10ba2d17d2972926c60e01dace6d7a3f8d968c4f
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2021-04-07 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 4:11 [PATCH v2 0/3] KVM: arm64: Minor page fault handler improvement Gavin Shan
2021-03-16 4:11 ` [PATCH v2 1/3] KVM: arm64: Hide kvm_mmu_wp_memory_region() Gavin Shan
2021-03-16 4:11 ` [PATCH v2 2/3] KVM: arm64: Use find_vma_intersection() Gavin Shan
2021-03-16 4:11 ` [PATCH v2 3/3] KVM: arm64: Don't retrieve memory slot again in page fault handler Gavin Shan
2021-04-07 13:46 ` Marc Zyngier [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=161780318317.1871386.15067995969870728434.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=gshan@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=shan.gavin@gmail.com \
--cc=will@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).