Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
From: Ingo Molnar <mingo@xxxxxxxxxx>
Date: Wed, 14 Oct 2015 19:48:51 +0200
Cc: Andy Lutomirski <luto@xxxxxxxxxxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, Paul McKenney <paulmck@xxxxxxxxxxxxxxxxxx>, tip-bot for Andrey Ryabinin <tipbot@xxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>, kasan-dev <kasan-dev@xxxxxxxxxxxxxxxx>, Kostya Serebryany <kcc@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Sasha Levin <sasha.levin@xxxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Wolfram Gloger <wmglo@xxxxxxxxxxxxxxxxxxxxxxxx>, Andrey Konovalov <andreyknvl@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Alexander Potapenko <glider@xxxxxxxxxx>
In-reply-to: <20151014163423.GI3816@twins.programming.kicks-ass.net>
User-agent: Mutt/1.5.23 (2014-03-12)

* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> > I'd still rather find a way to just delete get_wchan, but whatever.
> 
> :-)

AFAICS can only do that at the price of slowing down various scheduler functions 
by saving the caller address.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Andy Lutomirski

References:
- [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: tip-bot for Andrey Ryabinin
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Paul E. McKenney
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Dmitry Vyukov
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Paul E. McKenney
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Dmitry Vyukov
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Peter Zijlstra
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Dmitry Vyukov
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Peter Zijlstra
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Andy Lutomirski
- Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
  - From: Peter Zijlstra

Prev by Date: Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
Next by Date: Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
Previous by thread: Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
Next by thread: Re: [tip:locking/urgent] compiler, atomics: Provide READ_ONCE_NOCHECK ()
Index(es):
- Date
- Thread

[Index of Archives] [Linux Stable Commits] [Linux Stable Kernel] [Linux Kernel] [Linux USB Devel] [Linux Video &Media] [Linux Audio Users] [Yosemite News] [Linux SCSI]