lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 29 Jul 2010 16:33:54 +0800
From:	Luming Yu <luming.yu@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: reasonable to compile out trace_irqflags completely ?

Hi there,

Anyone knows if there is value to have a patch to compile out
TRACE_IRQFLAGS_SUPPORT?
if there is one already, please share it with me, since I'm wondering
if it could be casuing
some performance problem I've.

Thanks,
Luming

  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CC      arch/x86/kernel/asm-offsets.s
In file included from /root/linux-2.6.32/arch/x86/include/asm/system.h:304,
                 from /root/linux-2.6.32/arch/x86/include/asm/processor.h:17,
                 from include/linux/prefetch.h:14,
                 from include/linux/list.h:6,
                 from include/linux/module.h:9,
                 from include/linux/crypto.h:21,
                 from arch/x86/kernel/asm-offsets_64.c:8,
                 from arch/x86/kernel/asm-offsets.c:4:
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:846: error:
expected identifier or â(â before âdoâ
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:846: error:
expected identifier or â(â before âwhileâ
In file included from /root/linux-2.6.32/arch/x86/include/asm/system.h:304,
                 from /root/linux-2.6.32/arch/x86/include/asm/processor.h:17,
                 from include/linux/prefetch.h:14,
                 from include/linux/list.h:6,
                 from include/linux/module.h:9,
                 from include/linux/crypto.h:21,
                 from arch/x86/kernel/asm-offsets_64.c:8,
                 from arch/x86/kernel/asm-offsets.c:4:
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:851:46: error:
macro "raw_local_irq_disable" passed 1 arguments, but takes just 0
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:852: error:
expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:856:45: error:
macro "raw_local_irq_enable" passed 1 arguments, but takes just 0
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:857: error:
expected â=â, â,â, â;â, âasmâ or â__attribute__â before â{â token
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h: In function
â__raw_local_irq_saveâ:
/root/linux-2.6.32/arch/x86/include/asm/paravirt.h:866: error:
implicit declaration of function âlocal_irq_disableâ
In file included from include/linux/spinlock.h:344,
                 from include/linux/seqlock.h:29,
                 from include/linux/time.h:8,
                 from include/linux/stat.h:60,
                 from include/linux/module.h:10,
                 from include/linux/crypto.h:21,
                 from arch/x86/kernel/asm-offsets_64.c:8,
                 from arch/x86/kernel/asm-offsets.c:4:
include/linux/spinlock_api_smp.h: In function â__spin_lock_irqsaveâ:
include/linux/spinlock_api_smp.h:245: error: implicit declaration of
function âlocal_irq_saveâ
include/linux/spinlock_api_smp.h: In function â__spin_unlock_irqrestoreâ:
include/linux/spinlock_api_smp.h:375: error: implicit declaration of
function âlocal_irq_restoreâ
include/linux/spinlock_api_smp.h: In function â__spin_unlock_irqâ:
include/linux/spinlock_api_smp.h:383: error: implicit declaration of
function âlocal_irq_enableâ
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
[root@...alhost linux-2.6.32]# grep -i trace_irqflag .config
# CONFIG_TRACE_IRQFLAGS_SUPPORT is not set
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