From: Ingo Molnar <mingo@elte.hu>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] irqtrace-option-off-compile-fix
Date: Tue, 11 Jul 2006 21:45:05 +0200 [thread overview]
Message-ID: <20060711194505.GA25611@elte.hu> (raw)
In-Reply-To: <1152644540.3578.1.camel@localhost.localdomain>
* Tim Chen <tim.c.chen@linux.intel.com> wrote:
> > The one you want is CONFIG_TRACE_IRQFLAGS .. which is the one that
> > actually turns the tracing on
>
> I could not turn off CONFIG_TRACE_IRQFLAGS_SUPPORT in .config
> directly. The command "scripts/kconfig/conf -s arch/x86_64/Kconfig" in
> Makefile overwrites changes made to CONFIG_TRACE_IRQFLAGS_SUPPORT in
> .config file. So this is always turned on in .config if the option
> TRACE_IRQFLAGS_SUPPORT is set in arch/x86_64/Kconfig.debug. I may be
> missing something. Any suggestions?
correct, that flag is always set - it signals towards the core kernel
that the architecture in question (x86_64) that it has trace-irqflags
support. NOTE: this does not mean that irqflags tracing is turned on -
that is another option: CONFIG_TRACE_IRQFLAGS.
unsetting the support flag makes no sense and will likely break the
build. There is no overhead from irqflags tracing if it's turned off.
(even if the CONFIG_TRACE_IRQFLAGS_SUPPORT option is set)
does this explain things? We could rename the boolean value to
CONFIG_TRACE_IRQFLAGS_SUPPORT_AVAILABLE perhaps, to avoid future
confusion.
Ingo
next prev parent reply other threads:[~2006-07-11 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 0:18 [PATCH] irqtrace-option-off-compile-fix Tim Chen
2006-07-11 7:13 ` Arjan van de Ven
2006-07-11 16:23 ` Tim Chen
2006-07-11 17:13 ` Arjan van de Ven
2006-07-11 16:36 ` Tim Chen
2006-07-11 18:05 ` Arjan van de Ven
2006-07-11 19:02 ` Tim Chen
2006-07-11 19:45 ` Ingo Molnar [this message]
2006-07-11 19:48 ` Tim Chen
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=20060711194505.GA25611@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox