From: Andrew Morton <akpm@linux-foundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Henrik Kretzschmar <henne@nachtwindheim.de>,
steffen.klassert@secunet.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] padata: section cleanup
Date: Wed, 31 Mar 2010 14:58:17 -0700 [thread overview]
Message-ID: <20100331145817.bd0a1a08.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100329081550.GA22334@gondor.apana.org.au>
On Mon, 29 Mar 2010 16:15:50 +0800
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sat, Mar 27, 2010 at 07:53:46AM +0100, Henrik Kretzschmar wrote:
> > This patch removes the __cupinit from padata_cpu_callback(),
> > which is refered by the exportet function padata_alloc().
> >
> > This could lead to problems if CONFIG_HOTPLUG_CPU is disabled,
> > which should happen very often.
> >
> > WARNING: kernel/built-in.o(.text+0x7ffcb): Section mismatch in reference from the function padata_alloc() to the function .cpuinit.text:padata_cpu_callback()
> > The function padata_alloc() references
> > the function __cpuinit padata_cpu_callback().
> > This is often because padata_alloc lacks a __cpuinit
> > annotation or the annotation of padata_cpu_callback is wrong.
> >
> > Signed-off-by: Henrik Kretzschmar <henne@nachtwindheim.de>
>
> Patch applied. Thanks!
(wtf?)
OK, on behalf of thousands I ask: what the heck is kernel/padata.c?
Seems to have popped up in 2.6.34, positioned as generic kernel-wide
code only it has been secreted away on the linux-crypto list. Please
don't do this.
What is it for, how does it work, where might it otherwise be used,
what are the dynamics, why does it use softirqs rather than (say)
kernel threads and how do we stop it from using yield()?
next prev parent reply other threads:[~2010-03-31 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 6:53 [PATCH] padata: section cleanup Henrik Kretzschmar
2010-03-29 7:42 ` Steffen Klassert
2010-03-29 8:15 ` Herbert Xu
2010-03-31 21:58 ` Andrew Morton [this message]
2010-04-01 0:24 ` Herbert Xu
2010-03-31 22:04 ` Andrew Morton
2010-04-01 1:38 ` Herbert Xu
2010-04-01 0:29 ` Andrew Morton
2010-04-01 7:15 ` David Miller
2010-04-01 13:59 ` Andrew Morton
2010-04-01 8:11 ` Steffen Klassert
2010-04-01 21:59 ` Andrew Morton
2010-04-02 1:09 ` Herbert Xu
2010-04-02 11:23 ` Steffen Klassert
2010-04-06 18:00 ` Jonathan Corbet
2010-04-07 13:34 ` Steffen Klassert
2010-04-29 12:14 ` Steffen Klassert
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=20100331145817.bd0a1a08.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=henne@nachtwindheim.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen.klassert@secunet.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).