linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: Wei-Lin Chang <weilin.chang@arm.com>
Cc: maz@kernel.org, oupton@kernel.org, kvmarm@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, joey.gouly@arm.com,
	seiden@linux.ibm.com, suzuki.poulose@arm.com,
	yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org,
	kernel-team@android.com, fuad.tabba@linux.dev,
	qperret@google.com, keirf@google.com
Subject: Re: [PATCH 12/20] KVM: arm64: Handle huge mappings in __pkvm_host_force_reclaim_page_guest()
Date: Tue, 8 Sep 2026 11:26:43 +0100	[thread overview]
Message-ID: <ap_i40-JQnXf4w4O@google.com> (raw)
In-Reply-To: <yzeb47zjrxdsfztilng7n4e22fnsm4ncqjeqzmryc7sqncuqw6@pjtshmjxwelh>

On Mon, Sep 07, 2026 at 05:52:35PM +0100, Wei-Lin Chang wrote:
> On Mon, Aug 03, 2026 at 11:08:56AM +0100, Vincent Donnefort wrote:
> 
> [...]
> 
> > -static void hyp_poison_page(phys_addr_t phys)
> > +static void __hyp_poison_page(void *addr, size_t size)
> >  {
> > -	void *addr = hyp_fixmap_map(phys);
> > -
> > -	memset(addr, 0, PAGE_SIZE);
> > +	memset(addr, 0, size);
> >  	/*
> >  	 * Prefer kvm_flush_dcache_to_poc() over __clean_dcache_guest_page()
> >  	 * here as the latter may elide the CMO under the assumption that FWB
> > @@ -1304,19 +1302,15 @@ static void hyp_poison_page(phys_addr_t phys)
> >  	 * host stage-2 and would otherwise lead to a malicious host potentially
> >  	 * being able to read the contents of newly reclaimed guest pages.
> >  	 */
> > -	kvm_flush_dcache_to_poc(addr, PAGE_SIZE);
> > -	hyp_fixmap_unmap();
> > +	kvm_flush_dcache_to_poc(addr, size);
> >  }
> >  
> >  static void hyp_poison_range(phys_addr_t phys, u64 size)
> >  {
> > -	u64 offset;
> > -
> > -	for (offset = 0; offset < size; offset += PAGE_SIZE)
> > -		hyp_poison_page(phys + offset);
> > +	__apply_guest_page(__hyp_va(phys), size, __hyp_poison_page);
> >  }
> 
> Patch 8 introduces hyp_poison_range(), and it is reimplemented in
> another way here. Maybe just do it this way in the first time?

Especially if I split it into a separate patch.

