From: Thomas Gleixner <tglx@linutronix.de>
To: Vincent Donnefort <vdonnefort@google.com>, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, vschneid@redhat.com,
kernel-team@android.com,
Vincent Donnefort <vdonnefort@google.com>,
Derek Dolney <z23@posteo.net>
Subject: Re: [PATCH v2] cpu/hotplug: Do not bail-out in DYING/STARTING sections
Date: Mon, 13 Jun 2022 14:36:18 +0200 [thread overview]
Message-ID: <87mteg3flp.ffs@tglx> (raw)
In-Reply-To: <20220523160536.2889162-1-vdonnefort@google.com>
Vincent,
On Mon, May 23 2022 at 17:05, Vincent Donnefort wrote:
> +static int _cpuhp_invoke_callback_range(bool bringup,
> + unsigned int cpu,
> + struct cpuhp_cpu_state *st,
> + enum cpuhp_state target,
> + bool nofail)
> {
> enum cpuhp_state state;
> - int err = 0;
> + int ret = 0;
>
> while (cpuhp_next_state(bringup, &state, st, target)) {
> + int err;
> +
> err = cpuhp_invoke_callback(cpu, state, bringup, NULL, NULL);
> - if (err)
> + if (!err)
> + continue;
> +
> + if (nofail) {
> + pr_warn("CPU %u %s state %s (%d) failed (%d)\n",
> + cpu, bringup ? "UP" : "DOWN",
> + cpuhp_get_step(st->state)->name,
> + st->state, err);
> + ret = -1;
I have a hard time to map this to the changelog:
> those sections. In that case, there's nothing the hotplug machinery can do,
> so let's just proceed and log the failures.
That's still returning an error code at the end. Confused.
Thanks,
tglx
next prev parent reply other threads:[~2022-06-13 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 16:05 [PATCH v2] cpu/hotplug: Do not bail-out in DYING/STARTING sections Vincent Donnefort
2022-05-25 16:52 ` Peter Zijlstra
2022-05-26 8:24 ` Vincent Donnefort
2022-05-26 10:15 ` Peter Zijlstra
2022-05-29 18:01 ` Derek Dolney
2022-05-26 11:48 ` Derek Dolney
2022-05-26 12:27 ` Derek Dolney
2022-06-13 12:36 ` Thomas Gleixner [this message]
2022-06-13 13:37 ` Vincent Donnefort
2022-07-04 10:01 ` Thorsten Leemhuis
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=87mteg3flp.ffs@tglx \
--to=tglx@linutronix.de \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=vdonnefort@google.com \
--cc=vschneid@redhat.com \
--cc=z23@posteo.net \
/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