From: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
n-horiguchi@ah.jp.nec.com, mike.kravetz@oracle.com,
hillf.zj@alibaba-inc.com, mhocko@suse.com,
baiyaowei@cmss.chinamobile.com, dingel@linux.vnet.ibm.com,
kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com,
paul.gortmaker@windriver.com, catalin.marinas@arm.com,
will.deacon@arm.com, cmetcalf@ezchip.com,
linux-arm-kernel@lists.infradead.org, james.hogan@imgtec.com,
linux-metag@vger.kernel.org, benh@kernel.crashing.org,
paulus@samba.org, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
Vaishali Thakkar <vaishali.thakkar@oracle.com>
Subject: [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize
Date: Wed, 23 Mar 2016 17:37:18 +0530 [thread overview]
Message-ID: <1458734844-14833-1-git-send-email-vaishali.thakkar@oracle.com> (raw)
Current code fails to ignore the 'hugepages=' parameters when unsupported
hugepagesize is specified. With this patchset, introduce new architecture
independent routine hugetlb_bad_size to handle such command line options.
And then call it in architecture specific code.
Changes since v1:
- Separated different architecture specific changes in different
patches
- CC'ed all arch maintainers
Vaishali Thakkar (6):
mm/hugetlb: Introduce hugetlb_bad_size
arm64: mm: Use hugetlb_bad_size
metag: mm: Use hugetlb_bad_size
powerpc: mm: Use hugetlb_bad_size
tile: mm: Use hugetlb_bad_size
x86: mm: Use hugetlb_bad_size
arch/arm64/mm/hugetlbpage.c | 1 +
arch/metag/mm/hugetlbpage.c | 1 +
arch/powerpc/mm/hugetlbpage.c | 6 ++++--
arch/tile/mm/hugetlbpage.c | 7 ++++++-
arch/x86/mm/hugetlbpage.c | 1 +
include/linux/hugetlb.h | 1 +
mm/hugetlb.c | 14 +++++++++++++-
7 files changed, 27 insertions(+), 4 deletions(-)
--
2.1.4
--
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 reply other threads:[~2016-03-23 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 12:07 Vaishali Thakkar [this message]
[not found] ` <1458734844-14833-1-git-send-email-vaishali.thakkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-03-23 13:30 ` [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize Michal Hocko
2016-03-23 16:01 ` Vaishali Thakkar
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=1458734844-14833-1-git-send-email-vaishali.thakkar@oracle.com \
--to=vaishali.thakkar@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@ezchip.com \
--cc=dave.hansen@linux.intel.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=hpa@zytor.com \
--cc=james.hogan@imgtec.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).