linux-kernel - Re: [PATCH] trace: add the MMIO-tracer to the tracer menu

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: <alpine.DEB.1.10.0810240755290.25677@gandalf.stny.rr.com>
Date:	Fri, 24 Oct 2008 07:56:05 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Pekka Paalanen <pq@....fi>
Subject: Re: [PATCH] trace: add the MMIO-tracer to the tracer menu


On Fri, 24 Oct 2008, Ingo Molnar wrote:
> >  #
> >  # IO delay types:
> > Index: linux-2.6/kernel/trace/Kconfig
> > ===================================================================
> > --- linux-2.6.orig/kernel/trace/Kconfig
> > +++ linux-2.6/kernel/trace/Kconfig
> > @@ -194,4 +194,32 @@ config FTRACE_STARTUP_TEST
> >  	  functioning properly. It will do tests on all the configured
> >  	  tracers of ftrace.
> >  
> > +config MMIOTRACE_HOOKS
> > +	bool
> > +
> > +config MMIOTRACE
> > +	bool "Memory mapped IO tracing"
> > +	depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI
> > +	select TRACING
> > +	select MMIOTRACE_HOOKS
> 
> change makes sense, but isnt MMIOTRACE_HOOKS basically overlapping 
> HAVE_MMIOTRACE_SUPPORT? So i think we could get rid of MMIOTRACE_HOOKS 
> altogether and just use HAVE_MMIOTRACE_SUPPORT.

And doing this will remove the need about my question on depends on X86.

-- Steve

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