All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ia64@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
	xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfs: event tracing support
Date: Thu, 16 Jul 2009 22:22:39 +0000	[thread overview]
Message-ID: <4A5FA82F.6050903@sandeen.net> (raw)
In-Reply-To: <20090622205904.GA1855@infradead.org>

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?

Thanks,
-Eric

WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ia64@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
	xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfs: event tracing support
Date: Thu, 16 Jul 2009 17:22:39 -0500	[thread overview]
Message-ID: <4A5FA82F.6050903@sandeen.net> (raw)
In-Reply-To: <20090622205904.GA1855@infradead.org>

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?

Thanks,
-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-07-16 22:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 21:48 [PATCH, RFC] xfs: event tracing support Christoph Hellwig
2009-06-22 18:01 ` Felix Blyakher
2009-06-22 20:59   ` Christoph Hellwig
2009-06-22 21:37     ` Felix Blyakher
2009-07-16 22:22     ` Eric Sandeen [this message]
2009-07-16 22:22       ` Eric Sandeen
2009-07-16 22:35       ` Steven Rostedt
2009-07-16 22:35         ` Steven Rostedt
2009-07-17 14:09       ` Christoph Hellwig
2009-07-17 14:09         ` Christoph Hellwig
2009-07-17 14:50 ` [PATCH] " Christoph Hellwig
2009-07-17 14:50   ` Christoph Hellwig
2009-07-17 18:04   ` Christoph Hellwig
2009-07-17 18:04     ` Christoph Hellwig
2009-07-17 18:40     ` Eric Sandeen
2009-07-18 14:02       ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5FA82F.6050903@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.