All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: torvalds@linux-foundation.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [GIT PULL] arm64 fixes for -rc1
Date: Fri, 19 Jan 2024 10:34:08 -0600	[thread overview]
Message-ID: <20240119163408.GA468084-robh@kernel.org> (raw)
In-Reply-To: <20240119160528.GA5336@willie-the-truck>

On Fri, Jan 19, 2024 at 04:05:28PM +0000, Will Deacon wrote:
> Hi Linus,
> 
> Please pull these arm64 fixes for -rc1. I think the main one is fixing
> the dynamic SCS patching when full LTO is enabled (clang was silently
> getting this horribly wrong), but it's all good stuff. Rob just pointed
> out that the fix to the workaround for erratum #2966298 might not be
> necessary, but in the worst case it's harmless and since the official
> description leaves a little to be desired here, I've left it in.
> 
> Cheers,
> 
> Will
> 
> --->8
> 
> The following changes since commit db32cf8e280b46726065c518e90761bb0229bacf:
> 
>   Merge branch 'for-next/fixes' into for-next/core (2024-01-04 12:32:33 +0000)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
> 
> for you to fetch changes up to 1b20d0486a602417defb5bf33320d31b2a7a47f8:
> 
>   arm64: Fix silcon-errata.rst formatting (2024-01-18 11:15:43 +0000)
> 
> ----------------------------------------------------------------
> arm64 fixes for -rc1
> 
> - Fix shadow call stack patching with LTO=full
> 
> - Fix voluntary preemption of the FPSIMD registers from assembly code
> 
> - Fix workaround for A520 CPU erratum #2966298 and extend to A510
> 
> - Fix SME issues that resulted in corruption of the register state
> 
> - Minor fixes (missing includes, formatting)
> 
> ----------------------------------------------------------------
> Ard Biesheuvel (2):
>       arm64: scs: Work around full LTO issue with dynamic SCS
>       arm64: fpsimd: Bring cond_yield asm macro in line with new rules
> 
> Mark Brown (3):
>       arm64/ptrace: Don't flush ZA/ZT storage when writing ZA via ptrace
>       arm64/fpsimd: Remove spurious check for SVE support
>       arm64/sme: Always exit sme_alloc() early with existing storage
> 
> Mark Rutland (2):
>       arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD

I've commented on the patch, but this doesn't fix anything. The original 
work-around was fine.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: torvalds@linux-foundation.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [GIT PULL] arm64 fixes for -rc1
Date: Fri, 19 Jan 2024 10:34:08 -0600	[thread overview]
Message-ID: <20240119163408.GA468084-robh@kernel.org> (raw)
In-Reply-To: <20240119160528.GA5336@willie-the-truck>

On Fri, Jan 19, 2024 at 04:05:28PM +0000, Will Deacon wrote:
> Hi Linus,
> 
> Please pull these arm64 fixes for -rc1. I think the main one is fixing
> the dynamic SCS patching when full LTO is enabled (clang was silently
> getting this horribly wrong), but it's all good stuff. Rob just pointed
> out that the fix to the workaround for erratum #2966298 might not be
> necessary, but in the worst case it's harmless and since the official
> description leaves a little to be desired here, I've left it in.
> 
> Cheers,
> 
> Will
> 
> --->8
> 
> The following changes since commit db32cf8e280b46726065c518e90761bb0229bacf:
> 
>   Merge branch 'for-next/fixes' into for-next/core (2024-01-04 12:32:33 +0000)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
> 
> for you to fetch changes up to 1b20d0486a602417defb5bf33320d31b2a7a47f8:
> 
>   arm64: Fix silcon-errata.rst formatting (2024-01-18 11:15:43 +0000)
> 
> ----------------------------------------------------------------
> arm64 fixes for -rc1
> 
> - Fix shadow call stack patching with LTO=full
> 
> - Fix voluntary preemption of the FPSIMD registers from assembly code
> 
> - Fix workaround for A520 CPU erratum #2966298 and extend to A510
> 
> - Fix SME issues that resulted in corruption of the register state
> 
> - Minor fixes (missing includes, formatting)
> 
> ----------------------------------------------------------------
> Ard Biesheuvel (2):
>       arm64: scs: Work around full LTO issue with dynamic SCS
>       arm64: fpsimd: Bring cond_yield asm macro in line with new rules
> 
> Mark Brown (3):
>       arm64/ptrace: Don't flush ZA/ZT storage when writing ZA via ptrace
>       arm64/fpsimd: Remove spurious check for SVE support
>       arm64/sme: Always exit sme_alloc() early with existing storage
> 
> Mark Rutland (2):
>       arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD

I've commented on the patch, but this doesn't fix anything. The original 
work-around was fine.

Rob

  reply	other threads:[~2024-01-19 16:34 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 16:05 [GIT PULL] arm64 fixes for -rc1 Will Deacon
2024-01-19 16:05 ` Will Deacon
2024-01-19 16:34 ` Rob Herring [this message]
2024-01-19 16:34   ` Rob Herring
2024-01-19 16:58   ` Rob Herring
2024-01-19 16:58     ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2024-01-19 22:50   ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-02-20 15:41 Will Deacon
2026-02-20 20:50 ` pr-tracker-bot
2025-10-07  8:28 Will Deacon
2025-10-07 16:13 ` pr-tracker-bot
2025-06-05 13:41 Will Deacon
2025-06-05 18:53 ` pr-tracker-bot
2024-07-26  8:42 Will Deacon
2024-07-26 18:07 ` pr-tracker-bot
2024-05-23 10:20 Will Deacon
2024-05-23 10:20 ` Will Deacon
2024-05-23 19:28 ` pr-tracker-bot
2024-05-23 19:28   ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 15:30 ` Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-09-08 20:00   ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 14:22 ` Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2023-05-04 19:49   ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 15:51 ` Will Deacon
2022-12-16 19:50 ` pr-tracker-bot
2022-12-16 19:50   ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 18:52 ` Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-11-10 20:09   ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 11:09 ` Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2021-02-26 18:31   ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 13:37 ` Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-09-20 19:10   ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-04 18:24 ` Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2019-01-05 20:20   ` pr-tracker-bot
2017-03-01  4:51 [GIT PULL] arm64 " Will Deacon
2017-03-01  4:51 ` Will Deacon
2016-08-05 15:48 [GIT PULL] arm64: " Will Deacon
2016-08-05 15:48 ` Will Deacon
2014-12-16 17:50 Will Deacon
2014-12-16 17:50 ` Will Deacon

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=20240119163408.GA468084-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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.