| commit | 845000241f4057b6c1b436e0a8673cc17a92d855 | [log] [tgz] |
|---|---|---|
| author | Chenbo Feng <fengc@google.com> | Tue May 15 14:01:55 2018 -0700 |
| committer | Chenbo Feng <fengc@google.com> | Tue May 15 14:01:55 2018 -0700 |
| tree | 0396d543433dc132d232b2d2f67aebea19a64b62 | |
| parent | 08ef68d14b1a00b9ebc993a9429224e1ea914056 [diff] |
Add xt_bpf support for android devices For device ship with P and kernel version is 4.9 or above, it should use xt_bpf to gather the per iface networkStats instead of reading the proc file of xt_qtaguid. Bug: 30950746 Test: device boot and the iptables rules is loaded correctly. Change-Id: Ic86613b382b99f407111abc8305c62d3129175e0
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.