From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: Re: [RFC 01/11] mm: debug: format flags in a buffer
Date: Thu, 30 Apr 2015 18:39:40 +0300 [thread overview]
Message-ID: <20150430153940.GA17156@node.dhcp.inet.fi> (raw)
In-Reply-To: <1429044993-1677-2-git-send-email-sasha.levin@oracle.com>
On Tue, Apr 14, 2015 at 04:56:23PM -0400, Sasha Levin wrote:
> Format various flags to a string buffer rather than printing them. This is
> a helper for later.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> ---
> mm/debug.c | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/mm/debug.c b/mm/debug.c
> index 3eb3ac2..c9f7dd7 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -80,6 +80,41 @@ static void dump_flags(unsigned long flags,
> pr_cont(")\n");
> }
>
> +static char *format_flags(unsigned long flags,
> + const struct trace_print_flags *names, int count,
> + char *buf, char *end)
> +{
> + const char *delim = "";
> + unsigned long mask;
> + int i;
> +
> + buf += snprintf(buf, (buf > end ? 0 : end - buf),
> + "flags: %#lx(", flags);
> +
> + /* remove zone id */
> + flags &= (1UL << NR_PAGEFLAGS) - 1;
> +
> + for (i = 0; i < count && flags; i++) {
> + mask = names[i].mask;
> + if ((flags & mask) != mask)
> + continue;
> +
> + flags &= ~mask;
> + buf += snprintf(buf, (buf > end ? 0 : end - buf),
> + "%s%s", delim, names[i].name);
Indent is off. Otherwise look okay to me.
> + delim = "|";
> + }
> +
> + /* check for left over flags */
> + if (flags)
> + buf += snprintf(buf, (buf > end ? 0 : end - buf),
> + "%s%#lx", delim, flags);
> +
> + buf += snprintf(buf, (buf > end ? 0 : end - buf), ")\n");
> +
> + return buf;
> +}
> +
> void dump_page_badflags(struct page *page, const char *reason,
> unsigned long badflags)
> {
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Kirill A. Shutemov
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-30 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 20:56 [RFC 00/11] mm: debug: formatting memory management structs Sasha Levin
2015-04-14 20:56 ` [RFC 01/11] mm: debug: format flags in a buffer Sasha Levin
2015-04-30 15:39 ` Kirill A. Shutemov [this message]
2015-04-14 20:56 ` [RFC 02/11] mm: debug: deal with a new family of MM pointers Sasha Levin
2015-04-30 16:17 ` Kirill A. Shutemov
2015-04-30 16:44 ` Sasha Levin
2015-04-14 20:56 ` [RFC 03/11] mm: debug: dump VMA into a string rather than directly on screen Sasha Levin
2015-04-30 16:18 ` Kirill A. Shutemov
2015-04-14 20:56 ` [RFC 04/11] mm: debug: dump struct MM " Sasha Levin
2015-04-14 20:56 ` [RFC 05/11] mm: debug: dump page " Sasha Levin
2015-04-14 20:56 ` [RFC 06/11] mm: debug: clean unused code Sasha Levin
2015-04-14 20:56 ` [RFC 07/11] mm: debug: VM_BUG() Sasha Levin
2015-04-30 16:22 ` Kirill A. Shutemov
2015-04-14 20:56 ` [RFC 08/11] mm: debug: kill VM_BUG_ON_PAGE Sasha Levin
2015-04-14 20:56 ` [RFC 09/11] mm: debug: kill VM_BUG_ON_VMA Sasha Levin
2015-04-14 20:56 ` [RFC 10/11] mm: debug: kill VM_BUG_ON_MM Sasha Levin
2015-04-14 20:56 ` [RFC 11/11] mm: debug: use VM_BUG() to help with debug output Sasha Levin
2015-04-15 8:45 ` [RFC 00/11] mm: debug: formatting memory management structs Kirill A. Shutemov
2015-04-15 12:52 ` Sasha Levin
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=20150430153940.GA17156@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).