| commit | 9d8bb70886d5f70120a8477d28d08b1d3061795c | [log] [tgz] |
|---|---|---|
| author | Alistair Strachan <astrachan@google.com> | Sun Apr 08 21:58:45 2018 -0700 |
| committer | Alistair Strachan <astrachan@google.com> | Mon Apr 09 17:25:57 2018 +0000 |
| tree | 6e333aba4f190ed9e5a38d339ddd9fb1f5c704e4 | |
| parent | d589b2ba94682f9140920e33779afd0085651d2a [diff] |
android-4.14: Add CONFIG_MEMCG{,_SWAP} requirement.
On older kernels it was ambiguous whether
CONFIG_ANDROID_LOW_MEMORY_KILLER or CONFIG_MEMCG should be enabled, but
on 4.14 there is no lmk driver so we rely on CONFIG_MEMCG.
Bug: 77736601
Change-Id: Iff24ac4ec903054cb2a9b858c09f01caeffc6d22
Signed-off-by: Alistair Strachan <astrachan@google.com>
The files in these directories are meant to be used as a base for an Android kernel config. All devices must have the options in android-base.cfg configured as specified. If an android-base-ARCH.cfg file exists for the architecture of your device, the options in that file must be configured as specified also.
While not mandatory, the options in android-recommended.cfg enable advanced Android features.
Assuming you already have a minimalist defconfig for your device, a possible way to enable these options would be to use the merge_config.sh script in the kernel tree. From the root of the kernel tree:
ARCH=<arch> scripts/kconfig/merge_config.sh <...>/<device>_defconfig <...>/android-base.cfg <...>/android-base-<arch>.cfg <...>/android-recommended.cfg
This will generate a .config that can then be used to save a new defconfig or compile a new kernel with Android features enabled.
Because there is no tool to consistently generate these config fragments, lets keep them alphabetically sorted instead of random.