All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: kexec@lists.infradead.org
Subject: [PATCHv3 1/2] cpu/hotplug: Keep cpu hotplug disabled until the rebooting cpu is stable
Date: Mon, 09 May 2022 12:57:59 +0200	[thread overview]
Message-ID: <87bkw7rn0o.ffs@tglx> (raw)
In-Reply-To: <87ee13rn52.ffs@tglx>

On Mon, May 09 2022 at 12:55, Thomas Gleixner wrote:
> On Mon, May 09 2022 at 12:13, Pingfan Liu wrote:
>> -		cpu_hotplug_enable();
>
> This is tinkering at best. Can we please sit down and rethink this whole
> machinery instead of applying random duct tape to it?

That said, I still have not figured out which real world problem you are
actually trying to solve.

Thanks,

        tglx


WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Pingfan Liu <kernelfans@gmail.com>, linux-kernel@vger.kernel.org
Cc: Pingfan Liu <kernelfans@gmail.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Vincent Donnefort <vincent.donnefort@arm.com>,
	Ingo Molnar <mingo@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	YueHaibing <yuehaibing@huawei.com>,
	Baokun Li <libaokun1@huawei.com>,
	Randy Dunlap <rdunlap@infradead.org>, Baoquan He <bhe@redhat.com>,
	kexec@lists.infradead.org
Subject: Re: [PATCHv3 1/2] cpu/hotplug: Keep cpu hotplug disabled until the rebooting cpu is stable
Date: Mon, 09 May 2022 12:57:59 +0200	[thread overview]
Message-ID: <87bkw7rn0o.ffs@tglx> (raw)
In-Reply-To: <87ee13rn52.ffs@tglx>

On Mon, May 09 2022 at 12:55, Thomas Gleixner wrote:
> On Mon, May 09 2022 at 12:13, Pingfan Liu wrote:
>> -		cpu_hotplug_enable();
>
> This is tinkering at best. Can we please sit down and rethink this whole
> machinery instead of applying random duct tape to it?

That said, I still have not figured out which real world problem you are
actually trying to solve.

Thanks,

        tglx

  reply	other threads:[~2022-05-09 10:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  4:13 [PATCHv3 0/2] cpu/hotplug: Keep cpu hotplug disabled until the rebooting cpu is stable Pingfan Liu
2022-05-09  4:13 ` Pingfan Liu
2022-05-09  4:13 ` Pingfan Liu
2022-05-09  4:13 ` Pingfan Liu
2022-05-09  4:13 ` [PATCHv3 1/2] " Pingfan Liu
2022-05-09  4:13   ` Pingfan Liu
2022-05-09 10:55   ` Thomas Gleixner
2022-05-09 10:55     ` Thomas Gleixner
2022-05-09 10:57     ` Thomas Gleixner [this message]
2022-05-09 10:57       ` Thomas Gleixner
2022-05-10  3:38     ` Pingfan Liu
2022-05-10  3:38       ` Pingfan Liu
2022-05-10  8:28       ` Thomas Gleixner
2022-05-10  8:28         ` Thomas Gleixner
2022-05-11  9:09         ` Pingfan Liu
2022-05-11  9:09           ` Pingfan Liu
2022-05-09  4:13 ` [PATCHv3 2/2] arm/arm64/ia64: kexec: fix the primary cpu passed to smp_shutdown_nonboot_cpus() Pingfan Liu
2022-05-09  4:13   ` Pingfan Liu
2022-05-09  4:13   ` Pingfan Liu

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=87bkw7rn0o.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=kexec@lists.infradead.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.