From: Steven Rostedt <rostedt@goodmis.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: tglx@linutronix.de, mingo@kernel.org, paulmck@linux.vnet.ibm.com,
josh@joshtriplett.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preempt/hardirq.h: Fix comment about PREEMPT_ACTIVE bit location
Date: Mon, 30 Jul 2012 23:49:43 -0400 [thread overview]
Message-ID: <1343706583.27983.28.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120720192459.6149.14821.stgit@srivatsabhat.in.ibm.com>
On Sat, 2012-07-21 at 00:54 +0530, Srivatsa S. Bhat wrote:
> PREEMPT_ACTIVE flag is bit 27, not 28. Fix the comment.
>
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> ---
>
> include/linux/hardirq.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/hardirq.h b/include/linux/hardirq.h
> index bb7f309..305f23c 100644
> --- a/include/linux/hardirq.h
> +++ b/include/linux/hardirq.h
> @@ -22,7 +22,7 @@
> *
> * - bits 16-25 are the hardirq count (max # of nested hardirqs: 1024)
> * - bit 26 is the NMI_MASK
> - * - bit 28 is the PREEMPT_ACTIVE flag
> + * - bit 27 is the PREEMPT_ACTIVE flag
Sorry but in arch/x86/include/asm/thread_info.h we have:
#define PREEMPT_ACTIVE 0x10000000
Which happens to be the 28th bit, not 27th. Although, if an arch did not
define PREEMPT_ACTIVE it would be 27th.
Perhaps the correct thing to do is to say:
By default the following bits are defined as:
[...]
Different architectures may modify these.
And then add your change.
-- Steve
> *
> * PREEMPT_MASK: 0x000000ff
> * SOFTIRQ_MASK: 0x0000ff00
next prev parent reply other threads:[~2012-07-31 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 19:24 Srivatsa S. Bhat
2012-07-26 15:15 ` [tip:sched/urgent] sched: " tip-bot for Srivatsa S. Bhat
2012-07-31 3:49 ` Steven Rostedt [this message]
2012-08-14 8:26 ` [PATCH] preempt/hardirq.h: " Srivatsa S. Bhat
2012-08-14 8:28 ` [PATCH] preempt/hardirq.h: Clarify " Srivatsa S. Bhat
2012-08-14 10:18 ` Thomas Gleixner
2012-08-14 12:46 ` Steven Rostedt
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=1343706583.27983.28.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®