All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>, Eric Auger <eauger@redhat.com>,
	Ben Horgan <ben.horgan@arm.com>
Subject: Re: [PATCH v5 0/6] KVM: arm64: Allow userspace to write GICD_TYPER2.nASSGIcap
Date: Fri, 25 Jul 2025 17:55:42 +0100	[thread overview]
Message-ID: <86a54s8b1t.wl-maz@kernel.org> (raw)
In-Reply-To: <20250724062805.2658919-1-oliver.upton@linux.dev>

On Thu, 24 Jul 2025 07:27:59 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
> 
> v4 -> v5:
>  - Fix polarity of nASSGIreq masking (Ben)
>  - Explicitly call out some subtle changes made in changelogs (Eric)
>  - Avoid open-coding irq_is_ppi() (Eric)
> 
> Oliver Upton (4):
>   KVM: arm64: Disambiguate support for vSGIs v. vLPIs
>   KVM: arm64: vgic-v3: Consolidate MAINT_IRQ handling
>   KVM: arm64: vgic-v3: Allow access to GICD_IIDR prior to initialization
>   Documentation: KVM: arm64: Describe VGICv3 registers writable pre-init
> 
> Raghavendra Rao Ananta (2):
>   KVM: arm64: vgic-v3: Allow userspace to write GICD_TYPER2.nASSGIcap
>   KVM: arm64: selftests: Add test for nASSGIcap attribute
> 
>  .../virt/kvm/devices/arm-vgic-v3.rst          | 17 +++++
>  arch/arm64/kvm/vgic/vgic-init.c               | 21 +++---
>  arch/arm64/kvm/vgic/vgic-kvm-device.c         | 70 ++++++++++++-------
>  arch/arm64/kvm/vgic/vgic-mmio-v3.c            | 33 +++++++--
>  arch/arm64/kvm/vgic/vgic-v4.c                 |  4 +-
>  arch/arm64/kvm/vgic/vgic.c                    |  4 +-
>  arch/arm64/kvm/vgic/vgic.h                    |  8 +++
>  include/kvm/arm_vgic.h                        |  3 +
>  tools/testing/selftests/kvm/arm64/vgic_init.c | 42 ++++++++++-
>  9 files changed, 150 insertions(+), 52 deletions(-)
> 
> 
> base-commit: 86731a2a651e58953fc949573895f2fa6d456841

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2025-07-25 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  6:27 [PATCH v5 0/6] KVM: arm64: Allow userspace to write GICD_TYPER2.nASSGIcap Oliver Upton
2025-07-24  6:28 ` [PATCH v5 1/6] KVM: arm64: Disambiguate support for vSGIs v. vLPIs Oliver Upton
2025-07-24  6:28 ` [PATCH v5 2/6] KVM: arm64: vgic-v3: Consolidate MAINT_IRQ handling Oliver Upton
2025-07-24  6:28 ` [PATCH v5 3/6] KVM: arm64: vgic-v3: Allow access to GICD_IIDR prior to initialization Oliver Upton
2025-07-24  6:28 ` [PATCH v5 4/6] KVM: arm64: vgic-v3: Allow userspace to write GICD_TYPER2.nASSGIcap Oliver Upton
2025-07-25 22:53   ` Raghavendra Rao Ananta
2025-07-26 15:45     ` Oliver Upton
2025-07-24  6:28 ` [PATCH v5 5/6] KVM: arm64: selftests: Add test for nASSGIcap attribute Oliver Upton
2025-07-24  6:28 ` [PATCH v5 6/6] Documentation: KVM: arm64: Describe VGICv3 registers writable pre-init Oliver Upton
2025-07-25 16:55 ` Marc Zyngier [this message]
2025-07-28 16:07 ` [PATCH v5 0/6] KVM: arm64: Allow userspace to write GICD_TYPER2.nASSGIcap Eric Auger
2025-07-28 17:15 ` Oliver Upton

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=86a54s8b1t.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ben.horgan@arm.com \
    --cc=eauger@redhat.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.