From: tip-bot for Juri Lelli <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: peterz@infradead.org, torvalds@linux-foundation.org,
tglx@linutronix.de, corbet@lwn.net, mingo@kernel.org,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
hpa@zytor.com
Subject: [tip:locking/core] Documentation/locking/lockdep: Update info about states
Date: Wed, 14 Feb 2018 03:04:11 -0800 [thread overview]
Message-ID: <tip-e5684bbfc3f03480d6ba2150f133630fb510d3eb@git.kernel.org> (raw)
In-Reply-To: <20180213185519.18186-2-juri.lelli@redhat.com>
Commit-ID: e5684bbfc3f03480d6ba2150f133630fb510d3eb
Gitweb: https://git.kernel.org/tip/e5684bbfc3f03480d6ba2150f133630fb510d3eb
Author: Juri Lelli <juri.lelli@redhat.com>
AuthorDate: Tue, 13 Feb 2018 19:55:18 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 14 Feb 2018 12:01:22 +0100
Documentation/locking/lockdep: Update info about states
Commit:
d92a8cfcb37e ("locking/lockdep: Rework FS_RECLAIM annotation")
removed the 'reclaim_fs' lockdep STATE.
Reflect the change in the documentation.
While we are at it, also clarify the formula to calculate the number of state bits.
Signed-off-by: Juri Lelli <juri.lelli@redhat.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-doc@vger.kernel.org
Link: http://lkml.kernel.org/r/20180213185519.18186-2-juri.lelli@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/locking/lockdep-design.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/lockdep-design.txt b/Documentation/locking/lockdep-design.txt
index 9de1c15..e341c2f 100644
--- a/Documentation/locking/lockdep-design.txt
+++ b/Documentation/locking/lockdep-design.txt
@@ -27,7 +27,8 @@ lock-class.
State
-----
-The validator tracks lock-class usage history into 4n + 1 separate state bits:
+The validator tracks lock-class usage history into 4 * nSTATEs + 1 separate
+state bits:
- 'ever held in STATE context'
- 'ever held as readlock in STATE context'
@@ -37,7 +38,6 @@ The validator tracks lock-class usage history into 4n + 1 separate state bits:
Where STATE can be either one of (kernel/locking/lockdep_states.h)
- hardirq
- softirq
- - reclaim_fs
- 'ever used' [ == !unused ]
next prev parent reply other threads:[~2018-02-14 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 18:55 [PATCH 0/2] Update lockdep doc and add section about annotations Juri Lelli
2018-02-13 18:55 ` [PATCH 1/2] Documentation/locking/lockdep: update info about states Juri Lelli
2018-02-14 11:04 ` tip-bot for Juri Lelli [this message]
2018-02-13 18:55 ` [RFC PATCH 2/2] Documentation/locking/lockdep: Add section about available annotations Juri Lelli
2018-02-14 11:04 ` [tip:locking/core] " tip-bot for Juri Lelli
2018-02-14 9:44 ` [PATCH 0/2] Update lockdep doc and add section about annotations Peter Zijlstra
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=tip-e5684bbfc3f03480d6ba2150f133630fb510d3eb@git.kernel.org \
--to=tipbot@zytor.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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