All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: oliver.upton@linux.dev, joey.gouly@arm.com,
	suzuki.poulose@arm.com, yuzenghui@huawei.com,
	catalin.marinas@arm.com, will@kernel.org, qperret@google.com,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v4 0/3] Count pKVM stage-2 usage in secondary pagetable stat
Date: Thu, 13 Mar 2025 13:13:24 +0000	[thread overview]
Message-ID: <86jz8tnkej.wl-maz@kernel.org> (raw)
In-Reply-To: <20250313114038.1502357-1-vdonnefort@google.com>

On Thu, 13 Mar 2025 11:40:35 +0000,
Vincent Donnefort <vdonnefort@google.com> wrote:
> 
> This series allows to count stage-2 related memory when using pKVM. The
> value can be found in the /proc/meminfo field SecPageTables.
> 
> Changes since v3: https://lore.kernel.org/all/20250307113411.469018-1-vdonnefort@google.com/
>   - Remove unnecessary void * cast (Marc)
>   - Rename reclaim_guest_pages() -> reclaim_pgtable_pages() (Marc)
>   - Remove unnecessary PAGE_ALIGN(pgd_sz)
> 
> Changes since v2: https://lore.kernel.org/all/20250304134347.369854-1-vdonnefort@google.com/
>   - Pass a pointer to kvm_hyp_memcache instead of just the flags
>     (Oliver)
> 
> Changes since v1: https://lore.kernel.org/all/20250228121355.1377891-1-vdonnefort@google.com/
>   - Flags to kvm_hyp_memcache
>   - Separate stage-2 memcache
>   - Account for PGD
> 
> Vincent Donnefort (3):
>   KVM: arm64: Add flags to kvm_hyp_memcache
>   KVM: arm64: Distinct pKVM teardown memcache for stage-2
>   KVM: arm64: Count pKVM stage-2 usage in secondary pagetable stats
> 
>  arch/arm64/include/asm/kvm_host.h             |  4 ++++
>  arch/arm64/kvm/hyp/include/nvhe/mem_protect.h |  2 +-
>  arch/arm64/kvm/hyp/nvhe/mem_protect.c         |  2 +-
>  arch/arm64/kvm/hyp/nvhe/pkvm.c                |  8 +++----
>  arch/arm64/kvm/mmu.c                          | 22 ++++++++++++++-----
>  arch/arm64/kvm/pkvm.c                         |  5 +++++
>  6 files changed, 32 insertions(+), 11 deletions(-)

Acked-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2025-03-13 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 11:40 [PATCH v4 0/3] Count pKVM stage-2 usage in secondary pagetable stat Vincent Donnefort
2025-03-13 11:40 ` [PATCH v4 1/3] KVM: arm64: Add flags to kvm_hyp_memcache Vincent Donnefort
2025-03-13 11:40 ` [PATCH v4 2/3] KVM: arm64: Distinct pKVM teardown memcache for stage-2 Vincent Donnefort
2025-03-13 11:40 ` [PATCH v4 3/3] KVM: arm64: Count pKVM stage-2 usage in secondary pagetable stats Vincent Donnefort
2025-03-13 13:13 ` Marc Zyngier [this message]
2025-03-14 23:11 ` [PATCH v4 0/3] Count pKVM stage-2 usage in secondary pagetable stat Oliver Upton

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=86jz8tnkej.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=vdonnefort@google.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 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.