All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Huacai Chen <chenhuacai@gmail.com>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH V2] MIPS: CPU#0 is not hotpluggable
Date: Sun, 26 Jul 2020 19:30:10 +0800	[thread overview]
Message-ID: <9b87ae28-a818-3c82-796a-d3dfca4a73cc@flygoat.com> (raw)
In-Reply-To: <20200726082501.GC5032@alpha.franken.de>



在 2020/7/26 下午4:25, Thomas Bogendoerfer 写道:
> On Sat, Jul 25, 2020 at 02:37:52PM +0800, Huacai Chen wrote:
>> Hi, Thomas,
>>
>> What do you think about this patch? Other archs also do the same thing
>> except those support hotplug CPU#0.
> I'm ok with the patch, I'm just wondering if this is a hardware or
> software limitation. If it's the latter, what needs to be done to
> support it ?

It should be a software limitation, x86 have already deal with that [1].
But there is no reason to spend extra effort on CPU0 hotplug. I don't 
think any user is expecting this feature.

Thanks.

[1]: 
https://events.static.linuxfound.org/sites/events/files/lcjpcojp13_fenghua.pdf

- Jiaxun
>
> Thomas.
>

  reply	other threads:[~2020-07-26 11:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:40 [PATCH V2] MIPS: CPU#0 is not hotpluggable Huacai Chen
2020-07-25  6:37 ` Huacai Chen
2020-07-25  6:49   ` Greg KH
2020-07-25  6:57     ` Huacai Chen
2020-07-25  7:45       ` Greg KH
2020-07-25  8:29         ` Huacai Chen
2020-07-25  8:57           ` Greg KH
2020-07-26  2:17             ` Jiaxun Yang
2020-07-26  8:25   ` Thomas Bogendoerfer
2020-07-26 11:30     ` Jiaxun Yang [this message]
2020-07-26  8:25 ` Thomas Bogendoerfer

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=9b87ae28-a818-3c82-796a-d3dfca4a73cc@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhuacai@gmail.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=wuzhangjin@gmail.com \
    --cc=zhangfx@lemote.com \
    /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.