From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Laszlo Toth <laszlth@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm, soft_offline: improve hugepage soft offlining error log
Date: Mon, 16 Oct 2017 22:35:22 +0000 [thread overview]
Message-ID: <3046fe8d-cdeb-6609-416e-8b016d162ea2@ah.jp.nec.com> (raw)
In-Reply-To: <20171016171757.GA3018@ubuntu-desk-vm>
On 10/17/2017 02:17 AM, Laszlo Toth wrote:
> On a failed attempt, we get the following entry:
> soft offline: 0x3c0000: migration failed 1, type 17ffffc0008008
> (uptodate|head)
>
> Make this more specific to be straightforward and to follow
> other error log formats in soft_offline_huge_page().
>
> Signed-off-by: Laszlo Toth <laszlth@gmail.com>
Looks good to me.
Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> ---
> mm/memory-failure.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 8836662..4acdf39 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -1587,7 +1587,7 @@ static int soft_offline_huge_page(struct page *page, int flags)
> ret = migrate_pages(&pagelist, new_page, NULL, MPOL_MF_MOVE_ALL,
> MIGRATE_SYNC, MR_MEMORY_FAILURE);
> if (ret) {
> - pr_info("soft offline: %#lx: migration failed %d, type %lx (%pGp)\n",
> + pr_info("soft offline: %#lx: hugepage migration failed %d, type %lx (%pGp)\n",
> pfn, ret, page->flags, &page->flags);
> if (!list_empty(&pagelist))
> putback_movable_pages(&pagelist);
>
--
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>
next prev parent reply other threads:[~2017-10-16 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 17:17 Laszlo Toth
2017-10-16 22:35 ` Naoya Horiguchi [this message]
2017-10-17 5:13 ` Anshuman Khandual
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=3046fe8d-cdeb-6609-416e-8b016d162ea2@ah.jp.nec.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=laszlth@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox