On 5 June 2014 00:36, Alexey Kardashevskiy a...@ozlabs.ru wrote:
I'd rather remove return value at all, my mistake, I cannot see how NMI
handler can possibly fail - noone can mask it after all :) If callback
exists, I just call it and that's it. If it does not exist, it is
unsupported and
On 06/04/2014 08:25 AM, Alexey Kardashevskiy wrote:
This introduces an NMI (non maskable interrupt) nmi_monitor_handler()
callback to the CPU class. It is called from QMP's nmi command and
performs an action required to cause debug crash dump on in-kernel
debugger invocation.
This adds
This introduces an NMI (non maskable interrupt) nmi_monitor_handler()
callback to the CPU class. It is called from QMP's nmi command and
performs an action required to cause debug crash dump on in-kernel
debugger invocation.
This adds support for it in qmp_inject_nmi(). Since no architecture
On 06/05/2014 04:10 AM, Eric Blake wrote:
On 06/04/2014 08:25 AM, Alexey Kardashevskiy wrote:
This introduces an NMI (non maskable interrupt) nmi_monitor_handler()
callback to the CPU class. It is called from QMP's nmi command and
performs an action required to cause debug crash dump on
