From: Paul Bolle <pebolle@tiscali.nl>
To: "Skidanov, Alexey" <Alexey.Skidanov@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gabbay, Oded" <Oded.Gabbay@amd.com>
Subject: Re: CONFIG_PREEMPT_COUNT
Date: Mon, 31 Mar 2014 14:24:57 +0200 [thread overview]
Message-ID: <1396268697.2110.15.camel@x220> (raw)
In-Reply-To: <AD975D71AAD7784D8D1265DF6444C2FD0132AD51@storexdag03.amd.com>
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
next prev parent reply other threads:[~2014-03-31 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:38 CONFIG_PREEMPT_COUNT Skidanov, Alexey
2014-03-31 12:24 ` Paul Bolle [this message]
2014-03-31 12:50 ` CONFIG_PREEMPT_COUNT Skidanov, Alexey
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=1396268697.2110.15.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=Alexey.Skidanov@amd.com \
--cc=Oded.Gabbay@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome