From: Will Deacon <will@kernel.org> To: torvalds@linux-foundation.org Cc: catalin.marinas@arm.com, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux ARM Kernel Mailing List <linux-arm-kernel@lists.infradead.org>, peterz@infradead.org Subject: [GIT PULL] arm64: Fixes for -rc6 Date: Fri, 1 Nov 2019 14:32:40 +0000 [thread overview] Message-ID: <20191101143240.GA3287@willie-the-truck> (raw) Hi Linus, Please pull these arm64 fixes for -rc6. They're almost exclusively related to CPU errata in CPUs from Broadcom and Qualcomm where the workarounds were either not being enabled when they should have been or enabled when they shouldn't have been. The only "interesting" fix is ensuring that writeable, shared mappings are initially mapped as clean since we inadvertently broke the logic back in v4.14 and then noticed the problem via code inspection the other day. The only critical issue we have outstanding is a sporadic NULL dereference in the scheduler, which doesn't appear to be arm64-specific and PeterZ is tearing his hair out over it at the moment. Cheers, Will --->8 The following changes since commit 777d062e5bee0e3c0751cdcbce116a76ee2310ec: Merge branch 'errata/tx2-219' into for-next/fixes (2019-10-17 13:42:42 -0700) 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 1cf45b8fdbb87040e1d1bd793891089f4678aa41: arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core (2019-11-01 10:47:37 +0000) ---------------------------------------------------------------- arm64 fixes for -rc6 - Enable CPU errata workarounds for Broadcom Brahma-B53 - Enable CPU errata workarounds for Qualcomm Hydra/Kryo CPUs - Fix initial dirty status of writeable, shared mappings ---------------------------------------------------------------- Bjorn Andersson (2): arm64: cpufeature: Enable Qualcomm Falkor/Kryo errata 1003 arm64: cpufeature: Enable Qualcomm Falkor errata 1009 for Kryo Catalin Marinas (1): arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default Doug Berger (1): arm64: apply ARM64_ERRATUM_845719 workaround for Brahma-B53 core Florian Fainelli (2): arm64: Brahma-B53 is SSB and spectre v2 safe arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core Documentation/arm64/silicon-errata.rst | 7 +++- arch/arm64/include/asm/cputype.h | 2 ++ arch/arm64/include/asm/pgtable-prot.h | 15 +++++---- arch/arm64/kernel/cpu_errata.c | 59 +++++++++++++++++++++++++++------- 4 files changed, 64 insertions(+), 19 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org> To: torvalds@linux-foundation.org Cc: peterz@infradead.org, catalin.marinas@arm.com, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux ARM Kernel Mailing List <linux-arm-kernel@lists.infradead.org> Subject: [GIT PULL] arm64: Fixes for -rc6 Date: Fri, 1 Nov 2019 14:32:40 +0000 [thread overview] Message-ID: <20191101143240.GA3287@willie-the-truck> (raw) Hi Linus, Please pull these arm64 fixes for -rc6. They're almost exclusively related to CPU errata in CPUs from Broadcom and Qualcomm where the workarounds were either not being enabled when they should have been or enabled when they shouldn't have been. The only "interesting" fix is ensuring that writeable, shared mappings are initially mapped as clean since we inadvertently broke the logic back in v4.14 and then noticed the problem via code inspection the other day. The only critical issue we have outstanding is a sporadic NULL dereference in the scheduler, which doesn't appear to be arm64-specific and PeterZ is tearing his hair out over it at the moment. Cheers, Will --->8 The following changes since commit 777d062e5bee0e3c0751cdcbce116a76ee2310ec: Merge branch 'errata/tx2-219' into for-next/fixes (2019-10-17 13:42:42 -0700) 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 1cf45b8fdbb87040e1d1bd793891089f4678aa41: arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core (2019-11-01 10:47:37 +0000) ---------------------------------------------------------------- arm64 fixes for -rc6 - Enable CPU errata workarounds for Broadcom Brahma-B53 - Enable CPU errata workarounds for Qualcomm Hydra/Kryo CPUs - Fix initial dirty status of writeable, shared mappings ---------------------------------------------------------------- Bjorn Andersson (2): arm64: cpufeature: Enable Qualcomm Falkor/Kryo errata 1003 arm64: cpufeature: Enable Qualcomm Falkor errata 1009 for Kryo Catalin Marinas (1): arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default Doug Berger (1): arm64: apply ARM64_ERRATUM_845719 workaround for Brahma-B53 core Florian Fainelli (2): arm64: Brahma-B53 is SSB and spectre v2 safe arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core Documentation/arm64/silicon-errata.rst | 7 +++- arch/arm64/include/asm/cputype.h | 2 ++ arch/arm64/include/asm/pgtable-prot.h | 15 +++++---- arch/arm64/kernel/cpu_errata.c | 59 +++++++++++++++++++++++++++------- 4 files changed, 64 insertions(+), 19 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-01 14:32 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-01 14:32 Will Deacon [this message] 2019-11-01 14:32 ` [GIT PULL] arm64: Fixes for -rc6 Will Deacon 2019-11-01 17:10 ` pr-tracker-bot 2019-11-01 17:10 ` pr-tracker-bot -- strict thread matches above, loose matches on Subject: below -- 2024-02-23 10:25 [GIT PULL] arm64 fixes " Will Deacon 2024-02-23 10:25 ` Will Deacon 2024-02-23 18:44 ` pr-tracker-bot 2024-02-23 18:44 ` pr-tracker-bot 2023-06-08 20:51 Will Deacon 2023-06-08 20:51 ` Will Deacon 2023-06-08 21:49 ` pr-tracker-bot 2023-06-08 21:49 ` pr-tracker-bot 2021-12-15 11:19 Will Deacon 2021-12-15 11:19 ` Will Deacon 2021-12-15 16:00 ` Catalin Marinas 2021-12-15 16:00 ` Catalin Marinas 2021-12-15 18:49 ` Linus Torvalds 2021-12-15 18:49 ` Linus Torvalds 2020-11-27 11:40 Will Deacon 2020-11-27 11:40 ` Will Deacon 2020-11-27 19:19 ` pr-tracker-bot 2020-11-27 19:19 ` pr-tracker-bot 2020-07-17 15:20 Will Deacon 2020-07-17 15:20 ` Will Deacon 2020-07-17 23:45 ` pr-tracker-bot 2020-07-17 23:45 ` pr-tracker-bot 2019-08-24 12:12 [GIT PULL] arm64: Fixes " Will Deacon 2019-08-24 12:12 ` Will Deacon 2019-08-24 12:12 ` Will Deacon 2019-08-24 18:45 ` pr-tracker-bot 2019-08-24 18:45 ` pr-tracker-bot 2019-08-24 18:45 ` pr-tracker-bot 2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon 2019-06-20 16:59 ` Will Deacon 2019-06-20 19:10 ` pr-tracker-bot 2019-06-20 19:10 ` pr-tracker-bot 2019-02-08 17:35 Will Deacon 2019-02-08 17:35 ` Will Deacon 2019-02-09 0:40 ` pr-tracker-bot 2019-02-09 0:40 ` pr-tracker-bot 2017-04-07 16:02 Will Deacon 2017-04-07 16:02 ` Will Deacon 2017-04-11 19:12 ` Jon Masters 2017-04-11 19:12 ` Jon Masters 2017-04-12 9:14 ` Will Deacon 2017-04-12 9:14 ` Will Deacon 2017-04-12 10:18 ` Punit Agrawal 2017-04-12 10:18 ` Punit Agrawal 2015-10-15 13:38 Will Deacon 2015-10-15 13:38 ` Will Deacon 2015-01-23 16:44 Will Deacon 2015-01-23 16:44 ` 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=20191101143240.GA3287@willie-the-truck \ --to=will@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=peterz@infradead.org \ --cc=torvalds@linux-foundation.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: linkBe 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.