From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Mel Gorman <mgorman@suse.de>, Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] Add decoder for GFP masks to tools.
Date: Tue, 8 Jan 2013 15:24:13 -0800 [thread overview]
Message-ID: <1357687455-13234-1-git-send-email-cody@linux.vnet.ibm.com> (raw)
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
next reply other threads:[~2013-01-08 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 23:24 Cody P Schafer [this message]
2013-01-08 23:24 ` [PATCH 1/2] gfp: split out defines for gfp flags into seperate header Cody P Schafer
2013-01-08 23:24 ` [PATCH 2/2] tools: add gfp mask decoder Cody P Schafer
2013-01-10 11:36 ` [PATCH 0/2] Add decoder for GFP masks to tools Mel Gorman
2013-01-10 17:37 ` Cody P Schafer
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=1357687455-13234-1-git-send-email-cody@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
/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
Powered by JetHome