From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Glauber Costa <gcosta@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
glommer@gmail.com, mingo@elte.hu, arjan@infradead.org
Subject: Re: [PATCH 2/2] make work have a static address in do_boot_cpu()
Date: Thu, 21 Feb 2008 23:12:47 +0100 [thread overview]
Message-ID: <1203631967.6112.16.camel@lappy> (raw)
In-Reply-To: <1203626456-3101-3-git-send-email-gcosta@redhat.com>
On Thu, 2008-02-21 at 17:40 -0300, Glauber Costa wrote:
> This patch makes the work field in create_idle have
> a static address. Otherwise, being a stack variable, it can
> boild down the lockdep system.
Looks way overkill. Doesn't something like:
> Signed-off-by: Glauber Costa <gcosta@redhat.com>
> ---
> arch/x86/kernel/smpboot_64.c | 13 +++++++------
> 1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/kernel/smpboot_64.c b/arch/x86/kernel/smpboot_64.c
> index f15b774..d79b7a8 100644
> --- a/arch/x86/kernel/smpboot_64.c
> +++ b/arch/x86/kernel/smpboot_64.c
> @@ -553,12 +554,12 @@ static int __cpuinit do_boot_cpu(int cpu
> unsigned long boot_error;
> int timeout;
> unsigned long start_rip;
> struct create_idle create_idle = {
> - .work = __WORK_INITIALIZER(create_idle.work, do_fork_idle),
> .cpu = cpu,
> .done = COMPLETION_INITIALIZER_ONSTACK(create_idle.done),
> };
> + INIT_WORK(&create_idle.work, do_fork_idle);
work?
next prev parent reply other threads:[~2008-02-21 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 20:40 [PATCH 0/2] onlining cpus can break lockdep Glauber Costa
2008-02-21 20:40 ` [PATCH 1/2] turn c_idle into a pointer Glauber Costa
2008-02-21 20:40 ` [PATCH 2/2] make work have a static address in do_boot_cpu() Glauber Costa
2008-02-21 22:12 ` Peter Zijlstra [this message]
2008-02-21 22:57 ` Glauber Costa
2008-02-22 9:46 ` Ingo Molnar
2008-02-21 21:12 ` [PATCH 0/2] onlining cpus can break lockdep Ingo Molnar
2008-02-21 21:17 ` Glauber Costa
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=1203631967.6112.16.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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