From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu
Cc: James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Eric Auger <eric.auger@redhat.com>,
Hector Martin <marcan@marcan.st>,
Mark Rutland <mark.rutland@arm.com>,
kernel-team@android.com
Subject: Re: [PATCH v3 0/9] KVM: arm64: Initial host support for the Apple M1
Date: Wed, 12 May 2021 17:22:43 +0100 [thread overview]
Message-ID: <3a21048a-a084-a884-7a3d-9b283f8b15ed@arm.com> (raw)
In-Reply-To: <20210510134824.1910399-1-maz@kernel.org>
Hi Marc,
On 5/10/21 2:48 PM, Marc Zyngier wrote:
> This is a new version of the series previously posted at [2], reworking
> the vGIC and timer code to cope with the M1 braindead^Wamusing nature.
>
> Hardly any change this time around, mostly rebased on top of upstream
> now that the dependencies have made it in.
>
> Tested with multiple concurrent VMs running from an initramfs.
>
> * From v2:
> - Rebased on 5.13-rc1
> - Fixed a couple of nits in the GIC registration code
>
> * From v1 [1]:
> - Rebased on Hector's v4 posting[0]
> - Dropped a couple of patches that have been merged in the above series
> - Fixed irq_ack callback on the timer path
>
> [0] https://lore.kernel.org/r/20210402090542.131194-1-marcan@marcan.st
> [1] https://lore.kernel.org/r/20210316174617.173033-1-maz@kernel.org
> [2] https://lore.kernel.org/r/20210403112931.1043452-1-maz@kernel.org
This looks interesting and I want to take a look. For now, I can only review the
series, but maybe at some point I'll take the leap and try to run Linux on my
Macbook Air.
Can I find something resembling a specification for the Apple interrupt
controller, or the only available documentation is in the Linux driver and patches
on the mailing list?
Thanks,
Alex
>
> Marc Zyngier (9):
> irqchip/gic: Split vGIC probing information from the GIC code
> KVM: arm64: Handle physical FIQ as an IRQ while running a guest
> KVM: arm64: vgic: Be tolerant to the lack of maintenance interrupt
> KVM: arm64: vgic: Let an interrupt controller advertise lack of HW
> deactivation
> KVM: arm64: vgic: move irq->get_input_level into an ops structure
> KVM: arm64: vgic: Implement SW-driven deactivation
> KVM: arm64: timer: Refactor IRQ configuration
> KVM: arm64: timer: Add support for SW-based deactivation
> irqchip/apple-aic: Advertise some level of vGICv3 compatibility
>
> arch/arm64/kvm/arch_timer.c | 161 +++++++++++++++++++++----
> arch/arm64/kvm/hyp/hyp-entry.S | 6 +-
> arch/arm64/kvm/vgic/vgic-init.c | 34 +++++-
> arch/arm64/kvm/vgic/vgic-v2.c | 19 ++-
> arch/arm64/kvm/vgic/vgic-v3.c | 19 ++-
> arch/arm64/kvm/vgic/vgic.c | 14 +--
> drivers/irqchip/irq-apple-aic.c | 8 ++
> drivers/irqchip/irq-gic-common.c | 13 --
> drivers/irqchip/irq-gic-common.h | 2 -
> drivers/irqchip/irq-gic-v3.c | 6 +-
> drivers/irqchip/irq-gic.c | 6 +-
> include/kvm/arm_vgic.h | 41 +++++--
> include/linux/irqchip/arm-gic-common.h | 25 +---
> include/linux/irqchip/arm-vgic-info.h | 43 +++++++
> 14 files changed, 291 insertions(+), 106 deletions(-)
> create mode 100644 include/linux/irqchip/arm-vgic-info.h
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-12 16:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 13:48 [PATCH v3 0/9] KVM: arm64: Initial host support for the Apple M1 Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 1/9] irqchip/gic: Split vGIC probing information from the GIC code Marc Zyngier
2021-05-18 16:51 ` Alexandru Elisei
2021-05-10 13:48 ` [PATCH v3 2/9] KVM: arm64: Handle physical FIQ as an IRQ while running a guest Marc Zyngier
2021-05-20 17:46 ` Alexandru Elisei
2021-05-10 13:48 ` [PATCH v3 3/9] KVM: arm64: vgic: Be tolerant to the lack of maintenance interrupt Marc Zyngier
2021-05-10 16:19 ` Mark Rutland
2021-05-10 17:44 ` Marc Zyngier
2021-05-11 11:13 ` Mark Rutland
2021-05-10 13:48 ` [PATCH v3 4/9] KVM: arm64: vgic: Let an interrupt controller advertise lack of HW deactivation Marc Zyngier
2021-05-21 17:01 ` Alexandru Elisei
2021-05-24 17:17 ` Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 5/9] KVM: arm64: vgic: move irq->get_input_level into an ops structure Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 6/9] KVM: arm64: vgic: Implement SW-driven deactivation Marc Zyngier
2021-05-24 16:53 ` Alexandru Elisei
2021-05-24 17:43 ` Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 7/9] KVM: arm64: timer: Refactor IRQ configuration Marc Zyngier
2021-05-14 12:46 ` Zenghui Yu
2021-05-24 17:48 ` Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 8/9] KVM: arm64: timer: Add support for SW-based deactivation Marc Zyngier
2021-05-10 13:48 ` [PATCH v3 9/9] irqchip/apple-aic: Advertise some level of vGICv3 compatibility Marc Zyngier
2021-05-12 16:22 ` Alexandru Elisei [this message]
2021-05-12 16:33 ` [PATCH v3 0/9] KVM: arm64: Initial host support for the Apple M1 Marc Zyngier
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=3a21048a-a084-a884-7a3d-9b283f8b15ed@arm.com \
--to=alexandru.elisei@arm.com \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marcan@marcan.st \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).