linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>, Petr Mladek <pmladek@suse.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Matthew WilCox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH mm-unstable v4 0/3] mm, printk: introduce new format for page_type
Date: Mon, 30 Jan 2023 13:25:11 +0900	[thread overview]
Message-ID: <20230130042514.2418-1-42.hyeyoo@gmail.com> (raw)

RFC v3:
   https://lore.kernel.org/lkml/20221218101901.373450-1-42.hyeyoo@gmail.com

This series was originally part of "move PG_slab to page_type" series,
but printk format implementation for page_type is separated to this series.

RFC v3 -> v4:
  - dropped patch 1 ("mm/hwpoison: remove MF_MSG_SLAB from action_page_types")
    and patch 2 ("mm: move PG_slab flag to page_type") from previous
    spin as they are planned as separate series

  - adjusted comments from Andy Shevchenko [1] and Petr Mladek [2]

  - added patch 1 ("mmflags.h: use less error prone method to define pageflag_names")
    for consistency with patch 2 ("mm, printk: introduce new format %pGt for page_type"),
    as suggested by Andy Shevchenko [1]

[1] https://lore.kernel.org/lkml/Y6AycLbpjVzXM5I9@smile.fi.intel.com/
[2] https://lore.kernel.org/lkml/Y6HSutM8pmoKxQWp@alley/

Based on mm-unstable (ede43f2956cc "kasan: fix Oops due to missing calls
to kasan_arch_is_rea()") as there are recent changes in mmflags.h.

Hyeonggon Yoo (3):
  mmflags.h: use less error prone method to define pageflag_names
  mm, printk: introduce new format %pGt for page_type
  mm/debug: use %pGt to display page_type in dump_page()

 Documentation/core-api/printk-formats.rst | 16 ++--
 include/linux/page-flags.h                |  7 +-
 include/trace/events/mmflags.h            | 93 +++++++++++++----------
 lib/test_printf.c                         | 26 +++++++
 lib/vsprintf.c                            | 21 +++++
 mm/debug.c                                |  7 ++
 mm/internal.h                             |  1 +
 7 files changed, 124 insertions(+), 47 deletions(-)

-- 
2.39.1



             reply	other threads:[~2023-01-30  4:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  4:25 Hyeonggon Yoo [this message]
2023-01-30  4:25 ` [PATCH mm-unstable v4 1/3] mmflags.h: use less error prone method to define pageflag_names Hyeonggon Yoo
2023-01-30 12:35   ` Andy Shevchenko
2023-01-31  8:38     ` Hyeonggon Yoo
2023-01-31 21:09       ` Andrew Morton
2023-02-01 12:14         ` Hyeonggon Yoo
2023-01-30  4:25 ` [PATCH mm-unstable v4 2/3] mm, printk: introduce new format %pGt for page_type Hyeonggon Yoo
2023-03-03 19:50   ` Petr Mladek
2023-01-30  4:25 ` [PATCH mm-unstable v4 3/3] mm/debug: use %pGt to display page_type in dump_page() Hyeonggon Yoo

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=20230130042514.2418-1-42.hyeyoo@gmail.com \
    --to=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.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