From: Will Deacon <will@kernel.org> To: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org, kernel-team@android.com, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Qian Cai <cai@redhat.com>, "Paul E. McKenney" <paulmck@kernel.org> Subject: [PATCH 0/2] arm64: Fix issues with CPU hotplug and RCU Date: Fri, 6 Nov 2020 10:36:00 +0000 [thread overview] Message-ID: <20201106103602.9849-1-will@kernel.org> (raw) Hi folks, Here are a couple of patches following on from: https://lore.kernel.org/r/20201105222242.GA8842@willie-the-truck which address issues when CPU onlining fails but RCU is left none the wiser. Tested under QEMU. If Paul is happy with the second patch, then I can take both of these via arm64 as fixes for 5.11. Cheers, Will Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Qian Cai <cai@redhat.com> Cc: "Paul E. McKenney" <paulmck@kernel.org> --->8 Will Deacon (2): arm64: psci: Avoid printing in cpu_psci_cpu_die() arm64: smp: Tell RCU about CPUs that fail to come online arch/arm64/kernel/psci.c | 2 -- arch/arm64/kernel/smp.c | 1 + kernel/rcu/tree.c | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) -- 2.29.1.341.ge80a0c044ae-goog
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org> To: linux-arm-kernel@lists.infradead.org Cc: "Paul E. McKenney" <paulmck@kernel.org>, Qian Cai <cai@redhat.com>, kernel-team@android.com, linux-kernel@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org> Subject: [PATCH 0/2] arm64: Fix issues with CPU hotplug and RCU Date: Fri, 6 Nov 2020 10:36:00 +0000 [thread overview] Message-ID: <20201106103602.9849-1-will@kernel.org> (raw) Hi folks, Here are a couple of patches following on from: https://lore.kernel.org/r/20201105222242.GA8842@willie-the-truck which address issues when CPU onlining fails but RCU is left none the wiser. Tested under QEMU. If Paul is happy with the second patch, then I can take both of these via arm64 as fixes for 5.11. Cheers, Will Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Qian Cai <cai@redhat.com> Cc: "Paul E. McKenney" <paulmck@kernel.org> --->8 Will Deacon (2): arm64: psci: Avoid printing in cpu_psci_cpu_die() arm64: smp: Tell RCU about CPUs that fail to come online arch/arm64/kernel/psci.c | 2 -- arch/arm64/kernel/smp.c | 1 + kernel/rcu/tree.c | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) -- 2.29.1.341.ge80a0c044ae-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-06 10:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-06 10:36 Will Deacon [this message] 2020-11-06 10:36 ` [PATCH 0/2] arm64: Fix issues with CPU hotplug and RCU Will Deacon 2020-11-06 10:36 ` [PATCH 1/2] arm64: psci: Avoid printing in cpu_psci_cpu_die() Will Deacon 2020-11-06 10:36 ` Will Deacon 2020-11-19 13:24 ` kernel test robot 2020-11-06 10:36 ` [PATCH 2/2] arm64: smp: Tell RCU about CPUs that fail to come online Will Deacon 2020-11-06 10:36 ` Will Deacon 2020-11-06 14:43 ` Paul E. McKenney 2020-11-06 14:43 ` Paul E. McKenney
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=20201106103602.9849-1-will@kernel.org \ --to=will@kernel.org \ --cc=cai@redhat.com \ --cc=catalin.marinas@arm.com \ --cc=kernel-team@android.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=paulmck@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: 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.