mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valentin Schneider <vschneid@redhat.com>
To: Phil Auld <pauld@redhat.com>, linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 2/2] cpuhp: Set cpuhp target for boot cpu
Date: Fri, 27 May 2022 10:38:27 +0100	[thread overview]
Message-ID: <xhsmhwne7l3ho.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <20220526160615.7976-3-pauld@redhat.com>

On 26/05/22 12:06, Phil Auld wrote:
> Since the boot cpu does not go through the hotplug process it ends
> up with state == CPUHP_ONLINE but target == CPUHP_OFFLINE.
> Set the target to match in boot_cpu_hotplug_init().
>
> Signed-off-by: Phil Auld <pauld@redhat.com>

Reviewed-by: Valentin Schneider <vschneid@redhat.com>

> ---
>  kernel/cpu.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index cdb6ac10ad94..0bb8ad0fa2d9 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -2677,6 +2677,7 @@ void __init boot_cpu_hotplug_init(void)
>  	cpumask_set_cpu(smp_processor_id(), &cpus_booted_once_mask);
>  #endif
>  	this_cpu_write(cpuhp_state.state, CPUHP_ONLINE);
> +	this_cpu_write(cpuhp_state.target, CPUHP_ONLINE);
>  }
>  
>  /*
> -- 
> 2.18.0


      reply	other threads:[~2022-05-27  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 16:06 [PATCH v2 0/2] cpuhp: fix some st->target issues Phil Auld
2022-05-26 16:06 ` [PATCH v2 1/2] cpuhp: make target_store() a nop when target == state Phil Auld
2022-05-27  9:38   ` Valentin Schneider
2022-05-27 13:22     ` Phil Auld
2022-05-30 12:27       ` Valentin Schneider
2022-06-01 15:49         ` Phil Auld
2022-06-01 16:39           ` Valentin Schneider
2022-05-26 16:06 ` [PATCH v2 2/2] cpuhp: Set cpuhp target for boot cpu Phil Auld
2022-05-27  9:38   ` Valentin Schneider [this message]

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=xhsmhwne7l3ho.mognet@vschneid.remote.csb \
    --to=vschneid@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pauld@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®