linux-kernel - TRACE_EVENT without ARGS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <505C8937.4040505@grandegger.com>
Date:	Fri, 21 Sep 2012 17:35:19 +0200
From:	Wolfgang Grandegger <wg@...ndegger.com>
To:	LKML <linux-kernel@...r.kernel.org>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>
Subject: TRACE_EVENT without ARGS

Hello,

I would like to define trace events for functions without arguments,
e.g. my_yield(). But TRACE_EVENT requires at least one argument to be
defined and I also have not found an example in the kernel sources,
apart from:

  $ cat include/trace/events/xen.h
  ...
  TRACE_EVENT(xen_mmu_flush_tlb,
              TP_PROTO(int x),
              TP_ARGS(x),
              TP_STRUCT__entry(__array(char, x, 0)),
              TP_fast_assign((void)x),
              TP_printk("%s", "")
          );

It uses a dummy argument to work around the problem. Is that the
recommended way to handle such cases?

TIA,

Wolfgang
--
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/