linux-kernel - Re: ftrace function-graph and interprocessor interrupts

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]

Message-ID: <87mw9oelje.fsf@tassilo.jf.intel.com>
Date:	Wed, 24 Sep 2014 14:49:41 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	"Elliott\, Robert \(Server Storage\)" <Elliott@...com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"Jens Axboe \<axboe\@kernel.dk\> \(axboe\@kernel.dk\)" 
	<axboe@...nel.dk>, Christoph Hellwig <hch@....de>
Subject: Re: ftrace function-graph and interprocessor interrupts

"Elliott, Robert (Server Storage)" <Elliott@...com> writes:

> The function-graph tracer marks some interrupt handler functions
> with ==========>  and <========== labels.

I'm not sure the marking is really that useful. Isn't it always obvious
from the function names where an interrupt starts/end?

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/