lkml.org 
[lkml]   [2015]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 1/5] printk/nmi: Generic solution for safe printk in NMI
On Fri, 27 Nov 2015, Petr Mladek wrote:

> MN10300 has its own implementation for entering and exiting NMI
> handlers. It does not call nmi_enter() and nmi_exit(). Please, find
> below an updated patch that adds printk_nmi_enter() and
> printk_nmi_exit() to the custom entry points. Then we could add HAVE_NMI
> to arch/mn10300/Kconfig and avoid the above warning.

Hmm, so what exactly would go wrong if MN10300 (whatever that architecture
is) would call nmi_enter() and nmi_exit() at the places where it's
starting and finishing NMI handler?

From a cursory look, it seems like most (if not all) of the things called
from nmi_{enter,exit}() would be nops there anyway.

Thanks,

--
Jiri Kosina
SUSE Labs



\
 
 \ /
  Last update: 2015-12-02 00:41    [W:0.017 / U:1.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site