Re: [PATCH v3 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

2018-02-15 Thread Ingo Molnar
* Jerry Hoemann wrote: > Gen8 and prior Proliant systems supported the "CRU" interface > to firmware. This interfaces allows linux to "call back" into firmware > to source the cause of an NMI. This feature isn't fully utilized > as the actual source of the NMI isn't

Re: [PATCH v3 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

2018-02-15 Thread Ingo Molnar
* Jerry Hoemann wrote: > Gen8 and prior Proliant systems supported the "CRU" interface > to firmware. This interfaces allows linux to "call back" into firmware > to source the cause of an NMI. This feature isn't fully utilized > as the actual source of the NMI isn't printed, the driver only >

[PATCH v3 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

2018-02-15 Thread Jerry Hoemann
Gen8 and prior Proliant systems supported the "CRU" interface to firmware. This interfaces allows linux to "call back" into firmware to source the cause of an NMI. This feature isn't fully utilized as the actual source of the NMI isn't printed, the driver only indicates that the source couldn't

[PATCH v3 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

2018-02-15 Thread Jerry Hoemann
Gen8 and prior Proliant systems supported the "CRU" interface to firmware. This interfaces allows linux to "call back" into firmware to source the cause of an NMI. This feature isn't fully utilized as the actual source of the NMI isn't printed, the driver only indicates that the source couldn't