From: John Hubbard <jhubbard@nvidia.com>
To: Matthew Wilcox <willy@infradead.org>
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 16:41:01 -0700 [thread overview]
Message-ID: <05106091-a30e-8ed1-ba23-58d670ce2534@nvidia.com> (raw)
In-Reply-To: <20200629223550.GK25523@casper.infradead.org>
On 2020-06-29 15:35, Matthew Wilcox wrote:
...
> 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.
>
That is a much better fix. I hated myself for the code duplication there. :)
I've pasted in a sample run in the other thread (patch 1/3).
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2020-06-29 23:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 15:19 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
2020-06-29 23:41 ` John Hubbard [this message]
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=05106091-a30e-8ed1-ba23-58d670ce2534@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox