From: Marc Zyngier <maz@kernel.org>
To: catalin.marinas@arm.com, oupton@kernel.org, fuad.tabba@linux.dev,
will@kernel.org, Sebastian Ene <sebastianene@google.com>
Cc: joey.gouly@arm.com, korneld@google.com, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, android-kvm@google.com,
mrigendra.chaubey@gmail.com, perlarsen@google.com,
suzuki.poulose@arm.com, vdonnefort@google.com,
yuzenghui@huawei.com
Subject: Re: [PATCH v9 0/7] KVM: arm64: Forward FFA_NOTIFICATION* calls to TrustZone
Date: Mon, 14 Sep 2026 13:04:11 +0100 [thread overview]
Message-ID: <178938739472.3215146.2334012997642467231.b4-ty@b4> (raw)
In-Reply-To: <20260907171930.4037166-1-sebastianene@google.com>
On Mon, 07 Sep 2026 17:19:22 +0000, Sebastian Ene wrote:
> Remove the FFA_NOTIFICATION* calls from the blocklist used by the pKVM
> FF-A proxy. This restriction was preventing the use of asynchronous
> signaling mechanisms defined by the Arm FF-A specification to
> communicate with the secure services.
> While these calls are markes as optional, there is no reason why the
> hypervisor proxy would block them because:
>
> [...]
Applied to next, thanks!
[1/7] KVM: arm64: Forward FFA_NOTIFICATION_BITMAP calls to Trustzone
commit: 5224e6f027ee8ba0ebc825ce80c45c0a7b716ff3
[2/7] KVM: arm64: Support FFA_NOTIFICATION_BIND in host handler
commit: 85e44f7eeaec6c303fd6cb2d775cbfecebeb6802
[3/7] KVM: arm64: Support FFA_NOTIFICATION_UNBIND in host handler
commit: 69fde06ec15936551f97e67c7bdc93427e8b08a6
[4/7] KVM: arm64: Support FFA_NOTIFICATION_SET in host handler
commit: e3ba9aec202ae2911ae1166654e21bbbd41ff29d
[5/7] KVM: arm64: Support FFA_NOTIFICATION_GET in host handler
commit: 88180874ee3474ce866a00297aa238c64fc2ea85
[6/7] KVM: arm64: Support FFA_NOTIFICATION_INFO_GET in host handler
commit: 0aa3b20bbb2bf165d32fd802204a558fa461b130
[7/7] KVM: arm64: Enforce strict SBZ checks in the FF-A proxy
commit: 3e9df0b0ebd57e42b43842c996271275588660a2
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-09-14 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 17:19 Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 1/7] KVM: arm64: Forward FFA_NOTIFICATION_BITMAP calls to Trustzone Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 2/7] KVM: arm64: Support FFA_NOTIFICATION_BIND in host handler Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 3/7] KVM: arm64: Support FFA_NOTIFICATION_UNBIND " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 4/7] KVM: arm64: Support FFA_NOTIFICATION_SET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 5/7] KVM: arm64: Support FFA_NOTIFICATION_GET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 6/7] KVM: arm64: Support FFA_NOTIFICATION_INFO_GET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 7/7] KVM: arm64: Enforce strict SBZ checks in the FF-A proxy Sebastian Ene
2026-09-14 12:04 ` Marc Zyngier [this message]
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=178938739472.3215146.2334012997642467231.b4-ty@b4 \
--to=maz@kernel.org \
--cc=android-kvm@google.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=korneld@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrigendra.chaubey@gmail.com \
--cc=oupton@kernel.org \
--cc=perlarsen@google.com \
--cc=sebastianene@google.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.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
all inboxes | Powered by JetHome®