linux-kernel - Re: [RFC] kbuild: generic support for asm-generic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 8 Jan 2011 22:33:53 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	linux arch <linux-arch@...r.kernel.org>,
	Guan Xuetao <guanxuetao@...c.pku.edu.cn>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [RFC] kbuild: generic support for asm-generic

On Sat, Jan 08, 2011 at 09:53:31PM +0100, Arnd Bergmann wrote:
> On Saturday 08 January 2011, Sam Ravnborg wrote:
> > Hi Arnd et all.
> > 
> > This is my second attempt to provide generic support for
> > architectures that use existing headers from asm-generic.
> > 
> > With this kbuild will read the file: arch/$ARCH/include/asm-generic
> > 
> > For each file listed in this file a wrapper is generated in
> > arch/$ARCH/inclue/generated/asm/
> > 
> > The patch include support so headers_install works.
> > 
> > The inspiration came from the unicore32 patchset,
> > but I redid this to make it more general.
> > 
> > I will follow-up with two patches.
> > One that implment the functionality.
> > A second that convert two headers in x86 to use the
> > new asm-generic stuff (only as an example).
> 
> Very nice patch!
> 
> This is something I'd certainly like to see upstream, and you made
> a good point about keeping it seperate from the unicore32 submission.
> 
> One detail I don't like too much is that you now have two different
> formats for specifying lists of headers to do something with.
> 
> Instead of the new arch/*/include/asm-generic file, how about listing
> all files that are actually provided by the architecture as "header-y"
> in arch/*/include/asm/Kbuild, and listing all files as something
> else in include/asm-generic/Kbuild and include/asm-generic/Kbuild.asm?

Good point.
I will try to address this together with the comments from Guang.

If we use Kbuild syntax then I think we shall name the file
something like
 
    Kbuild.asm-generic

I need to think about the naming of the variables...

We need a variables to express:
In include/asm-generic/Kbuild.asm
- This file exists in a generic variant and it is exported.
  The arch may use it verbatim or may have a local variant

In arch/$(ARCH)/include/Kbuild.asm-generic
- This file is provided verbatim by asm-generic


Something like:

export-y - for files listed in Kbuild.asm
generic-y - for files listed in Kbuild.asm-generic

I will try to come up with a patch that uses this - or something
similar.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/