android/android_kernel_samsung_sm8650
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
f63b2625af
android_kernel_samsung_sm8650/BUILD.bazel

763 lines
24 KiB
Python
Raw Normal View History

ANDROID: Fix license for BUILD.bazel file. It should be GPLv2. Test: none Bug: 259137060 Change-Id: I6381a9e5a543c24d395984c211bfde5993ea4840 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-23 15:18:04 +09:00
# SPDX-License-Identifier: GPL-2.0
ANDROID: Kleaf: initial bazel based GKI kernel build Add build rules to build the GKI kernels using the hermetic bazel build. The rules understand how to set up a build environment from build_config and locations of the sources and build_configs. Sample invocations: $ bazel build //common:kernel_aarch64 $ bazel build //common:kernel_aarch64_debug $ bazel build //common:kernel_x86_64 $ bazel build //common:kernel_x86_64_debug Bug: 189451175 Change-Id: I2f06b2b79dbcbf197cb23d68b3c2f6786191e19d Signed-off-by: Matthias Maennich <maennich@google.com>
2021-06-21 20:54:56 +09:00
# Copyright (C) 2021 The Android Open Source Project
ANDROID: Fix license for BUILD.bazel file. It should be GPLv2. Test: none Bug: 259137060 Change-Id: I6381a9e5a543c24d395984c211bfde5993ea4840 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-23 15:18:04 +09:00
ANDROID: kleaf: android/gki_system_dlkm_modules is generated. modules.bzl is the source of truth for the list of GKI modules. There is no need to keep two lists. Test: TH Bug: 287697703 Signed-off-by: Yifan Hong <elsk@google.com> (cherry picked from https://android-review.googlesource.com/q/commit:a8a61755f67730af45d50f6173a4eedbcefa1c87) Merged-In: I8953e92696833cf8ec27aa80724ec468c08736f1 Change-Id: I8953e92696833cf8ec27aa80724ec468c08736f1
2023-06-17 09:05:00 +09:00
load("@bazel_skylib//rules:write_file.bzl", "write_file")
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
load("//build/bazel_common_rules/dist:dist.bzl", "copy_to_dist_dir")
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
load("//build/kernel/kleaf:common_kernels.bzl", "define_common_kernels")
load(
"//build/kernel/kleaf:kernel.bzl",
"ddk_headers",
"kernel_abi",
"kernel_build",
"kernel_images",
"kernel_modules_install",
"merged_kernel_uapi_headers",
)
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
load(":modules.bzl", "COMMON_GKI_MODULES_LIST")
ANDROID: Kleaf: common kernel public .... so it can be referenced in mixed builds. Test: build cuttlefish Bug: 202075496 Change-Id: I8d79847c54c639fa619edf3280c021f02ba76645 Signed-off-by: Yifan Hong <elsk@google.com> Signed-off-by: Matthias Maennich <maennich@google.com>
2021-11-03 08:26:49 +09:00
package(
default_visibility = [
"//visibility:public",
],
)
ANDROID: Kleaf: initial bazel based GKI kernel build Add build rules to build the GKI kernels using the hermetic bazel build. The rules understand how to set up a build environment from build_config and locations of the sources and build_configs. Sample invocations: $ bazel build //common:kernel_aarch64 $ bazel build //common:kernel_aarch64_debug $ bazel build //common:kernel_x86_64 $ bazel build //common:kernel_x86_64_debug Bug: 189451175 Change-Id: I2f06b2b79dbcbf197cb23d68b3c2f6786191e19d Signed-off-by: Matthias Maennich <maennich@google.com>
2021-06-21 20:54:56 +09:00
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
_GKI_AARCH64_MAKE_GOALS = [
"Image",
"Image.lz4",
"Image.gz",
"modules",
]
_GKI_RISCV64_MAKE_GOALS = [
"Image",
"Image.lz4",
"Image.gz",
"modules",
]
_GKI_X86_64_MAKE_GOALS = [
"bzImage",
"modules",
]
ANDROID: kleaf: android/gki_system_dlkm_modules is generated. modules.bzl is the source of truth for the list of GKI modules. There is no need to keep two lists. Test: TH Bug: 287697703 Signed-off-by: Yifan Hong <elsk@google.com> (cherry picked from https://android-review.googlesource.com/q/commit:a8a61755f67730af45d50f6173a4eedbcefa1c87) Merged-In: I8953e92696833cf8ec27aa80724ec468c08736f1 Change-Id: I8953e92696833cf8ec27aa80724ec468c08736f1
2023-06-17 09:05:00 +09:00
write_file(
name = "gki_system_dlkm_modules",
out = "android/gki_system_dlkm_modules",
content = COMMON_GKI_MODULES_LIST + [
# Ensure new line at the end.
"",
],
)
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
filegroup(
name = "aarch64_additional_kmi_symbol_lists",
srcs = [
# keep sorted
"android/abi_gki_aarch64_db845c",
ANDROID: Add initial symbol list for Exynos SoC This commit is for adding initial symbol list form Exynos SoC. "abi_gki_aarch64_exynos" is generated from minimal configs for build. 2 function symbol(s) added 'int devm_hwrng_register(struct device*, struct hwrng*)' 'int irq_force_affinity(unsigned int, const struct cpumask*)' Bug: 278466304 Change-Id: I6a700eda5639bf46f694524fefe91b759583704d Signed-off-by: Junki Min <joonki.min@samsung.com>
2023-04-19 15:03:19 +09:00
"android/abi_gki_aarch64_exynos",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
"android/abi_gki_aarch64_galaxy",
ANDROID: GKI: update symbol list file for honor Create the symbol list file for Honor Device Co. Bug: 279793369 Signed-off-by: Dezhi Huang <huangdezhi@hihonor.com> Change-Id: I11bca937366428bc87a174a64b7d6843e3d92339
2023-05-17 16:13:45 +09:00
"android/abi_gki_aarch64_honor",
ANDROID: Add initial symbols list for imx Initial symbol list for imx that adds it to the build and does not add any new symbols at this point in time. Bug: 277651618 Change-Id: I19d4463295bc2f2a22fa5983765a20838d8615ce Signed-off-by: Zhipeng Wang <zhipeng.wang_1@nxp.com> Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
2023-04-11 23:03:40 +09:00
"android/abi_gki_aarch64_imx",
ANDROID: Add initial symbol list for mtk Add initial MTK symbol list and add to the build system. Bug: 277305001 Change-Id: I3944eb4517c5040dac4fb8769907800af3b5495e Signed-off-by: Chun-Hung Wu <chun-hung.wu@mediatek.com> Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
2023-04-07 16:48:38 +09:00
"android/abi_gki_aarch64_mtk",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
"android/abi_gki_aarch64_oplus",
"android/abi_gki_aarch64_pixel",
"android/abi_gki_aarch64_qcom",
ANDROID: GKI: add symbol list file for unisoc Add abi_gki_aarch64_unisoc 4 function symbol(s) added 'struct hwspinlock* devm_hwspin_lock_request_specific(struct device*, unsigned int)' 'void sdhci_enable_v4_mode(struct sdhci_host*)' 'void sdhci_request(struct mmc_host*, struct mmc_request*)' 'int sdhci_request_atomic(struct mmc_host*, struct mmc_request*)' Bug: 282902304 Change-Id: I70eaba8be31407d3486b6e845241681c9995f27e Signed-off-by: Cixi Geng <cixi.geng1@unisoc.com>
2023-05-16 18:14:56 +09:00
"android/abi_gki_aarch64_unisoc",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
"android/abi_gki_aarch64_virtual_device",
ANDROID: GKI: add init symbol list file for vivo 6 function symbol(s) added 'struct buffer_head* __getblk_gfp(struct block_device*, sector_t, unsigned int, gfp_t)' 'void __lock_buffer(struct buffer_head*)' 'void __wait_on_buffer(struct buffer_head*)' 'void end_buffer_read_sync(struct buffer_head*, int)' 'void submit_bh(blk_opf_t, struct buffer_head*)' 'void unlock_buffer(struct buffer_head*)' Bug: 278801617 Change-Id: I3d850f7de9c7acc1c3dc88e65ab811ee16f56a9d Signed-off-by: litao <tao.li@vivo.corp-partner.google.com>
2023-04-19 11:16:07 +09:00
"android/abi_gki_aarch64_vivo",
ANDROID: GKI: add symbol list file for xiaomi add abi_gki_aarch64_xiaomi INFO: 59 function symbol(s) added 'void __blk_mq_end_request(struct request*, blk_status_t)' 'struct scsi_device* __scsi_add_device(struct Scsi_Host*, uint, uint, u64, void*)' 'int __traceiter_android_vh_binder_transaction_init(void*, struct binder_transaction*)' 'int __traceiter_android_vh_binder_wait_for_work(void*, bool, struct binder_thread*, struct binder_proc*)' 'void balance_dirty_pages_ratelimited(struct address_space*)' 'struct backing_dev_info* bdi_alloc(int)' 'void bdi_put(struct backing_dev_info*)' 'int bdi_register(struct backing_dev_info*, const char*, ...)' 'void blk_mq_freeze_queue(struct request_queue*)' 'struct request_queue* blk_mq_init_queue(struct blk_mq_tag_set*)' 'void blk_mq_tagset_busy_iter(struct blk_mq_tag_set*, busy_tag_iter_fn*, void*)' 'void blk_mq_unfreeze_queue(struct request_queue*)' 'void blk_queue_update_dma_alignment(struct request_queue*, int)' 'void blk_queue_update_dma_pad(struct request_queue*, unsigned int)' 'bool blk_update_request(struct request*, blk_status_t, unsigned int)' 'void bsg_job_done(struct bsg_job*, int, unsigned int)' 'void bsg_remove_queue(struct request_queue*)' 'struct request_queue* bsg_setup_queue(struct device*, const char*, bsg_job_fn*, bsg_timeout_fn*, int)' 'void deactivate_locked_super(struct super_block*)' 'void dev_pm_opp_remove(struct device*, unsigned long)' 'const char* drm_get_connector_type_name(unsigned int)' 'void generic_shutdown_super(struct super_block*)' 'int gpio_request_array(const struct gpio*, size_t)' 'void lockref_get(struct lockref*)' 'void logfc(struct fc_log*, const char*, char, const char*, ...)' 'int lookup_bdev(const char*, dev_t*)' 'void* mempool_alloc_pages(gfp_t, void*)' 'void mempool_free_pages(void*, void*)' 'int mempool_resize(mempool_t*, int)' 'struct nvmem_device* nvmem_register(const struct nvmem_config*)' 'void nvmem_unregister(struct nvmem_device*)' 'struct page* read_cache_page(struct address_space*, unsigned long, filler_t*, struct file*)' 'int scsi_add_host_with_dma(struct Scsi_Host*, struct device*, struct device*)' 'int scsi_change_queue_depth(struct scsi_device*, int)' 'struct scsi_device* scsi_device_lookup(struct Scsi_Host*, uint, uint, u64)' 'int scsi_dma_map(struct scsi_cmnd*)' 'void scsi_dma_unmap(struct scsi_cmnd*)' 'struct Scsi_Host* scsi_host_alloc(struct scsi_host_template*, int)' 'struct Scsi_Host* scsi_host_lookup(unsigned short)' 'void scsi_host_put(struct Scsi_Host*)' 'int scsi_is_host_device(const struct device*)' 'void scsi_print_command(struct scsi_cmnd*)' 'void scsi_remove_host(struct Scsi_Host*)' 'void scsi_report_bus_reset(struct Scsi_Host*, int)' 'void scsi_scan_host(struct Scsi_Host*)' 'struct super_block* sget_fc(struct fs_context*, int(*)(struct super_block*, struct fs_context*), int(*)(struct super_block*, struct fs_context*))' 'int ufshcd_alloc_host(struct device*, struct ufs_hba**)' 'int ufshcd_config_pwr_mode(struct ufs_hba*, struct ufs_pa_layer_attr*)' 'void ufshcd_dealloc_host(struct ufs_hba*)' 'int ufshcd_hba_enable(struct ufs_hba*)' 'int ufshcd_make_hba_operational(struct ufs_hba*)' 'void ufshcd_update_evt_hist(struct ufs_hba*, u32, u32)' 'int utf16s_to_utf8s(const wchar_t*, int, enum utf16_endian, u8*, int)' 'void wait_for_device_probe()' 'int wakeup_sources_read_lock()' 'void wakeup_sources_read_unlock(int)' 'struct wakeup_source* wakeup_sources_walk_next(struct wakeup_source*)' 'struct wakeup_source* wakeup_sources_walk_start()' 'int blk_mq_alloc_sq_tag_set(struct blk_mq_tag_set*, const struct blk_mq_ops*, unsigned int, unsigned int)' 3 variable symbol(s) added 'struct tracepoint __tracepoint_android_vh_binder_transaction_init' 'struct tracepoint __tracepoint_android_vh_binder_wait_for_work' 'u64 jiffies_64' Bug: 276850920 Change-Id: Ibc65a0bfb3332072be7bea17e0aea48277043510 Signed-off-by: fengqi <fengqi@xiaomi.com>
2023-04-06 16:53:09 +09:00
"android/abi_gki_aarch64_xiaomi",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
],
visibility = ["//visibility:public"],
)
ANDROID: GKI: enable KMI enforcement Add android/abi_gki_aarch64.stg as initial ABI representation of the KMI and start enforcing KMI. Kernel is not trimmed yet, the trimming will be enabled after adding symbols lists. This is not KMI freeze. While this is hard enforcement in the code base, we still allow controlled changes to the ABI. Test: TH Bug: 269323432 Change-Id: Ic3a126a6d60242ae713ae396bb239af5b3e58c53 Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
2023-02-16 23:03:19 +09:00
ANDROID: GKI: ZSMALLOC & ZRAM as modules for arm64 Enable zram and zsmalloc (dependency for zram) as unprotected modules for aarch64. These are already being used as modules by the vendor currently; so needs to be unprotected. Bug: 230519159 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I7c617c1a24f6e083301cbed67d0d323388cbd622 (cherry picked from commit 0fe423433bb3fa0b5003409bbd59a972e6c235e2)
2022-04-28 08:20:12 +09:00
define_common_kernels(target_configs = {
"kernel_aarch64": {
ANDROID: GKI: arm64: Enable KMI strict mode Enables the KMI strict mode for the aarch64; also remove the TODO comment for aarch64-debug as KMI strict mode shouldn't be enabled for that target. Bug: 269346251 Test: bazel build //common:kernel_aarch64 Test: TH Change-Id: If8cb717d2e3dfef29004fafe1315a69caa940716 Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
2023-03-17 06:25:22 +09:00
"kmi_symbol_list_strict_mode": True,
ANDROID: GKI: enable KMI enforcement Add android/abi_gki_aarch64.stg as initial ABI representation of the KMI and start enforcing KMI. Kernel is not trimmed yet, the trimming will be enabled after adding symbols lists. This is not KMI freeze. While this is hard enforcement in the code base, we still allow controlled changes to the ABI. Test: TH Bug: 269323432 Change-Id: Ic3a126a6d60242ae713ae396bb239af5b3e58c53 Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
2023-02-16 23:03:19 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
"kmi_symbol_list": "android/abi_gki_aarch64",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
"additional_kmi_symbol_lists": [":aarch64_additional_kmi_symbol_lists"],
ANDROID: GKI: Multi arch exports protection support ABI is being implemented for x86_64, making it necessary to support protected exports header file generation for the GKI modules for multiple architecture. Enable support to select required inputs based on the ARCH to generate gki_module_protected_exports.h during kernel build. Inputs for generating gki_module_protected_exports.h are: ARCH = arm64: ABI Protected exports list: abi_gki_protected_exports_aarch64 Protected GKI modules list: gki_aarch64_protected_modules ARCH = x86_64: ABI Protected exports list: abi_gki_protected_exports_x86_64 Protected GKI modules list: gki_x86_64_protected_modules Test: TH Test: Manual verification of the generated header file Test: bazel run //common:kernel_aarch64_abi_update_protected_exports Bug: 151893768 Change-Id: Ic4bcb2732199b71a7973b5ce4c852bcd95d37131 Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
2023-03-22 07:49:31 +09:00
"protected_exports_list": "android/abi_gki_protected_exports_aarch64",
"protected_modules_list": "android/gki_aarch64_protected_modules",
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_AARCH64_MAKE_GOALS,
ANDROID: GKI: ZSMALLOC & ZRAM as modules for arm64 Enable zram and zsmalloc (dependency for zram) as unprotected modules for aarch64. These are already being used as modules by the vendor currently; so needs to be unprotected. Bug: 230519159 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I7c617c1a24f6e083301cbed67d0d323388cbd622 (cherry picked from commit 0fe423433bb3fa0b5003409bbd59a972e6c235e2)
2022-04-28 08:20:12 +09:00
},
ANDROID: kleaf: add 16k variant of kernel_aarch64 Bug: 234045848 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: Ie8ba8a49347fc28ac9caa37dbcf82597344464e9
2022-10-01 04:27:02 +09:00
"kernel_aarch64_16k": {
ANDROID: Temporarily disable vendor symbol lists This will be reverted before freezing the KMI on this branch. Bug: 264279944 Change-Id: Ic0229cf4e8a9462732cb0555af980747eaee6ebc Signed-off-by: T.J. Mercier <tjmercier@google.com>
2023-01-19 10:46:38 +09:00
"kmi_symbol_list_strict_mode": False,
ANDROID: GKI: enable KMI enforcement Add android/abi_gki_aarch64.stg as initial ABI representation of the KMI and start enforcing KMI. Kernel is not trimmed yet, the trimming will be enabled after adding symbols lists. This is not KMI freeze. While this is hard enforcement in the code base, we still allow controlled changes to the ABI. Test: TH Bug: 269323432 Change-Id: Ic3a126a6d60242ae713ae396bb239af5b3e58c53 Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
2023-02-16 23:03:19 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_AARCH64_MAKE_GOALS,
ANDROID: kleaf: add 16k variant of kernel_aarch64 Bug: 234045848 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: Ie8ba8a49347fc28ac9caa37dbcf82597344464e9
2022-10-01 04:27:02 +09:00
},
ANDROID: GKI: ZSMALLOC & ZRAM as modules for arm64 Enable zram and zsmalloc (dependency for zram) as unprotected modules for aarch64. These are already being used as modules by the vendor currently; so needs to be unprotected. Bug: 230519159 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I7c617c1a24f6e083301cbed67d0d323388cbd622 (cherry picked from commit 0fe423433bb3fa0b5003409bbd59a972e6c235e2)
2022-04-28 08:20:12 +09:00
"kernel_aarch64_debug": {
ANDROID: Temporarily disable vendor symbol lists This will be reverted before freezing the KMI on this branch. Bug: 264279944 Change-Id: Ic0229cf4e8a9462732cb0555af980747eaee6ebc Signed-off-by: T.J. Mercier <tjmercier@google.com>
2023-01-19 10:46:38 +09:00
"kmi_symbol_list_strict_mode": False,
ANDROID: GKI: enable KMI enforcement Add android/abi_gki_aarch64.stg as initial ABI representation of the KMI and start enforcing KMI. Kernel is not trimmed yet, the trimming will be enabled after adding symbols lists. This is not KMI freeze. While this is hard enforcement in the code base, we still allow controlled changes to the ABI. Test: TH Bug: 269323432 Change-Id: Ic3a126a6d60242ae713ae396bb239af5b3e58c53 Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
2023-02-16 23:03:19 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
"kmi_symbol_list": "android/abi_gki_aarch64",
ANDROID: GKI: Add a filegroup instead of _aarch64_additional_kmi symbol list _aarch64_additional_kmi_symbol_list has all vendor's kmi symbol list file, but it is inaccessible from outside. Added a filegroup for it. Bug: 275670969 Signed-off-by: Junki Min <joonki.min@samsung.com> Change-Id: I65ad4008ae2135fae88c8eaf1c09d141ea562294
2023-03-29 19:18:01 +09:00
"additional_kmi_symbol_lists": [":aarch64_additional_kmi_symbol_lists"],
ANDROID: GKI: Multi arch exports protection support ABI is being implemented for x86_64, making it necessary to support protected exports header file generation for the GKI modules for multiple architecture. Enable support to select required inputs based on the ARCH to generate gki_module_protected_exports.h during kernel build. Inputs for generating gki_module_protected_exports.h are: ARCH = arm64: ABI Protected exports list: abi_gki_protected_exports_aarch64 Protected GKI modules list: gki_aarch64_protected_modules ARCH = x86_64: ABI Protected exports list: abi_gki_protected_exports_x86_64 Protected GKI modules list: gki_x86_64_protected_modules Test: TH Test: Manual verification of the generated header file Test: bazel run //common:kernel_aarch64_abi_update_protected_exports Bug: 151893768 Change-Id: Ic4bcb2732199b71a7973b5ce4c852bcd95d37131 Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
2023-03-22 07:49:31 +09:00
"protected_exports_list": "android/abi_gki_protected_exports_aarch64",
"protected_modules_list": "android/gki_aarch64_protected_modules",
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_AARCH64_MAKE_GOALS,
ANDROID: GKI: ZSMALLOC & ZRAM as modules for arm64 Enable zram and zsmalloc (dependency for zram) as unprotected modules for aarch64. These are already being used as modules by the vendor currently; so needs to be unprotected. Bug: 230519159 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I7c617c1a24f6e083301cbed67d0d323388cbd622 (cherry picked from commit 0fe423433bb3fa0b5003409bbd59a972e6c235e2)
2022-04-28 08:20:12 +09:00
},
ANDROID: GKI: Add 64-bit RISC-V config Add a "fake" GKI for RISC-V based on the arm64 one. This implementation simply symlinks the arm64 gki_defconfig and merges in two other configs: - arch/riscv/configs/64-bit.config This is an upstream file which enables RISC-V for 64-bit. - arch/riscv/configs/gki.config This is a workaround file which enables things the ARM64 architecture pre-selects, such as GPIOLIB. Without enabling these options, some drivers are incorrectly dropped from the gki_defconfig. Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: Ifad59ed483bdbb736e905eefc5107328155a361b
2022-11-22 09:11:21 +09:00
"kernel_riscv64": {
ANDROID: Temporarily disable vendor symbol lists This will be reverted before freezing the KMI on this branch. Bug: 264279944 Change-Id: Ic0229cf4e8a9462732cb0555af980747eaee6ebc Signed-off-by: T.J. Mercier <tjmercier@google.com>
2023-01-19 10:46:38 +09:00
"kmi_symbol_list_strict_mode": False,
ANDROID: GKI: enable KMI enforcement Add android/abi_gki_aarch64.stg as initial ABI representation of the KMI and start enforcing KMI. Kernel is not trimmed yet, the trimming will be enabled after adding symbols lists. This is not KMI freeze. While this is hard enforcement in the code base, we still allow controlled changes to the ABI. Test: TH Bug: 269323432 Change-Id: Ic3a126a6d60242ae713ae396bb239af5b3e58c53 Signed-off-by: Aleksei Vetrov <vvvvvv@google.com>
2023-02-16 23:03:19 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_RISCV64_MAKE_GOALS,
ANDROID: GKI: Add 64-bit RISC-V config Add a "fake" GKI for RISC-V based on the arm64 one. This implementation simply symlinks the arm64 gki_defconfig and merges in two other configs: - arch/riscv/configs/64-bit.config This is an upstream file which enables RISC-V for 64-bit. - arch/riscv/configs/gki.config This is a workaround file which enables things the ARM64 architecture pre-selects, such as GPIOLIB. Without enabling these options, some drivers are incorrectly dropped from the gki_defconfig. Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: Ifad59ed483bdbb736e905eefc5107328155a361b
2022-11-22 09:11:21 +09:00
},
ANDROID: GKI: x86_64: zram & zsmalloc as modules Enable zram and zsmalloc as modules to be in sync with the aarch64 builds. Bug: 232431151 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I55053eeb6beda342689c854f95f4307871a3729b (cherry picked from commit 44e9b82e013edee43f02f68e0b8a011135d290db)
2022-10-26 10:01:29 +09:00
"kernel_x86_64": {
"kmi_symbol_list_strict_mode": False,
ANDROID: kleaf: Move list of kernel modules to an extension. This is so that it can be loaded by other packages. Some device's may wish to not build mixed build, in which case they'll either need to use 'auto' in module_outs (discouraged), or load the list of GKI modules. Test: TH Bug: 258308697 Change-Id: Iff7778b9edae7101a2debd44a49bb5eb403bfb2f Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 08:32:17 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
ANDROID: GKI: Multi arch exports protection support ABI is being implemented for x86_64, making it necessary to support protected exports header file generation for the GKI modules for multiple architecture. Enable support to select required inputs based on the ARCH to generate gki_module_protected_exports.h during kernel build. Inputs for generating gki_module_protected_exports.h are: ARCH = arm64: ABI Protected exports list: abi_gki_protected_exports_aarch64 Protected GKI modules list: gki_aarch64_protected_modules ARCH = x86_64: ABI Protected exports list: abi_gki_protected_exports_x86_64 Protected GKI modules list: gki_x86_64_protected_modules Test: TH Test: Manual verification of the generated header file Test: bazel run //common:kernel_aarch64_abi_update_protected_exports Bug: 151893768 Change-Id: Ic4bcb2732199b71a7973b5ce4c852bcd95d37131 Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
2023-03-22 07:49:31 +09:00
"protected_exports_list": "android/abi_gki_protected_exports_x86_64",
"protected_modules_list": "android/gki_x86_64_protected_modules",
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_X86_64_MAKE_GOALS,
ANDROID: GKI: x86_64: zram & zsmalloc as modules Enable zram and zsmalloc as modules to be in sync with the aarch64 builds. Bug: 232431151 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I55053eeb6beda342689c854f95f4307871a3729b (cherry picked from commit 44e9b82e013edee43f02f68e0b8a011135d290db)
2022-10-26 10:01:29 +09:00
},
"kernel_x86_64_debug": {
"kmi_symbol_list_strict_mode": False,
ANDROID: kleaf: Move list of kernel modules to an extension. This is so that it can be loaded by other packages. Some device's may wish to not build mixed build, in which case they'll either need to use 'auto' in module_outs (discouraged), or load the list of GKI modules. Test: TH Bug: 258308697 Change-Id: Iff7778b9edae7101a2debd44a49bb5eb403bfb2f Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 08:32:17 +09:00
"module_implicit_outs": COMMON_GKI_MODULES_LIST,
ANDROID: GKI: Multi arch exports protection support ABI is being implemented for x86_64, making it necessary to support protected exports header file generation for the GKI modules for multiple architecture. Enable support to select required inputs based on the ARCH to generate gki_module_protected_exports.h during kernel build. Inputs for generating gki_module_protected_exports.h are: ARCH = arm64: ABI Protected exports list: abi_gki_protected_exports_aarch64 Protected GKI modules list: gki_aarch64_protected_modules ARCH = x86_64: ABI Protected exports list: abi_gki_protected_exports_x86_64 Protected GKI modules list: gki_x86_64_protected_modules Test: TH Test: Manual verification of the generated header file Test: bazel run //common:kernel_aarch64_abi_update_protected_exports Bug: 151893768 Change-Id: Ic4bcb2732199b71a7973b5ce4c852bcd95d37131 Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
2023-03-22 07:49:31 +09:00
"protected_exports_list": "android/abi_gki_protected_exports_x86_64",
"protected_modules_list": "android/gki_x86_64_protected_modules",
ANDROID: GKI: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. Bug: 236012223 Change-Id: Id90fa89dcadd95d8a8ecf570f46d9d71a925c388 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> (cherry picked from commit ab7e63ef765d74b388e881800ad500c5f93199fc)
2023-05-05 07:04:29 +09:00
"make_goals": _GKI_X86_64_MAKE_GOALS,
ANDROID: GKI: x86_64: zram & zsmalloc as modules Enable zram and zsmalloc as modules to be in sync with the aarch64 builds. Bug: 232431151 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I55053eeb6beda342689c854f95f4307871a3729b (cherry picked from commit 44e9b82e013edee43f02f68e0b8a011135d290db)
2022-10-26 10:01:29 +09:00
},
ANDROID: GKI: ZSMALLOC & ZRAM as modules for arm64 Enable zram and zsmalloc (dependency for zram) as unprotected modules for aarch64. These are already being used as modules by the vendor currently; so needs to be unprotected. Bug: 230519159 Test: TH Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I7c617c1a24f6e083301cbed67d0d323388cbd622 (cherry picked from commit 0fe423433bb3fa0b5003409bbd59a972e6c235e2)
2022-04-28 08:20:12 +09:00
})
ANDROID: enable db845c kleaf build. Kleaf replaces build.sh. Define db845c target in Bazel so it may be built with the following command. Kleaf requires the list of in-tree kernel modules to be listed explicitly. Test: tools/bazel run //common:db845c_dist Bug: 229913034 Change-Id: I725d7d6c4e9897cad58f970821cd2b222ac64889 Signed-off-by: Yifan Hong <elsk@google.com>
2022-04-26 13:17:00 +09:00
ANDROID: db845c: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally. Bug: 270320056 Change-Id: I0eafb118836e6a31dc3b0392ab7d60b5597b9367 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-23 19:03:10 +09:00
_DB845C_MODULE_OUTS = [
# keep sorted
"crypto/michael_mic.ko",
"drivers/base/regmap/regmap-sdw.ko",
"drivers/base/regmap/regmap-slimbus.ko",
"drivers/bus/mhi/host/mhi.ko",
"drivers/clk/qcom/clk-qcom.ko",
"drivers/clk/qcom/clk-rpmh.ko",
"drivers/clk/qcom/clk-spmi-pmic-div.ko",
"drivers/clk/qcom/dispcc-sdm845.ko",
"drivers/clk/qcom/dispcc-sm8250.ko",
"drivers/clk/qcom/gcc-sdm845.ko",
"drivers/clk/qcom/gcc-sm8250.ko",
"drivers/clk/qcom/gcc-sm8450.ko",
"drivers/clk/qcom/gpucc-sdm845.ko",
"drivers/clk/qcom/gpucc-sm8250.ko",
"drivers/clk/qcom/lpass-gfm-sm8250.ko",
"drivers/clk/qcom/videocc-sdm845.ko",
"drivers/clk/qcom/videocc-sm8250.ko",
"drivers/cpufreq/qcom-cpufreq-hw.ko",
"drivers/dma-buf/heaps/system_heap.ko",
"drivers/dma/qcom/bam_dma.ko",
"drivers/dma/qcom/gpi.ko",
"drivers/extcon/extcon-usb-gpio.ko",
"drivers/firmware/qcom-scm.ko",
"drivers/gpio/gpio-wcd934x.ko",
"drivers/gpu/drm/bridge/display-connector.ko",
"drivers/gpu/drm/bridge/lontium-lt9611.ko",
"drivers/gpu/drm/bridge/lontium-lt9611uxc.ko",
"drivers/gpu/drm/display/drm_display_helper.ko",
"drivers/gpu/drm/display/drm_dp_aux_bus.ko",
"drivers/gpu/drm/msm/msm.ko",
"drivers/gpu/drm/scheduler/gpu-sched.ko",
"drivers/hwspinlock/qcom_hwspinlock.ko",
"drivers/i2c/busses/i2c-designware-core.ko",
"drivers/i2c/busses/i2c-designware-platform.ko",
"drivers/i2c/busses/i2c-qcom-geni.ko",
"drivers/i2c/busses/i2c-qup.ko",
"drivers/i2c/busses/i2c-rk3x.ko",
"drivers/i2c/i2c-dev.ko",
"drivers/i2c/i2c-mux.ko",
"drivers/i2c/muxes/i2c-mux-pca954x.ko",
"drivers/iio/adc/qcom-spmi-adc5.ko",
"drivers/iio/adc/qcom-vadc-common.ko",
"drivers/input/misc/pm8941-pwrkey.ko",
"drivers/interconnect/qcom/icc-bcm-voter.ko",
"drivers/interconnect/qcom/icc-osm-l3.ko",
"drivers/interconnect/qcom/icc-rpmh.ko",
"drivers/interconnect/qcom/qnoc-sdm845.ko",
"drivers/interconnect/qcom/qnoc-sm8250.ko",
"drivers/interconnect/qcom/qnoc-sm8450.ko",
"drivers/iommu/arm/arm-smmu/arm_smmu.ko",
"drivers/irqchip/qcom-pdc.ko",
"drivers/leds/rgb/leds-qcom-lpg.ko",
"drivers/mailbox/qcom-apcs-ipc-mailbox.ko",
"drivers/mailbox/qcom-ipcc.ko",
"drivers/media/platform/qcom/venus/venus-core.ko",
"drivers/media/platform/qcom/venus/venus-dec.ko",
"drivers/media/platform/qcom/venus/venus-enc.ko",
"drivers/mfd/qcom-spmi-pmic.ko",
"drivers/mfd/wcd934x.ko",
"drivers/misc/fastrpc.ko",
"drivers/mmc/host/cqhci.ko",
"drivers/mmc/host/sdhci-msm.ko",
"drivers/net/can/spi/mcp251xfd/mcp251xfd.ko",
"drivers/net/wireless/ath/ath.ko",
"drivers/net/wireless/ath/ath10k/ath10k_core.ko",
"drivers/net/wireless/ath/ath10k/ath10k_pci.ko",
"drivers/net/wireless/ath/ath10k/ath10k_snoc.ko",
"drivers/net/wireless/ath/ath11k/ath11k.ko",
"drivers/net/wireless/ath/ath11k/ath11k_ahb.ko",
"drivers/net/wireless/ath/ath11k/ath11k_pci.ko",
"drivers/nvmem/nvmem_qfprom.ko",
"drivers/phy/qualcomm/phy-qcom-qmp-combo.ko",
"drivers/phy/qualcomm/phy-qcom-qmp-pcie.ko",
"drivers/phy/qualcomm/phy-qcom-qmp-pcie-msm8996.ko",
"drivers/phy/qualcomm/phy-qcom-qmp-ufs.ko",
"drivers/phy/qualcomm/phy-qcom-qmp-usb.ko",
"drivers/phy/qualcomm/phy-qcom-qusb2.ko",
"drivers/phy/qualcomm/phy-qcom-snps-femto-v2.ko",
"drivers/phy/qualcomm/phy-qcom-usb-hs.ko",
"drivers/pinctrl/qcom/pinctrl-lpass-lpi.ko",
"drivers/pinctrl/qcom/pinctrl-msm.ko",
"drivers/pinctrl/qcom/pinctrl-sdm845.ko",
"drivers/pinctrl/qcom/pinctrl-sm8250.ko",
"drivers/pinctrl/qcom/pinctrl-sm8250-lpass-lpi.ko",
"drivers/pinctrl/qcom/pinctrl-sm8450.ko",
"drivers/pinctrl/qcom/pinctrl-spmi-gpio.ko",
"drivers/pinctrl/qcom/pinctrl-spmi-mpp.ko",
"drivers/power/reset/qcom-pon.ko",
"drivers/power/reset/reboot-mode.ko",
"drivers/power/reset/syscon-reboot-mode.ko",
"drivers/regulator/gpio-regulator.ko",
"drivers/regulator/qcom-rpmh-regulator.ko",
"drivers/regulator/qcom_spmi-regulator.ko",
"drivers/regulator/qcom_usb_vbus-regulator.ko",
"drivers/remoteproc/qcom_common.ko",
"drivers/remoteproc/qcom_pil_info.ko",
"drivers/remoteproc/qcom_q6v5.ko",
"drivers/remoteproc/qcom_q6v5_adsp.ko",
"drivers/remoteproc/qcom_q6v5_mss.ko",
"drivers/remoteproc/qcom_q6v5_pas.ko",
"drivers/remoteproc/qcom_q6v5_wcss.ko",
"drivers/remoteproc/qcom_sysmon.ko",
"drivers/reset/reset-qcom-aoss.ko",
"drivers/reset/reset-qcom-pdc.ko",
"drivers/rpmsg/qcom_glink.ko",
"drivers/rpmsg/qcom_glink_rpm.ko",
"drivers/rpmsg/qcom_glink_smem.ko",
"drivers/rpmsg/qcom_smd.ko",
"drivers/rpmsg/rpmsg_ns.ko",
"drivers/rtc/rtc-pm8xxx.ko",
"drivers/slimbus/slim-qcom-ngd-ctrl.ko",
"drivers/slimbus/slimbus.ko",
"drivers/soc/qcom/apr.ko",
"drivers/soc/qcom/cmd-db.ko",
"drivers/soc/qcom/cpr.ko",
"drivers/soc/qcom/llcc-qcom.ko",
"drivers/soc/qcom/mdt_loader.ko",
"drivers/soc/qcom/pdr_interface.ko",
"drivers/soc/qcom/qcom_aoss.ko",
"drivers/soc/qcom/qcom_rpmh.ko",
"drivers/soc/qcom/qmi_helpers.ko",
"drivers/soc/qcom/rmtfs_mem.ko",
"drivers/soc/qcom/rpmhpd.ko",
"drivers/soc/qcom/smem.ko",
"drivers/soc/qcom/smp2p.ko",
"drivers/soc/qcom/smsm.ko",
"drivers/soc/qcom/socinfo.ko",
"drivers/soc/qcom/spm.ko",
"drivers/soundwire/soundwire-bus.ko",
"drivers/soundwire/soundwire-qcom.ko",
"drivers/spi/spi-geni-qcom.ko",
"drivers/spi/spi-pl022.ko",
"drivers/spi/spi-qcom-qspi.ko",
"drivers/spi/spi-qup.ko",
"drivers/spmi/spmi-pmic-arb.ko",
"drivers/thermal/qcom/lmh.ko",
"drivers/thermal/qcom/qcom-spmi-adc-tm5.ko",
"drivers/thermal/qcom/qcom-spmi-temp-alarm.ko",
"drivers/thermal/qcom/qcom_tsens.ko",
"drivers/tty/serial/msm_serial.ko",
"drivers/ufs/host/ufs_qcom.ko",
"drivers/usb/common/ulpi.ko",
"drivers/usb/host/ohci-hcd.ko",
"drivers/usb/host/ohci-pci.ko",
"drivers/usb/host/ohci-platform.ko",
"drivers/usb/typec/qcom-pmic-typec.ko",
"net/mac80211/mac80211.ko",
"net/qrtr/qrtr.ko",
"net/qrtr/qrtr-mhi.ko",
"net/qrtr/qrtr-smd.ko",
"net/qrtr/qrtr-tun.ko",
"net/wireless/cfg80211.ko",
"sound/soc/codecs/snd-soc-dmic.ko",
"sound/soc/codecs/snd-soc-hdmi-codec.ko",
"sound/soc/codecs/snd-soc-lpass-macro-common.ko",
"sound/soc/codecs/snd-soc-lpass-va-macro.ko",
"sound/soc/codecs/snd-soc-lpass-wsa-macro.ko",
"sound/soc/codecs/snd-soc-max98927.ko",
"sound/soc/codecs/snd-soc-rl6231.ko",
"sound/soc/codecs/snd-soc-rt5663.ko",
"sound/soc/codecs/snd-soc-wcd-mbhc.ko",
"sound/soc/codecs/snd-soc-wcd9335.ko",
"sound/soc/codecs/snd-soc-wcd934x.ko",
"sound/soc/codecs/snd-soc-wsa881x.ko",
"sound/soc/qcom/qdsp6/q6adm.ko",
"sound/soc/qcom/qdsp6/q6afe.ko",
"sound/soc/qcom/qdsp6/q6afe-clocks.ko",
"sound/soc/qcom/qdsp6/q6afe-dai.ko",
"sound/soc/qcom/qdsp6/q6apm-dai.ko",
"sound/soc/qcom/qdsp6/q6apm-lpass-dais.ko",
"sound/soc/qcom/qdsp6/q6asm.ko",
"sound/soc/qcom/qdsp6/q6asm-dai.ko",
"sound/soc/qcom/qdsp6/q6core.ko",
"sound/soc/qcom/qdsp6/q6prm.ko",
"sound/soc/qcom/qdsp6/q6prm-clocks.ko",
"sound/soc/qcom/qdsp6/q6routing.ko",
"sound/soc/qcom/qdsp6/snd-q6apm.ko",
"sound/soc/qcom/qdsp6/snd-q6dsp-common.ko",
"sound/soc/qcom/snd-soc-qcom-common.ko",
"sound/soc/qcom/snd-soc-qcom-sdw.ko",
"sound/soc/qcom/snd-soc-sdm845.ko",
"sound/soc/qcom/snd-soc-sm8250.ko",
]
_DB845C_WATCHDOG_MODULE_OUTS = [
"drivers/watchdog/pm8916_wdt.ko",
"drivers/watchdog/qcom-wdt.ko",
]
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
kernel_build(
ANDROID: db845c: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally. Bug: 270320056 Change-Id: I0eafb118836e6a31dc3b0392ab7d60b5597b9367 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-23 19:03:10 +09:00
name = "db845c_no_kgdb",
ANDROID: Convert db845c to a mixed build. * This means using GKI[0] artifacts as base for the kernel. [0] https://source.android.com/docs/core/architecture/kernel/generic-kernel-image#fragmentation-fix-gki * It was initially submitted as part of https://r.android.com/q/topic:db845c_mixed_build but then reverted in https://r.android.com/q/topic:revert-2188970-db845c_mixed_build-YESQWWKQCV * https://android-review.googlesource.com/c/kernel/common/+/2203435 fixes the previous reason for reverting, making it safe to submit it again. Bug: 233404531 Signed-off-by: Ulises Mendez Martinez <umendez@google.com> Change-Id: Id7986dacf4bcdb9a54193c5277e2c6d968b3aaa6
2022-09-03 04:21:44 +09:00
outs = [
ANDROID: enable db845c kleaf build. Kleaf replaces build.sh. Define db845c target in Bazel so it may be built with the following command. Kleaf requires the list of in-tree kernel modules to be listed explicitly. Test: tools/bazel run //common:db845c_dist Bug: 229913034 Change-Id: I725d7d6c4e9897cad58f970821cd2b222ac64889 Signed-off-by: Yifan Hong <elsk@google.com>
2022-04-26 13:17:00 +09:00
"arch/arm64/boot/dts/qcom/qrb5165-rb5.dtb",
"arch/arm64/boot/dts/qcom/sdm845-db845c.dtb",
ANDROID: Enable SM8450 drivers and DTB in the db845c config Bug: 217455793 Change-Id: I710c1e40161bb49ad68ae7ef8804fa25c7b8a232 Signed-off-by: Peter Collingbourne <pcc@google.com>
2022-02-02 09:18:49 +09:00
"arch/arm64/boot/dts/qcom/sm8450-qrd.dtb",
ANDROID: enable db845c kleaf build. Kleaf replaces build.sh. Define db845c target in Bazel so it may be built with the following command. Kleaf requires the list of in-tree kernel modules to be listed explicitly. Test: tools/bazel run //common:db845c_dist Bug: 229913034 Change-Id: I725d7d6c4e9897cad58f970821cd2b222ac64889 Signed-off-by: Yifan Hong <elsk@google.com>
2022-04-26 13:17:00 +09:00
],
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
# Enable mixed build.
base_kernel = ":kernel_aarch64",
build_config = "build.config.db845c",
collect_unstripped_modules = True,
kmi_symbol_list = "android/abi_gki_aarch64_db845c",
ANDROID: db845c: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. * This migrates rockpi4 `MAKE_GOALS` too. Bug: 236012223 Change-Id: Icf47eb42795100b4955f02170a002689c7566194 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-05-12 21:04:53 +09:00
make_goals = [
"modules",
"qcom/sdm845-db845c.dtb",
"qcom/qrb5165-rb5.dtb",
"qcom/sm8450-qrd.dtb",
],
ANDROID: db845c: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally. Bug: 270320056 Change-Id: I0eafb118836e6a31dc3b0392ab7d60b5597b9367 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-23 19:03:10 +09:00
module_outs = _DB845C_MODULE_OUTS + _DB845C_WATCHDOG_MODULE_OUTS,
strip_modules = True,
)
kernel_build(
name = "db845c_with_kgdb",
outs = [
"arch/arm64/boot/dts/qcom/qrb5165-rb5.dtb",
"arch/arm64/boot/dts/qcom/sdm845-db845c.dtb",
"arch/arm64/boot/dts/qcom/sm8450-qrd.dtb",
ANDROID: enable db845c kleaf build. Kleaf replaces build.sh. Define db845c target in Bazel so it may be built with the following command. Kleaf requires the list of in-tree kernel modules to be listed explicitly. Test: tools/bazel run //common:db845c_dist Bug: 229913034 Change-Id: I725d7d6c4e9897cad58f970821cd2b222ac64889 Signed-off-by: Yifan Hong <elsk@google.com>
2022-04-26 13:17:00 +09:00
],
ANDROID: db845c: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally. Bug: 270320056 Change-Id: I0eafb118836e6a31dc3b0392ab7d60b5597b9367 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-23 19:03:10 +09:00
# Enable mixed build.
base_kernel = ":kernel_aarch64",
build_config = "build.config.db845c",
make_goals = [
"modules",
"qcom/sdm845-db845c.dtb",
"qcom/qrb5165-rb5.dtb",
"qcom/sm8450-qrd.dtb",
],
module_outs = _DB845C_MODULE_OUTS,
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
strip_modules = True,
)
ANDROID: db845c: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally. Bug: 270320056 Change-Id: I0eafb118836e6a31dc3b0392ab7d60b5597b9367 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-23 19:03:10 +09:00
alias(
name = "db845c",
actual = select({
"//build/kernel/kleaf:kgdb_is_true": "db845c_with_kgdb",
"//conditions:default": "db845c_no_kgdb",
}),
)
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
kernel_abi(
name = "db845c_abi",
kernel_build = ":db845c",
kmi_symbol_list_add_only = True,
)
kernel_modules_install(
name = "db845c_modules_install",
kernel_build = ":db845c",
)
merged_kernel_uapi_headers(
name = "db845c_merged_kernel_uapi_headers",
kernel_build = ":db845c",
)
kernel_images(
name = "db845c_images",
build_initramfs = True,
kernel_build = ":db845c",
kernel_modules_install = ":db845c_modules_install",
)
copy_to_dist_dir(
name = "db845c_dist",
data = [
":db845c",
":db845c_images",
":db845c_modules_install",
":db845c_merged_kernel_uapi_headers",
# Mixed build: Additional GKI artifacts.
":kernel_aarch64",
":kernel_aarch64_modules",
":kernel_aarch64_additional_artifacts",
],
dist_dir = "out/db845/dist",
flat = True,
log = "info",
ANDROID: enable db845c kleaf build. Kleaf replaces build.sh. Define db845c target in Bazel so it may be built with the following command. Kleaf requires the list of in-tree kernel modules to be listed explicitly. Test: tools/bazel run //common:db845c_dist Bug: 229913034 Change-Id: I725d7d6c4e9897cad58f970821cd2b222ac64889 Signed-off-by: Yifan Hong <elsk@google.com>
2022-04-26 13:17:00 +09:00
)
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
_ROCKPI4_MODULE_OUTS = [
# keep sorted
"drivers/block/virtio_blk.ko",
"drivers/char/hw_random/virtio-rng.ko",
"drivers/clk/clk-rk808.ko",
"drivers/cpufreq/cpufreq-dt.ko",
"drivers/dma/pl330.ko",
"drivers/gpu/drm/bridge/analogix/analogix_dp.ko",
"drivers/gpu/drm/bridge/synopsys/dw-hdmi.ko",
"drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.ko",
"drivers/gpu/drm/display/drm_display_helper.ko",
"drivers/gpu/drm/drm_dma_helper.ko",
"drivers/gpu/drm/rockchip/rockchipdrm.ko",
"drivers/i2c/busses/i2c-rk3x.ko",
"drivers/iio/adc/rockchip_saradc.ko",
"drivers/iio/buffer/industrialio-triggered-buffer.ko",
"drivers/iio/buffer/kfifo_buf.ko",
"drivers/mfd/rk808.ko",
"drivers/mmc/core/pwrseq_simple.ko",
"drivers/mmc/host/cqhci.ko",
"drivers/mmc/host/dw_mmc.ko",
"drivers/mmc/host/dw_mmc-pltfm.ko",
"drivers/mmc/host/dw_mmc-rockchip.ko",
"drivers/mmc/host/sdhci-of-arasan.ko",
"drivers/net/ethernet/stmicro/stmmac/dwmac-rk.ko",
"drivers/net/ethernet/stmicro/stmmac/stmmac.ko",
"drivers/net/ethernet/stmicro/stmmac/stmmac-platform.ko",
"drivers/net/net_failover.ko",
"drivers/net/pcs/pcs_xpcs.ko",
"drivers/net/virtio_net.ko",
"drivers/pci/controller/pcie-rockchip-host.ko",
"drivers/phy/rockchip/phy-rockchip-emmc.ko",
"drivers/phy/rockchip/phy-rockchip-inno-usb2.ko",
"drivers/phy/rockchip/phy-rockchip-pcie.ko",
"drivers/phy/rockchip/phy-rockchip-typec.ko",
"drivers/pwm/pwm-rockchip.ko",
"drivers/regulator/fan53555.ko",
"drivers/regulator/pwm-regulator.ko",
"drivers/regulator/rk808-regulator.ko",
"drivers/rtc/rtc-rk808.ko",
"drivers/soc/rockchip/io-domain.ko",
"drivers/thermal/rockchip_thermal.ko",
"drivers/usb/host/ohci-hcd.ko",
"drivers/usb/host/ohci-platform.ko",
"drivers/virtio/virtio_pci.ko",
"drivers/virtio/virtio_pci_legacy_dev.ko",
"drivers/virtio/virtio_pci_modern_dev.ko",
"net/core/failover.ko",
]
_ROCKPI4_WATCHDOG_MODULE_OUTS = [
# keep sorted
"drivers/watchdog/dw_wdt.ko",
]
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
# TODO(b/258259749): Convert rockpi4 to mixed build
kernel_build(
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
name = "rockpi4_no_kgdb",
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
outs = [
"Image",
"System.map",
"modules.builtin",
"modules.builtin.modinfo",
"rk3399-rock-pi-4b.dtb",
"vmlinux",
"vmlinux.symvers",
],
build_config = "build.config.rockpi4",
dtstree = "//common-modules/virtual-device:rockpi4_dts",
ANDROID: db845c: Remove MAKE_GOALS from build.config * Instead use the equivalent kernel_build attribute. * This migrates rockpi4 `MAKE_GOALS` too. Bug: 236012223 Change-Id: Icf47eb42795100b4955f02170a002689c7566194 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-05-12 21:04:53 +09:00
make_goals = [
"Image",
"modules",
"rk3399-rock-pi-4b.dtb",
],
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
module_outs = COMMON_GKI_MODULES_LIST + _ROCKPI4_MODULE_OUTS + _ROCKPI4_WATCHDOG_MODULE_OUTS,
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
visibility = ["//visibility:private"],
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
)
# TODO(b/258259749): Convert rockpi4 to mixed build
kernel_build(
name = "rockpi4_with_kgdb",
outs = [
"Image",
"System.map",
"modules.builtin",
"modules.builtin.modinfo",
"rk3399-rock-pi-4b.dtb",
"vmlinux",
"vmlinux.symvers",
],
build_config = "build.config.rockpi4",
dtstree = "//common-modules/virtual-device:rockpi4_dts",
make_goals = [
"Image",
"modules",
"rk3399-rock-pi-4b.dtb",
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
],
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
module_outs = COMMON_GKI_MODULES_LIST + _ROCKPI4_MODULE_OUTS,
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
visibility = ["//visibility:private"],
ANDROID: rockpi4: Fix build when using --kgdb * CONFIG_WATCHDOG is disabled when compiling with --kgdb option, hence the list of modules produced is adjusted conditionally on its value. Bug: 270320056 Change-Id: I4db55fdf6b91a65209d2e0ae3bbb5f384c7eca22 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-04-11 19:52:32 +09:00
)
alias(
name = "rockpi4",
actual = select({
"//build/kernel/kleaf:kgdb_is_true": "rockpi4_with_kgdb",
"//conditions:default": "rockpi4_no_kgdb",
}),
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
)
kernel_modules_install(
name = "rockpi4_modules_install",
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
kernel_build = ":rockpi4",
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
)
kernel_images(
name = "rockpi4_images",
build_initramfs = True,
ANDROID: db845c: Local define for db845c targets Generally DAMP is a best practice in Bazel, for this specific case, it helps with: * Better target discoverability and auto-completion. * It's possible to use `select` for KGDB fixes later on without encountering name expectations broken. Bug: 256196368 Bug: 270320056 Change-Id: I300404a9b2b4b7c6569145a942ecb445d23e8e9a Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2023-06-22 23:08:27 +09:00
kernel_build = ":rockpi4",
kernel_modules_install = ":rockpi4_modules_install",
ANDROID: convert rockpi4 to kleaf. Use Kleaf to build rockpi4. This does not enable mixed build. Mixed build is enabled in follow-up CLs. Test: bazel build //common:rockpi4_dist Bug: 258259749 Change-Id: I4828953495c862afe517fff48195d2f6a97e3fcf Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-16 16:01:00 +09:00
)
copy_to_dist_dir(
name = "rockpi4_dist",
data = [
":rockpi4",
":rockpi4_images",
":rockpi4_modules_install",
],
dist_dir = "out/rockpi4/dist",
flat = True,
)
ANDROID: fips140: add kernel crypto module To meet FIPS 140 requirements, add support for building a kernel module "fips140.ko" that contains various cryptographic algorithms built from existing kernel source files. At load time, the module checks its own integrity and self-tests its algorithms, then registers the algorithms with the crypto API to supersede the original algorithms provided by the kernel itself. [ebiggers: this commit originated from "ANDROID: crypto: fips140 - perform load time integrity check", but I've folded many later commits into it to make forward porting easier. See below] Original commits: android12-5.10: 6be141eb36fe ("ANDROID: crypto: fips140 - perform load time integrity check") 868be244bbed ("ANDROID: inject correct HMAC digest into fips140.ko at build time") 091338cb398e ("ANDROID: fips140: add missing static keyword to fips140_init()") c799c6644b52 ("ANDROID: fips140: adjust some log messages") 92de53472e68 ("ANDROID: fips140: log already-live algorithms") 0af06624eadc ("ANDROID: fips140: check for errors from initcalls") 634445a640a4 ("ANDROID: fips140: fix deadlock in unregister_existing_fips140_algos()") e886dd4c339e ("ANDROID: fips140: unregister existing DRBG algorithms") b7397e89db29 ("ANDROID: fips140: add power-up cryptographic self-tests") 50661975be74 ("ANDROID: fips140: add/update module help text") b397a0387cb2 ("ANDROID: fips140: test all implementations") 17ccefe14021 ("ANDROID: fips140: use full 16-byte IV") 1be58af0776a ("ANDROID: fips140: remove non-prediction-resistant DRBG test") 2b5843ae2d90 ("ANDROID: fips140: add AES-CBC-CTS") 2ee56aad318c ("ANDROID: fips140: add AES-CMAC") 960ebb2b565b ("ANDROID: fips140: add jitterentropy to fips140 module") e5b14396f9d2 ("ANDROID: fips140: take into account AES-GCM not being approvable") 52b70d491bd4 ("ANDROID: fips140: use FIPS140_CFLAGS when compiling fips140-selftests.c") 6b995f5a5403 ("ANDROID: fips140: preserve RELA sections without relying on the module loader") e45108ecff64 ("ANDROID: fips140: block crypto operations until tests complete") ecf9341134d1 ("ANDROID: fips140: remove in-place updating of live algorithms") 482b0323cf29 ("ANDROID: fips140: zeroize temporary values from integrity check") 64d769e53f20 ("ANDROID: fips140: add service indicators") 8d7f609cdaa4 ("ANDROID: fips140: add name and version, and a function to retrieve them") 6b7c37f6c449 ("ANDROID: fips140: use UTS_RELEASE as FIPS version") 903e97a0ca6d ("ANDROID: fips140: refactor evaluation testing support") 97fb2104fe22 ("ANDROID: fips140: add support for injecting integrity error") 109f31ac23f5 ("ANDROID: fips140: add userspace interface for evaluation testing") android14-5.15: 84572a0c7981 ("ANDROID: fips140: split dump-section+add-section into 2 ops") b0f8873811d4 ("ANDROID: kleaf: convert fips140 to kleaf") 2535deae8069 ("ANDROID: GKI: Source GKI_BUILD_CONFIG_FRAGMENT after setting all variables") 685a2ade28bb ("ANDROID: fips140: add crypto_memneq() back to the module") 320dfca58a3d ("ANDROID: fips140: fix in-tree builds") d4966a820397 ("ANDROID: fips140: remove CONFIG_CRYPTO_FIPS140 option") 6da26b8750f5 ("ANDROID: fips140: require 'm' to enable CRYPTO_FIPS140_MOD") bfcfcce3803b ("ANDROID: fips140: unapply ABS32 relocations generated by KCFI") 63f46b45dda2 ("ANDROID: fips140: eliminate crypto-fips.a build step") ae4ca7a09bb6 ("ANDROID: fips140: allow building without LTO") Bug: 153614920 Bug: 188620248 Test: tested that the module builds and can be loaded on raven. Change-Id: I3fde49dbc3d16b149b072a27ba5b4c6219015c94 Signed-off-by: Ard Biesheuvel <ardb@google.com> Signed-off-by: Eric Biggers <ebiggers@google.com>
2021-03-23 18:54:38 +09:00
kernel_build(
name = "fips140",
outs = [],
base_kernel = ":kernel_aarch64",
build_config = "build.config.gki.aarch64.fips140",
module_outs = ["crypto/fips140.ko"],
)
copy_to_dist_dir(
name = "fips140_dist",
data = [
":fips140",
],
dist_dir = "out/fips140/dist",
flat = True,
)
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
# allmodconfig build tests.
# These are build tests only, so:
# - outs are intentionally set to empty to not copy anything to DIST_DIR
# - --allow-undeclared-modules must be used so modules are not declared or copied.
# - No dist target because these are build tests. We don't care about the artifacts.
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
# tools/bazel build --allow_undeclared_modules //common:kernel_aarch64_allmodconfig
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
kernel_build(
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
name = "kernel_aarch64_allmodconfig",
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
# Hack to actually check the build.
# Otherwise, Bazel thinks that there are no output files, and skip building.
outs = [".config"],
build_config = "build.config.allmodconfig.aarch64",
visibility = ["//visibility:private"],
)
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
# tools/bazel build --allow_undeclared_modules //common:kernel_x86_64_allmodconfig
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
kernel_build(
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
name = "kernel_x86_64_allmodconfig",
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
# Hack to actually check the build.
# Otherwise, Bazel thinks that there are no output files, and skip building.
outs = [".config"],
build_config = "build.config.allmodconfig.x86_64",
visibility = ["//visibility:private"],
)
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
# tools/bazel build --allow_undeclared_modules //common:kernel_arm_allmodconfig
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
kernel_build(
ANDROID: kleaf: Rename allmodconfig targets * This is to follow the convention: kernel_<arch>_<target> Bug: 260313194 Change-Id: I643fef0ed77b24c6564f8b8e1ed152180beeaf80 Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
2022-11-24 21:00:01 +09:00
name = "kernel_arm_allmodconfig",
ANDROID: kleaf: Add build rules for allmodconfig. These corresponds to the build.config.allmodconfig.* build configs. Unlike build.sh, the Kleaf variant deliberately does not copy any outputs to the distribution directory. There's not even a dist target. This is because allmodconfig is a build test only. Test: bazel build --allow_undeclared_mdoules //common:allmodconfig_{aarch64,arm,x86_64} Bug: 258259749 Change-Id: Iefe8f69149f6391938696e90243939d42d4fda84 Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-12 09:37:02 +09:00
# Hack to actually check the build.
# Otherwise, Bazel thinks that there are no output files, and skip building.
outs = [".config"],
build_config = "build.config.allmodconfig.arm",
visibility = ["//visibility:private"],
)
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
# DDK Headers
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
# All headers. These are the public targets for DDK modules to use.
alias(
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
name = "all_headers",
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
actual = "all_headers_aarch64",
visibility = ["//visibility:public"],
)
ddk_headers(
name = "all_headers_aarch64",
hdrs = [":all_headers_allowlist_aarch64"] + select({
"//build/kernel/kleaf:allow_ddk_unsafe_headers_set": [":all_headers_unsafe"],
"//conditions:default": [],
}),
visibility = ["//visibility:public"],
)
ANDROID: Add ddk_headers for arm architecture. Similar to aarch64 and x86_64, we also add ddk_headers for arm so we can build DDK (Driver development kit) modules for the arm architecture for virtual devices. Test: Treehugger Bug: 254735056 Change-Id: I7ade4a6053e59d84b825285fbc6162b6e642682e Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-23 07:32:14 +09:00
ddk_headers(
name = "all_headers_arm",
hdrs = [":all_headers_allowlist_arm"] + select({
"//build/kernel/kleaf:allow_ddk_unsafe_headers_set": [":all_headers_unsafe"],
"//conditions:default": [],
}),
visibility = ["//visibility:public"],
)
ANDROID: kleaf: add DDK definitions for risc64 Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: I6d6e90f927796d1355af3ad181624b7abd876a9a
2022-12-09 06:20:51 +09:00
ddk_headers(
name = "all_headers_riscv64",
hdrs = [":all_headers_allowlist_riscv64"] + select({
"//build/kernel/kleaf:allow_ddk_unsafe_headers_set": [":all_headers_unsafe"],
"//conditions:default": [],
}),
visibility = ["//visibility:public"],
)
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
ddk_headers(
name = "all_headers_x86_64",
hdrs = [":all_headers_allowlist_x86_64"] + select({
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
"//build/kernel/kleaf:allow_ddk_unsafe_headers_set": [":all_headers_unsafe"],
"//conditions:default": [],
}),
visibility = ["//visibility:public"],
)
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
# Implementation details for DDK headers. The targets below cannot be directly
# depended on by DDK modules.
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
# DDK headers allowlist. This is the list of all headers and include
# directories that are safe to use in DDK modules.
ddk_headers(
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
name = "all_headers_allowlist_aarch64",
hdrs = [
":all_headers_allowlist_aarch64_globs",
":all_headers_allowlist_common_globs",
],
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
# The list of include directories where source files can #include headers
# from. In other words, these are the `-I` option to the C compiler.
ANDROID: kleaf: //common:all_headers should use linux_includes. A new attribute, linux_includes, is added to ddk_headers to denote that certain include directories should be added to LINUXINCLUDE, not ccflags-y. Change includes to linux_includes for the allowlist of ddk_headers targets in //common. These are already added to LINUXINCLUDE in common/Makefile, but we should make them explicit in BUILD files too so the ordering can be listed clearly in BUILD files. Test: build cuttlefish with DDK Bug: 257342715 Bug: 254735056 Change-Id: I97678264b37036cb5ab86973428e4e0d7f5b645d Signed-off-by: Yifan Hong <elsk@google.com> (cherry picked from commit 943d5a70d5a3a79bae02690a20e600974c7a644a)
2022-11-04 08:12:31 +09:00
# These are prepended to LINUXINCLUDE.
linux_includes = [
ANDROID: kleaf: Initial list of ddk_headers (1: arm64) This CL includes headers used by the external modules of a typical arm64 device. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. - This list includes: - Everything under - arch/arm64/include - include Unsafe list: This is the list of headers that are known to be used by a certain Pixel device kernel build, minus allowlist. The unsafe list is untouched in this CL because: - mainline is volatile; - we don't have ddk_module's for arm64 devices on mainline yet. The command to generate this list is: bazel run //build/kernel/kleaf:gen_ddk_headers \ --gen_ddk_headers_target=//gs/google-modules/soc-modules:slider_modules_install -- -k Manual edits: - manually deleted changes to all_headers_unsafe This change is a partial cherry-pick of 14e14cc4e9407783a559b22dffd4bd2062714dd5 Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I2daf9c1583e59e6852c247c2f3f59a7c91d0022e
2022-10-22 12:19:28 +09:00
"arch/arm64/include",
"arch/arm64/include/uapi",
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
"include",
"include/uapi",
],
visibility = ["//visibility:private"],
)
ANDROID: Add ddk_headers for arm architecture. Similar to aarch64 and x86_64, we also add ddk_headers for arm so we can build DDK (Driver development kit) modules for the arm architecture for virtual devices. Test: Treehugger Bug: 254735056 Change-Id: I7ade4a6053e59d84b825285fbc6162b6e642682e Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-23 07:32:14 +09:00
ddk_headers(
name = "all_headers_allowlist_arm",
hdrs = [
":all_headers_allowlist_arm_globs",
":all_headers_allowlist_common_globs",
],
# The list of include directories where source files can #include headers
# from. In other words, these are the `-I` option to the C compiler.
# These are prepended to LINUXINCLUDE.
linux_includes = [
"arch/arm/include",
"arch/arm/include/uapi",
"include",
"include/uapi",
],
visibility = ["//visibility:private"],
)
ANDROID: kleaf: add DDK definitions for risc64 Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: I6d6e90f927796d1355af3ad181624b7abd876a9a
2022-12-09 06:20:51 +09:00
ddk_headers(
name = "all_headers_allowlist_riscv64",
hdrs = [
":all_headers_allowlist_common_globs",
":all_headers_allowlist_riscv64_globs",
],
# The list of include directories where source files can #include headers
# from. In other words, these are the `-I` option to the C compiler.
# These are prepended to LINUXINCLUDE.
linux_includes = [
"arch/riscv/include",
"arch/riscv/include/uapi",
"include",
"include/uapi",
],
visibility = ["//visibility:private"],
)
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
ddk_headers(
name = "all_headers_allowlist_x86_64",
hdrs = [
":all_headers_allowlist_common_globs",
":all_headers_allowlist_x86_64_globs",
],
# The list of include directories where source files can #include headers
# from. In other words, these are the `-I` option to the C compiler.
ANDROID: kleaf: //common:all_headers should use linux_includes. A new attribute, linux_includes, is added to ddk_headers to denote that certain include directories should be added to LINUXINCLUDE, not ccflags-y. Change includes to linux_includes for the allowlist of ddk_headers targets in //common. These are already added to LINUXINCLUDE in common/Makefile, but we should make them explicit in BUILD files too so the ordering can be listed clearly in BUILD files. Test: build cuttlefish with DDK Bug: 257342715 Bug: 254735056 Change-Id: I97678264b37036cb5ab86973428e4e0d7f5b645d Signed-off-by: Yifan Hong <elsk@google.com> (cherry picked from commit 943d5a70d5a3a79bae02690a20e600974c7a644a)
2022-11-04 08:12:31 +09:00
# These are prepended to LINUXINCLUDE.
linux_includes = [
ANDROID: kleaf: Initial list of ddk_headers (2: virtual_device_x86_64) This CL includes headers used by the external modules of virtual_device_x86_64. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. - This list includes: - Everything under - arch/x86/include - include Unsafe list: This is the list of headers that are known to be used by the external modules of virtual_device_x86_64, minus allowlist. This means, with the allowlist and unsafe list, the certain Pixel device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. The command to generate this list is: bazel run //build/kernel/kleaf:gen_ddk_headers \ --gen_ddk_headers_target=//common-modules/virtual-device:virtual_device_x86_64_modules_install \ --gen_ddk_headers_input_archives=//common:kernel_x86_64_ddk_allowlist_headers \ -- -k Manual edits: - arch/arm64/include/ is added back. This is due to a limitation of the generation script that globs aren't properly handled. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I0eae9213493d78a6899aa15c8096f3c7694328a3 (cherry picked from commit 3d56edf4a961a522ffc4d422c7d7f80eaa970391)
2022-10-22 15:07:21 +09:00
"arch/x86/include",
"arch/x86/include/uapi",
ANDROID: kleaf: Initial list of ddk_headers (1: arm64) This CL includes headers used by the external modules of a typical arm64 device. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. - This list includes: - Everything under - arch/arm64/include - include Unsafe list: This is the list of headers that are known to be used by a certain Pixel device kernel build, minus allowlist. The unsafe list is untouched in this CL because: - mainline is volatile; - we don't have ddk_module's for arm64 devices on mainline yet. The command to generate this list is: bazel run //build/kernel/kleaf:gen_ddk_headers \ --gen_ddk_headers_target=//gs/google-modules/soc-modules:slider_modules_install -- -k Manual edits: - manually deleted changes to all_headers_unsafe This change is a partial cherry-pick of 14e14cc4e9407783a559b22dffd4bd2062714dd5 Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I2daf9c1583e59e6852c247c2f3f59a7c91d0022e
2022-10-22 12:19:28 +09:00
"include",
"include/uapi",
],
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
visibility = ["//visibility:private"],
)
# List of DDK headers allowlist that are glob()-ed to avoid changes of BUILD
# file when the list of files changes. All headers in these directories
# are safe to use.
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
# These are separate filegroup targets so the all_headers_allowlist_* are
# more friendly to batch BUILD file update tools like buildozer.
ANDROID: kleaf: add DDK definitions for risc64 Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: I6d6e90f927796d1355af3ad181624b7abd876a9a
2022-12-09 06:20:51 +09:00
# globs() for arm64 only
filegroup(
name = "all_headers_allowlist_aarch64_globs",
srcs = glob(["arch/arm64/include/**/*.h"]),
visibility = ["//visibility:private"],
)
ANDROID: Add ddk_headers for arm architecture. Similar to aarch64 and x86_64, we also add ddk_headers for arm so we can build DDK (Driver development kit) modules for the arm architecture for virtual devices. Test: Treehugger Bug: 254735056 Change-Id: I7ade4a6053e59d84b825285fbc6162b6e642682e Signed-off-by: Yifan Hong <elsk@google.com>
2022-11-23 07:32:14 +09:00
# globs() for arm only
filegroup(
name = "all_headers_allowlist_arm_globs",
srcs = glob(["arch/arm/include/**/*.h"]),
visibility = ["//visibility:private"],
)
ANDROID: kleaf: add DDK definitions for risc64 Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: I6d6e90f927796d1355af3ad181624b7abd876a9a
2022-12-09 06:20:51 +09:00
# globs() for riscv64 only
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
filegroup(
ANDROID: kleaf: add DDK definitions for risc64 Bug: 260012551 Signed-off-by: Alistair Delva <adelva@google.com> Change-Id: I6d6e90f927796d1355af3ad181624b7abd876a9a
2022-12-09 06:20:51 +09:00
name = "all_headers_allowlist_riscv64_globs",
srcs = glob(["arch/riscv/include/**/*.h"]),
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
visibility = ["//visibility:private"],
)
# globs() for x86 only
filegroup(
name = "all_headers_allowlist_x86_64_globs",
srcs = glob(["arch/x86/include/**/*.h"]),
visibility = ["//visibility:private"],
)
# globs() for all architectures
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
filegroup(
ANDROID: Split x86 and arm64 DDK headers. The ddk_headers targets should be architecture specific; that is, an x86_64 ddk_module should not be able to see arm64 headers, and vice versa. Since the majority of devices is arm64, the //common:all_headers alias points to //common:all_headers_aarch64. x86_64 devices can use //common:all_headers_x86_64 instead. After this change: - arm64 ddk_modules can continue depending on //common:all_headers, or they can depend on //common:all_headers_aarch64 to be explicit. In this case, they will not see the x86 headers. - x86 ddk_modules can depend on //common:all_headers_x86_64. In this case, they will not see the arm64 headers. - unsafe headers under drivers/ are not splitted; they aren't arch specific. This change ensures that e.g. virtual_device_x86_64 does not search the headers from the arm64 folders. Test: bazel build //common:all_headers Test: bazel build --allow_ddk_unsafe_headers_set //common:all_headers Bug: 256225968 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I80dd33fb4c0e93dcba3e0714f9fd67d78596ab15 (cherry picked from commit 366ac32d7d8f0f67ac0c9b856cd387cb9e0354eb)
2022-10-29 08:55:44 +09:00
name = "all_headers_allowlist_common_globs",
srcs = glob(["include/**/*.h"]),
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
visibility = ["//visibility:private"],
)
# DDK headers unsafe list. This is the list of all headers and include
# directories that may be used during migration from kernel_module's, but
# should be avoided in general.
# Use with caution; items may:
# - be removed without notice
# - be moved into all_headers
ddk_headers(
name = "all_headers_unsafe",
ANDROID: kleaf: Initial list of ddk_headers (2: virtual_device_x86_64) This CL includes headers used by the external modules of virtual_device_x86_64. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. - This list includes: - Everything under - arch/x86/include - include Unsafe list: This is the list of headers that are known to be used by the external modules of virtual_device_x86_64, minus allowlist. This means, with the allowlist and unsafe list, the certain Pixel device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. The command to generate this list is: bazel run //build/kernel/kleaf:gen_ddk_headers \ --gen_ddk_headers_target=//common-modules/virtual-device:virtual_device_x86_64_modules_install \ --gen_ddk_headers_input_archives=//common:kernel_x86_64_ddk_allowlist_headers \ -- -k Manual edits: - arch/arm64/include/ is added back. This is due to a limitation of the generation script that globs aren't properly handled. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I0eae9213493d78a6899aa15c8096f3c7694328a3 (cherry picked from commit 3d56edf4a961a522ffc4d422c7d7f80eaa970391)
2022-10-22 15:07:21 +09:00
hdrs = [
"drivers/gpu/drm/virtio/virtgpu_trace.h",
],
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
# The list of include directories where source files can #include headers
# from. In other words, these are the `-I` option to the C compiler.
ANDROID: kleaf: //common:all_headers should use linux_includes. A new attribute, linux_includes, is added to ddk_headers to denote that certain include directories should be added to LINUXINCLUDE, not ccflags-y. Change includes to linux_includes for the allowlist of ddk_headers targets in //common. These are already added to LINUXINCLUDE in common/Makefile, but we should make them explicit in BUILD files too so the ordering can be listed clearly in BUILD files. Test: build cuttlefish with DDK Bug: 257342715 Bug: 254735056 Change-Id: I97678264b37036cb5ab86973428e4e0d7f5b645d Signed-off-by: Yifan Hong <elsk@google.com> (cherry picked from commit 943d5a70d5a3a79bae02690a20e600974c7a644a)
2022-11-04 08:12:31 +09:00
# Unsafe include directories are appended to ccflags-y.
ANDROID: kleaf: Initial list of ddk_headers (0: skeleton) Create the skeleton rules for DDK headers, and write comments with hands. This CL has no real effect; all targets are declared empty and content is filled in in follow up CLs. Allowlist: This is a list of headers and a list of include directories that are known to be safe to be used by modules. Unsafe list: This is the list of headers that are known to be used by some device kernel build, minus allowlist. This means, with the allowlist and unsafe list, an unspecified device kernel build can be transitioned to DDK without any change to the source code. - Note that for cleaness of DDK modules, we may want to remove some items in the allowlist of includes and require device source code to #include from the correct directory. Bug: 248351908 Bug: 254735056 Signed-off-by: Yifan Hong <elsk@google.com> Change-Id: I4f15d2fac703bc3b7100a72e90f289236db3e7e5 (cherry picked from commit ede1fd38eeafa71983e0f578bed60f12e0b87ca1)
2022-10-12 15:07:33 +09:00
includes = [],
visibility = ["//visibility:private"],
)
Reference in New Issue Copy Permalink