Skip to content

RFC KABI example conversion and cleanup

Kyle Moffett lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 78 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Create initial kernel ABI header infrastructureMakefile include/kabi/arch-alpha/stddef.h include/kabi/arch-arm/stddef.h +21 more+188 -320 replies
2/2Generalize fd_set handling across architecturesinclude/asm-alpha/posix_types.h include/asm-arm/posix_types.h include/asm-arm26/posix_types.h +22 more+112 -11020 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC][PATCH 0/2] KABI example conversion and cleanup
Quoted 2 lines · On Fri, 24 Mar 2006 17:46:27 -0500 Kyle Moffett <[email protected]> wrote:

I'm working on some sample patches now which I'll try to post in a few days if I get the time.

Ok, here's a sample of the KABI conversion and cleanup patches that I'm proposing. I have a few fundamental goals for these patches:
1) The Linux kernel compiles and works at every step along the way
2) Since most of the headers are currently quite broken with respect to GLIBC and userspace, I won't spend much extra time preserving compatibility with GLIBC, userspace, or non-GCC compilers.
3) Everything in include/kabi will have a __kabi_ or __KABI_ prefix.
4) Headers in include/linux that need the KABI interfaces will include the corresponding <kabi/*.h> header and define or typedef the necessary KABI definitions to the names the kernel wants.
5) The stuff in include/kabi/*.h should always be completely independent of userspace/kernelspace and not require any includes outside of <kabi/*>. This means that the only preprocessor symbols that we can assume are present are those provided by the compiler itself.

Cheers,
Kyle Moffett