From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 93A4B3B42E3 for ; Wed, 29 Jul 2026 12:13:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.72 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785327212; cv=none; b=rGldhwAwwnw3AE/EjB7+pXIEKrQZ0jh4NXOlYaBvpuP5AAw1Wu7TFRy7/Mm0/trDoYhXTqiqqoDY2m4zLl8PQlmqUrhFvBjdDf8XMV+zD6TihA+sk67TRIJ5YIDEPu8bXraC9C0UwZ8sCc0eI1nhuj10YJxIiossDRV9kUcKWcg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785327212; c=relaxed/simple; bh=FJKTe7w5oX4sNy96KRtCt95pc41IKsrn54ZS4gFoGX0=; h=Date:Mime-Version:Message-ID:Subject:From:To:Cc:Content-Type; b=K8ymOdxN/kDZavGQyKd/MKZnc/9T8aVBOnlI8JKxWAWgMKbTyv7wbPqfZAG7r9idFQkl2bwGCiG2mTMiMGLuxgLCKNyXK2ZL9iO24P7g/Y5lV59CCslv/cHVz6MjpMHLSXrGNgjx6GrciadWSzOYwg71w9x1jStV7PF9F4z6wTI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--sebastianene.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=GFAMcpqT; arc=none smtp.client-ip=209.85.221.72 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--sebastianene.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="GFAMcpqT" Received: by mail-wr1-f72.google.com with SMTP id ffacd0b85a97d-474170b59dfso687218f8f.3 for ; Wed, 29 Jul 2026 05:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1785327209; x=1785932009; darn=vger.kernel.org; h=content-type:cc:to:from:subject:message-id:mime-version:date:from :to:cc:subject:date:message-id:reply-to:content-type; bh=BAmImkqu1SFwL8NSZDIz5I9w1IjXZHC7hoAV+KdJnaA=; b=GFAMcpqTW+a29nn2GlQ3uGiw37aCbxDHpC1LAhXICX9bwjBYHCujdYmxcxTLFOurq5 NPISPgQ5jbvf3+kG6cpLqmXgbgw8S8CgzosKpKfTnMoYqHYMyF6BhMhuAfLqJyj2S1MV 7mIh8pjOyuWL3hg7EguJA+nBpbwnWjnTrC6Fb25dOT3OPXPg6Uk+nPEGnyXAUrEJZgpv MrehvlJPUWzCKjV3Bq/kq3v6YbSNx+vc4ghYDjK/3t+7XZeLzL77eBr2OISNICSOCbGz SLfZSpxxTOsaHg+HPjtjpNugHZGvYfu/ZSFXryF0tey05rgfOBlDVxaEpjwribqv8xLS TsVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785327209; x=1785932009; h=content-type:cc:to:from:subject:message-id:mime-version:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=BAmImkqu1SFwL8NSZDIz5I9w1IjXZHC7hoAV+KdJnaA=; b=tQaQo6xDbJ17mSUjprKMH4iyRpHzf/NApTx5WJn4mNRbHNZzda/9qfZsQsXdUgvSpr iXUHI3tlXuPGmClh9tX35peFv738RQ+L/Yc5ztV0valOTve3iX0Cr2KN/76MJsvOiFnf EYyHdejkWEeUMN0Swz7UFrzwVl8cT5w3HWJmCDPdQdQvOwcV9/m8vAgUU57rCMxtNqvP XUHETpJoGWvEOZi2O1BkRSSGdJ0/5qNm3Htn//nhMQynOfwT4CKjWI0mtByaNs8C4gIv acGKpOK/vbcqORGflTOS7M6X3LjcZ0jvxRUfnL8vOiYrrSUCuoCZG9CrtNt4TUfTmmoh wo4g== X-Forwarded-Encrypted: i=1; AHgh+Roh3JPAoWN/VlqLrPNVvA+bQYTCaqO3BGFHExncLEqDwb8R0ohAeCOy1c5tg9KkwMNZZjQGLXyA33g2mrg=@vger.kernel.org X-Gm-Message-State: AOJu0YxzAJ2RwVHicbNMF/voULIo/gkDFy+xU3Jq+roVhtbTu3lXMUUm y7RR5ne3PaUF1HSx9k8CT6ApudestztNU+9hdZqZm0QwZkpoWQ/vXm4sFO1BsPovAAK41vWLMQX 7OTOxVv6LeNb3C89SoGVu9zS3KOVY5g== X-Received: from wmbjj19.prod.google.com ([2002:a05:600c:6a13:b0:495:54c7:8c97]) (user=sebastianene job=prod-delivery.src-stubby-dispatcher) by 2002:a05:600c:4eca:b0:493:e460:1f6 with SMTP id 5b1f17b1804b1-496c60ba34amr69095735e9.0.1785327208512; Wed, 29 Jul 2026 05:13:28 -0700 (PDT) Date: Wed, 29 Jul 2026 12:13:00 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 X-Mailer: git-send-email 2.55.0.487.gaf234c4eb3-goog Message-ID: <20260729121306.1519473-2-sebastianene@google.com> Subject: [PATCH v8 0/7] KVM: arm64: Forward FFA_NOTIFICATION* calls to TrustZone From: Sebastian Ene To: catalin.marinas@arm.com, maz@kernel.org, oupton@kernel.org, fuad.tabba@linux.dev, will@kernel.org 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, sebastianene@google.com, suzuki.poulose@arm.com, vdonnefort@google.com, yuzenghui@huawei.com Content-Type: text/plain; charset="UTF-8" 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: 1. Host is the Sole Non-Secure Endpoint: The Host operates as the only Non-Secure VM ID (VM ID 0) recognized by the Secure World. Because all forwarded notifications are inherently attributed to the Host by the SPMC, there is no risk of VM ID spoofing originating from the Normal World. 2. No Memory Pointers or Addresses: The FFA_NOTIFICATION_* ABIs operate strictly via register-based parameters, passing only VM IDs, VCPU IDs, flags, and bitmaps. Because these calls do not contain memory addresses, offsets, or pointers, forwarding them doesn't pose a risk of memory-based confused deputy attack (e.g., tricking the SPMC into overwriting protected memory). The pKVM proxy behaves as a relayer and it doesn't currently have its own FF-A ID(only the host has the ID 0). The behavior of the setup flow is covered by the spec in the: '10.9 Notification support without a Hypervisor'. While at it, enforce the MBZ/SBZ fields defined by the spec to prevent odd behavior when a new version starts making use of the reserved registers. --- v8: - rebased on 7.2-rc3 - no other changes Changes in v7: - rebased on 7.2-rc1 - collected the Ack from Will - check for major version as well when doing the SBZ/MBZ enforcement Changes in v6: - applied Will's feedback and re-ordered the patch series so that we apply the MBZ enforcement at the end of the series - update ffa_check_unused_args_sbz so that we take into account the FF-A version because the spec changed the list of unused parameter registers for 64-bit SMCs from v1.1 to v1.2 Changes in v5: - handle 32-bit smc variants correctly when doing the MBZ enforcement - add check for FFA_FEATURES - handle missing FFA_FN64_NOTIFICATION_INFO_GET - collected the Review tags from Vincent, thank you Changes in v4: - previous series(v3) had serious issues with the patch number and it appeared like it used a mixed bag from v2 as well. Resend this to restore the correct order of the patches. - fix strict check in ffa_check_unused_args_sbz and make it "<= 17" - check the receiver endpoint Id in FFA_NOTIFICATION_BIND/FFA_NOTIFICATION_UNBIND instead of the sender - use hyp_smccc_1_2_smc all along - check the receiver endpoit Id when doing FFA_NOTIFICATION_GET Changes in v3: - applied Will's suggestion to use the introduced method ffa_check_unused_args_sbz for existing calls and added a new patch in the beggining of the series to do this. - merged the handling of FFA_NOTIFICATION_BITMAP_CREATE/FFA_NOTIFICATION_BITMAP_DESTROY into one patch as Vincent suggested and create one handler for both. Changes in v2: - enforce the MBZ/SBZ fields - split the calls into separate patches - rebase on 7.1-rc7 v7: https://lore.kernel.org/all/20260629093558.2425257-1-sebastianene@google.com/ v6: https://lore.kernel.org/all/20260626074545.433234-1-sebastianene@google.com/ v5: https://lore.kernel.org/all/20260623115354.632361-1-sebastianene@google.com/ v4: https://lore.kernel.org/all/20260616154149.2763214-1-sebastianene@google.com/ v3: https://lore.kernel.org/all/20260616105417.2578670-1-sebastianene@google.com/ v2: https://lore.kernel.org/all/20260608165549.1479409-1-sebastianene@google.com/ v1: https://lore.kernel.org/all/20260501114447.2389222-2-sebastianene@google.com/ Sebastian Ene (7): KVM: arm64: Forward FFA_NOTIFICATION_BITMAP calls to Trustzone KVM: arm64: Support FFA_NOTIFICATION_BIND in host handler KVM: arm64: Support FFA_NOTIFICATION_UNBIND in host handler KVM: arm64: Support FFA_NOTIFICATION_SET in host handler KVM: arm64: Support FFA_NOTIFICATION_GET in host handler KVM: arm64: Support FFA_NOTIFICATION_INFO_GET in host handler KVM: arm64: Enforce strict SBZ checks in the FF-A proxy arch/arm64/kvm/hyp/nvhe/ffa.c | 220 ++++++++++++++++++++++++++++++++-- 1 file changed, 212 insertions(+), 8 deletions(-) -- 2.55.0.487.gaf234c4eb3-goog