linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit"
@ 2017-11-28  6:03 Liu ping fan
  2017-11-28 11:05 ` Michael Ellerman
  2017-12-06 16:24 ` Guilherme G. Piccoli
  0 siblings, 2 replies; 3+ messages in thread
From: Liu ping fan @ 2017-11-28  6:03 UTC (permalink / raw)
  To: linuxppc-dev

Hi,

I can not find the history about:
https://patchwork.ozlabs.org/patch/577193/


Can we have this patch?

Thanks,
Pingfan

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit"
  2017-11-28  6:03 what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit" Liu ping fan
@ 2017-11-28 11:05 ` Michael Ellerman
  2017-12-06 16:24 ` Guilherme G. Piccoli
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Ellerman @ 2017-11-28 11:05 UTC (permalink / raw)
  To: Liu ping fan, linuxppc-dev

Liu ping fan <kernelfans@gmail.com> writes:

> Hi,
>
> I can not find the history about:
> https://patchwork.ozlabs.org/patch/577193/
>
>
> Can we have this patch?

I strongly dislike it.

Our CPU discovery code is already a big mess, in two separate places,
and this makes it worse.

In theory we have a split between logical and hardware CPU numbers, so
we should just be able to call the whatever CPU we boot on CPU 0. Why
does that not work? And should we fix that?

cheers

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit"
  2017-11-28  6:03 what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit" Liu ping fan
  2017-11-28 11:05 ` Michael Ellerman
@ 2017-12-06 16:24 ` Guilherme G. Piccoli
  1 sibling, 0 replies; 3+ messages in thread
From: Guilherme G. Piccoli @ 2017-12-06 16:24 UTC (permalink / raw)
  To: Liu ping fan, linuxppc-dev
  Cc: Thadeu Lima de Souza Cascardo, Michael Ellerman,
	Benjamin Herrenschmidt, paulus



On 11/28/2017 04:03 AM, Liu ping fan wrote:
> Hi,
> 
> I can not find the history about:
> https://patchwork.ozlabs.org/patch/577193/
> 
> 
> Can we have this patch?
> 
> Thanks,
> Pingfan
> 

Cross-referencing 2 threads on the same topic:
https://patchwork.ozlabs.org/patch/834860

Cascardo recently rebased this patch against latest kernel and tried to
get v3 merged, on the above linked thread.

Let's choose one of the threads to further discuss the solution to this
long-term bug!

Thanks,


Guilherme

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-12-06 16:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-28  6:03 what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit" Liu ping fan
2017-11-28 11:05 ` Michael Ellerman
2017-12-06 16:24 ` Guilherme G. Piccoli

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).