From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Victor Aoqui <victora@br.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
aneesh.kumar@linux.vnet.ibm.com, mpe@ellerman.id.au
Cc: victora@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc
Date: Wed, 5 Jul 2017 10:01:26 +0530 [thread overview]
Message-ID: <4d5950e6-d208-b8d1-ffee-6e54c741c8e0@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170703200559.3743-1-victora@br.ibm.com>
On 07/04/2017 01:35 AM, Victor Aoqui wrote:
> Implemented default hugepage size verification (default_hugepagesz=)
> in order to allow allocation of defined number of pages (hugepages=)
> only for supported hugepage sizes.
>
> Signed-off-by: Victor Aoqui <victora@br.ibm.com>
> ---
> arch/powerpc/mm/hugetlbpage.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/powerpc/mm/hugetlbpage.c b/arch/powerpc/mm/hugetlbpage.c
> index a4f33de..464e72e 100644
> --- a/arch/powerpc/mm/hugetlbpage.c
> +++ b/arch/powerpc/mm/hugetlbpage.c
> @@ -797,6 +797,21 @@ static int __init hugepage_setup_sz(char *str)
> }
> __setup("hugepagesz=", hugepage_setup_sz);
>
> +static int __init default_hugepage_setup_sz(char *str)
The function name should be hugetlb_default_size_setup in
sync with the generic function hugetlb_default_setup for the
same parameter default_hugepagesz.
> +{
> + unsigned long long size;
> +
> + size = memparse(str, &str);
> +
> + if (add_huge_page_size(size) != 0) {
I am little bit confused here. Do we always follow another
'hugepages=' element after 'default_hugepagesz' ? If not,
then we dont have to do 'add_huge_page_size'. But then
that function checks for valid huge page sizes and skips
adding hstate if its already added. So I guess it okay.
> + hugetlb_bad_size();
> + pr_err("Invalid default huge page size specified(%llu)\n", size);
Error message should have 'ppc' some where to indicate that
the arch rejected the size not core MM.
next prev parent reply other threads:[~2017-07-05 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 20:05 [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc Victor Aoqui
2017-07-05 4:26 ` Aneesh Kumar K.V
2017-07-05 16:03 ` victora
2017-07-12 15:15 ` victora
2017-07-05 4:31 ` Anshuman Khandual [this message]
2017-07-05 16:09 ` victora
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=4d5950e6-d208-b8d1-ffee-6e54c741c8e0@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=victora@br.ibm.com \
--cc=victora@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).