From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Laurent Vivier <lvivier@redhat.com>, linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] powerpc/mm: move a KERN_WARNING message to KERN_DEBUG
Date: Tue, 5 Feb 2019 19:11:22 +0100 [thread overview]
Message-ID: <ad592bd1-be25-2c3e-50ae-9d31913b9b2d@c-s.fr> (raw)
In-Reply-To: <20190205180329.1452-1-lvivier@redhat.com>
Le 05/02/2019 à 19:03, Laurent Vivier a écrit :
> resize_hpt_for_hotplug() reports a warning when it cannot
> increase the hash page table ("Unable to resize hash page
> table to target order") but this is not blocking and
> can make user thinks something has not worked properly.
>
> If the operation cannot be done the real error message
> will be reported by arch_add_memory() if create_section_mapping()
> fails.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> arch/powerpc/mm/hash_utils_64.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c
> index 0cc7fbc3bd1c..b762bdceb510 100644
> --- a/arch/powerpc/mm/hash_utils_64.c
> +++ b/arch/powerpc/mm/hash_utils_64.c
> @@ -778,7 +778,7 @@ void resize_hpt_for_hotplug(unsigned long new_mem_size)
>
> rc = mmu_hash_ops.resize_hpt(target_hpt_shift);
> if (rc && (rc != -ENODEV))
> - printk(KERN_WARNING
> + printk(KERN_DEBUG
You should use pr_debug() instead.
Christophe
> "Unable to resize hash page table to target order %d: %d\n",
> target_hpt_shift, rc);
> }
>
prev parent reply other threads:[~2019-02-05 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:03 [PATCH] powerpc/mm: move a KERN_WARNING message to KERN_DEBUG Laurent Vivier
2019-02-05 18:11 ` Christophe Leroy [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=ad592bd1-be25-2c3e-50ae-9d31913b9b2d@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.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