I needed to decode some gfp_masks to debug an oom-killer invocation, and wrote
this tool to avoid doing the decoding manually.
Bad things about this: slightly hacky use of code intended for use with ftrace,
splitting linux/gfp.h into 2 parts.
Good things: No additional places need modification to keep the decoder up to
date, no mistakes from manual gfp_mask decoding.
include/linux/gfp-flags.h | 143 +++++++++++++++++++++++++++++++++++++++++
include/linux/gfp.h | 144 +-----------------------------------------
tools/gfp-decode/.gitignore | 1 +
tools/gfp-decode/Makefile | 11 ++++
tools/gfp-decode/gfp-decode.c | 89 ++++++++++++++++++++++++++
5 files changed, 245 insertions(+), 143 deletions(-)
---
On the topic of writing Makefiles for tools/*, it would be extremely
convienient if a system was setup which allowed simple specification of final
executable(s) and the objects to compose them rather than having each tool
write a custom Makefile.
For example (potentially):
TARGETS = gfp-decode
obj-gfp-decode = gfp-decode.o
include ../scripts/Makefile.magic
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
