Linux-ARM-Kernel Archive on lore.kernel.org
 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 18/20] KVM: arm64: Add PKVM_HYP_REQ_SPLIT
Date: Tue, 8 Sep 2026 15:56:20 +0100	[thread overview]
Message-ID: <aqAiFGL4gm_j2HSv@google.com> (raw)
In-Reply-To: <b55i2bcuqp2wgadrj5a6nuc3t4o7ordrlcugxhhjw37k6hrlks@2h7ulmokholz>

[...]

> > +static void pkvm_mapping_split(struct pkvm_mapping *mapping, struct kvm_pgtable *pgt,
> > +			       struct list_head *spares)
> > +{
> > +	struct kvm *kvm = kvm_s2_mmu_to_kvm(pgt->mmu);
> > +	u64 nr_pages = mapping->nr_pages - 1;
> > +	gfn_t gfn = mapping->gfn + 1;
> > +	u64 pfn = mapping->pfn + 1;
> > +
> > +	lockdep_assert_held_write(&kvm->mmu_lock);
> > +
> > +	pkvm_mapping_remove(mapping, &pgt->pkvm_mappings);
> > +	mapping->nr_pages = 1;
> > +	pkvm_mapping_insert(mapping, &pgt->pkvm_mappings);
> > +
> > +	while (nr_pages--) {
> > +		struct pkvm_mapping *m;
> > +
> > +		if (WARN_ON(list_empty(spares)))
> > +			break;
> > +
> > +		m = list_first_entry(spares, struct pkvm_mapping, list);
> > +		list_del(&m->list);
> > +
> > +		m->nr_pages = 1;
> > +		m->gfn = gfn++;
> > +		m->pfn = pfn++;
> > +
> > +		pkvm_mapping_insert(m, &pgt->pkvm_mappings);
> > +	}
> > +}
> > +
> 
> I don't see anything wrong with this linked list approach, but have you
> considered just allocating an array of pointers for the allocated
> pkvm_mappings? The union in pkvm_mappings can be avoided.

I have, but it doesn't fit the reclaim path which frees pkvm_mapping as a single
object.

> 
> >  int pkvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm_s2_mmu *mmu,
> >  			     struct kvm_pgtable_mm_ops *mm_ops)
> >  {
> > @@ -619,6 +682,91 @@ int pkvm_pgtable_stage2_split(struct kvm_pgtable *pgt, u64 addr, u64 size, void
> >  	return -EINVAL;
> >  }
> >  
> > +/*
> > + * Splitting is only expected on the back of a guest HVC, while
> > + * pkvm_pgtable_stage2_split() can be called with dirty logging.
> > + */
> > +static int __pkvm_pgtable_stage2_split(struct kvm_vcpu *vcpu, phys_addr_t ipa, u64 size)
> > +{
> > +	struct kvm_hyp_memcache *mc = &vcpu->arch.pkvm_memcache;
> > +	struct kvm_pgtable *pgt = vcpu->arch.hw_mmu->pgt;
> > +	struct page **pages __free(kfree) = NULL;
> > +	struct mm_struct *mm = current->mm;
> > +	struct kvm_memory_slot *memslot;
> > +	struct pkvm_mapping *mapping;
> > +	struct kvm *kvm = vcpu->kvm;
> > +	struct list_head spares;
> > +	unsigned long hva;
> > +	bool writable;
> > +	u64 nr_pages;
> > +	int ret, idx;
> > +	gfn_t gfn;
> > +
> > +	if (WARN_ON(!kvm_vm_is_protected(kvm)))
> > +		return -EINVAL;
> > +
> > +	if (!IS_ALIGNED(ipa, PMD_SIZE) || size != PMD_SIZE)
> > +		return -EINVAL;
> > +
> > +	ret = topup_hyp_memcache(mc, 1);
> > +	if (ret)
> > +		return ret;
> > +
> > +	/* We already have 1 pin on the huge-page */
> > +	gfn = gpa_to_gfn(ipa) + 1;
> > +	nr_pages = (size / PAGE_SIZE) - 1;
> > +	pages = kmalloc_objs(struct page *, nr_pages);
> > +	if (!pages)
> > +		return -ENOMEM;
> > +
> > +	INIT_LIST_HEAD(&spares);
> > +	ret = pkvm_mapping_alloc_spares(&spares, nr_pages);
> > +	if (ret)
> > +		return ret;
> > +
> > +	idx = srcu_read_lock(&kvm->srcu);
> > +	memslot = gfn_to_memslot(kvm, gfn);
> > +	hva = gfn_to_hva_memslot_prot(memslot, gfn, &writable);
> > +	if (kvm_is_error_hva(hva) || !writable) {
> > +		ret = -EFAULT;
> > +		goto unlock_srcu;
> > +	}
> > +
> > +	mmap_read_lock(mm);
> > +	ret = pin_user_pages(hva, nr_pages, FOLL_HWPOISON | FOLL_LONGTERM | FOLL_WRITE, pages);
> 
> If I am not mistaken this is for getting additional pins only. hva walk
> and pages[] are just by-product.
> 
> Can we use folio_add_pins() here instead? Then I think we won't need
> pages[], the hva walk, and unpin_user_pages().

Good point, folio_add_pins() sounds way simpler.

-- 
Vincent

> 
> Thanks,
> Wei-Lin Chang
> 
> > +	mmap_read_unlock(mm);
> > +	if (ret != nr_pages) {
> > +		if (ret > 0)
> > +			unpin_user_pages(pages, ret);
> > +		ret = -EFAULT;
> > +		goto unlock_srcu;
> > +	}
> > +
> > +	write_lock(&kvm->mmu_lock);
> > +	mapping = pkvm_mapping_iter_first(&pgt->pkvm_mappings, ipa, ipa + size - 1);
> > +	if (!pkvm_mapping_can_split(mapping)) {
> > +		ret = -EINVAL;
> > +		goto unlock_mmu;
> > +	}
> > +
> > +	ret = kvm_call_hyp_nvhe(__pkvm_host_split_guest, gpa_to_gfn(ipa), size / PAGE_SIZE);
> > +	if (ret)
> > +		goto unlock_mmu;
> > +
> > +	pkvm_mapping_split(mapping, pgt, &spares);
> > +
> > +unlock_mmu:
> > +	write_unlock(&kvm->mmu_lock);
> > +	if (ret)
> > +		unpin_user_pages(pages, nr_pages);
> > +
> > +unlock_srcu:
> > +	srcu_read_unlock(&kvm->srcu, idx);
> > +	pkvm_mapping_free_spares(&spares);
> > +
> > +	return ret;
> > +}
> > +
> 
> [...]
> 


  reply	other threads:[~2026-09-08 14:56 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
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 [this message]
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=aqAiFGL4gm_j2HSv@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