linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	krinkin.m.u@gmail.com, mingo@elte.hu, peterz@infradead.org,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree
Date: Tue, 9 Feb 2016 12:00:29 +0100	[thread overview]
Message-ID: <20160209110029.GA27847@gmail.com> (raw)
In-Reply-To: <56B34E87.1030604@virtuozzo.com>


* Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:

> On 02/04/2016 12:44 AM, Andrew Morton wrote:
> > 
> > Probably lockdep_init() and lockdep_initialized can be done away with now.
> > 
> 
> Yup, it probably should be folded into your patch, or we could hold this off for 4.6.
> 
> 
> From: Andrey Ryabinin <aryabinin@virtuozzo.com>                                                                                                                                                                     
> Subject: kernel/lockdep: eliminate lockdep_init()
> 
> Lockdep is initialized at compile time now. Get rid of lockdep_init().
> 
> Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> ---
>  arch/c6x/kernel/setup.c                       |  2 -
>  arch/microblaze/kernel/setup.c                |  2 -
>  arch/powerpc/kernel/setup_32.c                |  2 -
>  arch/powerpc/kernel/setup_64.c                |  3 --
>  arch/s390/kernel/early.c                      |  1 -
>  arch/sparc/kernel/head_64.S                   |  8 ----
>  arch/x86/lguest/boot.c                        |  6 ---
>  include/linux/lockdep.h                       |  2 -
>  init/main.c                                   |  5 ---
>  kernel/locking/lockdep.c                      | 59 ---------------------------
>  tools/lib/lockdep/common.c                    |  5 ---
>  tools/lib/lockdep/include/liblockdep/common.h |  1 -
>  tools/lib/lockdep/preload.c                   |  2 -
>  13 files changed, 98 deletions(-)

Very nice! Should have done this from day one on ...

Thanks,

	Ingo

  parent reply	other threads:[~2016-02-09 11:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56b11d2d.vVw1kB2la7Y+70xF%akpm@linux-foundation.org>
2016-02-03  7:44 ` + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree Ingo Molnar
2016-02-03  9:42   ` Andrey Ryabinin
2016-02-03  9:49     ` Ingo Molnar
2016-02-03 16:51   ` Andrew Morton
2016-02-03 20:40     ` Andrew Morton
2016-02-03 21:44       ` Andrew Morton
2016-02-04 13:13         ` Andrey Ryabinin
2016-02-08  9:33           ` Michael Ellerman
2016-02-09 11:00           ` Ingo Molnar [this message]
2016-02-09 11:12     ` Ingo Molnar
2016-02-09 20:17       ` Andrew Morton
2016-02-29  9:11         ` Ingo Molnar
2016-02-29  9:25           ` Ingo Molnar
2016-02-29  9:30             ` Andrey Ryabinin

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=20160209110029.GA27847@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=krinkin.m.u@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).