From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Dominik Dingel <dingel@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
linux-s390@vger.kernel.org, linux-mm@kvack.org,
Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH 0/4] s390/mm: Fixup hugepage sw-emulated code removal
Date: Mon, 6 Jul 2015 10:05:24 +0200 [thread overview]
Message-ID: <20150706100524.3698c9f8@mschwide> (raw)
In-Reply-To: <1435927569-41132-1-git-send-email-dingel@linux.vnet.ibm.com>
On Fri, 3 Jul 2015 14:46:05 +0200
Dominik Dingel <dingel@linux.vnet.ibm.com> wrote:
> Heiko noticed that the current check for hugepage support on s390 is a little bit to
> harsh as systems which do not support will crash.
> The reason is that pageblock_order can now get negative when we set HPAGE_SHIFT to 0.
> To avoid all this and to avoid opening another can of worms with enabling
> HUGETLB_PAGE_SIZE_VARIABLE I think it would be best to simply allow architectures to
> define their own hugepages_supported().
>
> Thanks
> Dominik
>
> Dominik Dingel (4):
> Revert "s390/mm: change HPAGE_SHIFT type to int"
> Revert "s390/mm: make hugepages_supported a boot time decision"
> mm: hugetlb: allow hugepages_supported to be architecture specific
> s390/hugetlb: add hugepages_supported define
>
> arch/s390/include/asm/hugetlb.h | 1 +
> arch/s390/include/asm/page.h | 8 ++++----
> arch/s390/kernel/setup.c | 2 --
> arch/s390/mm/pgtable.c | 2 --
> include/linux/hugetlb.h | 17 ++++++++---------
> 5 files changed, 13 insertions(+), 17 deletions(-)
To have an architecture override for hugepages_supported is imho the
cleaner approach compared to the HPAGE_SHIFT tricks. I would have
preferred to use a __weak function but the #ifndef solution is fine
with me as well.
Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
--
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>
prev parent reply other threads:[~2015-07-06 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:46 [PATCH 0/4] s390/mm: Fixup hugepage sw-emulated code removal Dominik Dingel
2015-07-03 12:46 ` [PATCH 1/4] Revert "s390/mm: change HPAGE_SHIFT type to int" Dominik Dingel
2015-07-03 12:46 ` [PATCH 2/4] Revert "s390/mm: make hugepages_supported a boot time decision" Dominik Dingel
2015-07-03 12:46 ` [PATCH 3/4] mm: hugetlb: allow hugepages_supported to be architecture specific Dominik Dingel
2015-07-03 12:46 ` [PATCH 4/4] s390/hugetlb: add hugepages_supported define Dominik Dingel
2015-07-06 8:05 ` Martin Schwidefsky [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=20150706100524.3698c9f8@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.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).