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 00/11] mm: debug: formatting memory management structs
Date: Wed, 15 Apr 2015 11:45:36 +0300 [thread overview]
Message-ID: <20150415084536.GA27510@node.dhcp.inet.fi> (raw)
In-Reply-To: <1429044993-1677-1-git-send-email-sasha.levin@oracle.com>
On Tue, Apr 14, 2015 at 04:56:22PM -0400, Sasha Levin wrote:
> This patch series adds knowledge about various memory management structures
> to the standard print functions.
>
> In essence, it allows us to easily print those structures:
>
> printk("%pZp %pZm %pZv", page, mm, vma);
Notably, you don't have \n in your format line. And it brings question how
well dump_page() and friends fit printk-like interface. dump_page()
produces multi-line print out.
Is it something printk() users would expect?
--
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>
WARNING: multiple messages have this Message-ID (diff)
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 00/11] mm: debug: formatting memory management structs
Date: Wed, 15 Apr 2015 11:45:36 +0300 [thread overview]
Message-ID: <20150415084536.GA27510@node.dhcp.inet.fi> (raw)
In-Reply-To: <1429044993-1677-1-git-send-email-sasha.levin@oracle.com>
On Tue, Apr 14, 2015 at 04:56:22PM -0400, Sasha Levin wrote:
> This patch series adds knowledge about various memory management structures
> to the standard print functions.
>
> In essence, it allows us to easily print those structures:
>
> printk("%pZp %pZm %pZv", page, mm, vma);
Notably, you don't have \n in your format line. And it brings question how
well dump_page() and friends fit printk-like interface. dump_page()
produces multi-line print out.
Is it something printk() users would expect?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2015-04-15 8:45 UTC|newest]
Thread overview: 38+ 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 ` Sasha Levin
2015-04-14 20:56 ` [RFC 01/11] mm: debug: format flags in a buffer Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-30 15:39 ` Kirill A. Shutemov
2015-04-30 15:39 ` Kirill A. Shutemov
2015-04-14 20:56 ` [RFC 02/11] mm: debug: deal with a new family of MM pointers Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-30 16:17 ` Kirill A. Shutemov
2015-04-30 16:17 ` Kirill A. Shutemov
2015-04-30 16:44 ` Sasha Levin
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-14 20:56 ` Sasha Levin
2015-04-30 16:18 ` Kirill A. Shutemov
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 ` Sasha Levin
2015-04-14 20:56 ` [RFC 05/11] mm: debug: dump page " Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-14 20:56 ` [RFC 06/11] mm: debug: clean unused code Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-14 20:56 ` [RFC 07/11] mm: debug: VM_BUG() Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-30 16:22 ` Kirill A. Shutemov
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 ` Sasha Levin
2015-04-14 20:56 ` [RFC 09/11] mm: debug: kill VM_BUG_ON_VMA Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-14 20:56 ` [RFC 10/11] mm: debug: kill VM_BUG_ON_MM Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-14 20:56 ` [RFC 11/11] mm: debug: use VM_BUG() to help with debug output Sasha Levin
2015-04-14 20:56 ` Sasha Levin
2015-04-15 8:45 ` Kirill A. Shutemov [this message]
2015-04-15 8:45 ` [RFC 00/11] mm: debug: formatting memory management structs Kirill A. Shutemov
2015-04-15 12:52 ` Sasha Levin
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=20150415084536.GA27510@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.