linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Miaohe Lin <linmiaohe@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: memory-failure: convert to pr_fmt()
Date: Wed, 27 Jul 2022 02:24:12 +0000	[thread overview]
Message-ID: <20220727022406.GA3350995@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1774d0f6-9607-0111-c940-f0bd2b4f7c75@huawei.com>

On Wed, Jul 27, 2022 at 10:09:50AM +0800, Kefeng Wang wrote:
> 
> On 2022/7/27 9:12, HORIGUCHI NAOYA(堀口 直也) wrote:
> > On Tue, Jul 26, 2022 at 04:10:46PM +0800, Kefeng Wang wrote:
> > > Use pr_fmt to prefix pr_<level> output.
> > > 
> > > Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> > There're other classes of prefixes like "Unpoison:" and "soft offline:" in
> > mm/memory-failure.c.  So simply adding subsystem-wide pr_fmt() changes to
> > print out two prefixes like below:
> > 
> >    [ 1479.892348] Memory failure: soft offline: 0x1b8200: page migration failed 1, type 0x57ffffc00a000c(uptodate|dirty|mappedtodisk|swapbacked|node=1|zone=2|lastcpupid=0x1fffff)
> > 
> >    [ 1486.871130] Memory failure: Unpoison: Software-unpoisoned page 0x14f00
> > 
> > Do you intend this change?
> 
> 
> Firstly I think they are all in memory failure, with this prefix is no bad
> impact,
> 
> soft_offline_page() and unpoison_memory()  are used by error injection,

Yes, this is right, and I think that testing systems might save console
output to detect issues afterward, so the longer prefix might consume more
storage of such systems.  So I'd like to keep the output shorter if possible.

> 
> but soft_offline_page() could be used in memory hotremove,
> 
> so let's add
> 
> '#undef pr_fmt' before unpoison_pr_info definition, options? thanks.

Yes, I agree with this approach, thank you.

- Naoya Horiguchi

      reply	other threads:[~2022-07-27  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  8:10 Kefeng Wang
2022-07-27  1:12 ` HORIGUCHI NAOYA(堀口 直也)
2022-07-27  2:09   ` Kefeng Wang
2022-07-27  2:24     ` HORIGUCHI NAOYA(堀口 直也) [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=20220727022406.GA3350995@hori.linux.bs1.fc.nec.co.jp \
    --to=naoya.horiguchi@nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wangkefeng.wang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox