linux-kernel - Re: Function Profiler broken on today's linux-next

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: <20140716122921.71b118a9@gandalf.local.home>
Date:	Wed, 16 Jul 2014 12:29:21 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	<balbi@...com>
Cc:	<will.deacon@....com>, <mingo@...hat.com>,
	Linux ARM Kernel Mailing List 
	<linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: Function Profiler broken on today's linux-next

On Wed, 16 Jul 2014 11:23:28 -0500
Felipe Balbi <balbi@...com> wrote:

> Hi folks,
> 
> I was trying to use Kernel Function Profiler to figure out why my
> driver's IRQ handler is taking so much CPU time but to my surprise,
> whenever I try to trace anything, I get a "Unable to handle kernel
> paging request at virtual address XXXX" error.
> 
> Is anybody else seen that or did I screw up my Kernel config ?

No, it's probably my fault. The ftrace infrastructure is going through
an overhaul and some dramatic changes are happening. Although it has
passed all my tests, I can't cover everyone's configs and use cases.

Please send me your config and the steps you did to enable function
profiling. This is x86 correct? Other archs are already known to be
broken and I'm working on fixing them now.

-- Steve



> 
> cheers
> 
> ps: I have tried tracing a few different drivers and they all trigger
> the same problem.
> 

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