On Fri, 08 Dec 2017 22:46:49 +1100
Michael Ellerman wrote:
> Nicholas Piggin writes:
>
> > On Fri, 8 Dec 2017 14:35:33 +1100
> > Balbir Singh wrote:
> >
> >> Certain HMI's such as malfunction error propagate through
> >> all threads/core on the system. If a thread was offline
> >> prior to
Nicholas Piggin writes:
> On Fri, 8 Dec 2017 14:35:33 +1100
> Balbir Singh wrote:
>
>> Certain HMI's such as malfunction error propagate through
>> all threads/core on the system. If a thread was offline
>> prior to us crashing the system and jumping to the kdump
>> kernel, bad things happen wh
On Fri, 8 Dec 2017 14:35:33 +1100
Balbir Singh wrote:
> Certain HMI's such as malfunction error propagate through
> all threads/core on the system. If a thread was offline
> prior to us crashing the system and jumping to the kdump
> kernel, bad things happen when it wakes up due to an HMI
> in t
Certain HMI's such as malfunction error propagate through
all threads/core on the system. If a thread was offline
prior to us crashing the system and jumping to the kdump
kernel, bad things happen when it wakes up due to an HMI
in the kdump kernel.
There are several possible ways to solve this pro
On Wed, Dec 6, 2017 at 4:07 PM, Haren Myneni wrote:
> On 12/05/2017 08:29 PM, Balbir Singh wrote:
>> On Mon, Dec 4, 2017 at 2:10 PM, Nicholas Piggin wrote:
>>> On Mon, 4 Dec 2017 11:37:01 +1100
>>> Balbir Singh wrote:
>>>
On Sun, Dec 3, 2017 at 1:36 PM, Nicholas Piggin wrote:
> Seems l
On 12/05/2017 08:29 PM, Balbir Singh wrote:
> On Mon, Dec 4, 2017 at 2:10 PM, Nicholas Piggin wrote:
>> On Mon, 4 Dec 2017 11:37:01 +1100
>> Balbir Singh wrote:
>>
>>> On Sun, Dec 3, 2017 at 1:36 PM, Nicholas Piggin wrote:
Seems like a reasonable approach. Why do we only do this for
po
On Mon, Dec 4, 2017 at 2:10 PM, Nicholas Piggin wrote:
> On Mon, 4 Dec 2017 11:37:01 +1100
> Balbir Singh wrote:
>
>> On Sun, Dec 3, 2017 at 1:36 PM, Nicholas Piggin wrote:
>> > Seems like a reasonable approach. Why do we only do this for
>> > powernv? It seems like a good idea in general to pul
On Mon, 4 Dec 2017 11:37:01 +1100
Balbir Singh wrote:
> On Sun, Dec 3, 2017 at 1:36 PM, Nicholas Piggin wrote:
> > Seems like a reasonable approach. Why do we only do this for
> > powernv? It seems like a good idea in general to pull all
> > offlined CPUs out and into the same state for all plat
On Sun, Dec 3, 2017 at 1:36 PM, Nicholas Piggin wrote:
> Seems like a reasonable approach. Why do we only do this for
> powernv? It seems like a good idea in general to pull all
> offlined CPUs out and into the same state for all platforms
> and for all shutdown/restart/crash paths.
>
The reason
Seems like a reasonable approach. Why do we only do this for
powernv? It seems like a good idea in general to pull all
offlined CPUs out and into the same state for all platforms
and for all shutdown/restart/crash paths.
Also I wonder if there is anything we should do on the other
side of the equa
Certain HMI's such as malfunction error propagate through
all threads/core on the system. If a thread was offline
prior to us crashing the system and jumping to the kdump
kernel, bad things happen when it wakes up due to an HMI
in the kdump kernel.
There are several possible ways to solve this pro
11 matches
Mail list logo
