All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, broonie@kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 v3 02/11] KVM: arm64: Always start with clearing SVE flag on load
Date: Thu, 10 Apr 2025 11:53:32 -0400	[thread overview]
Message-ID: <20250410112437-6c51badd1fa7bb35@stable.kernel.org> (raw)
In-Reply-To: <20250408-stable-sve-5-15-v3-2-ca9a6b850f55@kernel.org>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
ℹ️ This is part 02/11 of a series
❌ Build failures detected

The upstream commit SHA1 provided is correct: d52d165d67c5aa26c8c89909003c94a66492d23d

WARNING: Author mismatch between patch and upstream commit:
Backport author: Mark Brown<broonie@kernel.org>
Commit author: Marc Zyngier<maz@kernel.org>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  d52d165d67c5a ! 1:  ab39b2accf324 KVM: arm64: Always start with clearing SVE flag on load
    @@ Metadata
      ## Commit message ##
         KVM: arm64: Always start with clearing SVE flag on load
     
    +    [ Upstream commit d52d165d67c5aa26c8c89909003c94a66492d23d ]
    +
         On each vcpu load, we set the KVM_ARM64_HOST_SVE_ENABLED
         flag if SVE is enabled for EL0 on the host. This is used to restore
         the correct state on vpcu put.
    @@ Commit message
         Cc: stable@vger.kernel.org
         Reviewed-by: Mark Brown <broonie@kernel.org>
         Link: https://lore.kernel.org/r/20220528113829.1043361-2-maz@kernel.org
    +    Signed-off-by: Mark Brown <broonie@kernel.org>
     
      ## arch/arm64/kvm/fpsimd.c ##
     @@ arch/arm64/kvm/fpsimd.c: void kvm_arch_vcpu_load_fp(struct kvm_vcpu *vcpu)
    @@ arch/arm64/kvm/fpsimd.c: void kvm_arch_vcpu_load_fp(struct kvm_vcpu *vcpu)
     +	vcpu->arch.flags &= ~KVM_ARM64_HOST_SVE_ENABLED;
      	if (read_sysreg(cpacr_el1) & CPACR_EL1_ZEN_EL0EN)
      		vcpu->arch.flags |= KVM_ARM64_HOST_SVE_ENABLED;
    - 
    + }
---

NOTE: These results are for this patch alone. Full series testing will be
performed when all parts are received.

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y        |  Success    |  Failed    |

Build Errors:
Build error:
    Segmentation fault
    make: *** [Makefile:1231: vmlinux] Error 139
    make: Target '__all' not remade because of errors.

  reply	other threads:[~2025-04-10 15:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 18:09 [PATCH 5.15 v3 00/11] KVM: arm64: Backport of SVE fixes to v5.15 Mark Brown
2025-04-08 18:09 ` [PATCH 5.15 v3 01/11] KVM: arm64: Get rid of host SVE tracking/saving Mark Brown
2025-04-10 15:54   ` Sasha Levin
2025-04-22  6:45   ` Patch "KVM: arm64: Get rid of host SVE tracking/saving" has been added to the 5.15-stable tree gregkh
2025-04-08 18:09 ` [PATCH 5.15 v3 02/11] KVM: arm64: Always start with clearing SVE flag on load Mark Brown
2025-04-10 15:53   ` Sasha Levin [this message]
2025-04-10 16:11     ` Mark Brown
2025-04-10 16:43       ` Sasha Levin
2025-04-10 16:46         ` Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Always start with clearing SVE flag on load" has been added to the 5.15-stable tree gregkh
2025-04-08 18:09 ` [PATCH 5.15 v3 03/11] KVM: arm64: Discard any SVE state when entering KVM guests Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Discard any SVE state when entering KVM guests" has been added to the 5.15-stable tree gregkh
2025-04-08 18:09 ` [PATCH 5.15 v3 04/11] arm64/fpsimd: Track the saved FPSIMD state type separately to TIF_SVE Mark Brown
2025-04-22  6:45   ` Patch "arm64/fpsimd: Track the saved FPSIMD state type separately to TIF_SVE" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 05/11] arm64/fpsimd: Have KVM explicitly say which FP registers to save Mark Brown
2025-04-22  6:45   ` Patch "arm64/fpsimd: Have KVM explicitly say which FP registers to save" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 06/11] arm64/fpsimd: Stop using TIF_SVE to manage register saving in KVM Mark Brown
2025-04-22  6:45   ` Patch "arm64/fpsimd: Stop using TIF_SVE to manage register saving in KVM" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 07/11] KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 08/11] KVM: arm64: Remove host FPSIMD saving for non-protected KVM Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Remove host FPSIMD saving for non-protected KVM" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 09/11] KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 10/11] KVM: arm64: Calculate cptr_el2 traps on activating traps Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Calculate cptr_el2 traps on activating traps" has been added to the 5.15-stable tree gregkh
2025-04-08 18:10 ` [PATCH 5.15 v3 11/11] KVM: arm64: Eagerly switch ZCR_EL{1,2} Mark Brown
2025-04-22  6:45   ` Patch "KVM: arm64: Eagerly switch ZCR_EL{1,2}" has been added to the 5.15-stable tree gregkh

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=20250410112437-6c51badd1fa7bb35@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=broonie@kernel.org \
    --cc=stable@vger.kernel.org \
    /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.