Added Ingo as well. On Thu, 16 Jul 2009, Eric Sandeen wrote: > Christoph Hellwig wrote: > > On Mon, Jun 22, 2009 at 01:01:35PM -0500, Felix Blyakher wrote: > >>> To use it make sure CONFIG_EVENT_TRACING is enabled and then enable > >>> all > >>> xfs trace channels by: > >>> > >>> echo 1 > /sys/kernel/debug/tracing/events/xfs/enable > >> Does event tracing work on ia64 platform? > >> I spent some time on it over weekend, but was not able even > >> to force "CONFIG_EVENT_TRACING=y" setting in the .config. > >> Seems to build ok on x86_64, which does have CONFIG_TRACING > >> in defconfig, and allows to set CONFIG_EVENT_TRACING. > > > > IA64 ftrace support was added earlier this year, but it seems it can't > > be enabled anymore since the big config option reshuffle. Now tracing > > support requires the architecture to define the TRACE_IRQFLAGS_SUPPORT > > and STACKTRACE_SUPPORT symbols, which seems to be missing on ia64. > > Where are we at with this one, I'd like to get this in for XFS but I > agree w/ Felix that throwing out a "working" trace infrastructure w/ > nothing to replace it on ia64 would not be great. > > Is this just config confusion, or is the functionality actually missing > on ia64? For PPC32, we have stacktrace support but there was lots of issues with the IRQFLAGS support. Namely, issues with handling traces in assembly when interrupts are off. Hence, we have an exception for PPC32 with the IRQFLAGS config. Is there a reason that we can't have STACKTRACE_SUPPORT for ia64? Perhaps it should be implemented? Probably not that difficult. Then we can add an exception for ia64 too if there's a technical reason that IRQFLAGS is not supported. Otherwise, IRQFLAGS should also be ported. That way, ia64 would benefit from lockdep as well. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|