From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: stable@vger.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 12:43:28 -0400 [thread overview]
Message-ID: <Z_f1MGoJ6T4m77wY@lappy> (raw)
In-Reply-To: <05817c61-13dd-42d4-86f8-4cf76ba1df4b@sirena.org.uk>
On Thu, Apr 10, 2025 at 05:11:06PM +0100, Mark Brown wrote:
>On Thu, Apr 10, 2025 at 11:53:32AM -0400, Sasha Levin wrote:
>
>> Summary of potential issues:
>> ℹ️ This is part 02/11 of a series
>> ❌ Build failures detected
>
>> Build Errors:
>> Build error:
>> Segmentation fault
>> make: *** [Makefile:1231: vmlinux] Error 139
>> make: Target '__all' not remade because of errors.
>
>This looks like some sort of infrastructure issue with the linker
>crashing? What configuration was this trying to build and with what
>toolchain? My own per-patch build tests were successful.
You're right - sorry about that.
The cooling setup on my build server started to fail, which caused
sporadic failures during heavy load.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-04-10 16:43 UTC|newest]
Thread overview: 17+ 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-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
2025-04-10 16:11 ` Mark Brown
2025-04-10 16:43 ` Sasha Levin [this message]
2025-04-10 16:46 ` Mark Brown
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-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-08 18:10 ` [PATCH 5.15 v3 05/11] arm64/fpsimd: Have KVM explicitly say which FP registers to save Mark Brown
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-08 18:10 ` [PATCH 5.15 v3 07/11] KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state Mark Brown
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-08 18:10 ` [PATCH 5.15 v3 09/11] KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN Mark Brown
2025-04-08 18:10 ` [PATCH 5.15 v3 10/11] KVM: arm64: Calculate cptr_el2 traps on activating traps Mark Brown
2025-04-08 18:10 ` [PATCH 5.15 v3 11/11] KVM: arm64: Eagerly switch ZCR_EL{1,2} Mark Brown
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=Z_f1MGoJ6T4m77wY@lappy \
--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 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).