[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201013125206.GU2611@hirez.programming.kicks-ass.net>
Date: Tue, 13 Oct 2020 14:52:06 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Boqun Feng <boqun.feng@...il.com>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 04/24] docs: lockdep-design: fix some warning issues
On Tue, Oct 13, 2020 at 02:14:31PM +0200, Mauro Carvalho Chehab wrote:
> + ===== ===================================================
> + ``.`` acquired while irqs disabled and not in irq context
> + ``-`` acquired in irq context
> + ``+`` acquired with irqs enabled
> + ``?`` acquired in irq context with irqs enabled.
> + ===== ===================================================
>
> The bits are illustrated with an example::
>
> @@ -96,14 +99,14 @@ exact case is for the lock as of the reporting time.
> +--------------+-------------+--------------+
> | | irq enabled | irq disabled |
> +--------------+-------------+--------------+
> - | ever in irq | ? | - |
> + | ever in irq | ``?`` | ``-`` |
> +--------------+-------------+--------------+
> - | never in irq | + | . |
> + | never in irq | ``+`` | ``.`` |
> +--------------+-------------+--------------+
>
> -The character '-' suggests irq is disabled because if otherwise the
> -charactor '?' would have been shown instead. Similar deduction can be
> -applied for '+' too.
> +The character ``-`` suggests irq is disabled because if otherwise the
> +charactor ``?`` would have been shown instead. Similar deduction can be
> +applied for ``+`` too.
>
NAK!
Powered by blists - more mailing lists