From: Oliver Upton <oupton@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 changes for 7.3, take #3
Date: Thu, 1 Oct 2026 00:09:27 -0700 [thread overview]
Message-ID: <ar4HJw9zON0mG2_t@kernel.org> (raw)
Hi Paolo,
As promised, the patches I was waiting on have baked and we have another
batch of fixes for 7.3. Continuing with the trend, the VGIC is getting
some additional attention, particularly on the handling of a vCPU's AP
list.
Unless there's something truly horrible brewing in the next couple of
weeks, I expect this to be the last fixes pull for 7.3 with Marc taking
over the tree for 7.4.
Please pull.
Thanks,
Oliver
The following changes since commit bc502b86a3cfd89e6740f877c90d06b02635935d:
KVM: arm64: Use stage-1 leaf size for VM_PFNMAP (2026-09-30 11:03:16 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git/ tags/kvmarm-fixes-7.3-2
for you to fetch changes up to bc502b86a3cfd89e6740f877c90d06b02635935d:
KVM: arm64: Use stage-1 leaf size for VM_PFNMAP (2026-09-30 11:03:16 -0700)
----------------------------------------------------------------
KVM/arm64 fixes for 7.3, round #2
- Take a reference on the last IRQ loaded into an LR to prevent it
from being freed while running the guest (Marc Zyngier)
- Ensure that the ITS MOVALL command only affects LPIs that were
previously affined to the source redistributor (Marc Zyngier)
- Fix + test for honoring the host's trap configuration when running
non-protected VMs while KVM is in protected mode (Fuad Tabba)
- Use the host stage-1 mapping granularity for VM_PFNMAP mappings at
stage-2 (Mostafa Saleh)
----------------------------------------------------------------
next reply other threads:[~2026-10-01 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 7:09 Oliver Upton [this message]
2026-10-01 17:22 ` [GIT PULL] KVM/arm64 changes for 7.3, take #3 Paolo Bonzini
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=ar4HJw9zON0mG2_t@kernel.org \
--to=oupton@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.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