From: Punit Agrawal <punitagrawal@gmail.com>
To: Christoffer Dall <christoffer.dall@arm.com>
Cc: kvm@vger.kernel.org, anshuman.khandual@arm.com,
marc.zyngier@arm.com, catalin.marinas@arm.com,
Suzuki K Poulose <suzuki.poulose@arm.com>,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v10 0/8] kvm: arm64: Support PUD hugepage at stage 2
Date: Fri, 04 Jan 2019 16:09:03 +0900 [thread overview]
Message-ID: <87ef9s292o.fsf@gmail.com> (raw)
In-Reply-To: <20181218113712.GA25383@e113682-lin.lund.arm.com> (Christoffer Dall's message of "Tue, 18 Dec 2018 12:37:12 +0100")
Christoffer Dall <christoffer.dall@arm.com> writes:
> On Tue, Dec 11, 2018 at 05:10:33PM +0000, Suzuki K Poulose wrote:
>> This series is an update to the PUD hugepage support previously posted
>> at [0]. This patchset adds support for PUD hugepages at stage 2 a
>> feature that is useful on cores that have support for large sized TLB
>> mappings (e.g., 1GB for 4K granule).
>>
>> The patches are based on v4.20-rc4
>>
>> The patches have been tested on AMD Seattle system with the following
>> hugepage sizes - 2M and 1G.
>>
>> Right now the PUD hugepage for stage2 is only supported if the stage2
>> has 4 levels. i.e, with an IPA size of minimum 44bits with 4K pages.
>> This could be relaxed to stage2 with 3 levels, with the stage1 PUD huge
>> page mapped in the entry level of the stage2 (i.e, pgd). I have not
>> added the change here to keep this version stable w.r.t the previous
>> version. I could post a patch later after further discussions in the
>> list.
>>
>
> For the series:
>
> Reviewed-by: Christoffer Dall <christoffer.dall@arm.com>
Thanks a lot for reviewing the patches and the tag. And to Suzuki for
picking up the patchset.
(I was happy to see this while catching up with the lists after an
extended break!)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-04 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 17:10 [PATCH v10 0/8] kvm: arm64: Support PUD hugepage at stage 2 Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 1/8] KVM: arm/arm64: Share common code in user_mem_abort() Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 2/8] KVM: arm/arm64: Re-factor setting the Stage 2 entry to exec on fault Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 3/8] KVM: arm/arm64: Introduce helpers to manipulate page table entries Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 4/8] KVM: arm64: Support dirty page tracking for PUD hugepages Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 5/8] KVM: arm64: Support PUD hugepage in stage2_is_exec() Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 6/8] KVM: arm64: Support handling access faults for PUD hugepages Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 7/8] KVM: arm64: Update age handlers to support " Suzuki K Poulose
2018-12-11 17:10 ` [PATCH v10 8/8] KVM: arm64: Add support for creating PUD hugepages at stage 2 Suzuki K Poulose
2018-12-18 11:37 ` [PATCH v10 0/8] kvm: arm64: Support PUD hugepage " Christoffer Dall
2019-01-04 7:09 ` Punit Agrawal [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=87ef9s292o.fsf@gmail.com \
--to=punitagrawal@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kvm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).