mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
	kvm@vger.kernel.org, marc.zyngier@arm.com, will.deacon@arm.com,
	catalin.marinas@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v10 0/8] kvm: arm64: Support PUD hugepage at stage 2
Date: Tue, 18 Dec 2018 12:37:12 +0100	[thread overview]
Message-ID: <20181218113712.GA25383@e113682-lin.lund.arm.com> (raw)
In-Reply-To: <1544548241-6417-1-git-send-email-suzuki.poulose@arm.com>

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>

  parent reply	other threads:[~2018-12-18 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 17:10 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 ` Christoffer Dall [this message]
2019-01-04  7:09   ` [PATCH v10 0/8] kvm: arm64: Support PUD hugepage " Punit Agrawal

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=20181218113712.GA25383@e113682-lin.lund.arm.com \
    --to=christoffer.dall@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@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

all inboxes | Powered by JetHome®