From: Punit Agrawal <punit.agrawal@arm.com>
To: <kvmarm@lists.cs.columbia.edu>
Cc: <linux-arm-kernel@lists.infradead.org>, <marc.zyngier@arm.com>,
<christoffer.dall@arm.com>, <linux-kernel@vger.kernel.org>,
<suzuki.poulose@arm.com>, <will.deacon@arm.com>
Subject: Re: [PATCH v5 0/7] KVM: Support PUD hugepages at stage 2
Date: Mon, 09 Jul 2018 15:49:44 +0100 [thread overview]
Message-ID: <871sccqx9z.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <20180709143835.28971-2-punit.agrawal@arm.com> (Punit Agrawal's message of "Mon, 9 Jul 2018 15:38:28 +0100")
Please ignore this cover letter.
Apologies for the duplicate cover-letter and a somewhat funky threading
(I blame emacs unsaved buffer).
The patches appear to be intact so don't let the threading get in the
way of review.
Punit Agrawal <punit.agrawal@arm.com> writes:
> This series is an update to the PUD hugepage support previously posted
> at [0]. This patchset adds support for PUD hugepages at stage
> 2. This feature is useful on cores that have support for large sized
> TLB mappings (e.g., 1GB for 4K granule).
>
> The biggest change in this version is to replace repeated instances of
> walking the page tables to get to a leaf-entry with a function to
> return the appropriate entry. This was suggested by Suzuki and should
> help reduce the amount of churn resulting from future changes. It also
> address other feedback on the previous version.
>
> Support is added to code that is shared between arm and arm64. Dummy
> helpers for arm are provided as the port does not support PUD hugepage
> sizes.
>
> The patches have been tested on an A57 based system. The patchset is
> based on v4.18-rc4. The are a few conflicts with the support for 52
> bit IPA[1] due to change in number of parameters for
> stage2_pmd_offset().
>
> Thanks,
> Punit
>
> v4 -> v5:
>
> * Patch 1 - Drop helper stage2_should_exec() and refactor the
> condition to decide if a page table entry should be marked
> executable
> * Patch 4-6 - Introduce stage2_get_leaf_entry() and use it in this and
> latter patches
> * Patch 7 - Use stage 2 accessors instead of using the page table
> helpers directly
> * Patch 7 - Add a note to update the PUD hugepage support when number
> of levels of stage 2 tables differs from stage 1
>
>
> v3 -> v4:
> * Patch 1 and 7 - Don't put down hugepages pte if logging is enabled
> * Patch 4-5 - Add PUD hugepage support for exec and access faults
> * Patch 6 - PUD hugepage support for aging page table entries
>
> v2 -> v3:
> * Update vma_pagesize directly if THP [1/4]. Previsouly this was done
> indirectly via hugetlb
> * Added review tag [4/4]
>
> v1 -> v2:
> * Create helper to check if the page should have exec permission [1/4]
> * Fix broken condition to detect THP hugepage [1/4]
> * Fix in-correct hunk resulting from a rebase [4/4]
>
> [0] https://www.spinics.net/lists/arm-kernel/msg663562.html
> [1] https://www.spinics.net/lists/kvm/msg171065.html
>
>
> Punit Agrawal (7):
> KVM: arm/arm64: Share common code in user_mem_abort()
> KVM: arm/arm64: Introduce helpers to manupulate page table entries
> KVM: arm64: Support dirty page tracking for PUD hugepages
> KVM: arm64: Support PUD hugepage in stage2_is_exec()
> KVM: arm64: Support handling access faults for PUD hugepages
> KVM: arm64: Update age handlers to support PUD hugepages
> KVM: arm64: Add support for creating PUD hugepages at stage 2
>
> arch/arm/include/asm/kvm_mmu.h | 60 +++++
> arch/arm64/include/asm/kvm_mmu.h | 47 ++++
> arch/arm64/include/asm/pgtable-hwdef.h | 4 +
> arch/arm64/include/asm/pgtable.h | 9 +
> virt/kvm/arm/mmu.c | 289 ++++++++++++++++++-------
> 5 files changed, 330 insertions(+), 79 deletions(-)
next prev parent reply other threads:[~2018-07-09 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:38 Punit Agrawal
2018-07-09 14:38 ` Punit Agrawal
2018-07-09 14:49 ` Punit Agrawal [this message]
2018-07-09 14:41 ` [PATCH v5 1/7] KVM: arm/arm64: Share common code in user_mem_abort() Punit Agrawal
2018-07-09 14:41 ` [PATCH v5 2/7] KVM: arm/arm64: Introduce helpers to manupulate page table entries Punit Agrawal
2018-07-11 13:00 ` Suzuki K Poulose
2018-07-11 16:10 ` Punit Agrawal
2018-07-09 14:41 ` [PATCH v5 3/7] KVM: arm64: Support dirty page tracking for PUD hugepages Punit Agrawal
2018-07-11 13:03 ` Suzuki K Poulose
2018-07-09 14:41 ` [PATCH v5 4/7] KVM: arm64: Support PUD hugepage in stage2_is_exec() Punit Agrawal
2018-07-11 13:41 ` Suzuki K Poulose
2018-07-11 15:05 ` Punit Agrawal
2018-07-09 14:41 ` [PATCH v5 5/7] KVM: arm64: Support handling access faults for PUD hugepages Punit Agrawal
2018-07-11 13:16 ` Suzuki K Poulose
2018-07-09 14:41 ` [PATCH v5 6/7] KVM: arm64: Update age handlers to support " Punit Agrawal
2018-07-11 13:23 ` Suzuki K Poulose
2018-07-09 14:41 ` [PATCH v5 7/7] KVM: arm64: Add support for creating PUD hugepages at stage 2 Punit Agrawal
2018-07-11 13:38 ` Suzuki K Poulose
2018-07-11 16:05 ` Punit Agrawal
2018-07-11 16:13 ` Suzuki K Poulose
2018-07-11 16:19 ` Punit Agrawal
2018-07-11 12:59 ` [PATCH v5 1/7] KVM: arm/arm64: Share common code in user_mem_abort() Suzuki K Poulose
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=871sccqx9z.fsf@e105922-lin.cambridge.arm.com \
--to=punit.agrawal@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.com \
/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®