| commit | d546dcbe8e9b10511bf32519fe2a57face7de182 | [log] [tgz] |
|---|---|---|
| author | Alistair Strachan <astrachan@google.com> | Wed May 16 13:54:15 2018 -0700 |
| committer | Alistair Strachan <astrachan@google.com> | Thu May 17 17:26:49 2018 -0700 |
| tree | 3025ecd35442594ae6667923cf2ceeb8038214d5 | |
| parent | 19ac9d8eba56dcb0259b8a940574b5df0627b379 [diff] |
android-4.9, android-4.14: Enable KPROBES (p/ directory version) Debugging the kernel with bcc using eBPF and KPROBES is possible in the 4.9 and 4.14 kernels. Suggest turning these debugging features on. A similar change was already made for various device kernels. Bug: 78013494 Change-Id: I420b99c07b98a83ec735d8e41e4d8a198f408207 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.