On 3/8/2017 2:28 AM, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
>>
>>
>> On 3/6/2017 11:42 PM, Ingo Molnar wrote:
>>>
>>> * Mike Travis wrote:
>>>
Add a new NMI call chain that is called last after all other NMI handlers
have been
On 3/8/2017 2:28 AM, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
>>
>>
>> On 3/6/2017 11:42 PM, Ingo Molnar wrote:
>>>
>>> * Mike Travis wrote:
>>>
Add a new NMI call chain that is called last after all other NMI handlers
have been checked and did not "handle" the NMI. This
* Mike Travis wrote:
>
>
> On 3/6/2017 11:42 PM, Ingo Molnar wrote:
> >
> > * Mike Travis wrote:
> >
> >> Add a new NMI call chain that is called last after all other NMI handlers
> >> have been checked and did not "handle" the NMI. This mimics
* Mike Travis wrote:
>
>
> On 3/6/2017 11:42 PM, Ingo Molnar wrote:
> >
> > * Mike Travis wrote:
> >
> >> Add a new NMI call chain that is called last after all other NMI handlers
> >> have been checked and did not "handle" the NMI. This mimics the current
> >> NMI_UNKNOWN call chain
On 3/7/2017 7:22 AM, Don Zickus wrote:
> On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
>>
>> * Mike Travis wrote:
>>
>>> Add a new NMI call chain that is called last after all other NMI handlers
>>> have been checked and did not "handle" the NMI. This mimics
On 3/7/2017 7:22 AM, Don Zickus wrote:
> On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
>>
>> * Mike Travis wrote:
>>
>>> Add a new NMI call chain that is called last after all other NMI handlers
>>> have been checked and did not "handle" the NMI. This mimics the current
>>>
On 3/7/2017 8:07 AM, Don Zickus wrote:
> Good to know. I keep thinking of the hpwdt that wants to eat all NMIs, I
> believe that still registers on the unknown nmi (drivers/watchdog/hpwdt.c).
Thanks for pointing that out. I'm guessing this happens only on
HPE systems, which are now us... :)
On 3/7/2017 8:07 AM, Don Zickus wrote:
> Good to know. I keep thinking of the hpwdt that wants to eat all NMIs, I
> believe that still registers on the unknown nmi (drivers/watchdog/hpwdt.c).
Thanks for pointing that out. I'm guessing this happens only on
HPE systems, which are now us... :)
On Tue, Mar 07, 2017 at 08:00:33AM -0800, Mike Travis wrote:
>
>
> On 3/7/2017 7:22 AM, Don Zickus wrote:
> > On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
> >>
> >> * Mike Travis wrote:
> >>
> >>> Add a new NMI call chain that is called last after all other
On Tue, Mar 07, 2017 at 08:00:33AM -0800, Mike Travis wrote:
>
>
> On 3/7/2017 7:22 AM, Don Zickus wrote:
> > On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
> >>
> >> * Mike Travis wrote:
> >>
> >>> Add a new NMI call chain that is called last after all other NMI handlers
> >>>
On 3/6/2017 11:42 PM, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
>> Add a new NMI call chain that is called last after all other NMI handlers
>> have been checked and did not "handle" the NMI. This mimics the current
>> NMI_UNKNOWN call chain except it eliminates the
On 3/6/2017 11:42 PM, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
>> Add a new NMI call chain that is called last after all other NMI handlers
>> have been checked and did not "handle" the NMI. This mimics the current
>> NMI_UNKNOWN call chain except it eliminates the WARNING message about
On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
> > Add a new NMI call chain that is called last after all other NMI handlers
> > have been checked and did not "handle" the NMI. This mimics the current
> > NMI_UNKNOWN call chain
On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
>
> * Mike Travis wrote:
>
> > Add a new NMI call chain that is called last after all other NMI handlers
> > have been checked and did not "handle" the NMI. This mimics the current
> > NMI_UNKNOWN call chain except it eliminates the
* Mike Travis wrote:
> Add a new NMI call chain that is called last after all other NMI handlers
> have been checked and did not "handle" the NMI. This mimics the current
> NMI_UNKNOWN call chain except it eliminates the WARNING message about
> multiple NMI handlers
* Mike Travis wrote:
> Add a new NMI call chain that is called last after all other NMI handlers
> have been checked and did not "handle" the NMI. This mimics the current
> NMI_UNKNOWN call chain except it eliminates the WARNING message about
> multiple NMI handlers registering on this call
Add a new NMI call chain that is called last after all other NMI handlers
have been checked and did not "handle" the NMI. This mimics the current
NMI_UNKNOWN call chain except it eliminates the WARNING message about
multiple NMI handlers registering on this call chain.
This call chain
Add a new NMI call chain that is called last after all other NMI handlers
have been checked and did not "handle" the NMI. This mimics the current
NMI_UNKNOWN call chain except it eliminates the WARNING message about
multiple NMI handlers registering on this call chain.
This call chain
18 matches
Mail list logo