[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091209142322.F4C8.A69D9226@jp.fujitsu.com>
Date: Wed, 9 Dec 2009 14:34:46 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: kosaki.motohiro@...fujitsu.com, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
lkml <linux-kernel@...r.kernel.org>,
systemtap <systemtap@...rces.redhat.com>,
DLE <dle-develop@...ts.sourceforge.net>,
Oleg Nesterov <oleg@...hat.com>,
Roland McGrath <roland@...hat.com>,
Jason Baron <jbaron@...hat.com>
Subject: Re: [PATCH v3] [RFC] tracepoint: Add signal coredump tracepoint
> + TP_fast_assign(
> + __entry->sig = (int)cprm->signr;
> + __entry->limit = cprm->limit;
> + __entry->flags = cprm->mm_flags;
> + __entry->retval = retval;
> + __assign_str(name, core_name);
> + ),
> +
> + TP_printk("sig=%d limit=%lu dumpable=0x%lx dump_filter=0x%lx "
> + "corename=\"%s\" retval=%d",
> + __entry->sig, __entry->limit,
> + __entry->flags & MMF_DUMPABLE_MASK,
> + (__entry->flags & MMF_DUMP_FILTER_MASK) >>
> + MMF_DUMP_FILTER_SHIFT,
> + __get_str(name), __entry->retval)
> +);
> #endif /* _TRACE_SIGNAL_H */
I don't think "limit" is userfriendly name, core_limit or core_size_limit is better?
plus, we have core_pipe_limit sysctl too. (it's similar but different concept limit).
other parts looks good to me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists