linux-kernel - Re: [PATCH] spmi-pmic-arb: add irq tracepoints to the pmic-arb driver

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 May 2015 13:06:29 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Ankit Gupta <ankgupta@...eaurora.org>
Cc:	gavidov@...eaurora.org, sdharia@...eaurora.org,
	ivan.ivanov@...aro.org, svarbanov@...sol.com, rostedt@...dmis.org,
	linux-arm-msm@...r.kernel.org, gregkh@...uxfoundation.org,
	collinsd@...eaurora.org, osvaldob@...eaurora.org,
	linux-kernel@...r.kernel.org, mlocke@...eaurora.org,
	galak@...eaurora.org, agross@...eaurora.org
Subject: Re: [PATCH] spmi-pmic-arb: add irq tracepoints to the pmic-arb driver

On 05/27, Ankit Gupta wrote:
> >
> > How is this any better than irq tracepoints that we already have for
> > generic irqs?
> >
> It is better than generic irq tracepoints because it provides bus specific
> information (sid and address(pid) of slave write), driver specific
> information (apid (pmic-peripheral) and func_num) and statistics (apid
> range).
> Recall that *slave* read/write cannot be traced by the spmi framework ftrace.
> 

Don't we already get all this information based on how we map
interrupts to devices in DT? It feels to me that the same
argument here could be applied to all the random gpio expanders
and chained interrupt controllers that we support in the kernel.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
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/