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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1396268697.2110.15.camel@x220>
Date:	Mon, 31 Mar 2014 14:24:57 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Skidanov, Alexey" <Alexey.Skidanov@....com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Gabbay, Oded" <Oded.Gabbay@....com>
Subject: Re: CONFIG_PREEMPT_COUNT

Alexey,

On Mon, 2014-03-31 at 10:38 +0000, Skidanov, Alexey wrote:
> What is the purpose of CONFIG_PREEMPT_COUNT define and how I can
> define it?

CONFIG_PREEMPT_COUNT is a Kconfig macro, ie it's (in short) to be
defined as a result one of the "*config" make targets. And doing
    git grep -nw PREEMPT_COUNT

gives
    kernel/Kconfig.preempt:38:      select PREEMPT_COUNT
    kernel/Kconfig.preempt:57:config PREEMPT_COUNT
    lib/Kconfig.debug:964:  select PREEMPT_COUNT

And looking at those hits it seems PREEMPT_COUNT will be set, and
therefore CONFIG_PREEMPT_COUNT defined, if either PREEMPT or
DEBUG_ATOMIC_SLEEP are set in a .config.

(I'm not familiar with PREEMPT_COUNT. I think I never used it.)

Hope this helps,


Paul Bolle

--
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