[Badmem-developer] Splitting memmap out of the badmem patch

[Yann D. <yd...@fr...>]

Hi,

I've the feeling that the memmap feature would be useful for other
things than badmem.  I'm planning to dive into the various ram hotplug
patches, and this looks like a useful diagnostic tool.  Not counting
that it would also be useful do play with the badram patch.

I've currently splitted the patch, assuming badmem would be applied
after memmap, so that <linux/badmem.h> can include a new
<linux/memmap.h> which only exports the 2 memmap functions.

But now:

1) I wonder whether those 2 funcs should be exported at all

2) memmap.c can possibly be made into a module (I'll be experimenting
that and submitting patches where applicable) whereas badram does not.

So I'm now considering doing things the other way round, and
attempting to have the same memmap patch applicable both on a vanilla
and a badmem/badram kernel.

I attach the current patches.  Currently my version of the badmem
patch is just a diff between the memmap-only tree and the badmem one,
modulo the #include tweeking described above.

Regards,
-- 
Yann Dirson <Yan...@fr...>                 http://www.alcove.com/
Technical support manager                Responsable de l'assistance technique
Senior Free-Software Consultant          Consultant senior en Logiciels Libres
Debian developer (di...@de...)                        Développeur Debian