From: Matthew Wilcox <willy@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH 0/3] Improvements for dump_page()
Date: Mon, 29 Jun 2020 23:35:50 +0100 [thread overview]
Message-ID: <20200629223550.GK25523@casper.infradead.org> (raw)
In-Reply-To: <f416eae5-869f-9da1-e1c3-b05f78cc1fc1@nvidia.com>
On Mon, Jun 29, 2020 at 02:55:21PM -0700, John Hubbard wrote:
> Cool! I've got a few minor feedback comments coming for the individual
> patches, but an easy question first:
>
> For the FOLL_PIN pages, I left in a minor mess: the lines are basically
> 2x too long. Would you be interested in folding in something approximately
> like this, below, to one of your patches? It's just a line break, effectively.
> It generates output like this:
>
> [ 260.545212] page:0000000035202f6e refcount:513 mapcount:1 mapping:0000000000000000 index:0x0
> [ 260.552834] head:0000000035202f6e order:9 compound_mapcount:1 compound_pincount:512
> [ 260.560087] anon flags: 0x17ffe000001000e(referenced|uptodate|dirty|head)
> [ 260.565993] raw: 017ffe000001000e ffffffff83649ca0 ffffea0020758008 ffff888890f03839
> [ 260.572888] raw: 0000000000000000 0000000000000000 00000201ffffffff 0000000000000000
> [ 260.579745] page dumped because: gup_benchmark: head page: dump_page test
>
> (I'm not sure if the indentation is a good idea or not, actually.)
>
> Or if it's too much fuss, I can send it separately with your series as a
> prerequisite:
>
> diff --git a/mm/debug.c b/mm/debug.c
> index fcf3a16902b2..d522bf24e3ff 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -87,19 +87,22 @@ void __dump_page(struct page *page, const char *reason)
> if (compound)
> if (hpage_pincount_available(page)) {
> pr_warn("page:%p refcount:%d mapcount:%d mapping:%p "
> - "index:%#lx head:%p order:%u "
> - "compound_mapcount:%d compound_pincount:%d\n",
> + "index:%#lx\n",
> page, page_ref_count(head), mapcount,
> - mapping, page_to_pgoff(page), head,
> - compound_order(head), compound_mapcount(page),
> + mapping, page_to_pgoff(page));
> + pr_warn(" head:%p order:%u compound_mapcount:%d "
> + "compound_pincount:%d\n",
> + head, compound_order(head),
> + compound_mapcount(page),
> compound_pincount(page));
> } else {
> pr_warn("page:%p refcount:%d mapcount:%d mapping:%p "
> - "index:%#lx head:%p order:%u "
> - "compound_mapcount:%d\n",
> - page, page_ref_count(head), mapcount,
> - mapping, page_to_pgoff(page), head,
> - compound_order(head), compound_mapcount(page));
> + "index:%#lx\n",
> + page, page_ref_count(head), mapcount, mapping,
> + page_to_pgoff(page));
> + pr_warn(" head:%p order:%u compound_mapcount:%d\n",
> + head, compound_order(head),
> + compound_mapcount(page));
> }
Hmm ... If we're going to two lines, then I'd rather do something like this:
+++ b/mm/debug.c
@@ -84,27 +84,22 @@ void __dump_page(struct page *page, const char *reason)
*/
mapcount = PageSlab(head) ? 0 : page_mapcount(page);
- if (compound)
+ pr_warn("page:%p refcount:%d mapcount:%d mapping:%p index:%#lx\n",
+ page, page_ref_count(head), mapcount, mapping,
+ page_to_pgoff(page));
+ if (compound) {
if (hpage_pincount_available(page)) {
- pr_warn("page:%p refcount:%d mapcount:%d mapping:%p "
- "index:%#lx head:%p order:%u "
- "compound_mapcount:%d compound_pincount:%d\n",
- page, page_ref_count(head), mapcount,
- mapping, page_to_pgoff(page), head,
- compound_order(head), compound_mapcount(page),
- compound_pincount(page));
+ pr_warn("head:%p order:%u compound_mapcount:%d compound_pincount:%d\n",
+ head, compound_order(head),
+ compound_mapcount(page),
+ compound_pincount(page));
} else {
- pr_warn("page:%p refcount:%d mapcount:%d mapping:%p "
- "index:%#lx head:%p order:%u "
- "compound_mapcount:%d\n",
- page, page_ref_count(head), mapcount,
- mapping, page_to_pgoff(page), head,
- compound_order(head), compound_mapcount(page));
+ pr_warn("head:%p order:%u compound_mapcount:%d\n",
+ head, compound_order(head),
+ compound_mapcount(page));
}
- else
- pr_warn("page:%p refcount:%d mapcount:%d mapping:%p index:%#lx\n",
- page, page_ref_count(page), mapcount,
- mapping, page_to_pgoff(page));
+ }
+
if (PageKsm(page))
type = "ksm ";
else if (PageAnon(page))
I haven't dumped a page with this yet, so I may change my mind, but
this seems like a good reduction in the amount of redundant code in
this function.
next prev parent reply other threads:[~2020-06-29 22:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 15:19 [PATCH 0/3] Improvements for dump_page() Matthew Wilcox (Oracle)
2020-06-29 15:19 ` [PATCH 1/3] mm: Print head flags in dump_page Matthew Wilcox (Oracle)
2020-06-29 22:38 ` John Hubbard
2020-06-29 22:51 ` Matthew Wilcox
2020-06-29 22:54 ` John Hubbard
2020-06-29 23:35 ` John Hubbard
2020-06-30 8:02 ` Vlastimil Babka
2020-06-30 11:59 ` Matthew Wilcox
2020-07-01 2:12 ` John Hubbard
2020-07-02 14:59 ` Vlastimil Babka
2020-07-02 15:53 ` Kirill A. Shutemov
2020-07-02 16:19 ` Vlastimil Babka
2020-07-02 20:39 ` Kirill A. Shutemov
2020-07-02 21:01 ` Matthew Wilcox
2020-06-29 15:19 ` [PATCH 2/3] mm: Print the inode number " Matthew Wilcox (Oracle)
2020-06-29 15:19 ` [PATCH 3/3] mm: Print hashed address of struct page Matthew Wilcox (Oracle)
2020-07-02 15:56 ` Kirill A. Shutemov
2020-06-29 16:57 ` [PATCH 0/3] Improvements for dump_page() William Kucharski
2020-06-29 20:17 ` Mike Rapoport
2020-06-29 21:55 ` John Hubbard
2020-06-29 22:35 ` Matthew Wilcox [this message]
2020-06-29 23:41 ` John Hubbard
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=20200629223550.GK25523@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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).