From: Randy Dunlap <rdunlap@infradead.org>
To: paulmck@linux.vnet.ibm.com, Richard Weinberger <richard@nod.at>
Cc: Rik van Riel <riel@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, umgwanakikbuti@gmail.com
Subject: Re: mmotm 2014-04-24-13-07 uploaded
Date: Mon, 28 Apr 2014 13:32:38 -0700 [thread overview]
Message-ID: <535EBAE6.3080907@infradead.org> (raw)
In-Reply-To: <20140428200640.GG4430@linux.vnet.ibm.com>
On 04/28/14 13:06, Paul E. McKenney wrote:
> On Mon, Apr 28, 2014 at 07:21:27PM +0200, Richard Weinberger wrote:
>> Am 28.04.2014 19:17, schrieb Randy Dunlap:
>>>
>>> uml defconfig on x86_64:
>>>
>>> CC arch/um/kernel/asm-offsets.s
>>> In file included from include/linux/sem.h:5:0,
>>> from include/linux/sched.h:35,
>>> from arch/x86/um/shared/sysdep/kernel-offsets.h:2,
>>> from arch/um/kernel/asm-offsets.c:1:
>>> include/linux/rcupdate.h:257:20: error: static declaration of 'rcu_sysrq_start' follows non-static declaration
>>> include/linux/rcupdate.h:250:6: note: previous declaration of 'rcu_sysrq_start' was here
>>> include/linux/rcupdate.h:260:20: error: static declaration of 'rcu_sysrq_end' follows non-static declaration
>>> include/linux/rcupdate.h:251:6: note: previous declaration of 'rcu_sysrq_end' was here
>>> make[2]: *** [arch/um/kernel/asm-offsets.s] Error 1
>>>
>>>
>>> Please test your patch(es).
>
> Against exactly what? ;-)
see $Subject
>> Just in case, to build an x86_64 UML please run:
>>
>> make defconfig ARCH=um SUBARCH=x86_64
>> make linux ARCH=um SUBARCH=x86_64
>
> Hmmm.... Builds without errors in my local tree.
>
> Make a clone of linux-next...
>
> OK, now I get a different build failure:
>
> /home/paulmck/public_git/linux-next/drivers/tty/sysrq.c:514: undefined reference to `rcu_sysrq_start'
> /home/paulmck/public_git/linux-next/drivers/tty/sysrq.c:558: undefined reference to `rcu_sysrq_end'
>
> This is due to Rik's "#include <linux/rcupdate.h>" getting lost somehow.
> This #include is needed in drivers/tty/sysrq.c.
>
> But maybe I need to be using some other branch of linux-next. Am currently
> on 5bd4e10b96ce20271688aa31d8bd739441249152, which is origin/master. And
> is also next-20140428. If I should be somewhere else, please let me know.
>
> OK, it also appears that my change to make TINY_RCU work is also missing,
> possibly because Randy applied it by hand.
nope.
> Please see below for a patch against next-20140428 that makes this build
> for me. This is derived from Rik's patch, my patch, and is consistent with
> Arnd's patch.
>
> Thanx, Paul
Thnx, works for me. Finally.
> ------------------------------------------------------------------------
>
> diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c
> index 6c3d11b..38d5f9a 100644
> --- a/drivers/tty/sysrq.c
> +++ b/drivers/tty/sysrq.c
> @@ -46,6 +46,7 @@
> #include <linux/jiffies.h>
> #include <linux/syscalls.h>
> #include <linux/of.h>
> +#include <linux/rcupdate.h>
>
> #include <asm/ptrace.h>
> #include <asm/irq_regs.h>
> diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> index e9cc71c..7b0a669 100644
> --- a/include/linux/rcupdate.h
> +++ b/include/linux/rcupdate.h
> @@ -247,8 +247,17 @@ void rcu_idle_enter(void);
> void rcu_idle_exit(void);
> void rcu_irq_enter(void);
> void rcu_irq_exit(void);
> +#ifdef CONFIG_RCU_STALL_COMMON
> void rcu_sysrq_start(void);
> void rcu_sysrq_end(void);
> +#else /* #ifdef CONFIG_RCU_STALL_COMMON */
> +static inline void rcu_sysrq_start(void)
> +{
> +}
> +static inline void rcu_sysrq_end(void)
> +{
> +}
> +#endif /* #else #ifdef CONFIG_RCU_STALL_COMMON */
>
> #ifdef CONFIG_RCU_USER_QS
> void rcu_user_enter(void);
> diff --git a/kernel/rcu/update.c b/kernel/rcu/update.c
> index 20caaf0..a2aeb4d 100644
> --- a/kernel/rcu/update.c
> +++ b/kernel/rcu/update.c
> @@ -322,7 +322,8 @@ int rcu_jiffies_till_stall_check(void)
>
> void rcu_sysrq_start(void)
> {
> - rcu_cpu_stall_suppress = 2;
> + if (!rcu_cpu_stall_suppress)
> + rcu_cpu_stall_suppress = 2;
> }
>
> void rcu_sysrq_end(void)
>
> --
--
~Randy
next prev parent reply other threads:[~2014-04-28 20:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:08 mmotm 2014-04-24-13-07 uploaded akpm
2014-04-24 22:40 ` Randy Dunlap
2014-04-25 2:49 ` Paul E. McKenney
2014-04-25 11:37 ` Rik van Riel
2014-04-25 13:25 ` Rik van Riel
2014-04-25 14:04 ` Rik van Riel
2014-04-25 20:44 ` Randy Dunlap
2014-04-25 20:52 ` Randy Dunlap
2014-04-27 6:26 ` Paul E. McKenney
2014-04-27 17:27 ` Randy Dunlap
2014-04-27 20:40 ` Randy Dunlap
2014-04-28 0:26 ` Paul E. McKenney
2014-04-28 13:55 ` Paul E. McKenney
2014-04-28 17:17 ` Randy Dunlap
2014-04-28 17:21 ` Richard Weinberger
2014-04-28 20:06 ` Paul E. McKenney
2014-04-28 20:32 ` Randy Dunlap [this message]
2014-04-28 21:15 ` Paul E. McKenney
2014-04-28 21:59 ` Randy Dunlap
2014-04-29 12:07 ` Rik van Riel
2014-04-29 16:36 ` Paul E. McKenney
2014-04-29 17:31 ` Rik van Riel
2014-04-29 17:45 ` Paul E. McKenney
2014-04-28 21:39 ` Paul E. McKenney
2014-04-28 23:05 ` Andrew Morton
2014-04-28 23:42 ` Stephen Rothwell
2014-04-24 22:51 ` mmotm 2014-04-24-13-07 uploaded (regulator/arizona-ldo1.c) Randy Dunlap
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=535EBAE6.3080907@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=richard@nod.at \
--cc=riel@redhat.com \
--cc=umgwanakikbuti@gmail.com \
/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).