linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Add machine initcall macros
Date: Sat, 01 Dec 2007 16:10:58 +1100	[thread overview]
Message-ID: <1196485858.13230.123.camel@pasglop> (raw)
In-Reply-To: <20071201002437.22923.31304.stgit@trillian.secretlab.ca>


On Fri, 2007-11-30 at 17:24 -0700, Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
> 
> The machine initcall macros allow initcalls to be registered which
> test machine_is() before executing the initcall.
> 
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
> 
> Ben, is this the sort of thing you're considering?

Exactly. You can add core and postcore while at it, I had use for them
in the past :-)

I'll look into turning that into magic ELF sections later, but in the
meantime, that gives us a nice solid API for use by BSPs.

Thanks !

Ben.

> g.
> 
>  include/asm-powerpc/machdep.h |   19 +++++++++++++++++++
>  1 files changed, 19 insertions(+), 0 deletions(-)
> 
> diff --git a/include/asm-powerpc/machdep.h b/include/asm-powerpc/machdep.h
> index 6968f43..f24af06 100644
> --- a/include/asm-powerpc/machdep.h
> +++ b/include/asm-powerpc/machdep.h
> @@ -326,5 +326,24 @@ static inline void log_error(char *buf, unsigned int err_type, int fatal)
>  		ppc_md.log_error(buf, err_type, fatal);
>  }
>  
> +#define __define_machine_initcall(mach,level,fn,id) \
> +	static int __init __machine_initcall_##mach##_##fn(void) { \
> +		if (machine_is(mach)) return fn(); \
> +		return 0; \
> +	} \
> +	__define_initcall(level,__machine_initcall_##mach##_##fn,id);
> +
> +#define machine_arch_initcall(mach,fn)		__define_machine_initcall(mach,"3",fn,3)
> +#define machine_arch_initcall_sync(mach,fn)	__define_machine_initcall(mach,"3s",fn,3s)
> +#define machine_subsys_initcall(mach,fn)	__define_machine_initcall(mach,"4",fn,4)
> +#define machine_subsys_initcall_sync(mach,fn)	__define_machine_initcall(mach,"4s",fn,4s)
> +#define machine_fs_initcall(mach,fn)		__define_machine_initcall(mach,"5",fn,5)
> +#define machine_fs_initcall_sync(mach,fn)	__define_machine_initcall(mach,"5s",fn,5s)
> +#define machine_rootfs_initcall(mach,fn)	__define_machine_initcall(mach,"rootfs",fn,rootfs)
> +#define machine_device_initcall(mach,fn)	__define_machine_initcall(mach,"6",fn,6)
> +#define machine_device_initcall_sync(mach,fn)	__define_machine_initcall(mach,"6s",fn,6s)
> +#define machine_late_initcall(mach,fn)		__define_machine_initcall(mach,"7",fn,7)
> +#define machine_late_initcall_sync(mach,fn)	__define_machine_initcall(mach,"7s",fn,7s)
> +
>  #endif /* __KERNEL__ */
>  #endif /* _ASM_POWERPC_MACHDEP_H */

  reply	other threads:[~2007-12-01  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01  0:24 [PATCH] [POWERPC] Add machine initcall macros Grant Likely
2007-12-01  5:10 ` Benjamin Herrenschmidt [this message]
2007-12-01  7:11 ` Michael Ellerman
2007-12-01  7:26   ` Benjamin Herrenschmidt

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=1196485858.13230.123.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).