mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	David Daney <david.daney@cavium.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: Linux 3.10-rc6
Date: Mon, 17 Jun 2013 13:30:55 -0700	[thread overview]
Message-ID: <20130617133055.20463ce157e104af15ef60a1@linux-foundation.org> (raw)
In-Reply-To: <CA+55aFzw7b7qH37ZLSCAZ8xTd5ez2q44LmeY+GLFPsHEqDPfxA@mail.gmail.com>

On Sun, 16 Jun 2013 08:01:44 -1000 Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sat, Jun 15, 2013 at 10:36 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> >
> > On Sun, Jun 16, 2013 at 12:12 AM, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > > David Daney (3):
> > >       smp.h: Use local_irq_{save,restore}() in !SMP version of on_each_cpu().
> >
> > This change (commit f21afc25f9ed45b8ffe200d0f071b0caec3ed2ef, which hasn't
> > been in linux-next), broke at least mn10300 and ia64:
> >
> > include/linux/smp.h:148:2: error: implicit declaration of function 'local_irq_save' [-Werror=implicit-function-declaration]
> 
> Hmm. DavidD already added the include for <linux/irqflags.h>, I wonder
> why that doesn't end up working. Do we have some silly header file
> circular include that means that we're already half-way through that
> irqflags.h file and thus will skip it the second time we see it, or
> why does it end up being undeclared?

Heaven knows; I don't think now is the time to try to fix this.

If I'd thought for two seconds I wouldn't have sent that patch at this
time - additional low-level includes in low-level header files are
often problematic.

> Anyway, I see a few options:
> 
>  - we could just make it a macro like it used to be (keeping the
> include and assuming that will sort out any circular include mess) and
> use a rare name for the internal "flags" variable (just prepending
> double underscores is the common one we tend to use in situations like
> this)
> 
>  - we could just make it a real function, the way the SMP one is, and
> take the extra call overhead (it's not like this should be all that
> critical in an UP environment).
> 
>  - somebody figures out why the <linux/irqflags.h> include ends up not
> working on nm10300 and ia64..

Methinks we should fight this battle at a later date.  I queued this:

From: Andrew Morton <akpm@linux-foundation.org>
Subject: include/linux/smp.h:on_each_cpu(): switch back to a macro

f21afc25f9ed4 ("smp.h: Use local_irq_{save,restore}() in !SMP version of
on_each_cpu()") converted on_each_cpu() to a C function.  This required
inclusion of irqflags.h, which broke ia64 and mn10300 (at least) due to
header ordering hell.

Switch on_each_cpu() back to a macro to fix this.

Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Daney <david.daney@cavium.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 include/linux/smp.h |   20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)

diff -puN include/linux/smp.h~include-linux-smph-on_each_cpu-switch-back-to-a-macro include/linux/smp.h
--- a/include/linux/smp.h~include-linux-smph-on_each_cpu-switch-back-to-a-macro
+++ a/include/linux/smp.h
@@ -11,7 +11,6 @@
 #include <linux/list.h>
 #include <linux/cpumask.h>
 #include <linux/init.h>
-#include <linux/irqflags.h>
 
 extern void cpu_idle(void);
 
@@ -140,17 +139,14 @@ static inline int up_smp_call_function(s
 }
 #define smp_call_function(func, info, wait) \
 			(up_smp_call_function(func, info))
-
-static inline int on_each_cpu(smp_call_func_t func, void *info, int wait)
-{
-	unsigned long flags;
-
-	local_irq_save(flags);
-	func(info);
-	local_irq_restore(flags);
-	return 0;
-}
-
+#define on_each_cpu(func,info,wait)		\
+	({					\
+		unsigned long flags;		\
+		local_irq_save(flags);		\
+		func(info);			\
+		local_irq_restore(flags);	\
+		0;				\
+	})
 /*
  * Note we still need to test the mask even for UP
  * because we actually can get an empty mask from
_


  reply	other threads:[~2013-06-17 20:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 22:12 Linus Torvalds
2013-06-16  8:36 ` Geert Uytterhoeven
2013-06-16 18:01   ` Linus Torvalds
2013-06-17 20:30     ` Andrew Morton [this message]
2013-06-17 20:48       ` David Daney
2013-06-17 20:59         ` Andrew Morton
2013-06-17 21:08           ` David Daney
2013-06-17 21:13             ` Andrew Morton
2013-06-17 21:26               ` David Daney
2013-06-17 21:38                 ` Andrew Morton
2013-06-18  8:37                   ` Geert Uytterhoeven
2013-06-19 16:57                   ` David Daney
2013-06-17 21:22       ` Geert Uytterhoeven
2013-06-16 12:37 ` Martin Steigerwald
2013-06-16 12:52   ` Linus Walleij
2013-06-16 13:45     ` Martin Steigerwald
2013-06-16 18:09   ` Linus Torvalds
2013-06-16 18:28     ` Linus Torvalds
2013-06-16 22:18       ` Davidlohr Bueso
2013-06-16 18:51     ` Martin Steigerwald
2013-06-16 19:51       ` Al Viro
2013-06-20  3:14         ` Steven Rostedt
2013-06-16 19:26     ` Guenter Roeck

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=20130617133055.20463ce157e104af15ef60a1@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david.daney@cavium.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=torvalds@linux-foundation.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®