All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kirill@shutemov.name
Subject: Re: [PATCH 00/11] mm: debug: formatting memory management structs
Date: Thu, 14 May 2015 16:26:27 -0400	[thread overview]
Message-ID: <555504F3.5020209@oracle.com> (raw)
In-Reply-To: <20150514132413.2a56b25489e0c644e68229bb@linux-foundation.org>

On 05/14/2015 04:24 PM, Andrew Morton wrote:
> On Thu, 14 May 2015 13:10:03 -0400 Sasha Levin <sasha.levin@oracle.com> 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);
>> > 
>> > This allows us to customize output when hitting bugs even further, thus
>> > we introduce VM_BUG() which allows printing anything when hitting a bug
>> > rather than just a single piece of information.
>> > 
>> > This also means we can get rid of VM_BUG_ON_* since they're now nothing
>> > more than a format string.
> A good set of example output would help people understand this proposal.

That would be the equivalent of doing:

	dump_page(page);
	dump_mm(mm);
	dump_vma(vma);

I'll add a few example usages in.


Thanks,
Sasha

--
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: Sasha Levin <sasha.levin@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kirill@shutemov.name
Subject: Re: [PATCH 00/11] mm: debug: formatting memory management structs
Date: Thu, 14 May 2015 16:26:27 -0400	[thread overview]
Message-ID: <555504F3.5020209@oracle.com> (raw)
In-Reply-To: <20150514132413.2a56b25489e0c644e68229bb@linux-foundation.org>

On 05/14/2015 04:24 PM, Andrew Morton wrote:
> On Thu, 14 May 2015 13:10:03 -0400 Sasha Levin <sasha.levin@oracle.com> 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);
>> > 
>> > This allows us to customize output when hitting bugs even further, thus
>> > we introduce VM_BUG() which allows printing anything when hitting a bug
>> > rather than just a single piece of information.
>> > 
>> > This also means we can get rid of VM_BUG_ON_* since they're now nothing
>> > more than a format string.
> A good set of example output would help people understand this proposal.

That would be the equivalent of doing:

	dump_page(page);
	dump_mm(mm);
	dump_vma(vma);

I'll add a few example usages in.


Thanks,
Sasha

  reply	other threads:[~2015-05-14 20:26 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 17:10 [PATCH 00/11] mm: debug: formatting memory management structs Sasha Levin
2015-05-14 17:10 ` Sasha Levin
2015-05-14 17:10 ` [PATCH 01/11] mm: debug: format flags in a buffer Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 02/11] mm: debug: deal with a new family of MM pointers Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 03/11] mm: debug: dump VMA into a string rather than directly on screen Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 04/11] mm: debug: dump struct MM " Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 05/11] mm: debug: dump page " Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-06-30 23:35   ` David Rientjes
2015-06-30 23:35     ` David Rientjes
2015-07-01  8:53     ` Kirill A. Shutemov
2015-07-01  8:53       ` Kirill A. Shutemov
2015-07-01 19:21     ` Sasha Levin
2015-07-01 19:21       ` Sasha Levin
2015-07-01 21:25       ` David Rientjes
2015-07-01 21:25         ` David Rientjes
2015-07-01 21:34         ` Kirill A. Shutemov
2015-07-01 21:34           ` Kirill A. Shutemov
2015-07-01 22:33         ` Vlastimil Babka
2015-07-01 22:33           ` Vlastimil Babka
2015-07-01 22:50         ` Sasha Levin
2015-07-01 22:50           ` Sasha Levin
2015-07-08 23:58           ` David Rientjes
2015-07-08 23:58             ` David Rientjes
2015-08-06 15:08             ` Sasha Levin
2015-08-06 15:08               ` Sasha Levin
2015-05-14 17:10 ` [PATCH 06/11] mm: debug: clean unused code Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 07/11] mm: debug: VM_BUG() Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 08/11] mm: debug: kill VM_BUG_ON_PAGE Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 09/11] mm: debug: kill VM_BUG_ON_VMA Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 10/11] mm: debug: kill VM_BUG_ON_MM Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 17:10 ` [PATCH 11/11] mm: debug: use VM_BUG() to help with debug output Sasha Levin
2015-05-14 17:10   ` Sasha Levin
2015-05-14 20:24 ` [PATCH 00/11] mm: debug: formatting memory management structs Andrew Morton
2015-05-14 20:24   ` Andrew Morton
2015-05-14 20:26   ` Sasha Levin [this message]
2015-05-14 20:26     ` Sasha Levin
2015-06-26 21:34 ` Sasha Levin
2015-06-26 21:34   ` 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=555504F3.5020209@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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.