Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1348666

RE: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function

From 河合英宏 / KAWAI,HIDEHIRO <hidehiro.kawai.ez@hitachi.com>
Newsgroups linux.kernel
Subject RE: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function
Date 2016-03-03 02:30 +0100
Message-ID <r8qfw-84R-7@gated-at.bofh.it> (permalink)
References <r8cvT-6qw-3@gated-at.bofh.it> <r8cvT-6qw-11@gated-at.bofh.it> <r8eR3-84M-1@gated-at.bofh.it> <r8f0L-89o-33@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

> From: Borislav Petkov [mailto:bp@alien8.de]
> On Wed, Mar 02, 2016 at 02:18:24PM +0100, Michal Hocko wrote:
> > On Wed 02-03-16 19:36:26, Hidehiro Kawai wrote:
> > [...]
> > > +void nmi_panic(struct pt_regs *regs, const char *fmt, ...)
> >
> > Do we really need vargs? All the current users seem to be OK with a
> > simple string. This makes the code slightly more complicated without any
> > apparent reason.
> 
> I was just wondering the exactly same thing...
> 
> The contra-arg would be that in case someone wants to do nmi_panic()
> with more than a string, then it won't work.

It's not necessary to use vargs at this point, and passing a simple
string is OK for me.  Even if someone wants to use vargs, we can modify
nmi_panic() without any changes in caller side.  So, I'll remove it.

> The question is, does nmi_panic() even need to dump something more than
> regs and a string?

Hmm, printing regs, especially for RIP, would be useful for hang-up
cases, but I don't want to do much things in nmi_panic() as long as
it is already done by current callers.  nmi_panic() can be called
concurrently on multiple CPUs, so it also needs another serialization
to print something.

By the way, I have a patch set to safely leave important information
by kexec's purgatory...but no one is interested in?
http://thread.gmane.org/gmane.linux.kernel.kexec/15382

Regards,
--
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group


Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[v2 PATCH 0/3] Use nmi_panic() in panic on NMI case Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> - 2016-03-02 11:50 +0100
  [v2 PATCH 2/3] ipmi/watchdog: Use nmi_panic() when kernel panics in  NMI handler Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> - 2016-03-02 11:50 +0100
  [v2 PATCH 1/3] panic: Change nmi_panic from macro to function Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> - 2016-03-02 11:50 +0100
    Re: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function Michal Hocko <mhocko@kernel.org> - 2016-03-02 14:20 +0100
      Re: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function Borislav Petkov <bp@alien8.de> - 2016-03-02 14:30 +0100
        RE: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function 河合英宏 / KAWAI,HIDEHIRO   <hidehiro.kawai.ez@hitachi.com> - 2016-03-03 02:30 +0100
      Re: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function Guenter Roeck <linux@roeck-us.net> - 2016-03-02 18:10 +0100

csiph-web