linux-kernel - [PATCH v2] Tracing events with GPIOs

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: <1387482876-17454-1-git-send-email-jjhiblot@traphandler.com>
Date:	Thu, 19 Dec 2013 20:54:35 +0100
From:	Jean-Jacques Hiblot <jjhiblot@...phandler.com>
To:	masami.hiramatsu.pt@...achi.com, tom.zanussi@...ux.intel.com,
	gnurou@...il.com
Cc:	rostedt@...dmis.org, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jean-Jacques Hiblot <jjhiblot@...phandler.com>
Subject: [PATCH v2] Tracing events with GPIOs

Following the advice of Masami, I implemented the GPIO trace on top of the event
triggers (git://git.yoctoproject.org/linux-yocto-contrib
tzanussi/event-triggers-v11)

Alexandre,
This version uses the old gpio API (i-e gpio identifed by integers). GPIOs are
not requested in this patch, allowing any gpio to be used as a probe. It's a bit
dangerous but I think it's okay for the moment. When this patch is adapted to the
gpio descriptor API, we'll have to find a way to request the gpio properly.

Jean-Jacques Hiblot (1):
  Tracing events with GPIOs

 include/linux/ftrace_event.h        |   1 +
 kernel/trace/trace_events_trigger.c | 285 ++++++++++++++++++++++++++++++++++++
 2 files changed, 286 insertions(+)

-- 
1.8.3.1

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