public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, akpm@osdl.org
Subject: Re: [PATCH] irqtrace-option-off-compile-fix
Date: Tue, 11 Jul 2006 09:23:22 -0700	[thread overview]
Message-ID: <1152635003.7654.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1152601989.3128.10.camel@laptopd505.fenrus.org>

I was testing on x86_64 and turned off the option in
arch/x86_64/Kconfig.debug. 

When the option is turned off, the following functions become undefined:
local_irq_disable()           
local_irq_enable()             
local_irq_save(flags)          
local_irq_restore(flags)       
safe_halt() 
local_save_flags()
irqs_disabled()
irqs_disabled_flags(flags)                   

It seems plausible that some users may want to avoid the overhead of
tracing IRQFLAGS by turning the option off.

Regards,
Tim Chen

On Tue, 2006-07-11 at 09:13 +0200, Arjan van de Ven wrote:
> On Mon, 2006-07-10 at 17:18 -0700, Tim Chen wrote:
> > When CONFIG_TRACE_IRQFLAGS_SUPPORT is turned off, the latest kernel has
> > compile errors.  The patch below fix the problems.
> 
> 
> Hi,
> 
> which architecture did you see this on? (asking because IA64 and PPC
> compile just fine without this, and for x86 and x86-64 this is not an
> option you can turn off as user, it's not a user selectable config
> option but it's a "I have this feature in arch" option)
> 
> Greetings,
>    Arjan van de Ven


  reply	other threads:[~2006-07-11 17:04 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 [this message]
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
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=1152635003.7654.40.camel@localhost.localdomain \
    --to=tim.c.chen@linux.intel.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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