Linux KVM/arm64 development list
 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 04/20] KVM: arm64: Use block-level annotations when setting up the host stage-2
Date: Tue, 8 Sep 2026 11:18:01 +0100	[thread overview]
Message-ID: <ap_g2eb1sn1Mp_Qd@google.com> (raw)
In-Reply-To: <n2cker7zphcsacuck5ovwtj6k622ykpadg6njs2qirhqxj5keh@ub2dnnarnmmm>

On Mon, Sep 07, 2026 at 03:37:56PM +0100, Wei-Lin Chang wrote:
> On Mon, Aug 03, 2026 at 11:08:48AM +0100, Vincent Donnefort wrote:
> 
> [...]
> 
> > +static int fix_host_ownership_walker(const struct kvm_pgtable_visit_ctx *ctx,
> > +				     enum kvm_pgtable_walk_flags visit)
> > +{
> > +	struct fix_host_ownership_data *data = ctx->arg;
> > +	enum kvm_pgtable_prot prot = 0;
> > +	phys_addr_t phys = 0;
> > +	int ret;
> > +
> > +	if (kvm_pte_valid(ctx->old))
> > +		prot = kvm_pgtable_hyp_pte_prot(ctx->old);
> > +
> > +	if (!prot) {
> > +		/* Unchanged region */
> > +		if (!data->prot)
> > +			return 0;
> > +
> > +		goto apply_ownership;
> > +	}
> > +
> > +	phys = kvm_pte_to_phys(ctx->old);
> > +	if (!addr_is_memory(phys))
> > +		return -EINVAL;
> > +
> > +	/* We already know phys is contiguous as we walk the linear map */
> > +
> > +	if (prot != data->prot)
> > +		goto apply_ownership;
> > +
> > +	/* Accumulate in the current region */
> > +	data->size += kvm_granule_size(ctx->level);
> > +
> > +	return 0;
> > +
> > +apply_ownership:
> > +	ret = __fix_host_ownership(data);
> > +	if (ret)
> > +		return ret;
> > +
> > +	data->phys = phys;
> > +	data->size = kvm_granule_size(ctx->level);
> > +	data->prot = prot;
> > +
> > +	return 0;
> > +}
> 
> I think this function can be simplified, if we check phys first:
> 
> static int fix_host_ownership_walker(const struct kvm_pgtable_visit_ctx *ctx,
> 				     enum kvm_pgtable_walk_flags visit)
> {
> 	struct fix_host_ownership_data *data = ctx->arg;
> 	enum kvm_pgtable_prot prot = 0;
> 	phys_addr_t phys = 0;
> 	int ret;
> 
> 	if (kvm_pte_valid(ctx->old))
> 		prot = kvm_pgtable_hyp_pte_prot(ctx->old);
> 
> 	if (prot) {
> 		phys = kvm_pte_to_phys(ctx->old);
> 		if (!addr_is_memory(phys))
> 			return -EINVAL;
> 	}
> 
> 	if (prot != data->prot) {
> 		ret = __fix_host_ownership(data);
> 		if (ret)
> 			return ret;
> 
> 		data->phys = phys;
> 		data->size = kvm_granule_size(ctx->level);
> 		data->prot = prot;
> 	} else {
> 		data->size += kvm_granule_size(ctx->level);
> 	}
> 	return 0;
> }
> 
> Did I miss anything?
> 
> Thanks,
> Wei-Lin Chang

Indeed, I think it's my:

   if (prot != data->prot)
       goto apply_ownership

that is clumsy. With

  if (prot == data->prot) {
      data->size += kvm_granule_size();
      return 0;
  }

(which is basically what you suggested)

I can get rid of the label.

-- 
Vincent

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

Thread overview: 55+ 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-08-03 10:31   ` sashiko-bot
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:40   ` sashiko-bot
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 [this message]
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:26   ` sashiko-bot
2026-08-03 10:08 ` [PATCH 08/20] KVM: arm64: Add a range to __pkvm_host_reclaim_page_guest() Vincent Donnefort
2026-08-03 10:28   ` sashiko-bot
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-08-03 10:48   ` sashiko-bot
2026-09-07 10:13     ` 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
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:46   ` sashiko-bot
2026-08-03 10:09 ` [PATCH 16/20] KVM: arm64: Add __pkvm_host_split_guest HVC Vincent Donnefort
2026-08-03 10:54   ` sashiko-bot
2026-09-07 10:14     ` 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 11:01   ` sashiko-bot
2026-08-03 10:09 ` [PATCH 18/20] KVM: arm64: Add PKVM_HYP_REQ_SPLIT Vincent Donnefort
2026-08-03 10:54   ` sashiko-bot
2026-09-07 10:23     ` Vincent Donnefort
2026-09-08 10:35       ` Wei-Lin Chang
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 11:02   ` sashiko-bot
2026-09-07 10:26     ` Vincent Donnefort
2026-08-03 10:09 ` [PATCH 20/20] KVM: arm64: Stage-2 huge mappings for protected VMs Vincent Donnefort
2026-08-03 11:04   ` sashiko-bot
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_g2eb1sn1Mp_Qd@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