[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181019105851.GG3121@hirez.programming.kicks-ass.net>
Date: Fri, 19 Oct 2018 12:58:51 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Dmitry Vyukov <dvyukov@...gle.com>,
Clark Williams <williams@...hat.com>,
Alexander Potapenko <glider@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] mm/kasan: make quarantine_lock a raw_spinlock_t
On Mon, Oct 15, 2018 at 04:35:29PM -0700, Andrew Morton wrote:
> On Sat, 13 Oct 2018 15:50:58 +0200 Peter Zijlstra <peterz@...radead.org> wrote:
>
> > The whole raw_spinlock_t is for RT, no other reason.
>
> Oh. I never realised that.
>
> Is this documented anywhere? Do there exist guidelines which tell
> non-rt developers and reviewers when it should be used?
I'm afraid not; I'll put it on the todo list ... I've also been working
on some lockdep validation for the lock order stuff.
Powered by blists - more mailing lists