All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linuxppc-dev@ozlabs.org, Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix TRACING_SUPPORT dependency
Date: Sat, 21 Mar 2009 17:46:04 +0100	[thread overview]
Message-ID: <20090321164604.GL11183@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0903211242530.13615@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> On Sat, 21 Mar 2009, Steven Rostedt wrote:
> > 
> > Since we know that's not an issue with PPC32, perhaps we should add (I 
> > hate to do this)...
> > 
> > 
> > 	depends on TRACE_IRQFLAGS_SUPPORT || PPC32
> > 
> > And document that the "|| PPC32" should go when PowerPC32 gets its act
> > together.  :-/
> 
> Note, the only tracer broken on PPC32 is the IRQSOFF tracer, and 
> that already depends on TRACE_IRQFLAGS_SUPPORT.

Ok, that's fine with me too. Perhaps we could add a TRACING_SUPPORT 
thing that architectures can enable - but it's probably overkill in 
this case.

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Anton Vorontsov <avorontsov@ru.mvista.com>,
	Steven Rostedt <srostedt@redhat.com>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix TRACING_SUPPORT dependency
Date: Sat, 21 Mar 2009 17:46:04 +0100	[thread overview]
Message-ID: <20090321164604.GL11183@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0903211242530.13615@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> On Sat, 21 Mar 2009, Steven Rostedt wrote:
> > 
> > Since we know that's not an issue with PPC32, perhaps we should add (I 
> > hate to do this)...
> > 
> > 
> > 	depends on TRACE_IRQFLAGS_SUPPORT || PPC32
> > 
> > And document that the "|| PPC32" should go when PowerPC32 gets its act
> > together.  :-/
> 
> Note, the only tracer broken on PPC32 is the IRQSOFF tracer, and 
> that already depends on TRACE_IRQFLAGS_SUPPORT.

Ok, that's fine with me too. Perhaps we could add a TRACING_SUPPORT 
thing that architectures can enable - but it's probably overkill in 
this case.

	Ingo

  reply	other threads:[~2009-03-21 16:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 15:09 [PATCH] tracing: Fix TRACING_SUPPORT dependency Anton Vorontsov
2009-03-20 19:04 ` Ingo Molnar
2009-03-20 19:04   ` Ingo Molnar
2009-03-20 19:39   ` Anton Vorontsov
2009-03-20 19:39     ` Anton Vorontsov
2009-03-20 19:57     ` Ingo Molnar
2009-03-20 19:57       ` Ingo Molnar
2009-03-20 20:22       ` Anton Vorontsov
2009-03-20 20:22         ` Anton Vorontsov
2009-03-21 16:18         ` Ingo Molnar
2009-03-21 16:18           ` Ingo Molnar
2009-03-21 16:31           ` Steven Rostedt
2009-03-21 16:31             ` Steven Rostedt
2009-03-21 16:33             ` Ingo Molnar
2009-03-21 16:33               ` Ingo Molnar
2009-03-21 16:41               ` Steven Rostedt
2009-03-21 16:41                 ` Steven Rostedt
2009-03-21 16:43                 ` Steven Rostedt
2009-03-21 16:43                   ` Steven Rostedt
2009-03-21 16:46                   ` Ingo Molnar [this message]
2009-03-21 16:46                     ` Ingo Molnar
2009-03-23 22:07           ` [PATCH] tracing: Fix TRACING_SUPPORT dependency for PPC32 Anton Vorontsov
2009-03-23 22:07             ` Anton Vorontsov
2009-03-23 22:24             ` [tip:tracing/ftrace] " Anton Vorontsov
2009-03-24  0:51             ` [PATCH] " Steven Rostedt
2009-03-24  0:51               ` Steven Rostedt
2009-03-24  5:43         ` [PATCH] tracing: Fix TRACING_SUPPORT dependency Benjamin Herrenschmidt
2009-03-24  5:43           ` Benjamin Herrenschmidt
2009-03-21  3:09       ` Steven Rostedt
2009-03-21  3:09         ` Steven Rostedt

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=20090321164604.GL11183@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.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.