From: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Suzuki K Poulose <suzuki.poulose@arm.com>,
will@kernel.org, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, steven.price@arm.com,
aneesh.kumar@kernel.org, oupton@kernel.org, gshan@redhat.com,
joey.gouly@arm.com, yuzenghui@huawei.com,
linux-coco@lists.linux.dev, gankulkarni@os.amperecomputing.com,
sdonthineni@nvidia.com, alpergun@google.com,
fj0570is@fujitsu.com, WeiLin.Chang@arm.com,
lpieralisi@kernel.org, enju.kohei@fujitsu.com,
jonathan.cameron@oss.qualcomm.com,
Sudeep Holla <sudeep.holla@kernel.org>
Subject: Re: [PATCH v23 00/14] KVM: arm64: CCA: Add basic plumbing for Realms
Date: Sat, 10 Oct 2026 10:19:07 +0100 [thread overview]
Message-ID: <865wz93oc4.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+EHjTymHEqCJco+d_yy33ndqPPsoZARhOQZ5A0Zwc5N3SV4Qg@mail.gmail.com>
On Fri, 09 Oct 2026 15:20:44 +0100,
Fuad Tabba <fuad.tabba@linux.dev> wrote:
>
> Hi Marc,
>
> On Fri, 09 Oct 2026 14:28:03 +0100, Marc Zyngier <maz@kernel.org> wrote:
> [...]
> > Of course, mmu.c is where the crap happens, so anyone with any interest
> > in this stuff being halfway sane, please review the conflict resolution.
>
> I went through the mmu.c resolution and it looks good to me. Unmap and
> aging are still no-ops for protected VMs, their abort handler is
> unchanged, and the default op keeps the tracked unmap for nested MMUs.
> Two minor things you might want to tidy up.
>
> kvm_vm_stage2_unmap_range() repeats the lockdep_assert_held_write()
> and WARN_ON(size & ~PAGE_MASK) that kvm_stage2_unmap_range() already
> does before calling the op.
>
> The VM_WARN_ON_ONCE() in kvm_vm_mem_abort() reads the ESR from the
> vcpu again, where next had moved these checks to s2fd->esr. It's the
> same result today, since the only caller handles a real abort, but
> this (and dropping the vcpu local) would keep it in line with the
> rest:
>
> VM_WARN_ON_ONCE(kvm_s2_fault_is_perm(s2fd) &&
> !esr_abt_is_write_fault(s2fd->esr) &&
> !kvm_s2_fault_is_exec(s2fd));
Thanks for looking. I've now applied this to the merge resolution.
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-10-10 9:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 7:35 [PATCH v23 00/14] KVM: arm64: CCA: Add basic plumbing for Realms Suzuki K Poulose
2026-10-07 7:35 ` [PATCH v23 01/14] KVM: arm64: protected VM: Handle user writes to CNTVCT_EL0/CNTPCT_EL0 Suzuki K Poulose
2026-10-07 10:43 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 02/14] KVM: arm64: Disable Steal time accounting for protected guests Suzuki K Poulose
2026-10-07 10:51 ` Fuad Tabba
2026-10-07 13:10 ` Suzuki K Poulose
2026-10-07 7:35 ` [PATCH v23 03/14] KVM: arm64: Include kvm_emulate.h in kvm/arm_psci.h Suzuki K Poulose
2026-10-07 11:00 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 04/14] KVM: arm64: Avoid including linux/kvm_host.h in kvm_pgtable.h Suzuki K Poulose
2026-10-07 7:35 ` [PATCH v23 05/14] KVM: arm64: Track the type of VM in kvm_arch Suzuki K Poulose
2026-10-07 7:35 ` [PATCH v23 06/14] KVM: arm64: Don't call vcpu_set_pauth_traps for pKVM host Suzuki K Poulose
2026-10-07 11:07 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 07/14] KVM: arm64: Refactor the vcpu_load to allow for VM specific callbacks Suzuki K Poulose
2026-10-07 11:12 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 08/14] KVM: arm64: Add vcpu load/put call backs for flavors Suzuki K Poulose
2026-10-07 11:18 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 09/14] KVM: arm64: Consolidate stage2 unmap range into kvm_stage2_unmap_range Suzuki K Poulose
2026-10-07 11:23 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 10/14] KVM: arm64: Add VM specific callback for S2 MMU operations Suzuki K Poulose
2026-10-07 11:38 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 11/14] KVM: arm64: Use a local kvm pointer in kvm_handle_guest_abort() Suzuki K Poulose
2026-10-07 7:35 ` [PATCH v23 12/14] KVM: arm64: Abstract out memory abort handling Suzuki K Poulose
2026-10-07 13:45 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 13/14] KVM: arm64: Mandate VGIC v3 for pKVM VMs and Realms Suzuki K Poulose
2026-10-07 13:45 ` Fuad Tabba
2026-10-08 8:51 ` Suzuki K Poulose
2026-10-08 11:17 ` Fuad Tabba
2026-10-07 7:35 ` [PATCH v23 14/14] KVM: arm64: Prevent unsupported vcpu features for VM types Suzuki K Poulose
2026-10-07 14:19 ` Fuad Tabba
2026-10-09 8:55 ` Marc Zyngier
2026-10-09 10:10 ` Fuad Tabba
2026-10-09 12:16 ` Marc Zyngier
2026-10-09 13:28 ` [PATCH v23 00/14] KVM: arm64: CCA: Add basic plumbing for Realms Marc Zyngier
2026-10-09 14:20 ` Fuad Tabba
2026-10-10 9:19 ` Marc Zyngier [this message]
2026-10-10 9:44 ` Suzuki K Poulose
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=865wz93oc4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=WeiLin.Chang@arm.com \
--cc=alpergun@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=enju.kohei@fujitsu.com \
--cc=fj0570is@fujitsu.com \
--cc=fuad.tabba@linux.dev \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gshan@redhat.com \
--cc=joey.gouly@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=oupton@kernel.org \
--cc=sdonthineni@nvidia.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@kernel.org \
--cc=suzuki.poulose@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