mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [patch 0/2] Refactor spinlock inlining
Date: Mon, 09 Nov 2009 15:21:26 -0000	[thread overview]
Message-ID: <20091109150033.125758935@linutronix.de> (raw)

While moving preempt-rt to 2.6.32-rc I tripped over the spinlock
inlining changes and had a hard time to figure out when and which lock
function is inlined as the __always_inline__ defines are not directly
controlling the inlining because there are overrides depending on
various config options.

Merging the -rt modifications into this results in a horrible mess and
I tried to find a solution which simplifies the inlining decisions and
makes it more obvious when the decision is taken. 

To allow easier intergration of preempt-rt I reworked the inline
decision ifdeffery to be completely Kconfig based.

The result is slightly smaller in code lines, but adds a Kconfig file
which contains all the rules of inlining decisions. Architecturs can
select each locking function for inlining in the arch Kconfig instead
of defining __always_inline__*.

Thanks,

	tglx


             reply	other threads:[~2009-11-09 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 15:21 Thomas Gleixner [this message]
2009-11-09 15:21 ` [patch 1/2] locking: Make inlining decision Kconfig based Thomas Gleixner
2009-11-09 19:16   ` Peter Zijlstra
2009-11-09 20:27     ` Thomas Gleixner
2009-11-13  9:09   ` Heiko Carstens
2009-11-13 19:57   ` [tip:core/locking] " tip-bot for Thomas Gleixner
2009-11-09 15:21 ` [patch 2/2] locking: Reduce ifdefs in kernel/spinlock.c Thomas Gleixner
2009-11-13 19:57   ` [tip:core/locking] " tip-bot for Thomas Gleixner

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=20091109150033.125758935@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®