> 
> >  
> > -static int host_stage2_get_guest_info(phys_addr_t phys, struct pkvm_hyp_vm **vm,
> > +static int host_stage2_get_guest_info(phys_addr_t phys, u64 *size, struct pkvm_hyp_vm **vm,
> >  				      u64 *gfn)
> >  {
> >  	enum pkvm_page_state state;
> > @@ -1344,34 +1338,43 @@ static int host_stage2_get_guest_info(phys_addr_t phys, struct pkvm_hyp_vm **vm,
> >  	if (ret)
> >  		return ret;
> >  
> > -	if (WARN_ON(level != KVM_PGTABLE_LAST_LEVEL))
> > -		return -EINVAL;
> > +	/* We only support either PAGE_SIZE or PMD_SIZE */
> > +	if (level < KVM_PGTABLE_LAST_LEVEL - 1)
> > +		return -E2BIG;
> >  
> > -	return host_stage2_decode_gfn_meta(pte, vm, gfn);
> > +	ret = host_stage2_decode_gfn_meta(pte, vm, gfn);
> > +	if (ret)
> > +		return ret;
> > +
> > +	*size = kvm_granule_size(level);
> > +
> > +	return 0;
> 
> This can also be moved into its own patch with get_valid_guest_pte(),
> hyp_poison_range() changes in my opinion.
> 
> Thanks,
> Wei-Lin Chang
> 
> [...]


  reply	other threads:[~2026-09-08 10:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 10:08 [PATCH 00/20] Huge mapping support for protected VMs Vincent Donnefort
2026-08-03 10:08 ` [PATCH 01/20] KVM: arm64: Prefault host stage-2 entries on block split Vincent Donnefort
2026-09-07 18:34   ` Wei-Lin Chang
2026-08-03 10:08 ` [PATCH 02/20] KVM: arm64: Propagate host stage-2 annotated " Vincent Donnefort
2026-09-07 13:58   ` Wei-Lin Chang
2026-09-08 10:07     ` Vincent Donnefort
2026-08-03 10:08 ` [PATCH 03/20] KVM: arm64: Allow block-level stage-2 annotation Vincent Donnefort
2026-08-03 10:08 ` [PATCH 04/20] KVM: arm64: Use block-level annotations when setting up the host stage-2 Vincent Donnefort
2026-09-07 14:37   ` Wei-Lin Chang
2026-09-08 10:18     ` Vincent Donnefort
2026-08-03 10:08 ` [PATCH 05/20] KVM: arm64: Make pKVM ownership selftest an HVC Vincent Donnefort
2026-08-03 10:08 ` [PATCH 06/20] KVM: arm64: Add a range to __pkvm_host_share/unshare_hyp() Vincent Donnefort
2026-08-03 10:08 ` [PATCH 07/20] KVM: arm64: Add a range to __pkvm_host_donate_guest() Vincent Donnefort
2026-08-03 10:08 ` [PATCH 08/20] KVM: arm64: Add a range to __pkvm_host_reclaim_page_guest() Vincent Donnefort
2026-09-07 14:52   ` Wei-Lin Chang
2026-09-08 10:22     ` Vincent Donnefort
2026-08-03 10:08 ` [PATCH 09/20] KVM: arm64: Add a range to __pkvm_guest_share_host() Vincent Donnefort
2026-08-03 10:08 ` [PATCH 10/20] KVM: arm64: Add a range to __pkvm_guest_unshare_host() Vincent Donnefort
2026-08-03 10:08 ` [PATCH 11/20] KVM: arm64: Add a range to pKVM ownership selftest Vincent Donnefort
2026-09-07 14:58   ` Wei-Lin Chang
2026-09-08 10:25     ` Vincent Donnefort
2026-09-10 10:04       ` Vincent Donnefort
2026-08-03 10:08 ` [PATCH 12/20] KVM: arm64: Handle huge mappings in __pkvm_host_force_reclaim_page_guest() Vincent Donnefort
2026-09-07 16:52   ` Wei-Lin Chang
2026-09-08 10:26     ` Vincent Donnefort [this message]
2026-08-03 10:08 ` [PATCH 13/20] KVM: arm64: Handle huge mappings in __pkvm_vcpu_in_poison_fault() Vincent Donnefort
2026-08-03 10:08 ` [PATCH 14/20] KVM: arm64: pkvm: Warn on guest stage-2 block collapse Vincent Donnefort
2026-08-03 10:08 ` [PATCH 15/20] KVM: arm64: Add pkvm_hyp_req infrastructure Vincent Donnefort
2026-08-03 10:09 ` [PATCH 16/20] KVM: arm64: Add __pkvm_host_split_guest HVC Vincent Donnefort
2026-09-07 17:39   ` Wei-Lin Chang
2026-09-08 14:46     ` Vincent Donnefort
2026-08-03 10:09 ` [PATCH 17/20] KVM: arm64: Extend pKVM page ownership selftests to cover guest block split Vincent Donnefort
2026-08-03 10:09 ` [PATCH 18/20] KVM: arm64: Add PKVM_HYP_REQ_SPLIT Vincent Donnefort
2026-09-07 18:15   ` Wei-Lin Chang
2026-09-08 14:56     ` Vincent Donnefort
2026-08-03 10:09 ` [PATCH 19/20] KVM: arm64: Raise PKVM_HYP_REQ_SPLIT on guest to host sharing Vincent Donnefort
2026-08-03 10:09 ` [PATCH 20/20] KVM: arm64: Stage-2 huge mappings for protected VMs Vincent Donnefort
2026-09-07 18:31   ` Wei-Lin Chang
2026-09-07 18:41 ` [PATCH 00/20] Huge mapping support " Wei-Lin Chang

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=ap_i40-JQnXf4w4O@google.com \
    --to=vdonnefort@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=fuad.tabba@linux.dev \
    --cc=joey.gouly@arm.com \
    --cc=keirf@google.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=oupton@kernel.org \
    --cc=qperret@google.com \
    --cc=seiden@linux.ibm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=weilin.chang@arm.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 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).