Heiko Carstens 3c5f2eb969 s390/mm: avoid trimming to MAX_ORDER
Trimming to MAX_ORDER was originally done in order to avoid to set
HOLES_IN_ZONE, which in turn would enable a quite expensive
pfn_valid() check. pfn_valid() however only checks if a struct page
exists for a given pfn.

With sparsemen vmemmap there are always struct pages, since memmaps
are allocated for whole sections. Therefore remove the HOLES_IN_ZONE
comment and the trimming.

Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
2020-07-20 10:55:32 +02:00
2020-07-20 10:55:32 +02:00
2020-06-27 08:59:32 -07:00
2020-06-29 16:32:20 +02:00
2020-06-13 13:29:16 -07:00
2020-06-28 10:37:39 -07:00
2020-06-28 09:42:47 -07:00
2020-06-27 09:35:47 -07:00
2020-06-28 10:29:38 -07:00
2020-06-21 15:41:24 -07:00
2020-06-25 09:15:24 -07:00
2020-06-28 10:16:15 -07:00
2020-06-12 11:05:52 -07:00
2020-06-28 14:55:18 -07:00
2020-06-28 15:00:24 -07:00

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.
Description
No description provided
Readme 5.7 GiB
Languages
C 97.6%
Assembly 1%
Shell 0.5%
Python 0.3%
Makefile 0.3%