BTF-defined BPF map definitions
Subsystems (7)
cover BTF-defined BPF map definitions
This patch set implements initial version (as discussed at LSF/MM2019 conference) of a new way to specify BPF maps, relying on BTF type information, which allows for easy extensibility, preserving forward and backward compatibility. See details and examples in description for patch #6.
Patch #1 centralizes commonly used min/max macro in libbpf_internal.h. Patch #2 extracts .BTF and .BTF.ext loading loging from elf_collect(). Patch #3 refactors map initialization logic into user-provided maps and global data maps, in preparation to adding another way (BTF-defined maps). Patch #4 adds support for map definitions in multiple ELF sections and deprecates bpf_object__find_map_by_offset() API which doesn't appear to be used anymore and makes assumption that all map definitions reside in single ELF section.
Patch #5 splits BTF intialization from sanitization/loading into kernel to preserve original BTF at the time of map initialization.
Patch #6 adds support for BTF-defined maps.
Patch #7 adds new test for BTF-defined map definition.
Patch #8 converts test BPF map definitions to use BTF way.
Andrii Nakryiko (8):
libbpf: add common min/max macro to libbpf_internal.h
libbpf: extract BTF loading and simplify ELF parsing logic
libbpf: refactor map initialization
libbpf: identify maps by section index in addition to offset
libbpf: split initialization and loading of BTF
libbpf: allow specifying map definitions using BTF selftests/bpf: add test for BTF-defined maps selftests/bpf: switch tests to BTF-defined map definitions
tools/lib/bpf/bpf.c | 7 +- tools/lib/bpf/bpf_prog_linfo.c | 5 +- tools/lib/bpf/btf.c | 3 - tools/lib/bpf/btf.h | 1 + tools/lib/bpf/btf_dump.c | 3 - tools/lib/bpf/libbpf.c | 762 +++++++++++++----- tools/lib/bpf/libbpf_internal.h | 7 + tools/testing/selftests/bpf/progs/bpf_flow.c | 18 +- .../selftests/bpf/progs/get_cgroup_id_kern.c | 18 +- .../testing/selftests/bpf/progs/netcnt_prog.c | 22 +- .../selftests/bpf/progs/sample_map_ret0.c | 18 +- .../selftests/bpf/progs/socket_cookie_prog.c | 9 +- .../bpf/progs/sockmap_verdict_prog.c | 36 +- .../selftests/bpf/progs/test_btf_newkv.c | 73 ++ .../bpf/progs/test_get_stack_rawtp.c | 27 +- .../selftests/bpf/progs/test_global_data.c | 27 +- tools/testing/selftests/bpf/progs/test_l4lb.c | 45 +- .../selftests/bpf/progs/test_l4lb_noinline.c | 45 +- .../selftests/bpf/progs/test_map_in_map.c | 20 +- .../selftests/bpf/progs/test_map_lock.c | 22 +- .../testing/selftests/bpf/progs/test_obj_id.c | 9 +- .../bpf/progs/test_select_reuseport_kern.c | 45 +- .../bpf/progs/test_send_signal_kern.c | 22 +- .../bpf/progs/test_skb_cgroup_id_kern.c | 9 +- .../bpf/progs/test_sock_fields_kern.c | 60 +- .../selftests/bpf/progs/test_spin_lock.c | 33 +- .../bpf/progs/test_stacktrace_build_id.c | 44 +- .../selftests/bpf/progs/test_stacktrace_map.c | 40 +- .../testing/selftests/bpf/progs/test_tc_edt.c | 9 +- .../bpf/progs/test_tcp_check_syncookie_kern.c | 9 +- .../selftests/bpf/progs/test_tcp_estats.c | 9 +- .../selftests/bpf/progs/test_tcpbpf_kern.c | 18 +- .../selftests/bpf/progs/test_tcpnotify_kern.c | 18 +- tools/testing/selftests/bpf/progs/test_xdp.c | 18 +- .../selftests/bpf/progs/test_xdp_noinline.c | 60 +- tools/testing/selftests/bpf/test_btf.c | 10 +- .../selftests/bpf/test_queue_stack_map.h | 20 +- .../testing/selftests/bpf/test_sockmap_kern.h | 72 +- 38 files changed, 1182 insertions(+), 491 deletions(-) create mode 100644 tools/testing/selftests/bpf/progs/test_btf_newkv.c
Signature · 1 line
2.17.1
RFC PATCH 1/8 libbpf: add common min/max macro to libbpf_internal.h
Multiple files in libbpf redefine their own definitions for min/max. Let's define them in libbpf_internal.h and use those everywhere.
--- tools/lib/bpf/bpf.c | 7 ++----- tools/lib/bpf/bpf_prog_linfo.c | 5 +---- tools/lib/bpf/btf.c | 3 --- tools/lib/bpf/btf_dump.c | 3 --- tools/lib/bpf/libbpf_internal.h | 7 +++++++ 5 files changed, 10 insertions(+), 15 deletions(-)
tools/lib/bpf/bpf.c +2 -5
@@ -26,10 +26,11 @@#include <memory.h> #include <unistd.h> #include <asm/unistd.h> +#include <errno.h> #include <linux/bpf.h> #include "bpf.h" #include "libbpf.h" -#include <errno.h> +#include "libbpf_internal.h" /* * When building perf, unistd.h is overridden. __NR_bpf is
@@ -53,10 +54,6 @@# endif #endif -#ifndef min -#define min (x, y) ((x) < (y) ? (x) : (y)) -#endif -static inline __u64 ptr_to_u64 (const void *ptr) {return (__u64 ) (unsigned long ) ptr;
tools/lib/bpf/bpf_prog_linfo.c +1 -4
@@ -6,10 +6,7 @@#include <linux/err.h> #include <linux/bpf.h> #include "libbpf.h" - -#ifndef min -#define min (x, y) ((x) < (y) ? (x) : (y)) -#endif +#include "libbpf_internal.h" struct bpf_prog_linfo {void *raw_linfo;
tools/lib/bpf/btf.c +0 -3
@@ -16,9 +16,6 @@#include "libbpf_internal.h" #include "hashmap.h" -#define max (a, b) ((a) > (b) ? (a) : (b)) -#define min (a, b) ((a) < (b) ? (a) : (b)) -#define BTF_MAX_NR_TYPES 0x7fffffff#define BTF_MAX_STR_OFFSET 0x7fffffff
tools/lib/bpf/btf_dump.c +0 -3
@@ -18,9 +18,6 @@#include "libbpf.h" #include "libbpf_internal.h" -#define min (x, y) ((x) < (y) ? (x) : (y)) -#define max (x, y) ((x) < (y) ? (y) : (x)) -static const char PREFIXES [] ="\t\t\t\t\t\t\t\t\t\t\t\t\t" ;static const size_t PREFIX_CNT =sizeof (PREFIXES ) -1 ;
tools/lib/bpf/libbpf_internal.h +7 -0
@@ -23,6 +23,13 @@#define BTF_PARAM_ENC (name, type) (name), (type)#define BTF_VAR_SECINFO_ENC (type, offset, size) (type), (offset), (size) +#ifndef min +# define min (x, y) ((x) < (y) ? (x) : (y)) +#endif +#ifndef max +# define max (x, y) ((x) < (y) ? (y) : (x)) +#endif +extern void libbpf_print (enum libbpf_print_level level,const char *format, ...) __attribute__((format (printf,2 ,3 )));
Signature · 1 line
2.17.1
RFC PATCH 2/8 libbpf: extract BTF loading and simplify ELF parsing logic
In reply to Andrii NakryikoAs a preparation for adding BTF-based BPF map loading, extract .BTF and .BTF.ext loading logic. Also simplify error handling in bpf_object__elf_collect() by returning early, as there is no common clean up to be done.
--- tools/lib/bpf/libbpf.c | 137 ++++++++++++++++++++++------------------- 1 file changed, 75 insertions(+), 62 deletions(-)
tools/lib/bpf/libbpf.c +75 -62
@@ -1078,6 +1078,58 @@ static void bpf_object__sanitize_btf_ext(struct bpf_object *obj) } } +static int bpf_object__load_btf (struct bpf_object *obj, +Elf_Data *btf_data, +Elf_Data *btf_ext_data) +{ +int err =0 ; + +if (btf_data) { + obj->btf =btf__new (btf_data->d_buf, btf_data->d_size); +if (IS_ERR (obj->btf)) { +pr_warning ("Error loading ELF section %s: %d.\n" , +BTF_ELF_SEC , err); + goto out; + } + err =btf__finalize_data (obj, obj->btf); +if (err) { +pr_warning ("Error finalizing %s: %d.\n" , +BTF_ELF_SEC , err); + goto out; + } +bpf_object__sanitize_btf (obj); + err =btf__load (obj->btf); +if (err) { +pr_warning ("Error loading %s into kernel: %d.\n" , +BTF_ELF_SEC , err); + goto out; + } + } +if (btf_ext_data) { +if (!obj->btf) { +pr_debug ("Ignore ELF section %s because its depending ELF section %s is not found.\n" , +BTF_EXT_ELF_SEC ,BTF_ELF_SEC ); + goto out; + } + obj->btf_ext =btf_ext__new (btf_ext_data->d_buf, + btf_ext_data->d_size); +if (IS_ERR (obj->btf_ext)) { +pr_warning ("Error loading ELF section %s: %ld. Ignored and continue.\n" , +BTF_EXT_ELF_SEC ,PTR_ERR (obj->btf_ext)); + obj->btf_ext =NULL ; + goto out; + } +bpf_object__sanitize_btf_ext (obj); + } +out: +if (err ||IS_ERR (obj->btf)) { +if (!IS_ERR_OR_NULL (obj->btf)) +btf__free (obj->btf); + obj->btf =NULL ; + } +return 0 ; +} +static int bpf_object__elf_collect (struct bpf_object *obj,int flags) {Elf *elf = obj->efile.elf;
@@ -1102,24 +1154,21 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)if (gelf_getshdr (scn, &sh) != &sh) {pr_warning ("failed to get section(%d) header from %s\n" , idx, obj->path); - err = -LIBBPF_ERRNO__FORMAT ; - goto out; +return -LIBBPF_ERRNO__FORMAT ; } name =elf_strptr (elf, ep->e_shstrndx, sh.sh_name);if (!name) {pr_warning ("failed to get section(%d) name from %s\n" , idx, obj->path); - err = -LIBBPF_ERRNO__FORMAT ; - goto out; +return -LIBBPF_ERRNO__FORMAT ; } data =elf_getdata (scn,0 );if (!data) {pr_warning ("failed to get section(%d) data from %s(%s)\n" , idx, name, obj->path); - err = -LIBBPF_ERRNO__FORMAT ; - goto out; +return -LIBBPF_ERRNO__FORMAT ; } pr_debug("section(%d) %s, size %ld, link %d, flags %lx, type=%d\n", idx, name, (unsigned long)data->d_size,
@@ -1130,10 +1179,14 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags) err =bpf_object__init_license (obj, data->d_buf, data->d_size); +if (err) +return err; }else if (strcmp (name,"version" ) ==0 ) { err =bpf_object__init_kversion (obj, data->d_buf, data->d_size); +if (err) +return err; }else if (strcmp (name,"maps" ) ==0 ) { obj->efile.maps_shndx = idx; }else if (strcmp (name,BTF_ELF_SEC ) ==0 ) {
@@ -1144,11 +1197,10 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)if (obj->efile.symbols) {pr_warning ("bpf: multiple SYMTAB in %s\n" , obj->path); - err = -LIBBPF_ERRNO__FORMAT ; - }else { - obj->efile.symbols = data; - obj->efile.strtabidx = sh.sh_link; +return -LIBBPF_ERRNO__FORMAT ; } + obj->efile.symbols = data; + obj->efile.strtabidx = sh.sh_link; }else if (sh.sh_type ==SHT_PROGBITS && data->d_size >0 ) {if (sh.sh_flags &SHF_EXECINSTR ) {if (strcmp (name,".text" ) ==0 )
@@ -1162,6 +1214,7 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)pr_warning ("failed to alloc program %s (%s): %s" , name, obj->path, cp); +return err; } }else if (strcmp (name,".data" ) ==0 ) { obj->efile.data = data;
@@ -1173,8 +1226,8 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)pr_debug ("skip section(%d) %s\n" , idx, name); } }else if (sh.sh_type ==SHT_REL ) { +int nr_reloc = obj->efile.nr_reloc;void *reloc = obj->efile.reloc; -int nr_reloc = obj->efile.nr_reloc +1 ;int sec = sh.sh_info;/* points to other section */ /* Only do relo for section with exec instructions */
@@ -1184,79 +1237,39 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)continue ; } - reloc =reallocarray (reloc, nr_reloc, + reloc =reallocarray (reloc, nr_reloc +1 ,sizeof (*obj->efile.reloc));if (!reloc) {pr_warning ("realloc failed\n" ); - err = -ENOMEM ; - }else { -int n = nr_reloc -1 ; +return -ENOMEM ; + } - obj->efile.reloc = reloc; - obj->efile.nr_reloc = nr_reloc; + obj->efile.reloc = reloc; + obj->efile.nr_reloc++; - obj->efile.reloc[n].shdr = sh; - obj->efile.reloc[n].data = data; - } + obj->efile.reloc[nr_reloc].shdr = sh; + obj->efile.reloc[nr_reloc].data = data; }else if (sh.sh_type ==SHT_NOBITS &&strcmp (name,".bss" ) ==0 ) { obj->efile.bss = data; obj->efile.bss_shndx = idx; }else {pr_debug ("skip section(%d) %s\n" , idx, name); } -if (err) - goto out; }if (!obj->efile.strtabidx || obj->efile.strtabidx >= idx) {pr_warning ("Corrupted ELF file: index of strtab invalid\n" );return -LIBBPF_ERRNO__FORMAT ; } -if (btf_data) { - obj->btf =btf__new (btf_data->d_buf, btf_data->d_size); -if (IS_ERR (obj->btf)) { -pr_warning ("Error loading ELF section %s: %ld. Ignored and continue.\n" , -BTF_ELF_SEC ,PTR_ERR (obj->btf)); - obj->btf =NULL ; - }else { - err =btf__finalize_data (obj, obj->btf); -if (!err) { -bpf_object__sanitize_btf (obj); - err =btf__load (obj->btf); - } -if (err) { -pr_warning ("Error finalizing and loading %s into kernel: %d. Ignored and continue.\n" , -BTF_ELF_SEC , err); -btf__free (obj->btf); - obj->btf =NULL ; - err =0 ; - } - } - } -if (btf_ext_data) { -if (!obj->btf) { -pr_debug ("Ignore ELF section %s because its depending ELF section %s is not found.\n" , -BTF_EXT_ELF_SEC ,BTF_ELF_SEC ); - }else { - obj->btf_ext =btf_ext__new (btf_ext_data->d_buf, - btf_ext_data->d_size); -if (IS_ERR (obj->btf_ext)) { -pr_warning ("Error loading ELF section %s: %ld. Ignored and continue.\n" , -BTF_EXT_ELF_SEC , -PTR_ERR (obj->btf_ext)); - obj->btf_ext =NULL ; - }else { -bpf_object__sanitize_btf_ext (obj); - } - } - } + err =bpf_object__load_btf (obj, btf_data, btf_ext_data); +if (err) +return err;if (bpf_object__has_maps (obj)) { err =bpf_object__init_maps (obj, flags);if (err) - goto out; +return err; } err =bpf_object__init_prog_names (obj); -out:return err; }
Signature · 1 line
2.17.1
RFC PATCH 3/8 libbpf: refactor map initialization
In reply to Andrii NakryikoUser and global data maps initialization has gotten pretty complicated and unnecessarily convoluted. This patch splits out the logic for global data map and user-defined map initialization. It also removes the restriction of pre-calculating how many maps will be initialized, instead allowing to keep adding new maps as they are discovered, which will be used later for BTF-defined map definitions.
--- tools/lib/bpf/libbpf.c | 244 ++++++++++++++++++++++------------------- 1 file changed, 134 insertions(+), 110 deletions(-)
tools/lib/bpf/libbpf.c +134 -110
@@ -234,6 +234,7 @@ struct bpf_object {size_t nr_programs;struct bpf_map *maps;size_t nr_maps; +size_t maps_cap;struct bpf_secdata sections;bool loaded;
@@ -763,12 +764,38 @@ int bpf_object__variable_offset(const struct bpf_object *obj, const char *name,return -ENOENT ; } -static bool bpf_object__has_maps (const struct bpf_object *obj) +static struct bpf_map *bpf_object__add_map (struct bpf_object *obj) { -return obj->efile.maps_shndx >=0 || - obj->efile.data_shndx >=0 || - obj->efile.rodata_shndx >=0 || - obj->efile.bss_shndx >=0 ; +struct bpf_map *new_maps; +size_t new_cap; +int i; + +if (obj->nr_maps +1 <= obj->maps_cap) +return &obj->maps[obj->nr_maps++]; + + new_cap =max (4ul , obj->maps_cap *3 /2 ); + new_maps =realloc (obj->maps, new_cap *sizeof (*obj->maps)); +if (!new_maps) { +pr_warning ("alloc maps for object failed\n" ); +return ERR_PTR (-ENOMEM ); + } + + obj->maps_cap = new_cap; + obj->maps = new_maps; + +/* zero out new maps */ +memset (obj->maps + obj->nr_maps,0 , + (obj->maps_cap - obj->nr_maps) *sizeof (*obj->maps)); +/* +* fill all fd with -1 so won't close incorrect fd (fd=0 is stdin) +* when failure (zclose won't close negative fd)). +*/ +for (i = obj->nr_maps; i < obj->maps_cap; i++) { + obj->maps[i].fd =-1 ; + obj->maps[i].inner_map_fd =-1 ; + } + +return &obj->maps[obj->nr_maps++]; } static int
@@ -808,29 +835,68 @@ bpf_object__init_internal_map(struct bpf_object *obj, struct bpf_map *map,return 0 ; } -static int bpf_object__init_maps (struct bpf_object *obj,int flags) +static int bpf_object__init_global_data_maps (struct bpf_object *obj) +{ +struct bpf_map *map; +int err; + +if (!obj->caps.global_data) +return 0 ; +/* +* Populate obj->maps with libbpf internal maps. +*/ +if (obj->efile.data_shndx >=0 ) { + map =bpf_object__add_map (obj); +if (IS_ERR (map)) +return PTR_ERR (map); + err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_DATA , + obj->efile.data, + &obj->sections.data); +if (err) +return err; + } +if (obj->efile.rodata_shndx >=0 ) { + map =bpf_object__add_map (obj); +if (IS_ERR (map)) +return PTR_ERR (map); + err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_RODATA , + obj->efile.rodata, + &obj->sections.rodata); +if (err) +return err; + } +if (obj->efile.bss_shndx >=0 ) { + map =bpf_object__add_map (obj); +if (IS_ERR (map)) +return PTR_ERR (map); + err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_BSS , + obj->efile.bss,NULL ); +if (err) +return err; + } +return 0 ; +} + +static int bpf_object__init_user_maps (struct bpf_object *obj,bool strict) { -int i, map_idx, map_def_sz =0 , nr_syms, nr_maps =0 , nr_maps_glob =0 ; -bool strict = !(flags &MAPS_RELAX_COMPAT );Elf_Data *symbols = obj->efile.symbols; +int i, map_def_sz =0 , nr_maps =0 , nr_syms;Elf_Data *data =NULL ; -int ret =0 ; +Elf_Scn *scn; + +if (obj->efile.maps_shndx <0 ) +return 0 ;if (!symbols)return -EINVAL ; - nr_syms = symbols->d_size /sizeof (GElf_Sym); - -if (obj->efile.maps_shndx >=0 ) { -Elf_Scn *scn =elf_getscn (obj->efile.elf, - obj->efile.maps_shndx); -if (scn) - data =elf_getdata (scn,NULL ); -if (!scn || !data) { -pr_warning ("failed to get Elf_Data from map section %d\n" , - obj->efile.maps_shndx); -return -EINVAL ; - } + scn =elf_getscn (obj->efile.elf, obj->efile.maps_shndx); +if (scn) + data =elf_getdata (scn,NULL ); +if (!scn || !data) { +pr_warning ("failed to get Elf_Data from map section %d\n" , + obj->efile.maps_shndx); +return -EINVAL ; }/*
@@ -840,16 +906,8 @@ static int bpf_object__init_maps(struct bpf_object *obj, int flags)* * TODO: Detect array of map and report error. */ -if (obj->caps.global_data) { -if (obj->efile.data_shndx >=0 ) - nr_maps_glob++; -if (obj->efile.rodata_shndx >=0 ) - nr_maps_glob++; -if (obj->efile.bss_shndx >=0 ) - nr_maps_glob++; - } - -for (i =0 ; data && i < nr_syms; i++) { + nr_syms = symbols->d_size /sizeof (GElf_Sym); +for (i =0 ; i < nr_syms; i++) {GElf_Sym sym;if (!gelf_getsym (symbols, i, &sym))
@@ -858,79 +916,56 @@ static int bpf_object__init_maps(struct bpf_object *obj, int flags)continue ; nr_maps++; } - -if (!nr_maps && !nr_maps_glob) -return 0 ; -/* Assume equally sized map definitions */ -if (data) { -pr_debug ("maps in %s: %d maps in %zd bytes\n" , obj->path, - nr_maps, data->d_size); - - map_def_sz = data->d_size / nr_maps; -if (!data->d_size || (data->d_size % nr_maps) !=0 ) { -pr_warning ("unable to determine map definition size " -"section %s, %d maps in %zd bytes\n" , - obj->path, nr_maps, data->d_size); -return -EINVAL ; - } - } - - nr_maps += nr_maps_glob; - obj->maps =calloc (nr_maps,sizeof (obj->maps[0 ])); -if (!obj->maps) { -pr_warning ("alloc maps for object failed\n" ); -return -ENOMEM ; - } - obj->nr_maps = nr_maps; - -for (i =0 ; i < nr_maps; i++) { -/* -* fill all fd with -1 so won't close incorrect -* fd (fd=0 is stdin) when failure (zclose won't close -* negative fd)). -*/ - obj->maps[i].fd =-1 ; - obj->maps[i].inner_map_fd =-1 ; +pr_debug ("maps in %s: %d maps in %zd bytes\n" , + obj->path, nr_maps, data->d_size); + + map_def_sz = data->d_size / nr_maps; +if (!data->d_size || (data->d_size % nr_maps) !=0 ) { +pr_warning ("unable to determine map definition size " +"section %s, %d maps in %zd bytes\n" , + obj->path, nr_maps, data->d_size); +return -EINVAL ; } -/* -* Fill obj->maps using data in "maps" section. -*/ -for (i =0 , map_idx =0 ; data && i < nr_syms; i++) { +/* Fill obj->maps using data in "maps" section. */ +for (i =0 ; i < nr_syms; i++) {GElf_Sym sym;const char *map_name;struct bpf_map_def *def; +struct bpf_map *map;if (!gelf_getsym (symbols, i, &sym))continue ;if (sym.st_shndx != obj->efile.maps_shndx)continue ; - map_name =elf_strptr (obj->efile.elf, - obj->efile.strtabidx, + map =bpf_object__add_map (obj); +if (IS_ERR (map)) +return PTR_ERR (map); + + map_name =elf_strptr (obj->efile.elf, obj->efile.strtabidx, sym.st_name);if (!map_name) {pr_warning ("failed to get map #%d name sym string for obj %s\n" , - map_idx, obj->path); + i, obj->path);return -LIBBPF_ERRNO__FORMAT ; } - obj->maps[map_idx].libbpf_type =LIBBPF_MAP_UNSPEC ; - obj->maps[map_idx].offset = sym.st_value; + map->libbpf_type =LIBBPF_MAP_UNSPEC ; + map->offset = sym.st_value;if (sym.st_value + map_def_sz > data->d_size) {pr_warning ("corrupted maps section in %s: last map \"%s\" too small\n" , obj->path, map_name);return -EINVAL ; } - obj->maps[map_idx].name =strdup (map_name); -if (!obj->maps[map_idx].name) { + map->name =strdup (map_name); +if (!map->name) {pr_warning ("failed to alloc map name\n" );return -ENOMEM ; } -pr_debug ("map %d is \"%s\"\n" , map_idx, - obj->maps[map_idx].name); +pr_debug ("map %d is \"%s\"\n" , i, map->name); def = (struct bpf_map_def *)(data->d_buf + sym.st_value);/* * If the definition of the map in the object file fits in
@@ -939,7 +974,7 @@ static int bpf_object__init_maps(struct bpf_object *obj, int flags)* calloc above. */ if (map_def_sz <=sizeof (struct bpf_map_def )) { -memcpy (&obj->maps[map_idx].def, def, map_def_sz); +memcpy (&map->def, def, map_def_sz); }else {/* * Here the map structure being read is bigger than what
@@ -959,37 +994,30 @@ static int bpf_object__init_maps(struct bpf_object *obj, int flags)return -EINVAL ; } } -memcpy (&obj->maps[map_idx].def, def, -sizeof (struct bpf_map_def )); +memcpy (&map->def, def,sizeof (struct bpf_map_def )); } - map_idx++; } +return 0 ; +} -if (!obj->caps.global_data) - goto finalize; +static int bpf_object__init_maps (struct bpf_object *obj,int flags) +{ +bool strict = !(flags &MAPS_RELAX_COMPAT ); +int err; -/* -* Populate rest of obj->maps with libbpf internal maps. -*/ -if (obj->efile.data_shndx >=0 ) - ret =bpf_object__init_internal_map (obj, &obj->maps[map_idx++], -LIBBPF_MAP_DATA , - obj->efile.data, - &obj->sections.data); -if (!ret && obj->efile.rodata_shndx >=0 ) - ret =bpf_object__init_internal_map (obj, &obj->maps[map_idx++], -LIBBPF_MAP_RODATA , - obj->efile.rodata, - &obj->sections.rodata); -if (!ret && obj->efile.bss_shndx >=0 ) - ret =bpf_object__init_internal_map (obj, &obj->maps[map_idx++], -LIBBPF_MAP_BSS , - obj->efile.bss,NULL ); -finalize: -if (!ret) + err =bpf_object__init_user_maps (obj, strict); +if (err) +return err; + + err =bpf_object__init_global_data_maps (obj); +if (err) +return err; + +if (obj->nr_maps) {qsort (obj->maps, obj->nr_maps,sizeof (obj->maps[0 ]), compare_bpf_map); -return ret; + } +return 0 ; }static bool section_have_execinstr (struct bpf_object *obj,int idx)
@@ -1262,14 +1290,10 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)return -LIBBPF_ERRNO__FORMAT ; } err =bpf_object__load_btf (obj, btf_data, btf_ext_data); -if (err) -return err; -if (bpf_object__has_maps (obj)) { +if (!err) err =bpf_object__init_maps (obj, flags); -if (err) -return err; - } - err =bpf_object__init_prog_names (obj); +if (!err) + err =bpf_object__init_prog_names (obj);return err; }
Signature · 1 line
2.17.1
RFC PATCH 4/8 libbpf: identify maps by section index in addition to offset
In reply to Andrii NakryikoTo support maps to be defined in multiple sections, it's important to identify map not just by offset within its section, but section index as well. This patch adds tracking of section index.
For global data, we record section index of corresponding .data/.bss/.rodata ELF section for uniformity, and thus don't need a special value of offset for those maps.
--- tools/lib/bpf/libbpf.c | 42 ++++++++++++++++++++++++++---------------- 1 file changed, 26 insertions(+), 16 deletions(-)
tools/lib/bpf/libbpf.c +26 -16
@@ -207,7 +207,8 @@ static const char * const libbpf_type_to_btf_name[] = {struct bpf_map {int fd;char *name; -size_t offset; +int sec_idx; +size_t sec_offset;int map_ifindex;int inner_map_fd;struct bpf_map_def def;
@@ -647,7 +648,9 @@ static int compare_bpf_map(const void *_a, const void *_b)const struct bpf_map *a = _a;const struct bpf_map *b = _b; -return a->offset - b->offset; +if (a->sec_idx != b->sec_idx) +return a->sec_idx - b->sec_idx; +return a->sec_offset - b->sec_offset; }static bool bpf_map_type__is_map_in_map (enum bpf_map_type type)
@@ -800,14 +803,15 @@ static struct bpf_map *bpf_object__add_map(struct bpf_object *obj)static int bpf_object__init_internal_map (struct bpf_object *obj,struct bpf_map *map, -enum libbpf_map_type type,Elf_Data *data, -void **data_buff) +enum libbpf_map_type type,int sec_idx, +Elf_Data *data,void **data_buff) {struct bpf_map_def *def = &map->def;char map_name[BPF_OBJ_NAME_LEN ]; map->libbpf_type = type; - map->offset = ~(typeof(map->offset))0; + map->sec_idx = sec_idx; + map->sec_offset =0 ;snprintf (map_name,sizeof (map_name),"%.8s%.7s" , obj->name, libbpf_type_to_btf_name[type]); map->name =strdup (map_name);
@@ -815,6 +819,8 @@ bpf_object__init_internal_map(struct bpf_object *obj, struct bpf_map *map,pr_warning ("failed to alloc map name\n" );return -ENOMEM ; } +pr_debug ("map '%s' (global data): at sec_idx %d, offset %zu.\n" , + map_name, map->sec_idx, map->sec_offset); def->type =BPF_MAP_TYPE_ARRAY ; def->key_size =sizeof (int );
@@ -850,6 +856,7 @@ static int bpf_object__init_global_data_maps(struct bpf_object *obj)if (IS_ERR (map))return PTR_ERR (map); err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_DATA , + obj->efile.data_shndx, obj->efile.data, &obj->sections.data);if (err)
@@ -860,6 +867,7 @@ static int bpf_object__init_global_data_maps(struct bpf_object *obj)if (IS_ERR (map))return PTR_ERR (map); err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_RODATA , + obj->efile.rodata_shndx, obj->efile.rodata, &obj->sections.rodata);if (err)
@@ -870,6 +878,7 @@ static int bpf_object__init_global_data_maps(struct bpf_object *obj)if (IS_ERR (map))return PTR_ERR (map); err =bpf_object__init_internal_map (obj, map,LIBBPF_MAP_BSS , + obj->efile.bss_shndx, obj->efile.bss,NULL );if (err)return err;
@@ -953,7 +962,10 @@ static int bpf_object__init_user_maps(struct bpf_object *obj, bool strict) } map->libbpf_type =LIBBPF_MAP_UNSPEC ; - map->offset = sym.st_value; + map->sec_idx = sym.st_shndx; + map->sec_offset = sym.st_value; +pr_debug ("map '%s' (legacy): at sec_idx %d, offset %zu.\n" , + map_name, map->sec_idx, map->sec_offset);if (sym.st_value + map_def_sz > data->d_size) {pr_warning ("corrupted maps section in %s: last map \"%s\" too small\n" , obj->path, map_name);
@@ -1453,9 +1465,13 @@ bpf_program__collect_reloc(struct bpf_program *prog, GElf_Shdr *shdr,if (maps[map_idx].libbpf_type != type)continue ;if (type !=LIBBPF_MAP_UNSPEC || - maps[map_idx].offset == sym.st_value) { -pr_debug ("relocation: find map %zd (%s) for insn %u\n" , - map_idx, maps[map_idx].name, insn_idx); + (maps[map_idx].sec_idx == sym.st_shndx && + maps[map_idx].sec_offset == sym.st_value)) { +pr_debug ("relocation: found map %zd (%s, sec_idx %d, offset %zu) for insn %u\n" , + map_idx, maps[map_idx].name, + maps[map_idx].sec_idx, + maps[map_idx].sec_offset, + insn_idx);break ; } }
@@ -3472,13 +3488,7 @@ bpf_object__find_map_fd_by_name(struct bpf_object *obj, const char *name)struct bpf_map *bpf_object__find_map_by_offset (struct bpf_object *obj,size_t offset) { -int i; - -for (i =0 ; i < obj->nr_maps; i++) { -if (obj->maps[i].offset == offset) -return &obj->maps[i]; - } -return ERR_PTR (-ENOENT ); +return ERR_PTR (-ENOTSUP ); }long libbpf_get_error (const void *ptr)
Signature · 1 line
2.17.1
RFC PATCH 5/8 libbpf: split initialization and loading of BTF
In reply to Andrii NakryikoLibbpf does sanitization of BTF before loading it into kernel, if kernel doesn't support some of newer BTF features. This removes some of the important information from BTF (e.g., DATASEC and VAR description), which will be used for map construction. This patch splits BTF processing into initialization step, in which BTF is initialized from ELF and all the original data is still preserved; and sanitization/loading step, which ensures that BTF is safe to load into kernel. This allows to use full BTF information to construct maps, while still loading valid BTF into older kernels.
--- tools/lib/bpf/libbpf.c | 34 ++++++++++++++++++++++++---------- 1 file changed, 24 insertions(+), 10 deletions(-)
tools/lib/bpf/libbpf.c +24 -10
@@ -1118,7 +1118,7 @@ static void bpf_object__sanitize_btf_ext(struct bpf_object *obj) } } -static int bpf_object__load_btf (struct bpf_object *obj, +static int bpf_object__init_btf (struct bpf_object *obj,Elf_Data *btf_data,Elf_Data *btf_ext_data) {
@@ -1137,13 +1137,6 @@ static int bpf_object__load_btf(struct bpf_object *obj, BTF_ELF_SEC, err); goto out; } -bpf_object__sanitize_btf (obj); - err =btf__load (obj->btf); -if (err) { -pr_warning ("Error loading %s into kernel: %d.\n" , -BTF_ELF_SEC , err); - goto out; - } }if (btf_ext_data) {if (!obj->btf) {
@@ -1159,7 +1152,6 @@ static int bpf_object__load_btf(struct bpf_object *obj, obj->btf_ext =NULL ; goto out; } -bpf_object__sanitize_btf_ext (obj); } out:if (err ||IS_ERR (obj->btf)) {
@@ -1170,6 +1162,26 @@ static int bpf_object__load_btf(struct bpf_object *obj,return 0 ; } +static int bpf_object__sanitize_and_load_btf (struct bpf_object *obj) +{ +int err =0 ; + +if (!obj->btf) +return 0 ; + +bpf_object__sanitize_btf (obj); +bpf_object__sanitize_btf_ext (obj); + + err =btf__load (obj->btf); +if (err) { +pr_warning ("Error loading %s into kernel: %d.\n" , +BTF_ELF_SEC , err); +btf__free (obj->btf); + obj->btf =NULL ; + } +return 0 ; +} +static int bpf_object__elf_collect (struct bpf_object *obj,int flags) {Elf *elf = obj->efile.elf;
@@ -1301,9 +1313,11 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)pr_warning ("Corrupted ELF file: index of strtab invalid\n" );return -LIBBPF_ERRNO__FORMAT ; } - err =bpf_object__load_btf (obj, btf_data, btf_ext_data); + err =bpf_object__init_btf (obj, btf_data, btf_ext_data);if (!err) err =bpf_object__init_maps (obj, flags); +if (!err) + err =bpf_object__sanitize_and_load_btf (obj);if (!err) err =bpf_object__init_prog_names (obj);return err;
Signature · 1 line
2.17.1
RFC PATCH 6/8 libbpf: allow specifying map definitions using BTF
In reply to Andrii NakryikoThis patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for BPF_ANNOTATE_KV_PAIR hack and ensures key/value sizes are always in sync with the key/value type.
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions in maps sections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
- max_entries attribute is optional; if max_entries is not specified or initialized, it has to be provided in runtime through libbpf API before loading bpf_object;
- map_flags is optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Use key_size and value_size fields to do that (see example below).
Here's an example of simple ARRAY map defintion:
struct my_value { int x, y, z; };
struct {
int type;
int max_entries;
int *key;
struct my_value *value;
} btf_map SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map 'btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is struct my_value of size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through struct bpf_map_def.
Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct {
__u32 type;
__u32 max_entries;
__u32 map_flags;
__u32 key_size;
__u32 value_size;
} stackmap SEC(".maps") = { .type = BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags = BPF_F_STACK_BUILD_ID,
.key_size = sizeof(__u32),
.value_size = PERF_MAX_STACK_DEPTH * sizeof(struct bpf_stack_build_id),
};
This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)
tools/lib/bpf/btf.h +1 -0
@@ -17,6 +17,7 @@ extern "C" {#define BTF_ELF_SEC ".BTF"#define BTF_EXT_ELF_SEC ".BTF.ext" +#define MAPS_ELF_SEC ".maps"struct btf ;struct btf_ext ;
tools/lib/bpf/libbpf.c +324 -9
429 lines not on this page · raw message
Signature · 1 line
2.17.1
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.
My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I don't know how others feel about it, but I'd be much more comfortable with a simpler TLV-like approach. Have a new section where the format is |4-byte size|struct bpf_map_def_extendable|. That would essentially allow us to extend it the way we do with a syscall args.
Also, (un)related: we don't currently use BTF internally, so if you convert all tests, we'd be unable to run them :-(
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Quoted 531 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, .max_entries = 16, };This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
Signed-off-by Andrii Nakryiko <[email protected]>--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)tools/lib/bpf/btf.h +1
-0@@ -17,6 +17,7 @@ extern "C" {#define BTF_ELF_SEC ".BTF"#define BTF_EXT_ELF_SEC ".BTF.ext" +#define MAPS_ELF_SEC ".maps"struct btf ;struct btf_ext ;tools/lib/bpf/libbpf.c +324
-9@@ -262,6 +262,7 @@ struct bpf_object { } *reloc;int nr_reloc;int maps_shndx; +int btf_maps_shndx;int text_shndx;int data_shndx;int rodata_shndx;@@ -514,6 +515,7 @@ static struct bpf_object *bpf_object__new(const char *path, obj->efile.obj_buf = obj_buf; obj->efile.obj_buf_sz = obj_buf_sz; obj->efile.maps_shndx =-1 ; + obj->efile.btf_maps_shndx =-1 ; obj->efile.data_shndx =-1 ; obj->efile.rodata_shndx =-1 ; obj->efile.bss_shndx =-1 ;@@ -1012,6 +1014,292 @@ static int bpf_object__init_user_maps(struct bpf_object *obj, bool strict)return 0 ; } +static const struct btf_type *skip_mods_and_typedefs (const struct btf *btf, +__u32 id) +{ +const struct btf_type *t =btf__type_by_id (btf, id); + +while (true) { +switch (BTF_INFO_KIND (t->info)) { +case BTF_KIND_VOLATILE : +case BTF_KIND_CONST : +case BTF_KIND_RESTRICT : +case BTF_KIND_TYPEDEF : + t =btf__type_by_id (btf, t->type); +break ; +default : +return t; + } + } +} + +static bool get_map_attr_int (const char *map_name, +const struct btf *btf, +const struct btf_type *def, +const struct btf_member *m, +const void *data,__u32 *res) { +const struct btf_type *t =skip_mods_and_typedefs (btf, m->type); +const char *name =btf__name_by_offset (btf, m->name_off); +__u32 int_info = *(const __u32 *)(const void *)(t +1 ); + +if (BTF_INFO_KIND (t->info) !=BTF_KIND_INT ) { +pr_warning ("map '%s': attr '%s': expected INT, got %u.\n" , + map_name, name,BTF_INFO_KIND (t->info)); +return false; + } +if (t->size !=4 ||BTF_INT_BITS (int_info) !=32 || +BTF_INT_OFFSET (int_info)) { +pr_warning ("map '%s': attr '%s': expected 32-bit non-bitfield integer, " +"got %u-byte (%d-bit) one with bit offset %d.\n" , + map_name, name, t->size,BTF_INT_BITS (int_info), +BTF_INT_OFFSET (int_info)); +return false; + } +if (BTF_INFO_KFLAG (def->info) &&BTF_MEMBER_BITFIELD_SIZE (m->offset)) { +pr_warning ("map '%s': attr '%s': bitfield is not supported.\n" , + map_name, name); +return false; + } +if (m->offset %32 ) { +pr_warning ("map '%s': attr '%s': unaligned fields are not supported.\n" , + map_name, name); +return false; + } + + *res = *(const __u32 *)(data + m->offset /8 ); +return true; +} + +static int bpf_object__init_user_btf_map (struct bpf_object *obj, +const struct btf_type *sec, +int var_idx,int sec_idx, +const Elf_Data *data) +{ +const struct btf_type *var, *def, *t; +const struct btf_var_secinfo *vi; +const struct btf_var *var_extra; +const struct btf_member *m; +const void *def_data; +const char *map_name; +struct bpf_map *map; +int vlen, i; + + vi = (const struct btf_var_secinfo *)(const void *)(sec +1 ) + var_idx; + var =btf__type_by_id (obj->btf, vi->type); + var_extra = (const void *)(var +1 ); + map_name =btf__name_by_offset (obj->btf, var->name_off); + vlen =BTF_INFO_VLEN (var->info); + +if (map_name ==NULL || map_name[0 ] =='\0' ) { +pr_warning ("map #%d: empty name.\n" , var_idx); +return -EINVAL ; + } +if ((__u64 )vi->offset + vi->size > data->d_size) { +pr_warning ("map '%s' BTF data is corrupted.\n" , map_name); +return -EINVAL ; + } +if (BTF_INFO_KIND (var->info) !=BTF_KIND_VAR ) { +pr_warning ("map '%s': unexpected var kind %u.\n" , + map_name,BTF_INFO_KIND (var->info)); +return -EINVAL ; + } +if (var_extra->linkage !=BTF_VAR_GLOBAL_ALLOCATED && + var_extra->linkage !=BTF_VAR_STATIC ) { +pr_warning ("map '%s': unsupported var linkage %u.\n" , + map_name, var_extra->linkage); +return -EOPNOTSUPP ; + } + + def =skip_mods_and_typedefs (obj->btf, var->type); +if (BTF_INFO_KIND (def->info) !=BTF_KIND_STRUCT ) { +pr_warning ("map '%s': unexpected def kind %u.\n" , + map_name,BTF_INFO_KIND (var->info)); +return -EINVAL ; + } +if (def->size > vi->size) { +pr_warning ("map '%s': invalid def size.\n" , map_name); +return -EINVAL ; + } + + map =bpf_object__add_map (obj); +if (IS_ERR (map)) +return PTR_ERR (map); + map->name =strdup (map_name); +if (!map->name) { +pr_warning ("map '%s': failed to alloc map name.\n" , map_name); +return -ENOMEM ; + } + map->libbpf_type =LIBBPF_MAP_UNSPEC ; + map->def.type =BPF_MAP_TYPE_UNSPEC ; + map->sec_idx = sec_idx; + map->sec_offset = vi->offset; +pr_debug ("map '%s': at sec_idx %d, offset %zu.\n" , + map_name, map->sec_idx, map->sec_offset); + + def_data = data->d_buf + vi->offset; + vlen =BTF_INFO_VLEN (def->info); + m = (const void *)(def +1 ); +for (i =0 ; i < vlen; i++, m++) { +const char *name =btf__name_by_offset (obj->btf, m->name_off); + +if (strcmp (name,"type" ) ==0 ) { +if (!get_map_attr_int (map_name, obj->btf, def, m, + def_data, &map->def.type)) +return -EINVAL ; +pr_debug ("map '%s': found type = %u.\n" , + map_name, map->def.type); + }else if (strcmp (name,"max_entries" ) ==0 ) { +if (!get_map_attr_int (map_name, obj->btf, def, m, + def_data, &map->def.max_entries)) +return -EINVAL ; +pr_debug ("map '%s': found max_entries = %u.\n" , + map_name, map->def.max_entries); + }else if (strcmp (name,"map_flags" ) ==0 ) { +if (!get_map_attr_int (map_name, obj->btf, def, m, + def_data, &map->def.map_flags)) +return -EINVAL ; +pr_debug ("map '%s': found map_flags = %u.\n" , + map_name, map->def.map_flags); + }else if (strcmp (name,"key_size" ) ==0 ) { +__u32 sz; + +if (!get_map_attr_int (map_name, obj->btf, def, m, + def_data, &sz)) +return -EINVAL ; +pr_debug ("map '%s': found key_size = %u.\n" , + map_name, sz); +if (map->def.key_size && map->def.key_size != sz) { +pr_warning ("map '%s': conflictling key size %u != %u.\n" , + map_name, map->def.key_size, sz); +return -EINVAL ; + } + map->def.key_size = sz; + }else if (strcmp (name,"key" ) ==0 ) { +__s64 sz; + + t =btf__type_by_id (obj->btf, m->type); +if (BTF_INFO_KIND (t->info) !=BTF_KIND_PTR ) { +pr_warning ("map '%s': key spec is not PTR: %u.\n" , + map_name,BTF_INFO_KIND (t->info)); +return -EINVAL ; + } + sz =btf__resolve_size (obj->btf, t->type); +if (sz <0 ) { +pr_warning ("map '%s': can't determine key size for type [%u]: %lld.\n" , + map_name, t->type, sz); +return sz; + } +pr_debug ("map '%s': found key [%u], sz = %lld.\n" , + map_name, t->type, sz); +if (map->def.key_size && map->def.key_size != sz) { +pr_warning ("map '%s': conflictling key size %u != %lld.\n" , + map_name, map->def.key_size, sz); +return -EINVAL ; + } + map->def.key_size = sz; + map->btf_key_type_id = t->type; + }else if (strcmp (name,"value_size" ) ==0 ) { +__u32 sz; + +if (!get_map_attr_int (map_name, obj->btf, def, m, + def_data, &sz)) +return -EINVAL ; +pr_debug ("map '%s': found value_size = %u.\n" , + map_name, sz); +if (map->def.value_size && map->def.value_size != sz) { +pr_warning ("map '%s': conflictling value size %u != %u.\n" , + map_name, map->def.value_size, sz); +return -EINVAL ; + } + map->def.value_size = sz; + }else if (strcmp (name,"value" ) ==0 ) { +__s64 sz; + + t =btf__type_by_id (obj->btf, m->type); +if (BTF_INFO_KIND (t->info) !=BTF_KIND_PTR ) { +pr_warning ("map '%s': value spec is not PTR: %u.\n" , + map_name,BTF_INFO_KIND (t->info)); +return -EINVAL ; + } + sz =btf__resolve_size (obj->btf, t->type); +if (sz <0 ) { +pr_warning ("map '%s': can't determine value size for type [%u]: %lld.\n" , + map_name, t->type, sz); +return sz; + } +pr_debug ("map '%s': found value [%u], sz = %lld.\n" , + map_name, t->type, sz); +if (map->def.value_size && map->def.value_size != sz) { +pr_warning ("map '%s': conflictling value size %u != %lld.\n" , + map_name, map->def.value_size, sz); +return -EINVAL ; + } + map->def.value_size = sz; + map->btf_value_type_id = t->type; + }else { +pr_debug ("map '%s': ignoring unknown def field '%s'.\n" , + map_name, name); + } + } + +if (map->def.type ==BPF_MAP_TYPE_UNSPEC ) { +pr_warning ("map '%s': map type isn't specified.\n" , map_name); +return -EINVAL ; + } + +return 0 ; +} + +static int bpf_object__init_user_btf_maps (struct bpf_object *obj) +{ +const struct btf_type *sec =NULL ; +int nr_types, i, vlen, err; +const struct btf_type *t; +const char *name; +Elf_Data *data; +Elf_Scn *scn; + +if (obj->efile.btf_maps_shndx <0 ) +return 0 ; + + scn =elf_getscn (obj->efile.elf, obj->efile.btf_maps_shndx); +if (scn) + data =elf_getdata (scn,NULL ); +if (!scn || !data) { +pr_warning ("failed to get Elf_Data from map section %d (%s)\n" , + obj->efile.maps_shndx,MAPS_ELF_SEC ); +return -EINVAL ; + } + + nr_types =btf__get_nr_types (obj->btf); +for (i =1 ; i <= nr_types; i++) { + t =btf__type_by_id (obj->btf, i); +if (BTF_INFO_KIND (t->info) !=BTF_KIND_DATASEC ) +continue ; + name =btf__name_by_offset (obj->btf, t->name_off); +if (strcmp (name,MAPS_ELF_SEC ) ==0 ) { + sec = t; +break ; + } + } + +if (!sec) { +pr_warning ("DATASEC '%s' not found.\n" ,MAPS_ELF_SEC ); +return -ENOENT ; + } + + vlen =BTF_INFO_VLEN (sec->info); +for (i =0 ; i < vlen; i++) { + err =bpf_object__init_user_btf_map (obj, sec, i, + obj->efile.btf_maps_shndx, + data); +if (err) +return err; + } + +return 0 ; +} +static int bpf_object__init_maps (struct bpf_object *obj,int flags) {bool strict = !(flags &MAPS_RELAX_COMPAT );@@ -1021,6 +1309,10 @@ static int bpf_object__init_maps(struct bpf_object *obj, int flags)if (err)return err; + err =bpf_object__init_user_btf_maps (obj); +if (err) +return err; + err =bpf_object__init_global_data_maps (obj);if (err)return err;@@ -1118,10 +1410,16 @@ static void bpf_object__sanitize_btf_ext(struct bpf_object *obj) } } +static bool bpf_object__is_btf_mandatory (const struct bpf_object *obj) +{ +return obj->efile.btf_maps_shndx >=0 ; +} +static int bpf_object__init_btf (struct bpf_object *obj,Elf_Data *btf_data,Elf_Data *btf_ext_data) { +bool btf_required =bpf_object__is_btf_mandatory (obj);int err =0 ;if (btf_data) {@@ -1155,10 +1453,18 @@ static int bpf_object__init_btf(struct bpf_object *obj, } out:if (err ||IS_ERR (obj->btf)) { +if (btf_required) + err = err ? :PTR_ERR (obj->btf); +else + err =0 ;if (!IS_ERR_OR_NULL (obj->btf))btf__free (obj->btf); obj->btf =NULL ; } +if (btf_required && !obj->btf) { +pr_warning ("BTF is required, but is missing or corrupted.\n" ); +return err ==0 ? -ENOENT : err; + }return 0 ; }@@ -1178,6 +1484,8 @@ static int bpf_object__sanitize_and_load_btf(struct bpf_object *obj) BTF_ELF_SEC, err);btf__free (obj->btf); obj->btf =NULL ; +if (bpf_object__is_btf_mandatory (obj)) +return err; }return 0 ; }@@ -1241,6 +1549,8 @@ static int bpf_object__elf_collect(struct bpf_object *obj, int flags)return err; }else if (strcmp (name,"maps" ) ==0 ) { obj->efile.maps_shndx = idx; + }else if (strcmp (name,MAPS_ELF_SEC ) ==0 ) { + obj->efile.btf_maps_shndx = idx; }else if (strcmp (name,BTF_ELF_SEC ) ==0 ) { btf_data = data; }else if (strcmp (name,BTF_EXT_ELF_SEC ) ==0 ) {@@ -1360,7 +1670,8 @@ static bool bpf_object__shndx_is_data(const struct bpf_object *obj,static bool bpf_object__shndx_is_maps (const struct bpf_object *obj,int shndx) { -return shndx == obj->efile.maps_shndx; +return shndx == obj->efile.maps_shndx || + shndx == obj->efile.btf_maps_shndx; } static bool bpf_object__relo_in_known_section(const struct bpf_object *obj,@@ -1404,14 +1715,14 @@ bpf_program__collect_reloc(struct bpf_program *prog, GElf_Shdr *shdr, prog->nr_reloc = nrels;for (i =0 ; i < nrels; i++) { -GElf_Sym sym; -GElf_Rel rel; -unsigned int insn_idx; -unsigned int shdr_idx;struct bpf_insn *insns = prog->insns;enum libbpf_map_type type; +unsigned int insn_idx; +unsigned int shdr_idx;const char *name;size_t map_idx; +GElf_Sym sym; +GElf_Rel rel;if (!gelf_getrel (data, i, &rel)) {pr_warning ("relocation: failed to get %d reloc\n" , i);@@ -1505,14 +1816,18 @@ bpf_program__collect_reloc(struct bpf_program *prog, GElf_Shdr *shdr,return 0 ; } -static int bpf_map_find_btf_info (struct bpf_map *map,const struct btf *btf) +static int bpf_map_find_btf_info (struct bpf_object *obj,struct bpf_map *map) {struct bpf_map_def *def = &map->def;__u32 key_type_id =0 , value_type_id =0 ;int ret; +/* if it's BTF-defined map, we don't need to search for type IDs */ +if (map->sec_idx == obj->efile.btf_maps_shndx) +return 0 ; +if (!bpf_map__is_internal (map)) { - ret =btf__get_map_kv_tids (btf, map->name, def->key_size, + ret =btf__get_map_kv_tids (obj->btf, map->name, def->key_size, def->value_size, &key_type_id, &value_type_id); }else {@@ -1520,7 +1835,7 @@ static int bpf_map_find_btf_info(struct bpf_map *map, const struct btf *btf)* LLVM annotates global data differently in BTF, that is, * only as '.data', '.bss' or '.rodata'. */ - ret =btf__find_by_name (btf, + ret =btf__find_by_name (obj->btf, libbpf_type_to_btf_name[map->libbpf_type]); }if (ret <0 )@@ -1810,7 +2125,7 @@ bpf_object__create_maps(struct bpf_object *obj) map->inner_map_fd >= 0) create_attr.inner_map_fd = map->inner_map_fd; -if (obj->btf && !bpf_map_find_btf_info (map, obj->btf)) { +if (obj->btf && !bpf_map_find_btf_info (obj, map)) { create_attr.btf_fd =btf__fd (obj->btf); create_attr.btf_key_type_id = map->btf_key_type_id; create_attr.btf_value_type_id = map->btf_value_type_id;Signature · 1 line
2.17.1
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 9 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I don't think it's really worse than current bpf_map_def approach. In typical scenario, there are only two fields you need to remember: type and max_entries (notice, they are called exactly the same as in bpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).
I can relate a bit to that with bpf_map_def you can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.
One big advantage of this scheme, though, is that you get that type association automagically without using BPF_ANNOTATE_KV_PAIR hack, with no chance of having a mismatch, etc. This is less duplication (no need to do sizeof(struct my_struct) and struct my_struct as an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.
Quoted 5 lines
I don't know how others feel about it, but I'd be much more comfortable with a simpler TLV-like approach. Have a new section where the format is |4-byte size|struct bpf_map_def_extendable|. That would essentially allow us to extend it the way we do with a syscall args.
It would help with extensibility, sure, though even current bpf_map_def approach sort of can be extended already. But it won't solve the problem of having BTF types captured for key/value (see above). Also, you'd need another macro to lay everything out properly.
Quoted 3 lines
Also, (un)related: we don't currently use BTF internally, so if you convert all tests, we'd be unable to run them :-(
Not exactly sure what you mean "you'd be unable to run them". Do you mean that you use old Clang that doesn't emit BTF? If that's what you are saying, a lot of tests already rely on latest Clang, so those tests already don't work for you, probably. I'll leave it up to Daniel and Alexei to decide if we want to convert selftests right now or not. I did it mostly to prove that we can handle all existing cases (and found few gotchas and bugs along the way, both in my implementation and in kernel - fixes coming soon).
Quoted 9 lines
Quoted 5 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
Quoted 70 lines
Quoted 70 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
Signed-off-by Andrii Nakryiko <[email protected]>--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 9 lines · Andrii Nakryiko
Quoted 8 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I have mixed feelings, too. Especially the key and value fields are very non-idiomatic for C :( They never hold any value or data, while the other fields do. That feels so awkward. I'm no compiler expert, but even something like:
struct map_def {
void *key_type_ref;
} mamap = {
.key_type_ref = &(struct key_xyz){},
};Would feel like less of a hack to me, and then map_def doesn't have to be different for every map. But yea, IDK if it's easy to (a) resolve the type of what key_type points to, or (b) how to do this for scalar types.
Quoted 33 lines
I don't think it's really worse than current
bpf_map_defapproach. In typical scenario, there are only two fields you need to remember: type andmax_entries(notice, they are called exactly the same as inbpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).I can relate a bit to that with
bpf_map_defyou can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.One big advantage of this scheme, though, is that you get that type association automagically without using
BPF_ANNOTATE_KV_PAIRhack, with no chance of having a mismatch, etc. This is less duplication (no need to dosizeof(struct my_struct)and structmy_structas an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.Quoted 8 lines
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
On forward compatibility my 0.02c would be - if we want to go there and silently ignore fields it'd be good to have some form of "hard required" bit. For TLVs ABIs it can be a "you have to understand this one" bit, for libbpf perhaps we could add a "min libbpf version required" section? That kind of ties us ELF formats to libbpf specifics (the libbpf version presumably would imply support for features), but I think we want to go there, anyway.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 23 lines · Jakub Kicinski
Quoted 9 lines · Andrii Nakryiko
Quoted 8 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I have mixed feelings, too. Especially the key and value fields are very non-idiomatic for C :( They never hold any value or data, while the other fields do. That feels so awkward. I'm no compiler expert, but even something like:
struct map_def { void *key_type_ref; } mamap = { .key_type_ref = &(struct key_xyz){}, };
Quoted 4 lines
Would feel like less of a hack to me, and then
map_defdoesn't have to be different for every map. But yea, IDK if it's easy to (a) resolve the type of whatkey_typepoints to, or (b) how to do this for scalar types.
The syntax for scalar would be &(int){0}, that compiles.
But there are a bunch of things that make it infeasible. So let's take an example and see what's happening:
/* huge struct */
struct custom {int a; int b; int c; int d[1000000];};
struct {
void *key;
void *value;
} new_map = {
.key = &(int){0},
.value = &(struct custom){},
};If we dump BTF, here's what we get:
$ bpftool btf dump file tail_call_test.o
[1] FUNC_PROTO '(anon)' ret_type_id=2 vlen=0
[2] INT 'int' size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[3] FUNC 'main' type_id=1
[4] VAR '.compoundliteral' type_id=0, linkage=static
[5] VAR '.compoundliteral.1' type_id=0, linkage=static
[6] STRUCT '(anon)' size=24 vlen=3
'type' type_id=2 bits_offset=0
'key' type_id=7 bits_offset=64
'value' type_id=7 bits_offset=128
[7] PTR '(anon)' type_id=0
[8] VAR 'new_map' type_id=6, linkage=global-alloc
[9] DATASEC '.bss' size=0 vlen=2
type_id=4 offset=0 size=4
type_id=5 offset=4 size=4000012
[10] DATASEC '.maps' size=0 vlen=1
type_id=8 offset=0 size=24So notice how we get two .bss entries, one for 4 bytes (for key, var 'compoundliteral') and another for 4MB (for huge struct, var '.compoundliteral.1'). So while this won't increase the size of ELF, it will force a huge .bss (and corresponding global data map) to be created, which is no good.
Also, notice how there is no type information associated with [4] and
[5] vars, they are just of type void. There is no type information about struct custom at all, though it might be (?) possible to fix it by modifying compiler to preserve more type information.
So while the second one is a technical hurdle, which we might overcome (not sure, actually), the issue with big .BSS is a showstopper for some applications.
To eliminate .BSS issue, we'd need something like this to capture type information:
struct {
void *key;
void *value;
} new_map = { .key = (int)0,
.value = (struct custom *)0,
};
But that doesn't capture any type information for those type casts at all, so more compiler work (if at all possible).
Which is why I think capturing type information using a standard non-convoluted C way/syntax using a field declaration is the most reliable, simple, and clean way. You do intialize key/value, it's just a NULL pointer to corresponding type:
struct {
int type;
int *key;
struct custom *value;
} new_map __attribute__((section(".maps"), used)) = {
.type = 2,
.key = (int)0,
.value = (struct custom *)NULL,
};Notice, btw, that this approach doesn't prevent you to re-use struct definitions for multiple maps, if they have identical key/value types or if you are not capturing type information at all.
struct my_typical_map {
int type;
int max_entries;
u64 *key;
struct custom *value;
};struct my_typical_map map1 SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 10,
};
struct my_typical_map map2 SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 20,
};
Or, you can just re-use struct bpf_map_def today like this (but you won't have type info for key/value, of course):
struct bpf_map_def my_map_without_type_info SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 100,
.key_size = sizeof(u64),
.value_size = sizeof(struct custom),
};
This approach gives you as much flexibility as possible, you only will have to have different definition struct, if you have different key/value type (in C++ that would be solved by templates, but alas we are in C land).
Quoted 39 lines
Quoted 34 lines
I don't think it's really worse than current
bpf_map_defapproach. In typical scenario, there are only two fields you need to remember: type andmax_entries(notice, they are called exactly the same as inbpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).I can relate a bit to that with
bpf_map_defyou can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.One big advantage of this scheme, though, is that you get that type association automagically without using
BPF_ANNOTATE_KV_PAIRhack, with no chance of having a mismatch, etc. This is less duplication (no need to dosizeof(struct my_struct)and structmy_structas an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.Quoted 8 lines
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
Quoted 7 lines
On forward compatibility my 0.02c would be - if we want to go there and silently ignore fields it'd be good to have some form of "hard required" bit. For TLVs ABIs it can be a "you have to understand this one" bit, for libbpf perhaps we could add a "min libbpf version required" section? That kind of ties us ELF formats to libbpf specifics (the libbpf version presumably would imply support for features), but I think we want to go there, anyway.
I think we can go with strict/non-strict mode, which we already support in libbpf with MAPS_RELAX_COMPAT flag (see __bpf_object__open_xattr), would that work?
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 70 lines · Andrii Nakryiko
Quoted 22 lines · Jakub Kicinski
Quoted 9 lines · Andrii Nakryiko
Quoted 8 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I have mixed feelings, too. Especially the key and value fields are very non-idiomatic for C :( They never hold any value or data, while the other fields do. That feels so awkward. I'm no compiler expert, but even something like:
struct map_def { void *key_type_ref; } mamap = { .key_type_ref = &(struct key_xyz){}, };Quoted 4 lines
Would feel like less of a hack to me, and then
map_defdoesn't have to be different for every map. But yea, IDK if it's easy to (a) resolve the type of whatkey_typepoints to, or (b) how to do this for scalar types.The syntax for scalar would be &(int){0}, that compiles.
But there are a bunch of things that make it infeasible. So let's take an example and see what's happening:
/* huge struct */
struct custom {int a; int b; int c; int d[1000000];};struct { void *key; void *value; } new_map = { .key = &(int){0}, .value = &(struct custom){}, };If we dump BTF, here's what we get:
$ bpftool btf dump file tail_call_test.o [1] FUNC_PROTO '(anon)' ret_type_id=2 vlen=0 [2] INT 'int' size=4 bits_offset=0 nr_bits=32 encoding=SIGNED [3] FUNC 'main' type_id=1 [4] VAR '.compoundliteral' type_id=0, linkage=static [5] VAR '.compoundliteral.1' type_id=0, linkage=static [6] STRUCT '(anon)' size=24 vlen=3 'type' type_id=2 bits_offset=0 'key' type_id=7 bits_offset=64 'value' type_id=7 bits_offset=128 [7] PTR '(anon)' type_id=0 [8] VAR 'new_map' type_id=6, linkage=global-alloc [9] DATASEC '.bss' size=0 vlen=2 type_id=4 offset=0 size=4 type_id=5 offset=4 size=4000012 [10] DATASEC '.maps' size=0 vlen=1 type_id=8 offset=0 size=24So notice how we get two .bss entries, one for 4 bytes (for key, var 'compoundliteral') and another for 4MB (for huge struct, var '.compoundliteral.1'). So while this won't increase the size of ELF, it will force a huge .bss (and corresponding global data map) to be created, which is no good.
Quoted 8 lines
Also, notice how there is no type information associated with [4] and
[5] vars, they are just of type void. There is no type information about struct custom at all, though it might be (?) possible to fix it by modifying compiler to preserve more type information.So while the second one is a technical hurdle, which we might overcome (not sure, actually), the issue with big .BSS is a showstopper for some applications.
Ah :/
Quoted 2 lines
To eliminate .BSS issue, we'd need something like this to capture type information:
Well, or we can track that the part of BSS is only referenced from map def, but that's hairy as well.
Quoted 58 lines
struct { void *key; void *value; } new_map = {.key = (int)0,
.value = (struct custom *)0,
};But that doesn't capture any type information for those type casts at all, so more compiler work (if at all possible).
Which is why I think capturing type information using a standard non-convoluted C way/syntax using a field declaration is the most reliable, simple, and clean way. You do intialize key/value, it's just a NULL pointer to corresponding type:
struct { int type; int *key; struct custom *value; } new_map __attribute__((section(".maps"), used)) = { .type = 2, .key = (int)0, .value = (struct custom *)NULL, };Notice, btw, that this approach doesn't prevent you to re-use struct definitions for multiple maps, if they have identical key/value types or if you are not capturing type information at all.
struct my_typical_map { int type; int max_entries; u64 *key; struct custom *value; };struct
my_typical_mapmap1SEC(".maps")= {
.type =BPF_MAP_TYPE_ARRAY,
.max_entries = 10,
};struct
my_typical_mapmap2SEC(".maps")= {
.type =BPF_MAP_TYPE_ARRAY,
.max_entries = 20,
};Or, you can just re-use struct
bpf_map_deftoday like this (but you won't have type info for key/value, of course):struct
bpf_map_defmy_map_without_type_infoSEC(".maps")= {
.type =BPF_MAP_TYPE_ARRAY,
.max_entries = 100,
.key_size = sizeof(u64),
.value_size = sizeof(struct custom),
};
Quoted 4 lines
This approach gives you as much flexibility as possible, you only will have to have different definition struct, if you have different key/value type (in C++ that would be solved by templates, but alas we are in C land).
To be clear I'm not arguing that the proposal is not flexible. To a C guy like me having struct members which don't hold value mixed with struct members for storing data seems very dirty, dare I say the BPF_ANNOTATE_KV_PAIR() construct feels cleaner :( I like that it has the "meta structure" separate from the actual def structure. In a sense this would feel better to me:
BPF_DECLARE_KV_PAIR(kv_ref, struct key, struct val);
struct { .. } def = {
.btf_ref = &kv_ref,
};BPF_DECLARE_KV_PAIR() can stuff the structure into a custom ignored section.
Initially I was thinking to try to force a relocation to avoid the BSS issue:
extern struct key_ext;
extern struct value_ext;
struct def {
void *key;
void *value;
} new_map = { .key = &key_ext,
.value = &value_ext,
};
But then I'm not super happy with needed the extern declarations :(
IDK, I would really like a cleaner solution, but perhaps there is none ;)
Quoted 28 lines
Quoted 20 lines
Quoted 15 lines
Quoted 8 lines
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
Quoted 7 lines
On forward compatibility my 0.02c would be - if we want to go there and silently ignore fields it'd be good to have some form of "hard required" bit. For TLVs ABIs it can be a "you have to understand this one" bit, for libbpf perhaps we could add a "min libbpf version required" section? That kind of ties us ELF formats to libbpf specifics (the libbpf version presumably would imply support for features), but I think we want to go there, anyway.
Quoted 3 lines
I think we can go with strict/non-strict mode, which we already support in libbpf with
MAPS_RELAX_COMPATflag (see__bpf_object__open_xattr), would that work?
I'd be a lil worried that all or nothing may not be flexible enough. IOW someone may need a future from 5.5 but optionally want a 5.10 features if available? No strong feelings, tho.
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
In reply to Andrii NakryikoQuoted 22 lines · Andrii Nakryiko
Quoted 9 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I don't think it's really worse than current
bpf_map_defapproach. In typical scenario, there are only two fields you need to remember: type andmax_entries(notice, they are called exactly the same as inbpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).I can relate a bit to that with
bpf_map_defyou can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.
Quoted 6 lines
One big advantage of this scheme, though, is that you get that type association automagically without using
BPF_ANNOTATE_KV_PAIRhack, with no chance of having a mismatch, etc. This is less duplication (no need to dosizeof(struct my_struct)and structmy_structas an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.
Don't get me wrong, it looks good and there are advantages compared to the existing way. But, again, feels to me a bit too magic. We should somehow make it less magic (see below).
Quoted 9 lines
Quoted 4 lines
I don't know how others feel about it, but I'd be much more comfortable with a simpler TLV-like approach. Have a new section where the format is |4-byte size|struct bpf_map_def_extendable|. That would essentially allow us to extend it the way we do with a syscall args.
It would help with extensibility, sure, though even current
bpf_map_defapproach sort of can be extended already. But it won't solve the problem of having BTF types captured for key/value (see above). Also, you'd need another macro to lay everything out properly.
I didn't know that we look into the list of exported symbols to estimate the number of maps and then use it to derive struct bpf_map_def size.
In that case, maybe we can keep extending struct bpf_map_def and support BTF mode as a better alternative? bpf_map_def could be used as a reference for which fields there are, people can still use it (with BPF_ANNOTATE_KV_PAIR if needed), but they can also use new BTF mode if they find that works better for them?
Because the biggest issue for me with the BTF mode is the question of where to look for the supported fields (and misspellings). People on this mailing list can probably figure it out, but people who don't work full time on bpf might find it hard. Having 'struct bpf_map_def' as a reference (or a good supported piece of documentation) might help with that.
What do you think? The only issue is that we now have two formats to support :-/
Quoted 11 lines
Quoted 2 lines
Also, (un)related: we don't currently use BTF internally, so if you convert all tests, we'd be unable to run them :-(
Not exactly sure what you mean "you'd be unable to run them". Do you mean that you use old Clang that doesn't emit BTF? If that's what you are saying, a lot of tests already rely on latest Clang, so those tests already don't work for you, probably. I'll leave it up to Daniel and Alexei to decide if we want to convert selftests right now or not. I did it mostly to prove that we can handle all existing cases (and found few gotchas and bugs along the way, both in my implementation and in kernel - fixes coming soon).
Yes, I mean that we don't always use the latest features of clang, so having the existing tests in the old form (at least for a while) would be appreciated. Good candidates to showcase new format can be features that explicitly require BTF, stuff like spinlocks.
Quoted 15 lines
Quoted 8 lines
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
In general, doing what we do right now with bpf_map_def (returning an error for non-zero unknown options) seems like the safest option. We should probably do the same with the unknown BTF fields (return an error for non-zero value).
For a general BTF case, we can have some predefined policy: if, for example, the field name starts with an underscore, it's optional and doesn't require non-zero check. (or the name ends with '_opt' or some other clear policy).
Quoted 69 lines
Quoted 69 lines
Quoted 69 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
Signed-off-by Andrii Nakryiko <[email protected]>--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 52 lines · Stanislav Fomichev
Quoted 22 lines · Andrii Nakryiko
Quoted 9 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I don't think it's really worse than current
bpf_map_defapproach. In typical scenario, there are only two fields you need to remember: type andmax_entries(notice, they are called exactly the same as inbpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).I can relate a bit to that with
bpf_map_defyou can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.Quoted 6 lines
One big advantage of this scheme, though, is that you get that type association automagically without using
BPF_ANNOTATE_KV_PAIRhack, with no chance of having a mismatch, etc. This is less duplication (no need to dosizeof(struct my_struct)and structmy_structas an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.Don't get me wrong, it looks good and there are advantages compared to the existing way. But, again, feels to me a bit too magic. We should somehow make it less magic (see below).
Quoted 9 lines
Quoted 4 lines
I don't know how others feel about it, but I'd be much more comfortable with a simpler TLV-like approach. Have a new section where the format is |4-byte size|struct bpf_map_def_extendable|. That would essentially allow us to extend it the way we do with a syscall args.
It would help with extensibility, sure, though even current
bpf_map_defapproach sort of can be extended already. But it won't solve the problem of having BTF types captured for key/value (see above). Also, you'd need another macro to lay everything out properly.I didn't know that we look into the list of exported symbols to estimate the number of maps and then use it to derive struct
bpf_map_defsize.In that case, maybe we can keep extending struct
bpf_map_defand support BTF mode as a better alternative?bpf_map_defcould be used as a reference for which fields there are, people can still use it (withBPF_ANNOTATE_KV_PAIRif needed), but they can also use new BTF mode if they find that works better for them?
Quoted 5 lines
Because the biggest issue for me with the BTF mode is the question of where to look for the supported fields (and misspellings). People on this mailing list can probably figure it out, but people who don't work full time on bpf might find it hard. Having 'struct
bpf_map_def' as a reference (or a good supported piece of documentation) might help
So yeah, it's more about documentation and examples, it seems, rather than having a C struct in code, right? Today, if I need to add new map, I copy/paste either from example, existing code or look up documentation. You'll be able to do the same with new way (just grep for \.maps).
Quoted 4 lines
with that.
What do you think? The only issue is that we now have two formats to support :-/
We'll have to support existing bpf_map_def for backwards compatibility (and see my reply to Jakub, you can just plain re-use struct bpf_map_def today with BTF approach, just put it into .maps section), but I'd love to avoid having to support new features using two different way, so if we go with BTF, I'd restrict new features to BTF only, moving forward.
Quoted 12 lines
Quoted 4 lines
Quoted 3 lines
Also, (un)related: we don't currently use BTF internally, so if you convert all tests, we'd be unable to run them :-(
Quoted 8 lines
Not exactly sure what you mean "you'd be unable to run them". Do you mean that you use old Clang that doesn't emit BTF? If that's what you are saying, a lot of tests already rely on latest Clang, so those tests already don't work for you, probably. I'll leave it up to Daniel and Alexei to decide if we want to convert selftests right now or not. I did it mostly to prove that we can handle all existing cases (and found few gotchas and bugs along the way, both in my implementation and in kernel - fixes coming soon).
Quoted 4 lines
Yes, I mean that we don't always use the latest features of clang, so having the existing tests in the old form (at least for a while) would be appreciated. Good candidates to showcase new format can be features that explicitly require BTF, stuff like spinlocks.
I totally understand a concern, but I'll still defer to maintainers to make a call as to when to do conversion.
Quoted 16 lines
Quoted 16 lines
Quoted 9 lines
Quoted 5 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 8 lines
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
In general, doing what we do right now with
bpf_map_def(returning an error for non-zero unknown options) seems like the safest option. We should probably do the same with the unknown BTF fields (return an error for non-zero value).
Yeah, as I replied to Jakub, libbpf already has strict/non-strict mode, we should probably do the same. The only potential difference is that there is no need to check for zeros and stuff: just don't define a field. And using an extra flag, we can allow more relaxed semantics (just debug/info/warn message on unknown fields). This is what __bpf_object__open_xattr does today with MAPS_RELAX_COMPAT flag.
Quoted 74 lines
For a general BTF case, we can have some predefined policy: if, for example, the field name starts with an underscore, it's optional and doesn't require non-zero check. (or the name ends with '
_opt' or some other clear policy).Quoted 69 lines
Quoted 69 lines
Quoted 69 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
Signed-off-by Andrii Nakryiko <[email protected]>--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 59 lines · Andrii Nakryiko
Quoted 52 lines · Stanislav Fomichev
Quoted 22 lines · Andrii Nakryiko
Quoted 9 lines · Stanislav Fomichev
Quoted 5 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.My 2c: this is too magical and relies on me knowing the expected fields. (also, the compiler won't be able to help with the misspellings).
I don't think it's really worse than current
bpf_map_defapproach. In typical scenario, there are only two fields you need to remember: type andmax_entries(notice, they are called exactly the same as inbpf_map_def, so this knowledge is transferrable). Then you'll have key/value, using which you are describing both type (using field's type) and size (calculated from the type).I can relate a bit to that with
bpf_map_defyou can find definition and see all possible fields, but one can also find a lot of examples for new map definitions as well.Quoted 6 lines
One big advantage of this scheme, though, is that you get that type association automagically without using
BPF_ANNOTATE_KV_PAIRhack, with no chance of having a mismatch, etc. This is less duplication (no need to dosizeof(struct my_struct)and structmy_structas an arg to that macro) and there is no need to go and ping people to add those annotations to improve introspection of BPF maps.Don't get me wrong, it looks good and there are advantages compared to the existing way. But, again, feels to me a bit too magic. We should somehow make it less magic (see below).
Quoted 9 lines
Quoted 4 lines
I don't know how others feel about it, but I'd be much more comfortable with a simpler TLV-like approach. Have a new section where the format is |4-byte size|struct bpf_map_def_extendable|. That would essentially allow us to extend it the way we do with a syscall args.
It would help with extensibility, sure, though even current
bpf_map_defapproach sort of can be extended already. But it won't solve the problem of having BTF types captured for key/value (see above). Also, you'd need another macro to lay everything out properly.I didn't know that we look into the list of exported symbols to estimate the number of maps and then use it to derive struct
bpf_map_defsize.In that case, maybe we can keep extending struct
bpf_map_defand support BTF mode as a better alternative?bpf_map_defcould be used as a reference for which fields there are, people can still use it (withBPF_ANNOTATE_KV_PAIRif needed), but they can also use new BTF mode if they find that works better for them?Quoted 5 lines
Because the biggest issue for me with the BTF mode is the question of where to look for the supported fields (and misspellings). People on this mailing list can probably figure it out, but people who don't work full time on bpf might find it hard. Having 'struct
bpf_map_def' as a reference (or a good supported piece of documentation) might help
Quoted 3 lines
So yeah, it's more about documentation and examples, it seems, rather than having a C struct in code, right? Today, if I need to add new map, I copy/paste either from example, existing code or look up
Well, you know where to copy paste from ;-)
Quoted 2 lines
documentation. You'll be able to do the same with new way (just grep for \.maps).
Yes, it's mostly about discoverability. Either documentation or the real underlaying structure could help with that.
Quoted 11 lines
Quoted 4 lines
with that.
What do you think? The only issue is that we now have two formats to support :-/
We'll have to support existing
bpf_map_deffor backwards compatibility (and see my reply to Jakub, you can just plain re-use structbpf_map_deftoday with BTF approach, just put it into .maps section), but I'd love to avoid having to support new features using two different way, so if we go with BTF, I'd restrict new features to BTF only, moving forward.
But what's wrong with trying to extend bpf_map_def for a while? It looks like we have everything in place to do that. I understand your desire to deprecate everything and move on, but when was BTF support added to LLVM? 8.0.0? 8.0.1? Six months ago? Is there a major distro with the latest llvm+btf? Do we want to lock everyone out of new libbpf features? (Consider that a lot of people run on the LTS kernels).
What's wrong with having BTF be just a syntactic sugar on top of bpf_map_def? One major use-case is supporting iproute2 features, but some of those features can go into bpf_map_def as well and be used by non-BTF enabled users.
One other point to consider here might be pure Go libbpf that Lorenz is maintaining. Having simple underlying bpf_map_def which we can agree on might be beneficial.
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 2 lines
Also, (un)related: we don't currently use BTF internally, so if you convert all tests, we'd be unable to run them :-(
Not exactly sure what you mean "you'd be unable to run them". Do you mean that you use old Clang that doesn't emit BTF? If that's what you are saying, a lot of tests already rely on latest Clang, so those tests already don't work for you, probably. I'll leave it up to Daniel and Alexei to decide if we want to convert selftests right now or not. I did it mostly to prove that we can handle all existing cases (and found few gotchas and bugs along the way, both in my implementation and in kernel - fixes coming soon).
Quoted 7 lines
Quoted 4 lines
Yes, I mean that we don't always use the latest features of clang, so having the existing tests in the old form (at least for a while) would be appreciated. Good candidates to showcase new format can be features that explicitly require BTF, stuff like spinlocks.
I totally understand a concern, but I'll still defer to maintainers to make a call as to when to do conversion.
Sure, totally up to you and the maintainers. Just raising my voice, so you'd at least consider not converting everything.
Quoted 105 lines
Quoted 15 lines
Quoted 15 lines
Quoted 8 lines
Quoted 4 lines
Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
I also don't know how to feel about old libbpf ignoring some attributes. In the kernel we require that the unknown fields are zeroed. We probably need to do something like that here? What do you think would be a good example of an optional attribute?
Ignoring is required for forward-compatibility, where old libbpf will be used to load newer user BPF programs. We can decided not to do it, in that case it's just a question of erroring out on first unknown field. This RFC was posted exactly to discuss all these issues with more general community, as there is no single true way to do this.
Quoted 8 lines
Quoted 4 lines
As for examples of when it can be used. It's any feature that can be considered optional or a hint, so if old libbpf doesn't do that, it's still not the end of the world (and we can live with that, or can correct using direct libbpf API calls).
In general, doing what we do right now with
bpf_map_def(returning an error for non-zero unknown options) seems like the safest option. We should probably do the same with the unknown BTF fields (return an error for non-zero value).Yeah, as I replied to Jakub, libbpf already has strict/non-strict mode, we should probably do the same. The only potential difference is that there is no need to check for zeros and stuff: just don't define a field. And using an extra flag, we can allow more relaxed semantics (just debug/info/warn message on unknown fields). This is what
__bpf_object__open_xattrdoes today withMAPS_RELAX_COMPATflag.Quoted 74 lines
For a general BTF case, we can have some predefined policy: if, for example, the field name starts with an underscore, it's optional and doesn't require non-zero check. (or the name ends with '
_opt' or some other clear policy).Quoted 69 lines
Quoted 69 lines
Quoted 69 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
Signed-off-by Andrii Nakryiko <[email protected]>--- tools/lib/bpf/btf.h | 1 + tools/lib/bpf/libbpf.c | 333 +++++++++++++++++++++++++++++++++++++++-- 2 files changed, 325 insertions(+), 9 deletions(-)
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 1 line · Stanislav Fomichev
Do we want to lock everyone out of new libbpf features?
BTF is mandatory for _any_ new feature.
It's for introspection and debuggability in the first place. Good debugging is not optional.
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 9 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)? If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 7 lines · Stanislav Fomichev
Quoted 5 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)?
In general, the motivation is to arrive at a way to support declaratively defining maps in such a way, that:
- captures type information (for debuggability/introspection) in coherent and hard-to-screw-up way;
- allows to support missing useful features w/ good syntax (e.g., natural map-in-map case vs current completely manual non-declarative way for libbpf);
- ultimately allow iproute2 to use libbpf as unified loader (and thus the need to support its existing features, like BPF_MAP_TYPE_PROG_ARRAY initialization, pinning, map-in-map);
The only missing feature that can be supported reasonably with bpf_map_def is pinning (as it's just another int field), but all the other use cases requires awkward approach of matching arbitrary IDs, which feels like a bad way forward.
Quoted 2 lines
If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Stanislav Fomichev
reviewerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 23 lines · Andrii Nakryiko
Quoted 7 lines · Stanislav Fomichev
Quoted 5 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)?In general, the motivation is to arrive at a way to support declaratively defining maps in such a way, that:
- captures type information (for debuggability/introspection) in coherent and hard-to-screw-up way;
- allows to support missing useful features w/ good syntax (e.g., natural map-in-map case vs current completely manual non-declarative way for libbpf);
[..]
Quoted 3 lines
- ultimately allow iproute2 to use libbpf as unified loader (and thus the need to support its existing features, like
BPF_MAP_TYPE_PROG_ARRAYinitialization, pinning, map-in-map);
So prog_array tail call info would be encoded in the magic struct instead of a __section_tail(whatever) macros that iproute2 is using? Does it mean that the programs that target iproute2 would have to be rewritten? Or we don't have a goal to provide source-level compatibility?
In general, supporting iproute2 seems like the most compelling reason to use BTF given current state of llvm+btf adoption. BPF_ANNOTATE_KV_PAIR and map-in-map syntax while ugly, is not the major paint point (imho); but I agree, with BTF both of those things look much better.
That's why I was trying to understand whether we can start with using BTF to support _existing_ iproute2 format and then, once it's working, generalize it (and kill bpf_map_def or make it a subset of generic BTF). That way we are not implementing another way to support pinning/tail calls, but enabling iproute2 to use libbpf.
But feel free to ignore all my nonsense above; I don't really have any major concerns with the new generic format rather than discoverability (the docs might help) and a mandate that everyone switches to it immediately.
Quoted 8 lines
The only missing feature that can be supported reasonably with
bpf_map_defis pinning (as it's just another int field), but all the other use cases requires awkward approach of matching arbitrary IDs, which feels like a bad way forward.Quoted 2 lines
If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 26 lines · Stanislav Fomichev
Quoted 16 lines · Andrii Nakryiko
Quoted 7 lines · Stanislav Fomichev
Quoted 5 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)?Quoted 7 lines
In general, the motivation is to arrive at a way to support declaratively defining maps in such a way, that:
- captures type information (for debuggability/introspection) in coherent and hard-to-screw-up way;
- allows to support missing useful features w/ good syntax (e.g., natural map-in-map case vs current completely manual non-declarative way for libbpf);
Quoted 6 lines
[..]
Quoted 3 lines
- ultimately allow iproute2 to use libbpf as unified loader (and thus the need to support its existing features, like
BPF_MAP_TYPE_PROG_ARRAYinitialization, pinning, map-in-map);So
prog_arraytail call info would be encoded in the magic struct instead of a__section_tail(whatever)macros that iproute2 is using? Does it
Yes. It will be C-style array initialization (where value is address of a function, corresponding to a BPF program).
Quoted 2 lines
mean that the programs that target iproute2 would have to be rewritten? Or we don't have a goal to provide source-level compatibility?
As outlined in separate email I sent out yesterday, my goal was making sure we have very easy transition path not changing the semantics (field renaming for common case, functionally-equivalent, but different syntax for tail call prog array initialization, etc). Let's see what folks working on Cilium think about this.
Quoted 7 lines
In general, supporting iproute2 seems like the most compelling reason to use BTF given current state of llvm+btf adoption.
BPF_ANNOTATE_KV_PAIRand map-in-map syntax while ugly, is not the major paint point (imho); but I agree, with BTF both of those things look much better.
Quoted 5 lines
That's why I was trying to understand whether we can start with using BTF to support _existing_ iproute2 format and then, once it's working, generalize it (and kill
bpf_map_defor make it a subset of generic BTF). That way we are not implementing another way to support pinning/tail calls, but enabling iproute2 to use libbpf.
We currently don't have a good way (except for programmatic API) to do either tail call or map-in-map declaratively in libbpf, so the hope is this approach will allow us to address that lack, and preferrably in a bit more intuitive way, than iproute2 support today. Given it's simple to convert iproute2 approach to BTF-based one, I'd vote for not back-porting that logic into libbpf, if possible.
Quoted 4 lines
But feel free to ignore all my nonsense above; I don't really have any major concerns with the new generic format rather than discoverability (the docs might help) and a mandate that everyone switches to it immediately.
No, thanks for feedback! For documentation, I think we might want to add description to https://docs.cilium.io/en/v1.4/bpf/ (though timing-wise it would be better to do after iproute2 starts using libbpf, so a bit of a chicken-and-egg problem). If you have better suggestions where to put it, let me know.
Quoted 9 lines
Quoted 9 lines
The only missing feature that can be supported reasonably with
bpf_map_defis pinning (as it's just another int field), but all the other use cases requires awkward approach of matching arbitrary IDs, which feels like a bad way forward.Quoted 2 lines
If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Daniel Borkmann
maintainerRe: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
In reply to Andrii NakryikoQuoted 15 lines · Andrii Nakryiko
Quoted 6 lines · Stanislav Fomichev
Quoted 5 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)?
Quoted 10 lines
In general, the motivation is to arrive at a way to support declaratively defining maps in such a way, that:
- captures type information (for debuggability/introspection) in coherent and hard-to-screw-up way;
- allows to support missing useful features w/ good syntax (e.g., natural map-in-map case vs current completely manual non-declarative way for libbpf);
- ultimately allow iproute2 to use libbpf as unified loader (and thus the need to support its existing features, likeBPF_MAP_TYPE_PROG_ARRAYinitialization, pinning, map-in-map);
Thanks for working on this & sorry for jumping in late! Generally, I like the approach of using BTF to make sense out of the individual members and to have extensibility, so overall I think it's a step in the right direction. Going back to the example where others complained that the k/v NULL initialization feels too much magic from a C pov:
struct {
int type;
int max_entries;
int *key;
struct my_value *value;
} my_map SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Given LLVM is in charge of emitting BTF plus given gcc/clang seem /both/ to support *target* specific attributes [0], how about something along these lines where the type specific info is annotated as a variable BPF target attribute, like:
struct {
int type;
int max_entries;
} my_map __attribute__((map(int,struct my_value))) = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Of course this would need BPF backend support, but at least that approach would be more C like. Thus this would define types where we can automatically derive key/val sizes etc. The SEC() could be dropped as well as map attribute would imply it for LLVM to do the right thing underneath. The normal/actual members from the struct has a base set of well-known names that are minimally required but there could be custom stuff as well where libbpf would query some user defined callback that can handle these. Anyway, main point, what do you think about the __attribute__ approach instead? I think this feels cleaner to me at least iff feasible.
Thanks,
Daniel
[0] https://clang.llvm.org/docs/AttributeReference.html
https://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html
Quoted 7 lines
The only missing feature that can be supported reasonably with
bpf_map_defis pinning (as it's just another int field), but all the other use cases requires awkward approach of matching arbitrary IDs, which feels like a bad way forward.Quoted 2 lines
If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 53 lines · Daniel Borkmann
Quoted 15 lines · Andrii Nakryiko
Quoted 6 lines · Stanislav Fomichev
Quoted 5 lines · Stanislav Fomichev
Quoted 1 line
BTF is mandatory for _any_ new feature.
If something is easy to support without asking everyone to upgrade to a bleeding edge llvm, why not do it?
So much for backwards compatibility and flexibility.Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
It's for introspection and debuggability in the first place. Good debugging is not optional.
Once llvm 8+ is everywhere, sure, but we are not there yet (I'm talking about upstream LTS distros like ubuntu/redhat).
But putting this aside, one thing that I didn't see addressed in the cover letter is: what is the main motivation for the series?
Is it to support iproute2 map definitions (so cilium can switch to libbpf)?Quoted 10 lines
In general, the motivation is to arrive at a way to support declaratively defining maps in such a way, that:
- captures type information (for debuggability/introspection) in coherent and hard-to-screw-up way;
- allows to support missing useful features w/ good syntax (e.g., natural map-in-map case vs current completely manual non-declarative way for libbpf);
- ultimately allow iproute2 to use libbpf as unified loader (and thus the need to support its existing features, likeBPF_MAP_TYPE_PROG_ARRAYinitialization, pinning, map-in-map);Thanks for working on this & sorry for jumping in late! Generally, I like the approach of using BTF to make sense out of the individual members and to have extensibility, so overall I think it's a step in the right direction. Going back to the example where others complained that the k/v NULL initialization feels too much magic from a C pov:
struct { int type; int max_entries; int *key; struct my_value *value; } my_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Given LLVM is in charge of emitting BTF plus given gcc/clang seem /both/ to support *target* specific attributes [0], how about something along these lines where the type specific info is annotated as a variable BPF target attribute, like:
struct { int type; int max_entries; } my_map __attribute__((map(int,struct my_value))) = {
Quoted 6 lines
.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Of course this would need BPF backend support, but at least that approach would be more C like. Thus this would define types where we can automatically
I guess it's technically possible (not a compiler guru, but I don't see why it wouldn't be possible). But it will require at least two things:
1. Compiler support, obviously, as you mentioned.
2. BTF specification on how to describe attributes and how to describe what entities (variable in this case) it is attached to.
2. is not straightforward, as attributes in general is a collection of values of vastly different types: some values could be integers, some strings, some, like in this case, would be a reference another BTF type. It seems like a powerful and potentially useful addition to BTF, of course, but it's very unclear at this point what's the best way to represent them.
I'm not relating with "non idiomatic C" motive, though, so all that seems like unnecessarily heavy-weight way to get something that we can get today w/o compiler support in a clean, succinct and familiar C syntax, that to me doesn't look like magic at all.
And if anything, attribute feels just as much magic to me. But here's very similarly looking macro-trick:
#define MAP_KEY_VALUE_META(KEY, VALUE) KEY *key; VALUE *value;
struct {
MAP_KEY_VALUE_META(int, struct my_value)
int type;
int max_entries;
} my_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};
Or even:
#define MAP_DEF(KEY, VALUE) struct { KEY *key; VALUE *value; int type; int max_entries; }
MAP_DEF(int, struct my_value) my_map SEC(".maps") = {
.type = BPF_MAP_TYPE_ARRAY, .max_entries = 16,
};
Quoted 1 line
derive key/val sizes etc. The
SEC()could be dropped as well as map attribute
I think we should at least have an ability to override ELF section name, just in case we add support to have maps in multiple sections (e.g., shared library with its own set of maps, or whatever).
Quoted 4 lines
would imply it for LLVM to do the right thing underneath. The normal/actual members from the struct has a base set of well-known names that are minimally required but there could be custom stuff as well where libbpf would query some user defined callback that can handle these. Anyway, main point, what do you think
So regarding callback. I find it hard to imagine how that could be implemented interface-wise. As each field can have very different value (it could be another embedded custom struct, not just integer; or it could be char array of fixed size, etc), which is determined by BTF, I don't know how I would expose that to custom callback in C type system.
If I absolutely had to do it, though, how about this approach. We either add BTF type id of a defining struct to bpf_map_def or add bpf_map__btf_def() API, which returns it, so:
struct bpf_map *map = bpf_object__find_map_by_name(obj, "my_fancy_map"); struct btf *btf = bpf_object__btf(obj);__u32 def_id = bpf_map__btf_map_def_type_id(map);
const void *def_data = bpf_map__btf_map_def_data(map); struct btf_type *t = btf__type_by_id(btf, def_id);
Then application can do whatever parsing it wants on BTF map definition and extract values in whatever manner suits it. This way it's just a bunch of very straightforward APIs, instead of callbacks w/ unclear interface (i.e., you'd still need to expose field_name, field's type_id, raw pointer to data).
Does this make sense?
But having said that, what are the use cases you have in mind that require application to put custom stuff into a standardized map definition?
Quoted 17 lines
about the
__attribute__approach instead? I think this feels cleaner to me at least iff feasible.Thanks,
Daniel[0] https://clang.llvm.org/docs/AttributeReference.html
https://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.htmlQuoted 7 lines
The only missing feature that can be supported reasonably with
bpf_map_defis pinning (as it's just another int field), but all the other use cases requires awkward approach of matching arbitrary IDs, which feels like a bad way forward.Quoted 2 lines
If that's the case, maybe explicitly focus on that? Once we have proof-of-concept working for iproute2 mode, we can extend it to everything.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 8 lines · Andrii Nakryiko
Quoted 8 lines
struct { int type; int max_entries; } my_map __attribute__((map(int,struct my_value))) = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};
Quoted 6 lines
Quoted 2 lines
Of course this would need BPF backend support, but at least that approach would be more C like. Thus this would define types where we can automatically
I guess it's technically possible (not a compiler guru, but I don't see why it wouldn't be possible). But it will require at least two things:
1. Compiler support, obviously, as you mentioned.
every time we're doing llvm common change it takes many months. Adding BTF took 6 month, though the common changes were trivial. Now we're already 1+ month into adding 4 intrinsics to support CO-RE.
In the past I was very much in favor of extending __attribute__ with bpf specific stuff. Now not so much. __attribute__((map(int,struct my_value))) cannot be done as strings. clang has to process the types, create new objects inside debug info. It's not clear to me how this modified debug info will be associated with the variable my_map.
So I suspect doing __attribute__ with actual C type inside (()) will not be possible.
I think in the future we might still add string based attributes, but it's not going to be easy.
So... Unless somebody in the community who is doing full time llvm work will not step in right now and says "I will code the above attr stuff", we should not count on such clang+llvm feature.
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 20 lines · Alexei Starovoitov
Quoted 8 lines · Andrii Nakryiko
Quoted 8 lines
struct { int type; int max_entries; } my_map __attribute__((map(int,struct my_value))) = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Quoted 6 lines
Quoted 2 lines
Of course this would need BPF backend support, but at least that approach would be more C like. Thus this would define types where we can automatically
I guess it's technically possible (not a compiler guru, but I don't see why it wouldn't be possible). But it will require at least two things:
1. Compiler support, obviously, as you mentioned.every time we're doing llvm common change it takes many months. Adding BTF took 6 month, though the common changes were trivial. Now we're already 1+ month into adding 4 intrinsics to support CO-RE.
Quoted 13 lines
In the past I was very much in favor of extending
__attribute__with bpf specific stuff. Now not so much.__attribute__((map(int,struct my_value)))cannot be done as strings. clang has to process the types, create new objects inside debug info. It's not clear to me how this modified debug info will be associated with the variablemy_map.
So I suspect doing__attribute__with actual C type inside (()) will not be possible.
I think in the future we might still add string based attributes, but it's not going to be easy.
So... Unless somebody in the community who is doing full time llvm work will not step in right now and says "I will code the above attr stuff", we should not count on such clang+llvm feature.
If nobody has resources to commit to this, perhaps we can just stick to BPF_ANNOTATE_KV_PAIR()?
Apologies, but I think I missed the memo on why that's considered a hack. Could someone point me to the relevant discussion?
We could conceivably add BTF-based map_def for other features, and solve the K/V problem once a clean solution becomes apparent and tractable? BPF_ANNOTATE_KV_PAIR() is not great, but we kinda already have it..
Perhaps I'm not thinking clearly about this and I should stay quiet :)
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 41 lines · Jakub Kicinski
Quoted 20 lines · Alexei Starovoitov
Quoted 8 lines · Andrii Nakryiko
Quoted 8 lines
struct { int type; int max_entries; } my_map __attribute__((map(int,struct my_value))) = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};Quoted 6 lines
Quoted 2 lines
Of course this would need BPF backend support, but at least that approach would be more C like. Thus this would define types where we can automatically
I guess it's technically possible (not a compiler guru, but I don't see why it wouldn't be possible). But it will require at least two things:
1. Compiler support, obviously, as you mentioned.every time we're doing llvm common change it takes many months. Adding BTF took 6 month, though the common changes were trivial. Now we're already 1+ month into adding 4 intrinsics to support CO-RE.
Quoted 13 lines
In the past I was very much in favor of extending
__attribute__with bpf specific stuff. Now not so much.__attribute__((map(int,struct my_value)))cannot be done as strings. clang has to process the types, create new objects inside debug info. It's not clear to me how this modified debug info will be associated with the variablemy_map.
So I suspect doing__attribute__with actual C type inside (()) will not be possible.
I think in the future we might still add string based attributes, but it's not going to be easy.
So... Unless somebody in the community who is doing full time llvm work will not step in right now and says "I will code the above attr stuff", we should not count on such clang+llvm feature.If nobody has resources to commit to this, perhaps we can just stick to
BPF_ANNOTATE_KV_PAIR()?Apologies, but I think I missed the memo on why that's considered a hack. Could someone point me to the relevant discussion?
Quoted 6 lines
We could conceivably add BTF-based
map_deffor other features, and solve the K/V problem once a clean solution becomes apparent and tractable?BPF_ANNOTATE_KV_PAIR()is not great, but we kinda already have it..Perhaps I'm not thinking clearly about this and I should stay quiet :)
the solution we're discussing should solve BPF_ANNOTATE_KV_PAIR too. That hack must go.
If I understood your objections to Andrii's format is that you don't like pointer part of key/value while Andrii explained why we picked the pointer, right?
So how about:
struct {
int type;
int max_entries;
struct {
__u32 key;
struct my_value value; } types[];
} ...
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 2 lines · Alexei Starovoitov
the solution we're discussing should solve
BPF_ANNOTATE_KV_PAIRtoo. That hack must go.
I see.
Quoted 6 lines
If I understood your objections to Andrii's format is that you don't like pointer part of key/value while Andrii explained why we picked the pointer, right?
So how about:
Quoted 8 lines
struct {
int type;
int max_entries;
struct {
__u32 key;
struct my_value value;
} types[];
} ...My objection is that k/v fields are never initialized, so they're "metafields", mixed with real fields which hold parameters - like type, max_entries etc.
But I thought about this 3 times now, and I see no better solution. FWIW my best shot was relos:
extern struct my_key my_key;
extern int type_int;
struct map_def {
int type;
int max_entries;
void *btf_key_ref;
void *btf_val_ref;
} = {
...
.btf_key_ref = &my_key,
.btf_val_ref = &type_int,
};The advantage being that map_def is no longer modified for each instance and k/v combination. And I get my assignment to k/v members :)
But really, I give up, I can't come up with anything better :)
explicit maps. Was: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 21 lines · Jakub Kicinski
Quoted 2 lines · Alexei Starovoitov
the solution we're discussing should solve
BPF_ANNOTATE_KV_PAIRtoo. That hack must go.I see.
Quoted 6 lines
If I understood your objections to Andrii's format is that you don't like pointer part of key/value while Andrii explained why we picked the pointer, right?
So how about:
Quoted 8 lines
struct { int type; int max_entries; struct { __u32 key; struct my_value value; } types[]; } ...
Quoted 3 lines
My objection is that k/v fields are never initialized, so they're "metafields", mixed with real fields which hold parameters - like type,
max_entriesetc.
I don't share this meta fields vs real fields distinction. All of the fields are meta.
Kernel implementation of the map doesn't need to hold type and max_entries as actual configuration fields.
The map definition in c++ would have looked like:
bpf::hash_map<int, struct my_value, 1000, NO_PREALLOC> foo; bpf::array_map<struct my_value, 2000> bar;
Sometime key is not necessary. Sometimes flags have to be zero. bpf syscall api is a superset of all fiels for all maps. All of them are configuration and meta fields at the same time. In c++ example there is really no difference between 'struct my_value' and '1000' attributes.
I'm pretty sure bpf will have C++ front-end in the future, but until then we have to deal with C and, I think, the map definition should be the most natural C syntax.
In that sense what you're proposing with extern:
Quoted 13 lines
extern struct
my_keymy_key;
extern inttype_int;struct map_def { int type; int max_entries; void *btf_key_ref; void *btf_val_ref; } = { ... .btf_key_ref = &my_key, .btf_val_ref = &type_int, };
is worse than
struct map_def {
int type;
int max_entries;
int btf_key;
struct my_key btf_value;
};imo explicit key and value would be ideal,
but they take too much space. Hence pointers
or zero sized array:
struct {
int type;
int max_entries;
struct {
__u32 key;
struct my_value value;
} types[];
};I think we should also consider explicit map creation.
Something like:
struct my_map {
__u32 key;
struct my_value value;
} *my_hash_map, *my_pinned_hash_map;
struct {
__u64 key; struct my_map *value;
} *my_hash_of_maps;
struct {
struct my_map *value;
} *my_array_of_maps;
__init void create_my_maps(void)
{
bpf_create_hash_map(&my_hash_map, 1000/*max_entries*/); bpf_obj_get(&my_pinned_hash_map, "/sys/fs/bpf/my_map"); bpf_create_hash_of_maps(&my_hash_of_maps, 1000/*max_entries*/); bpf_create_array_of_maps(&my_array_of_maps, 20);
}
SEC("cgroup/skb")
int bpf_prog(struct __sk_buff *skb)
{
struct my_value *val;
__u32 key;
__u64 key64;
struct my_map *map;
val = bpf_map_lookup(my_hash_map, &key);
map = bpf_map_lookup(my_hash_of_maps, &key64);
}
'__init' section will be compiled by llvm into bpf instructions that will be executed in users space by libbpf.
The __init prog has to succeed otherwise prog load fails.
May be all map pointers should be in a special section to avoid putting them into datasec, but libbpf should be able to figure that out without requiring user to specify the .map section. The rest of global vars would go into special datasec map.
No llvm changes necessary and BTF is available for keys and values.
libbpf can start with simple __init and eventually grow into complex init procedure where maps are initialized, prog_array is populated, etc.
Thoughts?
Re: explicit maps. Was: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 70 lines · Alexei Starovoitov
Quoted 21 lines · Jakub Kicinski
Quoted 2 lines · Alexei Starovoitov
the solution we're discussing should solve
BPF_ANNOTATE_KV_PAIRtoo. That hack must go.I see.
Quoted 6 lines
If I understood your objections to Andrii's format is that you don't like pointer part of key/value while Andrii explained why we picked the pointer, right?
So how about:
Quoted 8 lines
struct { int type; int max_entries; struct { __u32 key; struct my_value value; } types[]; } ...Quoted 3 lines
My objection is that k/v fields are never initialized, so they're "metafields", mixed with real fields which hold parameters - like type,
max_entriesetc.I don't share this meta fields vs real fields distinction. All of the fields are meta.
Kernel implementation of the map doesn't need to hold type andmax_entriesas actual configuration fields.
The map definition in c++ would have looked like:
bpf::hash_map<int, structmy_value, 1000,NO_PREALLOC> foo; bpf::array_map<structmy_value, 2000> bar;Sometime key is not necessary. Sometimes flags have to be zero. bpf syscall api is a superset of all fiels for all maps. All of them are configuration and meta fields at the same time. In c++ example there is really no difference between 'struct
my_value' and '1000' attributes.I'm pretty sure bpf will have C++ front-end in the future, but until then we have to deal with C and, I think, the map definition should be the most natural C syntax.
In that sense what you're proposing with extern:Quoted 13 lines
extern struct
my_keymy_key;
extern inttype_int;struct map_def { int type; int max_entries; void *btf_key_ref; void *btf_val_ref; } = { ... .btf_key_ref = &my_key, .btf_val_ref = &type_int, };is worse than
struct map_def { int type; int max_entries; int btf_key; struct my_key btf_value; };imo explicit key and value would be ideal,
but they take too much space. Hence pointers
or zero sized array:
Quoted 8 lines
struct {
int type;
int max_entries;
struct {
__u32 key;
struct my_value value;
} types[];
};It is a C syntax problem, I do agree with you that it works well for templates. The map_def structure holds parameters, and we can't take a type as a value in C. Hence the types[] in your proposal - you could as well call them ghost_fields[] :)
Quoted 47 lines
I think we should also consider explicit map creation.
Something like:
struct my_map { __u32 key; struct my_value value; } *my_hash_map, *my_pinned_hash_map;struct { __u64 key;struct
my_map*value;
}*my_hash_of_maps;struct { struct my_map *value; } *my_array_of_maps;
__initvoidcreate_my_maps(void){ bpf_create_hash_map(&my_hash_map, 1000/*max_entries*/); bpf_obj_get(&my_pinned_hash_map, "/sys/fs/bpf/my_map"); bpf_create_hash_of_maps(&my_hash_of_maps, 1000/*max_entries*/); bpf_create_array_of_maps(&my_array_of_maps, 20); }
SEC("cgroup/skb")
intbpf_prog(struct __sk_buff *skb){ struct my_value *val; __u32 key; __u64 key64; struct my_map *map; val = bpf_map_lookup(my_hash_map, &key); map = bpf_map_lookup(my_hash_of_maps, &key64); }'
__init' section will be compiled by llvm into bpf instructions that will be executed in users space by libbpf.
The__initprog has to succeed otherwise prog load fails.May be all map pointers should be in a special section to avoid putting them into datasec, but libbpf should be able to figure that out without requiring user to specify the .map section. The rest of global vars would go into special datasec map.
Quoted 7 lines
No llvm changes necessary and BTF is available for keys and values.
libbpf can start with simple
__initand eventually grow into complex init procedure where maps are initialized,prog_arrayis populated, etc.Thoughts?
I like it! :)
Re: explicit maps. Was: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
In reply to Alexei StarovoitovQuoted 23 lines · Alexei Starovoitov
Quoted 21 lines · Jakub Kicinski
Quoted 2 lines · Alexei Starovoitov
the solution we're discussing should solve
BPF_ANNOTATE_KV_PAIRtoo. That hack must go.I see.
Quoted 14 lines
If I understood your objections to Andrii's format is that you don't like pointer part of key/value while Andrii explained why we picked the pointer, right?
So how about:
struct { int type; int max_entries; struct { __u32 key; struct my_value value; } types[]; } ...
Quoted 5 lines
Quoted 3 lines
My objection is that k/v fields are never initialized, so they're "metafields", mixed with real fields which hold parameters - like type,
max_entriesetc.I don't share this meta fields vs real fields distinction.
100% agree.
Quoted 33 lines
All of the fields are meta.
Kernel implementation of the map doesn't need to hold type andmax_entriesas actual configuration fields.
The map definition in c++ would have looked like:
bpf::hash_map<int, structmy_value, 1000,NO_PREALLOC> foo; bpf::array_map<structmy_value, 2000> bar;Sometime key is not necessary. Sometimes flags have to be zero. bpf syscall api is a superset of all fiels for all maps. All of them are configuration and meta fields at the same time. In c++ example there is really no difference between 'struct
my_value' and '1000' attributes.I'm pretty sure bpf will have C++ front-end in the future, but until then we have to deal with C and, I think, the map definition should be the most natural C syntax.
In that sense what you're proposing with extern:Quoted 13 lines
extern struct
my_keymy_key;
extern inttype_int;struct map_def { int type; int max_entries; void *btf_key_ref; void *btf_val_ref; } = { ... .btf_key_ref = &my_key, .btf_val_ref = &type_int, };is worse than
Quoted 8 lines
struct map_def { int type; int max_entries; int btf_key; struct my_key btf_value; };imo explicit key and value would be ideal,
also agree 100%, that's how I started, but then was quickly pointed to a real cases where value is just way too big.
Quoted 10 lines
but they take too much space. Hence pointers
or zero sized array:struct { int type; int max_entries; struct { __u32 key; struct my_value value; } types[]; };
This works, but I still prefer simpler
__u32 *key;
struct my_value *value;
It has less visual clutter and doesn't rely on somewhat obscure flexible array feature (and it will have to be last in the struct, unless you do zero-sized array w/ [0]).
Quoted 48 lines
I think we should also consider explicit map creation.
Something like:
struct my_map { __u32 key; struct my_value value; } *my_hash_map, *my_pinned_hash_map;struct { __u64 key;struct
my_map*value;
}*my_hash_of_maps;struct { struct my_map *value; } *my_array_of_maps;
__initvoidcreate_my_maps(void){ bpf_create_hash_map(&my_hash_map, 1000/*max_entries*/); bpf_obj_get(&my_pinned_hash_map, "/sys/fs/bpf/my_map"); bpf_create_hash_of_maps(&my_hash_of_maps, 1000/*max_entries*/); bpf_create_array_of_maps(&my_array_of_maps, 20); }
SEC("cgroup/skb")
intbpf_prog(struct __sk_buff *skb){ struct my_value *val; __u32 key; __u64 key64; struct my_map *map; val = bpf_map_lookup(my_hash_map, &key); map = bpf_map_lookup(my_hash_of_maps, &key64); }'
__init' section will be compiled by llvm into bpf instructions that will be executed in users space by libbpf.
The__initprog has to succeed otherwise prog load fails.May be all map pointers should be in a special section to avoid putting them into datasec, but libbpf should be able to figure that out without requiring user to specify the .map section. The rest of global vars would go into special datasec map.
Quoted 7 lines
No llvm changes necessary and BTF is available for keys and values.
libbpf can start with simple
__initand eventually grow into complex init procedure where maps are initialized,prog_arrayis populated, etc.Thoughts?
I have few. :)
I think it would be great to have this feature as a sort of "escape hatch" for really complicated initialization of maps, which can't be done w/ declarative syntax (and doing it from user-land driving app is not possible/desirable). But there is a lot of added complexity and work to be done to make this happen:
1. We'll need to build BPF interpreter into libbpf (so partial duplication of in-kernel BPF machinery);
2. We'll need to define some sort of user-space BPF API, so that these init functions can call into libbpf API (at least). So now in addition to in-kernel BPF helpers, we'll have another and different set of helpers/APIs exposed to user-land BPF code. This will certainly add confusion and raise learning curve.
3. Next we'll be adding not-just-libbpf APIs, for cases where the size of map depends on some system parameter (e.g., number of CPUs, or amount of free RAM, or something else). This probably can be done through exposed libbpf APIs again, but now we'll need to decide what gets exposed, in what format, etc.
It's all doable, but looks like a very large effort, while we yet don't have a realistic use case for this. Today cases like that are handled by driving user-land app. It seems like having prog_array and map-in-map declarative initialization covers a lot of advanced use cases (plus, of course, pinning), so for starters I'd concentrate effort there to get declarative approach powerful enough to address a lot of real-world needs.
The good thing, though, is that nothing prevents us from specifying and adding this later, once we have good use cases and most needs already covered w/ declarative syntax.
But, assuming we do explicit map creation, I'd also vote for per-map "factory" functions, like this:
typedef int (*map_factory_fn)(struct bpf_map); /* can be provided by libbpf */
int init_my_map(struct bpf_map *map)
{
/* something fancy here */
}struct {
__u64 *key;
struct my_value *value;
map_factory_fn factory;
} my_map SEC(".maps") = { .factory = &init_my_map,
};
/* we can still have per-BPF object init function: */
int init_my_app(struct bpf_object *obj) {
/* some more initialization of BPF object */
}Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
In reply to Andrii NakryikoQuoted 71 lines · Andrii Nakryiko
This patch adds support for a new way to define BPF maps. It relies on BTF to describe mandatory and optional attributes of a map, as well as captures type information of key and value naturally. This eliminates the need for
BPF_ANNOTATE_KV_PAIRhack and ensures key/value sizes are always in sync with the key/value type.Relying on BTF, this approach allows for both forward and backward compatibility w.r.t. extending supported map definition features. Old libbpf implementation will ignore fields it doesn't recognize, while new implementations will parse and recognize new optional attributes.
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
2. The map declaration and initialization is done through
a global/static variable of a struct type with few mandatory and extra optional fields:
- type field is mandatory and specified type of BPF map;
- key/value fields are mandatory and capture key/value type/size information;
-max_entriesattribute is optional; ifmax_entriesis not specified or initialized, it has to be provided in runtime through libbpf API before loadingbpf_object;
-map_flagsis optional and if not defined, will be assumed to be 0.
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Usekey_sizeandvalue_sizefields to do that (see example below).Here's an example of simple ARRAY map defintion:
struct
my_value{ int x, y, z; };struct { int type; int max_entries; int *key; struct my_value *value; } btf_map SEC(".maps") = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};This will define BPF ARRAY map '
btf_map' with 16 elements. The key will be of type int and thus key size will be 4 bytes. The value is structmy_valueof size 12 bytes. This map can be used from C code exactly the same as with existing maps defined through structbpf_map_def.Here's an example of STACKMAP definition (which currently disallows BTF type IDs for key/value):
struct { __u32 type; __u32 max_entries; __u32 map_flags; __u32 key_size; __u32 value_size; } stackmap SEC(".maps") = {.type =
BPF_MAP_TYPE_STACK_TRACE,
.max_entries = 128,
.map_flags =BPF_F_STACK_BUILD_ID,
.key_size =sizeof(__u32),
.value_size =PERF_MAX_STACK_DEPTH*sizeof(struct bpf_stack_build_id),
};
Quoted 4 lines
This approach is naturally extended to support map-in-map, by making a value field to be another struct that describes inner map. This feature is not implemented yet. It's also possible to incrementally add features like pinning with full backwards and forward compatibility.
So I wanted to elaborate a bit more on what I'm planning to add, once we agree on the approach. Those are the features that are currently supported by iproute2 loader and here's how I was thinking to support them with BTF-defined maps. Once all this is implemented, there should be just a mechanical field rename to switch BPF apps relying on iproute2 loader (size_key -> key_size, size_value -> value_size, max_elem -> max_entries) for most maps. For more complicated cases described below, I hope we can agree it's easy to migrate and end result might even look better (because more explicit).
1. Pinning. This one is simple:
- add pinning attribute, that will either be "no pinning", "global
pinning", "object-scope pinning".
- by default pinning root will be "/sys/fs/bpf", but one will be
able to override this per-object using extra options (so that "/sys/fs/bpf/tc" can be specified).
2. Map-in-map declaration:
As outlined at LSF/MM, we can extend value type to be another map definition, specifying a prototype for inner map:
struct {
int type;
int max_entries;
struct outer_key *key;
struct { /* this is definition of inner map */
int type;
int max_entries;
struct inner_key *key;
struct inner_value *value;
} value;
} my_hash_of_arrays BPF_MAP = {
.type = BPF_MAP_TYPE_HASH_OF_MAPS,
.max_entries = 1024,
.value = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 64,
},
};This would declare a hash_of_maps, where inner maps are arrays of 64 elements each. Notice, that struct defining inner map can be declared outside and shared with other maps:
struct inner_map_t {
int type;
int max_entries;
struct inner_key *key;
struct inner_value *value;
};struct {
int type;
int max_entries;
struct outer_key *key;
struct inner_map_t value;
} my_hash_of_arrays BPF_MAP = {
.type = BPF_MAP_TYPE_HASH_OF_MAPS,
.max_entries = 1024,
.value = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 64,
},
};3. Initialization of prog array. Iproute2 supports a convention-driven initialization of BPF_MAP_TYPE_PROG_ARRAY using special section names (wrapped into __section_tail(ID, IDX)):
struct bpf_elf_map SEC("maps") POLICY_CALL_MAP = {
.type = BPF_MAP_TYPE_PROG_ARRAY,
.id = MAP_ID,
.size_key = sizeof(__u32),
.size_value = sizeof(__u32),
.max_elem = 16,
};__section_tail(MAP_ID, MAP_IDX) int handle_policy(struct __sk_buff *skb)
{
...
}For each such program, iproute2 will put its FD (for later tail-calling) into a corresponding MAP with id == MAP_ID at index MAP_IDX.
Here's how I see this supported in BTF-defined maps case.
typedef int (* skbuff_tailcall_fn)(struct __sk_buff *);
struct {
int type;
int max_entries;
int *key;
skbuff_tailcall_fb value[];
} POLICY_CALL_MAP SEC(".maps") = {
.type = BPF_MAP_TYPE_PROG_ARRAY,
.max_entries = 16,
.value = {
&handle_policy,
NULL,
&handle_some_other_policy,
},
};libbpf loader will greate BPF_MAP_TYPE_PROG_ARRAY map with 16 elements and will initialize first and third entries with FDs of handle_policy and handle_some_other_policy programs. As an added nice bonus, compiler should also warn on signature mismatch. ;)
4. We can extend this idea into ARRAY_OF_MAPS initialization. This is currently implemented in iproute2 using .id, .inner_id, and .inner_idx fields.
struct inner_map_t {
int type;
int max_entries;
struct inner_key *key;
struct inner_value *value;
};struct inner_map_t map1 = {...};
struct inner_map_t map2 = {...};
struct {
int type;
int max_entries;
struct outer_key *key;
struct inner_map_t value[];
} my_hash_of_arrays BPF_MAP = {
.type = BPF_MAP_TYPE_ARRAY_OF_MAPS,
.max_entries = 2,
.value = {
&map1,
&map2,
},
};There are a bunch of slight variations we might consider (e.g., value vs values, when there is inline initialization, is it an array of structs or an array of pointers to structs, etc), but the overall idea stays the same.
So when all this is implemented and supported, from looking at Cilium, it seems like conversion of iproute2 to libbpf should be rather simple and painless. I'd be curious to hear what Cilium folks are thinking about that.
Quoted 3 lines
Signed-off-by Andrii Nakryiko <[email protected]>---
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
In reply to Andrii NakryikoThanks for sending this RFC! For me, the biggest draw is that map-in-map would be so much nicer to use, plus automatic dumping of map values.
Others on the thread have raised this point already: not everybody lives on the bleeding edge or can control all of their dependencies. To me this means that having a good compatibility story is paramount. I'd like to have very clear rules how the presence / absence of fields is handled.
For example:
- Fields that are present but not understood are an error. This makes sense because
the user can simply omit the field in their definition if they do
not use it. It's also necessary
to preserve the freedom to add new fields in the future without
risking user breakage.
- If libbpf adds support for a new field, it must be optional. Seems like this is what current
map extensions already do, so maybe a no-brainer.
Somewhat related to this: I really wish that BTF was self-describing, e.g. possible
to parse without understanding all types. I mentioned this in another thread of yours,
but the more we add features where BTF is required the more important it becomes IMO.
Finally, some nits inline:
Quoted 5 lines · Andrii Nakryiko
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
I'd prefer using a new map section "btf_maps" or whatever. No need to worry about code that deals with either type.
Quoted 5 lines
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
My biggest concern with the pointer is that there are cases when we want to _not_ use a pointer, e.g. your proposal for map in map and tail calling. There we need value to be a struct, an array, etc. The burden on the user for this is very high.
Quoted 4 lines
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Use
key_sizeandvalue_sizefields to do that (see example below).
Why not just make them use the legacy map?
Signature · 4 lines
Lorenz Bauer | Systems Engineer 6th Floor, County Hall/The Riverside Building, SE1 7PB, UK www.cloudflare.com
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 8 lines · Lorenz Bauer
Thanks for sending this RFC! For me, the biggest draw is that map-in-map would be so much nicer to use, plus automatic dumping of map values.
Others on the thread have raised this point already: not everybody lives on the bleeding edge or can control all of their dependencies. To me this means that having a good compatibility story is paramount. I'd like to have very clear rules how the presence / absence of fields is handled.
I think that discussion was more about selftests being switched to BTF-defined maps rather than BPF users having to switch to latest compiler. struct bpf_map_def is still supported for those who can't use clang that supports BTF_KIND_VAR/BTF_KIND_DATASEC. So I don't think this enforces anyone to switch compiler, but certainly incentivizes them :)
Quoted 8 lines
For example:
- Fields that are present but not understood are an error. This makes sense because
the user can simply omit the field in their definition if they do
not use it. It's also necessary
to preserve the freedom to add new fields in the future without
risking user breakage.
So you are arguing for strict-by-default behavior. It's fine by me, but exactly that strict-by-default behavior is the problem with BTF extensivility, that you care a lot about. You are advocating for skipping unknown BTF types (if it was possible), which is directly opposite to strict-by-default behavior. I have no strong preference here, but given amount of problem (and how many times we missed this problem in the past) w/ introducing new BTF feature and then forgetting about doing something for older kernels, kind of makes me lean towards skip-and-log behavior. But I'm happy to support both (through flags) w/ strict by default.
Quoted 3 lines
- If libbpf adds support for a new field, it must be optional. Seems like this is what current
map extensions already do, so maybe a no-brainer.
Yeah, of course.
Quoted 7 lines
Somewhat related to this: I really wish that BTF was self-describing, e.g. possible
to parse without understanding all types. I mentioned this in another thread of yours,
but the more we add features where BTF is required the more important it becomes IMO.
I relate, but have no new and better solution than previously discussed :) We should try to add new stuff to .BTF.ext as much as possible, which is self-describing.
Quoted 5 lines
Finally, some nits inline:
Quoted 1 line · Andrii Nakryiko
Quoted 7 lines
Quoted 4 lines
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.I'd prefer using a new map section "
btf_maps" or whatever. No need to worry about code that deals with either type.
We do use new map section. Its ".maps" vs "maps". Difference is subtle, but ".maps" looks a bit more "standardized" than "btf_maps" to me (and hopefully, eventually no one will use "maps" anymore :) ).
Quoted 11 lines
Quoted 6 lines
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
My biggest concern with the pointer is that there are cases when we want to _not_ use a pointer, e.g. your proposal for map in map and tail calling. There we need value to be a struct, an array, etc. The burden on the user for this is very high.
Well, map-in-map is still a special case and whichever syntax we go with, it will need to be of slightly different syntax to distinguish between those cases. Initialized maps fall into similar category, IMHO.
Embedding full value just to capture type info/size is unacceptable, as we have use cases that cause too big ELF size increase, which will prevent users from switching to this.
Quoted 7 lines
Quoted 5 lines
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Use
key_sizeandvalue_sizefields to do that (see example below).Why not just make them use the legacy map?
For completeness' sake at the least. E.g., what if you want to use map-in-map, where inner map is stackmap or something like that, which requires key_size/value_size? I think we all agree that it's better if application uses just one style, instead of a mix of both, right? Btw, for map cases where map key can be arbitrary, but value is FD or some other opaque value, libbpf can automatically "derive" value size and still capture key type. I haven't done that, but it's very easy to do (and also we can keep adding per-map-type checks/niceties, to help users understand what's wrong with their map definition, instead of getting EINVAL from kernel on map creation).
Quoted 6 lines
--
Lorenz Bauer | Systems Engineer
6th Floor, County Hall/The Riverside Building, SE1 7PB, UKwww.cloudflare.com
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 27 lines · Andrii Nakryiko
Quoted 8 lines · Lorenz Bauer
Thanks for sending this RFC! For me, the biggest draw is that map-in-map would be so much nicer to use, plus automatic dumping of map values.
Others on the thread have raised this point already: not everybody lives on the bleeding edge or can control all of their dependencies. To me this means that having a good compatibility story is paramount. I'd like to have very clear rules how the presence / absence of fields is handled.
I think that discussion was more about selftests being switched to BTF-defined maps rather than BPF users having to switch to latest compiler. struct
bpf_map_defis still supported for those who can't use clang that supports BTF_KIND_VAR/BTF_KIND_DATASEC. So I don't think this enforces anyone to switch compiler, but certainly incentivizes them :)Quoted 8 lines
For example:
- Fields that are present but not understood are an error. This makes sense because
the user can simply omit the field in their definition if they do
not use it. It's also necessary
to preserve the freedom to add new fields in the future without
risking user breakage.
Quoted 10 lines
So you are arguing for strict-by-default behavior. It's fine by me, but exactly that strict-by-default behavior is the problem with BTF extensivility, that you care a lot about. You are advocating for skipping unknown BTF types (if it was possible), which is directly opposite to strict-by-default behavior. I have no strong preference here, but given amount of problem (and how many times we missed this problem in the past) w/ introducing new BTF feature and then forgetting about doing something for older kernels, kind of makes me lean towards skip-and-log behavior. But I'm happy to support both (through flags) w/ strict by default.
In my mind, BPF loaders should be able to pass through BTF to the kernel as a binary blob as much as possible. That's why I want the format to be "self describing". Compatibility then becomes a question of: what feature are you using on which kernel. The kernel itself can then still be strict-by-default or what have you.
Quoted 29 lines
Quoted 4 lines
- If libbpf adds support for a new field, it must be optional. Seems like this is what current
map extensions already do, so maybe a no-brainer.Yeah, of course.
Quoted 7 lines
Somewhat related to this: I really wish that BTF was self-describing, e.g. possible
to parse without understanding all types. I mentioned this in another thread of yours,
but the more we add features where BTF is required the more important it becomes IMO.I relate, but have no new and better solution than previously discussed :) We should try to add new stuff to .BTF.ext as much as possible, which is self-describing.
Quoted 10 lines
Finally, some nits inline:
Quoted 5 lines · Andrii Nakryiko
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
Quoted 6 lines
Quoted 2 lines
I'd prefer using a new map section "
btf_maps" or whatever. No need to worry about code that deals with either type.We do use new map section. Its ".maps" vs "maps". Difference is subtle, but ".maps" looks a bit more "standardized" than "
btf_maps" to me (and hopefully, eventually no one will use "maps" anymore :) ).
Phew, spotting that difference is night impossible IMO.
Quoted 13 lines
Quoted 8 lines
Quoted 7 lines
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
Quoted 4 lines
My biggest concern with the pointer is that there are cases when we want to _not_ use a pointer, e.g. your proposal for map in map and tail calling. There we need value to be a struct, an array, etc. The burden on the user for this is very high.
Quoted 4 lines
Well, map-in-map is still a special case and whichever syntax we go with, it will need to be of slightly different syntax to distinguish between those cases. Initialized maps fall into similar category, IMHO.
I agree with you, the syntax probably has to be different. I'd just like it to differ by more than a "*" in the struct definition, because that is too small to notice.
Quoted 11 lines
Embedding full value just to capture type info/size is unacceptable, as we have use cases that cause too big ELF size increase, which will prevent users from switching to this.
Quoted 6 lines
Quoted 5 lines
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Use
key_sizeandvalue_sizefields to do that (see example below).
Quoted 6 lines
Quoted 1 line
Why not just make them use the legacy map?
For completeness' sake at the least. E.g., what if you want to use map-in-map, where inner map is stackmap or something like that, which requires key_size/value_size? I think we all agree that it's better if application uses just one style, instead of a mix of both, right?
I kind of assumed that BTF support for those maps would at some point appear, maybe I should have checked that.
Quoted 13 lines
Btw, for map cases where map key can be arbitrary, but value is FD or some other opaque value, libbpf can automatically "derive" value size and still capture key type. I haven't done that, but it's very easy to do (and also we can keep adding per-map-type checks/niceties, to help users understand what's wrong with their map definition, instead of getting EINVAL from kernel on map creation).
Quoted 6 lines
--
Lorenz Bauer | Systems Engineer
6th Floor, County Hall/The Riverside Building, SE1 7PB, UKwww.cloudflare.com
Signature · 4 lines
Lorenz Bauer | Systems Engineer 6th Floor, County Hall/The Riverside Building, SE1 7PB, UK www.cloudflare.com
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 40 lines · Lorenz Bauer
Quoted 27 lines · Andrii Nakryiko
Quoted 8 lines · Lorenz Bauer
Thanks for sending this RFC! For me, the biggest draw is that map-in-map would be so much nicer to use, plus automatic dumping of map values.
Others on the thread have raised this point already: not everybody lives on the bleeding edge or can control all of their dependencies. To me this means that having a good compatibility story is paramount. I'd like to have very clear rules how the presence / absence of fields is handled.
I think that discussion was more about selftests being switched to BTF-defined maps rather than BPF users having to switch to latest compiler. struct
bpf_map_defis still supported for those who can't use clang that supports BTF_KIND_VAR/BTF_KIND_DATASEC. So I don't think this enforces anyone to switch compiler, but certainly incentivizes them :)Quoted 8 lines
For example:
- Fields that are present but not understood are an error. This makes sense because
the user can simply omit the field in their definition if they do
not use it. It's also necessary
to preserve the freedom to add new fields in the future without
risking user breakage.Quoted 10 lines
So you are arguing for strict-by-default behavior. It's fine by me, but exactly that strict-by-default behavior is the problem with BTF extensivility, that you care a lot about. You are advocating for skipping unknown BTF types (if it was possible), which is directly opposite to strict-by-default behavior. I have no strong preference here, but given amount of problem (and how many times we missed this problem in the past) w/ introducing new BTF feature and then forgetting about doing something for older kernels, kind of makes me lean towards skip-and-log behavior. But I'm happy to support both (through flags) w/ strict by default.
Quoted 5 lines
In my mind, BPF loaders should be able to pass through BTF to the kernel as a binary blob as much as possible. That's why I want the format to be "self describing". Compatibility then becomes a question of: what feature are you using on which kernel. The kernel itself can then still be strict-by-default or what have you.
That would work in ideal world, where kernel is updated frequently (and BTF is self-describing, which it is not). In practice, though, libbpf is far more up-to-date and lends its hand on "sanitizing" .BTF from kernel-unsupported features (so far we manage to pull this off very reasonably). If you have a good proposal how to make .BTF self-describing, that would be great!
Quoted 30 lines
Quoted 30 lines
Quoted 5 lines
- If libbpf adds support for a new field, it must be optional. Seems like this is what current
map extensions already do, so maybe a no-brainer.Yeah, of course.
Quoted 7 lines
Somewhat related to this: I really wish that BTF was self-describing, e.g. possible
to parse without understanding all types. I mentioned this in another thread of yours,
but the more we add features where BTF is required the more important it becomes IMO.I relate, but have no new and better solution than previously discussed :) We should try to add new stuff to .BTF.ext as much as possible, which is self-describing.
Quoted 10 lines
Finally, some nits inline:
Quoted 5 lines · Andrii Nakryiko
The outline of the new map definition (short, BTF-defined maps) is as follows:
1. All the maps should be defined in .maps ELF section. It's possible to have both "legacy" map definitions inmapssections and BTF-defined maps in .maps sections. Everything will still work transparently.
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
I'd prefer using a new map section "
btf_maps" or whatever. No need to worry about code that deals with either type.We do use new map section. Its ".maps" vs "maps". Difference is subtle, but ".maps" looks a bit more "standardized" than "
btf_maps" to me (and hopefully, eventually no one will use "maps" anymore :) ).Phew, spotting that difference is night impossible IMO.
Eventually "maps" should die off, as people switch from bpf_map_def to to BTF-defined maps in .maps. Libbpf itself can just provide a macro hiding all that, something like:
#define BPF_MAP __attribute__((section(".maps"), used))
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
Quoted 8 lines
3. Key/value fields should be **a pointer** to a type describing key/value. The pointee type is assumed (and will be recorded as such and used for size determination) to be a type describing key/value of the map. This is done to save excessive amounts of space allocated in corresponding ELF sections for key/value of big size.
My biggest concern with the pointer is that there are cases when we want to _not_ use a pointer, e.g. your proposal for map in map and tail calling. There we need value to be a struct, an array, etc. The burden on the user for this is very high.
Quoted 8 lines
Quoted 4 lines
Well, map-in-map is still a special case and whichever syntax we go with, it will need to be of slightly different syntax to distinguish between those cases. Initialized maps fall into similar category, IMHO.
I agree with you, the syntax probably has to be different. I'd just like it to differ by more than a "*" in the struct definition, because that is too small to notice.
So let's lay out how it will be done in practice:
1. Simple map w/ custom key/value
struct my_key { ... };
struct my_value { ... };
struct {
__u32 type;
__u32 max_entries;
struct my_key *key;
struct my_value *value;
} my_simple_map BPF_MAP = { .type = BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};
2. Now map-in-map:
struct {
__u32 type;
__u32 max_entries;
struct my_key *key;
struct {
__u32 type;
__u32 max_entries;
__u64 *key;
struct my_value *value;
} value;
} my_map_in_map BPF_MAP = {
.type = BPF_MAP_TYPE_HASH_OF_MAPS,
.max_entries = 16,
.value = {
.type = BPF_MAP_TYPE_ARRAY,
.max_entries = 100,
},
};It's clearly hard to misinterpret inner map definition for a custom anonymous struct type, right?
Quoted 14 lines
Quoted 14 lines
Embedding full value just to capture type info/size is unacceptable, as we have use cases that cause too big ELF size increase, which will prevent users from switching to this.
Quoted 7 lines
Quoted 5 lines
4. As some maps disallow having BTF type ID associated with key/value, it's possible to specify key/value size explicitly without associating BTF type ID with it. Use
key_sizeandvalue_sizefields to do that (see example below).Why not just make them use the legacy map?
Quoted 7 lines
Quoted 4 lines
For completeness' sake at the least. E.g., what if you want to use map-in-map, where inner map is stackmap or something like that, which requires key_size/value_size? I think we all agree that it's better if application uses just one style, instead of a mix of both, right?
I kind of assumed that BTF support for those maps would at some point appear, maybe I should have checked that.
It will. Current situation with maps not supporting specifying BTF for key and/or value looks more like a bug, than feature and we should fix that. But even if we fix it today, kernels are updated much slower than libbpf, so by not supporting key_size/value_size, we force people to get stuck with legacy bpf_map_def for a really long time.
Quoted 22 lines
Quoted 14 lines
Btw, for map cases where map key can be arbitrary, but value is FD or some other opaque value, libbpf can automatically "derive" value size and still capture key type. I haven't done that, but it's very easy to do (and also we can keep adding per-map-type checks/niceties, to help users understand what's wrong with their map definition, instead of getting EINVAL from kernel on map creation).
Quoted 6 lines
--
Lorenz Bauer | Systems Engineer
6th Floor, County Hall/The Riverside Building, SE1 7PB, UKwww.cloudflare.com
--
Lorenz Bauer | Systems Engineer
6th Floor, County Hall/The Riverside Building, SE1 7PB, UKwww.cloudflare.com
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 6 lines · Andrii Nakryiko
Quoted 5 lines
In my mind, BPF loaders should be able to pass through BTF to the kernel as a binary blob as much as possible. That's why I want the format to be "self describing". Compatibility then becomes a question of: what feature are you using on which kernel. The kernel itself can then still be strict-by-default or what have you.
Quoted 6 lines
That would work in ideal world, where kernel is updated frequently (and BTF is self-describing, which it is not). In practice, though, libbpf is far more up-to-date and lends its hand on "sanitizing" .BTF from kernel-unsupported features (so far we manage to pull this off very reasonably). If you have a good proposal how to make .BTF self-describing, that would be great!
I think sanitizing is going to become a problem, but we've been around that argument a few times :)
Making .BTF self describing need at least adding length to certain fields, as I mentioned in another thread. Plus an interface to interrogate the kernel about a loaded BTF blob.
Quoted 42 lines
Quoted 3 lines
I agree with you, the syntax probably has to be different. I'd just like it to differ by more than a "*" in the struct definition, because that is too small to notice.
So let's lay out how it will be done in practice:
1. Simple map w/ custom key/value
struct
my_key{ ... };
structmy_value{ ... };struct { __u32 type; __u32 max_entries; struct my_key *key; struct my_value *value; } my_simple_map BPF_MAP = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};2. Now map-in-map:
struct { __u32 type; __u32 max_entries; struct my_key *key; struct { __u32 type; __u32 max_entries; __u64 *key; struct my_value *value; } value; } my_map_in_map BPF_MAP = { .type = BPF_MAP_TYPE_HASH_OF_MAPS, .max_entries = 16, .value = { .type = BPF_MAP_TYPE_ARRAY, .max_entries = 100, }, };
Quoted 2 lines
It's clearly hard to misinterpret inner map definition for a custom anonymous struct type, right?
That's not what I'm concerned about. My point is: sometimes you have to use a pointer, sometimes you don't. Every user has to learn this. Chance is, they'll probably get it wrong first. Is there a way to give a reasonable error message for this?
Quoted 8 lines
Quoted 2 lines
I kind of assumed that BTF support for those maps would at some point appear, maybe I should have checked that.
It will. Current situation with maps not supporting specifying BTF for key and/or value looks more like a bug, than feature and we should fix that. But even if we fix it today, kernels are updated much slower than libbpf, so by not supporting key_size/value_size, we force people to get stuck with legacy
bpf_map_deffor a really long time.
OK.
I'll go and look at the newest revision of the patch set now :o)
Signature · 4 lines
Lorenz Bauer | Systems Engineer 6th Floor, County Hall/The Riverside Building, SE1 7PB, UK www.cloudflare.com
Re: [RFC PATCH bpf-next 6/8] libbpf: allow specifying map definitions using BTF
Quoted 15 lines · Lorenz Bauer
Quoted 6 lines · Andrii Nakryiko
Quoted 5 lines
In my mind, BPF loaders should be able to pass through BTF to the kernel as a binary blob as much as possible. That's why I want the format to be "self describing". Compatibility then becomes a question of: what feature are you using on which kernel. The kernel itself can then still be strict-by-default or what have you.
Quoted 6 lines
That would work in ideal world, where kernel is updated frequently (and BTF is self-describing, which it is not). In practice, though, libbpf is far more up-to-date and lends its hand on "sanitizing" .BTF from kernel-unsupported features (so far we manage to pull this off very reasonably). If you have a good proposal how to make .BTF self-describing, that would be great!
Quoted 2 lines
I think sanitizing is going to become a problem, but we've been around that argument a few times :)
Yep :)
Quoted 47 lines
Making .BTF self describing need at least adding length to certain fields, as I mentioned in another thread. Plus an interface to interrogate the kernel about a loaded BTF blob.
Quoted 42 lines
Quoted 3 lines
I agree with you, the syntax probably has to be different. I'd just like it to differ by more than a "*" in the struct definition, because that is too small to notice.
So let's lay out how it will be done in practice:
1. Simple map w/ custom key/value
struct
my_key{ ... };
structmy_value{ ... };struct { __u32 type; __u32 max_entries; struct my_key *key; struct my_value *value; } my_simple_map BPF_MAP = {.type =
BPF_MAP_TYPE_ARRAY,
.max_entries = 16,
};2. Now map-in-map:
struct { __u32 type; __u32 max_entries; struct my_key *key; struct { __u32 type; __u32 max_entries; __u64 *key; struct my_value *value; } value; } my_map_in_map BPF_MAP = { .type = BPF_MAP_TYPE_HASH_OF_MAPS, .max_entries = 16, .value = { .type = BPF_MAP_TYPE_ARRAY, .max_entries = 100, }, };
Quoted 7 lines
Quoted 2 lines
It's clearly hard to misinterpret inner map definition for a custom anonymous struct type, right?
That's not what I'm concerned about. My point is: sometimes you have to use a pointer, sometimes you don't. Every user has to learn this. Chance is, they'll probably get it wrong first. Is there a way to give a reasonable error message for this?
Right now pointer is always required. My initial intent for map-in-map was to not use pointer, but since then I've proposed a slightly different approach, which eliminates all these concerns you mentioned. As for messaging, yeah, that the simplest part, which can always be improved.
Quoted 19 lines
Quoted 9 lines
Quoted 3 lines
I kind of assumed that BTF support for those maps would at some point appear, maybe I should have checked that.
It will. Current situation with maps not supporting specifying BTF for key and/or value looks more like a bug, than feature and we should fix that. But even if we fix it today, kernels are updated much slower than libbpf, so by not supporting key_size/value_size, we force people to get stuck with legacy
bpf_map_deffor a really long time.OK.
I'll go and look at the newest revision of the patch set now :o)
--
Lorenz Bauer | Systems Engineer
6th Floor, County Hall/The Riverside Building, SE1 7PB, UKwww.cloudflare.com
RFC PATCH 7/8 selftests/bpf: add test for BTF-defined maps
In reply to Andrii NakryikoAdd file test for BTF-defined map definition.
--- .../selftests/bpf/progs/test_btf_newkv.c | 73 +++++++++++++++++++ tools/testing/selftests/bpf/test_btf.c | 10 +-- 2 files changed, 76 insertions(+), 7 deletions(-) create mode 100644 tools/testing/selftests/bpf/progs/test_btf_newkv.c
tools/testing/selftests/bpf/progs/test_btf_newkv.c new file +73 -0
@@ -0,0 +1,73 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* Copyright (c) 2018 Facebook */ +#include <linux/bpf.h> +#include "bpf_helpers.h" + +int _version SEC("version") = 1; + +struct ipv_counts { +unsigned int v4; +unsigned int v6; +}; + +/* just to validate we can handle maps in multiple sections */ +struct bpf_map_def SEC("maps") btf_map_legacy = { + .type = BPF_MAP_TYPE_ARRAY, + .key_size = sizeof(int), + .value_size = sizeof(long long), + .max_entries = 4, +}; + +BPF_ANNOTATE_KV_PAIR(btf_map_legacy, int, struct ipv_counts); + +struct { +int *key; +struct ipv_counts *value; +unsigned int type; +unsigned int max_entries; +} btf_map SEC(".maps") = { + .type = BPF_MAP_TYPE_ARRAY, + .max_entries = 4, +}; + +struct dummy_tracepoint_args { +unsigned long long pad; +struct sock *sock; +}; + +__attribute__((noinline)) +static int test_long_fname_2 (struct dummy_tracepoint_args *arg) +{ +struct ipv_counts *counts; +int key =0 ; + +if (!arg->sock) +return 0 ; + + counts =bpf_map_lookup_elem (&btf_map, &key); +if (!counts) +return 0 ; + + counts->v6++; + +/* just verify we can reference both maps */ + counts =bpf_map_lookup_elem (&btf_map_legacy, &key); +if (!counts) +return 0 ; + +return 0 ; +} + +__attribute__((noinline)) +static int test_long_fname_1 (struct dummy_tracepoint_args *arg) +{ +return test_long_fname_2 (arg); +} + +SEC("dummy_tracepoint") +int _dummy_tracepoint (struct dummy_tracepoint_args *arg) +{ +return test_long_fname_1 (arg); +} + +char _license[] SEC("license") = "GPL";
tools/testing/selftests/bpf/test_btf.c +3 -7
@@ -4016,13 +4016,9 @@ struct btf_file_test { };static struct btf_file_test file_tests[] = { -{ - .file ="test_btf_haskv.o" , -}, -{ - .file ="test_btf_nokv.o" , - .btf_kv_notfound = true, -}, + { .file ="test_btf_haskv.o" , }, + { .file ="test_btf_newkv.o" , }, + { .file ="test_btf_nokv.o" , .btf_kv_notfound = true, }, };static int do_test_file (unsigned int test_num)
Signature · 1 line
2.17.1
RFC PATCH 8/8 selftests/bpf: switch tests to BTF-defined map definitions
In reply to Andrii NakryikoSwitch test map definition to new BTF-defined format.
--- tools/testing/selftests/bpf/progs/bpf_flow.c | 18 +++-- .../selftests/bpf/progs/get_cgroup_id_kern.c | 18 +++-- .../testing/selftests/bpf/progs/netcnt_prog.c | 22 +++--- .../selftests/bpf/progs/sample_map_ret0.c | 18 +++-- .../selftests/bpf/progs/socket_cookie_prog.c | 9 ++- .../bpf/progs/sockmap_verdict_prog.c | 36 +++++++--- .../bpf/progs/test_get_stack_rawtp.c | 27 ++++--- .../selftests/bpf/progs/test_global_data.c | 27 ++++--- tools/testing/selftests/bpf/progs/test_l4lb.c | 45 ++++++++---- .../selftests/bpf/progs/test_l4lb_noinline.c | 45 ++++++++---- .../selftests/bpf/progs/test_map_in_map.c | 20 ++++-- .../selftests/bpf/progs/test_map_lock.c | 22 +++--- .../testing/selftests/bpf/progs/test_obj_id.c | 9 ++- .../bpf/progs/test_select_reuseport_kern.c | 45 ++++++++---- .../bpf/progs/test_send_signal_kern.c | 22 +++--- .../bpf/progs/test_skb_cgroup_id_kern.c | 9 ++- .../bpf/progs/test_sock_fields_kern.c | 60 +++++++++------- .../selftests/bpf/progs/test_spin_lock.c | 33 ++++----- .../bpf/progs/test_stacktrace_build_id.c | 44 ++++++++---- .../selftests/bpf/progs/test_stacktrace_map.c | 40 +++++++---- .../testing/selftests/bpf/progs/test_tc_edt.c | 9 ++- .../bpf/progs/test_tcp_check_syncookie_kern.c | 9 ++- .../selftests/bpf/progs/test_tcp_estats.c | 9 ++- .../selftests/bpf/progs/test_tcpbpf_kern.c | 18 +++-- .../selftests/bpf/progs/test_tcpnotify_kern.c | 18 +++-- tools/testing/selftests/bpf/progs/test_xdp.c | 18 +++-- .../selftests/bpf/progs/test_xdp_noinline.c | 60 ++++++++++------ .../selftests/bpf/test_queue_stack_map.h | 20 ++++-- .../testing/selftests/bpf/test_sockmap_kern.h | 72 +++++++++++++------ 29 files changed, 526 insertions(+), 276 deletions(-)
tools/testing/selftests/bpf/progs/bpf_flow.c +13 -5
@@ -57,17 +57,25 @@ struct frag_hdr {__be32 identification; }; -struct bpf_map_def SEC("maps") jmp_table = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} jmp_table SEC(".maps") = { .type = BPF_MAP_TYPE_PROG_ARRAY, + .max_entries = 8, .key_size = sizeof(__u32), .value_size = sizeof(__u32), - .max_entries =8 }; -struct bpf_map_def SEC("maps") last_dissection = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct bpf_flow_keys *value; +} last_dissection SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(struct bpf_flow_keys), .max_entries = 1, };
tools/testing/selftests/bpf/progs/get_cgroup_id_kern.c +12 -6
@@ -4,17 +4,23 @@#include <linux/bpf.h> #include "bpf_helpers.h" -struct bpf_map_def SEC("maps") cg_ids = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} cg_ids SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 1, }; -struct bpf_map_def SEC("maps") pidmap = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u32 *value; +} pidmap SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u32), .max_entries = 1, };
tools/testing/selftests/bpf/progs/netcnt_prog.c +10 -12
@@ -10,24 +10,22 @@#define REFRESH_TIME_NS 100000000#define NS_PER_SEC 1000000000 -struct bpf_map_def SEC("maps") percpu_netcnt = { +struct { +__u32 type; +struct bpf_cgroup_storage_key *key; +struct percpu_net_cnt *value; +} percpu_netcnt SEC(".maps") = { .type = BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE, - .key_size = sizeof(struct bpf_cgroup_storage_key), - .value_size = sizeof(struct percpu_net_cnt), }; -BPF_ANNOTATE_KV_PAIR(percpu_netcnt, struct bpf_cgroup_storage_key, - struct percpu_net_cnt); - -struct bpf_map_def SEC("maps") netcnt = { +struct { +__u32 type; +struct bpf_cgroup_storage_key *key; +struct net_cnt *value; +} netcnt SEC(".maps") = { .type =BPF_MAP_TYPE_CGROUP_STORAGE , - .key_size = sizeof(struct bpf_cgroup_storage_key), - .value_size = sizeof(struct net_cnt), }; -BPF_ANNOTATE_KV_PAIR(netcnt, struct bpf_cgroup_storage_key, - struct net_cnt); - SEC("cgroup/skb")int bpf_nextcnt (struct __sk_buff *skb) {
tools/testing/selftests/bpf/progs/sample_map_ret0.c +12 -6
@@ -2,17 +2,23 @@#include <linux/bpf.h> #include "bpf_helpers.h" -struct bpf_map_def SEC("maps") htab = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +long *value; +} htab SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(__u32), - .value_size = sizeof(long), .max_entries = 2, }; -struct bpf_map_def SEC("maps") array = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +long *value; +} array SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(long), .max_entries = 2, };
tools/testing/selftests/bpf/progs/socket_cookie_prog.c +6 -3
@@ -7,10 +7,13 @@#include "bpf_helpers.h" #include "bpf_endian.h" -struct bpf_map_def SEC("maps") socket_cookies = { +struct { +__u32 type; +__u32 max_entries; +__u64 *key; +__u32 *value; +} socket_cookies SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(__u64), - .value_size = sizeof(__u32), .max_entries = 1 << 8, };
tools/testing/selftests/bpf/progs/sockmap_verdict_prog.c +27 -9
@@ -5,31 +5,49 @@ int _version SEC("version") = 1; -struct bpf_map_def SEC("maps") sock_map_rx = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} sock_map_rx SEC(".maps") = { .type = BPF_MAP_TYPE_SOCKMAP, + .max_entries = 20, .key_size = sizeof(int), .value_size = sizeof(int), - .max_entries = 20, }; -struct bpf_map_def SEC("maps") sock_map_tx = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} sock_map_tx SEC(".maps") = { .type = BPF_MAP_TYPE_SOCKMAP, + .max_entries = 20, .key_size = sizeof(int), .value_size = sizeof(int), - .max_entries = 20, }; -struct bpf_map_def SEC("maps") sock_map_msg = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} sock_map_msg SEC(".maps") = { .type = BPF_MAP_TYPE_SOCKMAP, + .max_entries = 20, .key_size = sizeof(int), .value_size = sizeof(int), - .max_entries = 20, }; -struct bpf_map_def SEC("maps") sock_map_break = { +struct { +__u32 type; +__u32 max_entries; +int *key; +int *value; +} sock_map_break SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(int), - .value_size = sizeof(int), .max_entries = 20, };
tools/testing/selftests/bpf/progs/test_get_stack_rawtp.c +19 -8
@@ -15,17 +15,25 @@ struct stack_trace_t {struct bpf_stack_build_id user_stack_buildid[MAX_STACK_RAWTP ]; }; -struct bpf_map_def SEC("maps") perfmap = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} perfmap SEC(".maps") = { .type = BPF_MAP_TYPE_PERF_EVENT_ARRAY, + .max_entries = 2, .key_size = sizeof(int), .value_size = sizeof(__u32), - .max_entries = 2, }; -struct bpf_map_def SEC("maps") stackdata_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct stack_trace_t *value; +} stackdata_map SEC(".maps") = { .type = BPF_MAP_TYPE_PERCPU_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(struct stack_trace_t), .max_entries = 1, };
@@ -47,10 +55,13 @@ struct bpf_map_def SEC("maps") stackdata_map = {* issue and avoid complicated C programming massaging. * This is an acceptable workaround since there is one entry here. */ -struct bpf_map_def SEC("maps") rawdata_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 (*value)[2 *MAX_STACK_RAWTP ]; +} rawdata_map SEC(".maps") = { .type = BPF_MAP_TYPE_PERCPU_ARRAY, - .key_size = sizeof(__u32), - .value_size = MAX_STACK_RAWTP * sizeof(__u64) * 2, .max_entries = 1, };
tools/testing/selftests/bpf/progs/test_global_data.c +18 -9
@@ -7,17 +7,23 @@#include "bpf_helpers.h" -struct bpf_map_def SEC("maps") result_number = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} result_number SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 11, }; -struct bpf_map_def SEC("maps") result_string = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +const char (*value)[32 ]; +} result_string SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = 32, .max_entries = 5, };
@@ -27,10 +33,13 @@ struct foo {__u64 c; }; -struct bpf_map_def SEC("maps") result_struct = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct foo *value; +} result_struct SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(struct foo), .max_entries = 5, };
tools/testing/selftests/bpf/progs/test_l4lb.c +30 -15
68 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_l4lb_noinline.c +30 -15
68 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_map_in_map.c +14 -6
@@ -5,22 +5,30 @@#include <linux/types.h> #include "bpf_helpers.h" -struct bpf_map_def SEC("maps") mim_array = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} mim_array SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY_OF_MAPS, + .max_entries = 1, .key_size = sizeof(int),/* must be sizeof(__u32) for map in map */ .value_size = sizeof(__u32), - .max_entries = 1, - .map_flags = 0, }; -struct bpf_map_def SEC("maps") mim_hash = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} mim_hash SEC(".maps") = { .type = BPF_MAP_TYPE_HASH_OF_MAPS, + .max_entries = 1, .key_size = sizeof(int),/* must be sizeof(__u32) for map in map */ .value_size =sizeof (__u32), - .max_entries = 1, - .map_flags = 0, };SEC ("xdp_mimtest" )
tools/testing/selftests/bpf/progs/test_map_lock.c +12 -10
@@ -11,29 +11,31 @@ struct hmap_elem {int var[VAR_NUM ]; }; -struct bpf_map_def SEC("maps") hash_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct hmap_elem *value; +} hash_map SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(int), - .value_size = sizeof(struct hmap_elem), .max_entries = 1, }; -BPF_ANNOTATE_KV_PAIR(hash_map, int, struct hmap_elem); -struct array_elem {struct bpf_spin_lock lock;int var[VAR_NUM ]; }; -struct bpf_map_def SEC("maps") array_map = { +struct { +__u32 type; +__u32 max_entries; +int *key; +struct array_elem *value; +} array_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(int), - .value_size = sizeof(struct array_elem), .max_entries =1 , }; -BPF_ANNOTATE_KV_PAIR(array_map, int, struct array_elem); - SEC("map_lock_demo")int bpf_map_lock_test (struct __sk_buff *skb) {
tools/testing/selftests/bpf/progs/test_obj_id.c +6 -3
@@ -16,10 +16,13 @@ int _version SEC("version") = 1; -struct bpf_map_def SEC("maps") test_map_id = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} test_map_id SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 1, };
tools/testing/selftests/bpf/progs/test_select_reuseport_kern.c +31 -14
69 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_send_signal_kern.c +12 -10
@@ -4,24 +4,26 @@#include <linux/version.h> #include "bpf_helpers.h" -struct bpf_map_def SEC("maps") info_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} info_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 1, }; -BPF_ANNOTATE_KV_PAIR (info_map, __u32, __u64); - -struct bpf_map_def SEC("maps") status_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} status_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 1, }; -BPF_ANNOTATE_KV_PAIR (status_map, __u32, __u64); - SEC("send_signal_demo")int bpf_send_signal_test (void *ctx) {
tools/testing/selftests/bpf/progs/test_skb_cgroup_id_kern.c +6 -3
@@ -10,10 +10,13 @@#define NUM_CGROUP_LEVELS 4 -struct bpf_map_def SEC("maps") cgroup_ids = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} cgroup_ids SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = NUM_CGROUP_LEVELS, };
tools/testing/selftests/bpf/progs/test_sock_fields_kern.c +36 -24
93 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_spin_lock.c +17 -16
@@ -10,30 +10,29 @@ struct hmap_elem {int test_padding; }; -struct bpf_map_def SEC("maps") hmap = { +struct { +__u32 type; +__u32 max_entries; +int *key; +struct hmap_elem *value; +} hmap SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(int), - .value_size = sizeof(struct hmap_elem), .max_entries = 1, }; -BPF_ANNOTATE_KV_PAIR(hmap, int, struct hmap_elem); - -struct cls_elem {struct bpf_spin_lock lock;volatile int cnt; }; -struct bpf_map_def SEC("maps") cls_map = { +struct { +__u32 type; +struct bpf_cgroup_storage_key *key; +struct cls_elem *value; +} cls_map SEC(".maps") = { .type = BPF_MAP_TYPE_CGROUP_STORAGE, - .key_size = sizeof(struct bpf_cgroup_storage_key), - .value_size = sizeof(struct cls_elem), }; -BPF_ANNOTATE_KV_PAIR(cls_map, struct bpf_cgroup_storage_key, - struct cls_elem); -struct bpf_vqueue {struct bpf_spin_lock lock;/* 4 byte hole */
@@ -42,14 +41,16 @@ struct bpf_vqueue {unsigned int rate; }; -struct bpf_map_def SEC("maps") vqueue = { +struct { +__u32 type; +__u32 max_entries; +int *key; +struct bpf_vqueue *value; +} vqueue SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(int), - .value_size = sizeof(struct bpf_vqueue), .max_entries = 1, }; -BPF_ANNOTATE_KV_PAIR(vqueue, int, struct bpf_vqueue);#define CREDIT_PER_NS (delta, rate) (((delta) * rate) >> 20)SEC ("spin_lock_demo" )
tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c +30 -14
64 lines not on this page · raw message
tools/testing/selftests/bpf/progs/test_stacktrace_map.c +28 -12
@@ -8,31 +8,47 @@#define PERF_MAX_STACK_DEPTH 127#endif -struct bpf_map_def SEC("maps") control_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u32 *value; +} control_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u32), .max_entries = 1, }; -struct bpf_map_def SEC("maps") stackid_hmap = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u32 *value; +} stackid_hmap SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(__u32), - .value_size = sizeof(__u32), .max_entries = 16384, }; -struct bpf_map_def SEC("maps") stackmap = { +typedef __u64 stack_trace_t [PERF_MAX_STACK_DEPTH ]; + +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} stackmap SEC(".maps") = { .type = BPF_MAP_TYPE_STACK_TRACE, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64) * PERF_MAX_STACK_DEPTH, .max_entries = 16384, + .key_size = sizeof(__u32), + .value_size = sizeof(stack_trace_t), }; -struct bpf_map_def SEC("maps") stack_amap = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 (*value)[PERF_MAX_STACK_DEPTH ]; +} stack_amap SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64) * PERF_MAX_STACK_DEPTH, .max_entries = 16384, };
tools/testing/selftests/bpf/progs/test_tc_edt.c +6 -3
@@ -16,10 +16,13 @@#define THROTTLE_RATE_BPS (5 * 1000 * 1000)/* flow_key => last_tstamp timestamp used */ -struct bpf_map_def SEC("maps") flow_map = { +struct { +__u32 type; +__u32 max_entries; +uint32_t *key; +uint64_t *value; +} flow_map SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(uint32_t), - .value_size = sizeof(uint64_t), .max_entries = 1, };
tools/testing/selftests/bpf/progs/test_tcp_check_syncookie_kern.c +6 -3
@@ -16,10 +16,13 @@#include "bpf_helpers.h" #include "bpf_endian.h" -struct bpf_map_def SEC("maps") results = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} results SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 1, };
tools/testing/selftests/bpf/progs/test_tcp_estats.c +6 -3
@@ -148,10 +148,13 @@ struct tcp_estats_basic_event {struct tcp_estats_conn_id conn_id; }; -struct bpf_map_def SEC("maps") ev_record_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct tcp_estats_basic_event *value; +} ev_record_map SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(__u32), - .value_size = sizeof(struct tcp_estats_basic_event), .max_entries = 1024, };
tools/testing/selftests/bpf/progs/test_tcpbpf_kern.c +12 -6
@@ -14,17 +14,23 @@#include "bpf_endian.h" #include "test_tcpbpf.h" -struct bpf_map_def SEC("maps") global_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct tcpbpf_globals *value; +} global_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(struct tcpbpf_globals), .max_entries = 4, }; -struct bpf_map_def SEC("maps") sockopt_results = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +int *value; +} sockopt_results SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(int), .max_entries = 2, };
tools/testing/selftests/bpf/progs/test_tcpnotify_kern.c +13 -5
@@ -14,18 +14,26 @@#include "bpf_endian.h" #include "test_tcpnotify.h" -struct bpf_map_def SEC("maps") global_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +struct tcpnotify_globals *value; +} global_map SEC(".maps") = { .type = BPF_MAP_TYPE_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(struct tcpnotify_globals), .max_entries = 4, }; -struct bpf_map_def SEC("maps") perf_event_map = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} perf_event_map SEC(".maps") = { .type = BPF_MAP_TYPE_PERF_EVENT_ARRAY, + .max_entries = 2, .key_size = sizeof(int), .value_size = sizeof(__u32), - .max_entries = 2, }; int _version SEC("version") = 1;
tools/testing/selftests/bpf/progs/test_xdp.c +12 -6
@@ -22,17 +22,23 @@ int _version SEC("version") = 1; -struct bpf_map_def SEC("maps") rxcnt = { +struct { +__u32 type; +__u32 max_entries; +__u32 *key; +__u64 *value; +} rxcnt SEC(".maps") = { .type = BPF_MAP_TYPE_PERCPU_ARRAY, - .key_size = sizeof(__u32), - .value_size = sizeof(__u64), .max_entries = 256, }; -struct bpf_map_def SEC("maps") vip2tnl = { +struct { +__u32 type; +__u32 max_entries; +struct vip *key; +struct iptnl_info *value; +} vip2tnl SEC(".maps") = { .type = BPF_MAP_TYPE_HASH, - .key_size = sizeof(struct vip), - .value_size = sizeof(struct iptnl_info), .max_entries = MAX_IPTNL_ENTRIES, };
tools/testing/selftests/bpf/progs/test_xdp_noinline.c +37 -23
89 lines not on this page · raw message
tools/testing/selftests/bpf/test_queue_stack_map.h +14 -6
@@ -10,20 +10,28 @@ int _version SEC("version") = 1; -struct bpf_map_def __attribute__ ((section ("maps" ), used)) map_in = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} map_in SEC(".maps") = { .type = MAP_TYPE, + .max_entries = 32, .key_size = 0, .value_size = sizeof(__u32), - .max_entries =32 , - .map_flags =0 , }; -struct bpf_map_def __attribute__ ((section ("maps" ), used)) map_out = { +struct { +__u32 type; +__u32 max_entries; +__u32 key_size; +__u32 value_size; +} map_out SEC(".maps") = { .type = MAP_TYPE, + .max_entries = 32, .key_size = 0, .value_size =sizeof (__u32), - .max_entries =32 , - .map_flags =0 , };SEC ("test" )
tools/testing/selftests/bpf/test_sockmap_kern.h +51 -21
110 lines not on this page · raw message
Signature · 1 line
2.17.1
kernel test robot
build bot[selftests/bpf] 84da156938: kernel_selftests.bpf.test_maps.fail
FYI, we noticed the following commit (built with gcc-7):
FYI, we noticed the following commit (built with gcc-7):
commit: 84da156938373b0f072b4a1394f199949631a081 ("[RFC PATCH bpf-next 8/8] selftests/bpf: switch tests to BTF-defined map definitions")
url: https://github.com/0day-ci/linux/commits/Andrii-Nakryiko/BTF-defined-BPF-map-definitions/20190602-062423
base: https://git.kernel.org/cgit/linux/kernel/git/bpf/bpf-next.git master
in testcase: kernel_selftests
with following parameters:
group: kselftests-00
test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
ok 1 selftests: bpf: test_verifier
# selftests: bpf: test_tag
# test_tag: OK (40945 tests)
ok 2 selftests: bpf: test_tag
# selftests: bpf: test_maps
# libbpf: BTF is required, but is missing or corrupted. # Failed to load SK_SKB verdict prog
not ok 3 selftests: bpf: test_maps
# selftests: bpf: test_lru_map
# nr_cpus:2
#
# test_lru_sanity0 (map_type:9 map_flags:0x0): Pass # test_lru_sanity1 (map_type:9 map_flags:0x0): Pass # test_lru_sanity2 (map_type:9 map_flags:0x0): Pass # test_lru_sanity3 (map_type:9 map_flags:0x0): Pass # test_lru_sanity4 (map_type:9 map_flags:0x0): Pass # test_lru_sanity5 (map_type:9 map_flags:0x0): Pass # test_lru_sanity7 (map_type:9 map_flags:0x0): Pass # test_lru_sanity8 (map_type:9 map_flags:0x0): Pass # # test_lru_sanity0 (map_type:10 map_flags:0x0): Pass # test_lru_sanity1 (map_type:10 map_flags:0x0): Pass # test_lru_sanity2 (map_type:10 map_flags:0x0): Pass # test_lru_sanity3 (map_type:10 map_flags:0x0): Pass # test_lru_sanity4 (map_type:10 map_flags:0x0): Pass # test_lru_sanity5 (map_type:10 map_flags:0x0): Pass # test_lru_sanity7 (map_type:10 map_flags:0x0): Pass # test_lru_sanity8 (map_type:10 map_flags:0x0): Pass # # test_lru_sanity0 (map_type:9 map_flags:0x2): Pass # test_lru_sanity4 (map_type:9 map_flags:0x2): Pass # test_lru_sanity6 (map_type:9 map_flags:0x2): Pass # test_lru_sanity7 (map_type:9 map_flags:0x2): Pass # test_lru_sanity8 (map_type:9 map_flags:0x2): Pass # # test_lru_sanity0 (map_type:10 map_flags:0x2): Pass # test_lru_sanity4 (map_type:10 map_flags:0x2): Pass # test_lru_sanity6 (map_type:10 map_flags:0x2): Pass # test_lru_sanity7 (map_type:10 map_flags:0x2): Pass # test_lru_sanity8 (map_type:10 map_flags:0x2): Pass # ok 4 selftests: bpf: test_lru_map # selftests: bpf: test_lpm_map # test_lpm: OK ok 5 selftests: bpf: test_lpm_map # selftests: bpf: test_progs
To reproduce:
# build kernel cd linux cp config-5.2.0-rc2-00579-g84da156 .config make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 prepare make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 modules_prepare make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 SHELL=/bin/bash make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.2.0-rc2 Kernel Configuration
#
#
# Compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
#CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=70300CONFIG_CLANG_VERSION=0CONFIG_CC_HAS_ASM_GOTO=yCONFIG_CC_HAS_WARN_MAYBE_UNINITIALIZED=yCONFIG_IRQ_WORK=yCONFIG_BUILDTIME_EXTABLE_SORT=yCONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_BUILD_SALT=""CONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not setCONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_CROSS_MEMORY_ATTACH=yCONFIG_USELIB=yCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_PENDING_IRQ=yCONFIG_GENERIC_IRQ_MIGRATION=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=yCONFIG_GENERIC_IRQ_RESERVATION_MODE=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_ARCH_CLOCKSOURCE_DATA=yCONFIG_ARCH_CLOCKSOURCE_INIT=yCONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=yCONFIG_GENERIC_CMOS_UPDATE=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not setCONFIG_NO_HZ_FULL=yCONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not setCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
# CONFIG_PREEMPT_NONE is not setCONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not setCONFIG_PREEMPT_COUNT=y
#
# CPU/Task time and stats accounting
#CONFIG_VIRT_CPU_ACCOUNTING=yCONFIG_VIRT_CPU_ACCOUNTING_GEN=y
# CONFIG_IRQ_TIME_ACCOUNTING is not setCONFIG_HAVE_SCHED_AVG_IRQ=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_NOCB_CPU=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS_PROC is not setCONFIG_LOG_BUF_SHIFT=20CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=yCONFIG_ARCH_SUPPORTS_NUMA_BALANCING=yCONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=yCONFIG_ARCH_SUPPORTS_INT128=yCONFIG_NUMA_BALANCING=yCONFIG_NUMA_BALANCING_DEFAULT_ENABLED=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_SWAP_ENABLED=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not setCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=yCONFIG_CGROUP_PIDS=yCONFIG_CGROUP_RDMA=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_HUGETLB=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_CGROUP_PERF=yCONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_DEBUG is not setCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_CHECKPOINT_RESTORE=yCONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not setCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SYSCTL=yCONFIG_HAVE_UID16=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_BPF=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not setCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_PRINTK_NMI=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KALLSYMS_ABSOLUTE_PERCPU=yCONFIG_KALLSYMS_BASE_RELATIVE=yCONFIG_BPF_SYSCALL=yCONFIG_BPF_JIT_ALWAYS_ON=yCONFIG_USERFAULTFD=yCONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=yCONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not setCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=y
# CONFIG_PC104 is not set
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_MEMCG_SYSFS_ON is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not setCONFIG_SLUB_CPU_PARTIAL=yCONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_64BIT=yCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_FILTER_PGPROT=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=yCONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=yCONFIG_X86_64_SMP=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_DYNAMIC_PHYSICAL_MASK=y CONFIG_PGTABLE_LEVELS=5 CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
#
# Processor type and features
#CONFIG_ZONE_DMA=yCONFIG_SMP=yCONFIG_X86_FEATURE_NAMES=yCONFIG_X86_X2APIC=yCONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not setCONFIG_RETPOLINE=yCONFIG_X86_CPU_RESCTRL=yCONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not setCONFIG_X86_UV=y
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_MID is not setCONFIG_X86_INTEL_LPSS=yCONFIG_X86_AMD_PLATFORM_DEVICE=yCONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not setCONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=yCONFIG_PARAVIRT_XXL=y
# CONFIG_PARAVIRT_DEBUG is not setCONFIG_PARAVIRT_SPINLOCKS=yCONFIG_XEN=yCONFIG_XEN_PV=yCONFIG_XEN_PV_SMP=y
# CONFIG_XEN_DOM0 is not setCONFIG_XEN_PVHVM=yCONFIG_XEN_PVHVM_SMP=yCONFIG_XEN_512GB=yCONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_PVH is not setCONFIG_KVM_GUEST=y
# CONFIG_PVH is not set
# CONFIG_KVM_DEBUG_FS is not setCONFIG_PARAVIRT_TIME_ACCOUNTING=yCONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not setCONFIG_GENERIC_CPU=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=64CONFIG_X86_DEBUGCTLMSR=y
# CONFIG_PROCESSOR_SELECT is not setCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_HYGON=yCONFIG_CPU_SUP_CENTAUR=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not setCONFIG_MAXSMP=yCONFIG_NR_CPUS_RANGE_BEGIN=8192CONFIG_NR_CPUS_RANGE_END=8192CONFIG_NR_CPUS_DEFAULT=8192CONFIG_NR_CPUS=8192CONFIG_SCHED_SMT=yCONFIG_SCHED_MC=yCONFIG_SCHED_MC_PRIO=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=yCONFIG_X86_MCE=yCONFIG_X86_MCELOG_LEGACY=yCONFIG_X86_MCE_INTEL=yCONFIG_X86_MCE_AMD=yCONFIG_X86_MCE_THRESHOLD=yCONFIG_X86_MCE_INJECT=mCONFIG_X86_THERMAL_VECTOR=y
#
# Performance monitoring
#CONFIG_PERF_EVENTS_INTEL_UNCORE=yCONFIG_PERF_EVENTS_INTEL_RAPL=yCONFIG_PERF_EVENTS_INTEL_CSTATE=y
# CONFIG_PERF_EVENTS_AMD_POWER is not set
# end of Performance monitoring
CONFIG_X86_16BIT=yCONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=yCONFIG_I8K=mCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=yCONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_X86_5LEVEL=yCONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set CONFIG_ARCH_HAS_MEM_ENCRYPT=y CONFIG_AMD_MEM_ENCRYPT=y
# CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set CONFIG_NUMA=yCONFIG_AMD_NUMA=yCONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64CONFIG_MTRR=yCONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=yCONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=yCONFIG_X86_SMAP=yCONFIG_X86_INTEL_UMIP=yCONFIG_X86_INTEL_MPX=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_EFI=yCONFIG_EFI_STUB=yCONFIG_EFI_MIXED=yCONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not setCONFIG_HZ_1000=yCONFIG_HZ=1000CONFIG_SCHED_HRTICK=yCONFIG_KEXEC=yCONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y CONFIG_KEXEC_VERIFY_SIG=y CONFIG_KEXEC_BZIMAGE_VERIFY_SIG=y CONFIG_CRASH_DUMP=yCONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=yCONFIG_RANDOMIZE_BASE=yCONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=yCONFIG_LIVEPATCH=y
# end of Processor type and features
CONFIG_ARCH_HAS_ADD_PAGES=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_USE_PERCPU_NUMA_NODE_ID=yCONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=yCONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=yCONFIG_ARCH_ENABLE_THP_MIGRATION=y
#
# Power management and ACPI options
#CONFIG_ARCH_HIBERNATION_HEADER=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not setCONFIG_HIBERNATE_CALLBACKS=yCONFIG_HIBERNATION=yCONFIG_PM_STD_PARTITION=""CONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=yCONFIG_PM_DEBUG=yCONFIG_PM_ADVANCED_DEBUG=y
# CONFIG_PM_TEST_SUSPEND is not setCONFIG_PM_SLEEP_DEBUG=y
# CONFIG_DPM_WATCHDOG is not setCONFIG_PM_TRACE=yCONFIG_PM_TRACE_RTC=yCONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not setCONFIG_ARCH_SUPPORTS_ACPI=yCONFIG_ACPI=yCONFIG_ACPI_LEGACY_TABLES_LOOKUP=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not setCONFIG_ACPI_SPCR_TABLE=yCONFIG_ACPI_LPIT=yCONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS_POWER is not setCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=yCONFIG_ACPI_EC_DEBUGFS=mCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=mCONFIG_ACPI_FAN=y
# CONFIG_ACPI_TAD is not setCONFIG_ACPI_DOCK=yCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_CPPC_LIB=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_IPMI=mCONFIG_ACPI_HOTPLUG_CPU=yCONFIG_ACPI_PROCESSOR_AGGREGATOR=mCONFIG_ACPI_THERMAL=yCONFIG_ACPI_NUMA=yCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not setCONFIG_ACPI_PCI_SLOT=yCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_MEMORY=yCONFIG_ACPI_HOTPLUG_IOAPIC=yCONFIG_ACPI_SBS=mCONFIG_ACPI_HED=yCONFIG_ACPI_CUSTOM_METHOD=mCONFIG_ACPI_BGRT=y
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not setCONFIG_ACPI_NFIT=m
# CONFIG_NFIT_SECURITY_DEBUG is not set
# CONFIG_ACPI_HMAT is not setCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=yCONFIG_ACPI_APEI=yCONFIG_ACPI_APEI_GHES=yCONFIG_ACPI_APEI_PCIEAER=yCONFIG_ACPI_APEI_MEMORY_FAILURE=yCONFIG_ACPI_APEI_EINJ=mCONFIG_ACPI_APEI_ERST_DEBUG=y
# CONFIG_DPTF_POWER is not setCONFIG_ACPI_WATCHDOG=yCONFIG_ACPI_EXTLOG=mCONFIG_ACPI_ADXL=y
# CONFIG_PMIC_OPREGION is not set
# CONFIG_ACPI_CONFIGFS is not setCONFIG_X86_PM_TIMER=yCONFIG_SFI=y
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
# CONFIG_CPU_FREQ_GOV_SCHEDUTIL is not set
#
# CPU frequency scaling drivers
#CONFIG_X86_INTEL_PSTATE=yCONFIG_X86_PCC_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ_CPB=yCONFIG_X86_POWERNOW_K8=mCONFIG_X86_AMD_FREQ_SENSITIVITY=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not setCONFIG_X86_P4_CLOCKMOD=m
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=m # end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not setCONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
# end of CPU Idle
CONFIG_INTEL_IDLE=y
# end of Power management and ACPI options
#
# Bus options (PCI etc.)
#CONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_XEN=yCONFIG_MMCONF_FAM10H=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_ISA_BUS is not setCONFIG_ISA_DMA_API=yCONFIG_AMD_NB=y
# CONFIG_X86_SYSFB is not set
# end of Bus options (PCI etc.)
#
# Binary Emulations
#CONFIG_IA32_EMULATION=y
# CONFIG_X86_X32 is not setCONFIG_COMPAT_32=yCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=y
# end of Binary Emulations
CONFIG_X86_DEV_DMA_OPS=yCONFIG_HAVE_GENERIC_GUP=y
#
# Firmware Drivers
#CONFIG_EDD=m
# CONFIG_EDD_OFF is not setCONFIG_FIRMWARE_MEMMAP=yCONFIG_DMIID=yCONFIG_DMI_SYSFS=yCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=yCONFIG_ISCSI_IBFT_FIND=yCONFIG_ISCSI_IBFT=mCONFIG_FW_CFG_SYSFS=y
# CONFIG_FW_CFG_SYSFS_CMDLINE is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_VARS=yCONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=yCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=yCONFIG_EFI_RUNTIME_MAP=y
# CONFIG_EFI_FAKE_MEMMAP is not setCONFIG_EFI_RUNTIME_WRAPPERS=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFI_TEST is not setCONFIG_APPLE_PROPERTIES=y
# CONFIG_RESET_ATTACK_MITIGATION is not set
# end of EFI (Extensible Firmware Interface) Support
CONFIG_UEFI_CPER=yCONFIG_UEFI_CPER_X86=yCONFIG_EFI_DEV_PATH_PARSER=yCONFIG_EFI_EARLYCON=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_HAVE_KVM=yCONFIG_HAVE_KVM_IRQCHIP=yCONFIG_HAVE_KVM_IRQFD=yCONFIG_HAVE_KVM_IRQ_ROUTING=yCONFIG_HAVE_KVM_EVENTFD=yCONFIG_KVM_MMIO=yCONFIG_KVM_ASYNC_PF=yCONFIG_HAVE_KVM_MSI=yCONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=yCONFIG_KVM_VFIO=yCONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=yCONFIG_KVM_COMPAT=yCONFIG_HAVE_KVM_IRQ_BYPASS=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=mCONFIG_KVM_INTEL=mCONFIG_KVM_AMD=mCONFIG_KVM_AMD_SEV=yCONFIG_KVM_MMU_AUDIT=yCONFIG_VHOST_NET=m
# CONFIG_VHOST_SCSI is not setCONFIG_VHOST_VSOCK=mCONFIG_VHOST=m
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_HOTPLUG_SMT=yCONFIG_OPROFILE=mCONFIG_OPROFILE_EVENT_MULTIPLEX=yCONFIG_HAVE_OPROFILE=yCONFIG_OPROFILE_NMI_TIMER=yCONFIG_KPROBES=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not setCONFIG_OPTPROBES=yCONFIG_KPROBES_ON_FTRACE=yCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_KRETPROBES=yCONFIG_USER_RETURN_NOTIFIER=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_ARCH_HAS_SET_DIRECT_MAP=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=yCONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_FUNCTION_ARG_ACCESS_API=yCONFIG_HAVE_CLK=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=yCONFIG_HAVE_RCU_TABLE_FREE=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_ALIGNED_STRUCT_PAGE=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=yCONFIG_ARCH_WANT_OLD_COMPAT_IPC=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP_FILTER=yCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_HAVE_STACKPROTECTOR=yCONFIG_CC_HAS_STACKPROTECTOR_NONE=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_CONTEXT_TRACKING=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOVE_PMD=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=yCONFIG_HAVE_ARCH_HUGE_VMAP=yCONFIG_HAVE_ARCH_SOFT_DIRTY=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=28CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=yCONFIG_ARCH_MMAP_RND_COMPAT_BITS=8CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=yCONFIG_HAVE_COPY_THREAD_TLS=yCONFIG_HAVE_STACK_VALIDATION=yCONFIG_HAVE_RELIABLE_STACKTRACE=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_COMPAT_OLD_SIGACTION=yCONFIG_64BIT_TIME=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_VMAP_STACK=yCONFIG_VMAP_STACK=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_ARCH_HAS_REFCOUNT=y
# CONFIG_REFCOUNT_FULL is not setCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=yCONFIG_ARCH_USE_MEMREMAP_PROT=y
# CONFIG_LOCK_EVENT_COUNTS is not set
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_PLUGIN_HOSTCC="g++"CONFIG_HAVE_GCC_PLUGINS=yCONFIG_GCC_PLUGINS=y
#
# GCC plugins
#
# CONFIG_GCC_PLUGIN_CYC_COMPLEXITY is not set
# CONFIG_GCC_PLUGIN_LATENT_ENTROPY is not set
# CONFIG_GCC_PLUGIN_RANDSTRUCT is not set
# end of GCC plugins # end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not setCONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not setCONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not setCONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not setCONFIG_MODULE_SIG_HASH="sha256"
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not setCONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLK_SCSI_REQUEST=yCONFIG_BLK_DEV_BSG=yCONFIG_BLK_DEV_BSGLIB=yCONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_DEV_ZONED=yCONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_CGROUP_IOLATENCY is not setCONFIG_BLK_DEBUG_FS=yCONFIG_BLK_DEBUG_FS_ZONED=y
# CONFIG_BLK_SED_OPAL is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not setCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLOCK_COMPAT=yCONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_PM=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_PREEMPT_NOTIFIERS=yCONFIG_PADATA=yCONFIG_ASN1=yCONFIG_INLINE_SPIN_UNLOCK_IRQ=yCONFIG_INLINE_READ_UNLOCK=yCONFIG_INLINE_READ_UNLOCK_IRQ=yCONFIG_INLINE_WRITE_UNLOCK=yCONFIG_INLINE_WRITE_UNLOCK_IRQ=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_MUTEX_SPIN_ON_OWNER=yCONFIG_RWSEM_SPIN_ON_OWNER=yCONFIG_LOCK_SPIN_ON_OWNER=yCONFIG_ARCH_USE_QUEUED_SPINLOCKS=yCONFIG_QUEUED_SPINLOCKS=yCONFIG_ARCH_USE_QUEUED_RWLOCKS=yCONFIG_QUEUED_RWLOCKS=yCONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=yCONFIG_ARCH_HAS_SYSCALL_WRAPPER=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=mCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SELECT_MEMORY_MODEL=yCONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=yCONFIG_NEED_MULTIPLE_NODES=yCONFIG_HAVE_MEMORY_PRESENT=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_SPARSEMEM_VMEMMAP_ENABLE=yCONFIG_SPARSEMEM_VMEMMAP=yCONFIG_HAVE_MEMBLOCK_NODE_MAP=yCONFIG_MEMORY_ISOLATION=yCONFIG_HAVE_BOOTMEM_INFO_NODE=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_SPARSE=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not setCONFIG_MEMORY_HOTREMOVE=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_MEMORY_BALLOON=yCONFIG_BALLOON_COMPACTION=yCONFIG_COMPACTION=yCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=yCONFIG_MEMORY_FAILURE=yCONFIG_HWPOISON_INJECT=mCONFIG_TRANSPARENT_HUGEPAGE=yCONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not setCONFIG_ARCH_WANTS_THP_SWAP=yCONFIG_THP_SWAP=yCONFIG_TRANSPARENT_HUGE_PAGECACHE=yCONFIG_CLEANCACHE=yCONFIG_FRONTSWAP=yCONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not setCONFIG_CMA_AREAS=7CONFIG_MEM_SOFT_DIRTY=yCONFIG_ZSWAP=yCONFIG_ZPOOL=yCONFIG_ZBUD=y
# CONFIG_Z3FOLD is not setCONFIG_ZSMALLOC=y
# CONFIG_PGTABLE_MAPPING is not set
# CONFIG_ZSMALLOC_STAT is not setCONFIG_GENERIC_EARLY_IOREMAP=yCONFIG_DEFERRED_STRUCT_PAGE_INIT=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ARCH_HAS_ZONE_DEVICE=yCONFIG_ZONE_DEVICE=yCONFIG_ARCH_HAS_HMM_MIRROR=yCONFIG_ARCH_HAS_HMM_DEVICE=yCONFIG_ARCH_HAS_HMM=yCONFIG_MIGRATE_VMA_HELPER=yCONFIG_DEV_PAGEMAP_OPS=yCONFIG_HMM=yCONFIG_HMM_MIRROR=y
# CONFIG_DEVICE_PRIVATE is not set
# CONFIG_DEVICE_PUBLIC is not setCONFIG_FRAME_VECTOR=yCONFIG_ARCH_USES_HIGH_VMA_FLAGS=yCONFIG_ARCH_HAS_PKEYS=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_BENCHMARK is not setCONFIG_ARCH_HAS_PTE_SPECIAL=y
# end of Memory Management options
CONFIG_NET=yCONFIG_COMPAT_NETLINK_MESSAGES=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=mCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_UNIX_DIAG=m
# CONFIG_TLS is not setCONFIG_XFRM=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=y
# CONFIG_XFRM_INTERFACE is not setCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_IPCOMP=mCONFIG_NET_KEY=mCONFIG_NET_KEY_MIGRATE=y
# CONFIG_XDP_SOCKETS is not setCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_FIB_TRIE_STATS=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_CLASSID=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not setCONFIG_NET_IPIP=mCONFIG_NET_IPGRE_DEMUX=mCONFIG_NET_IP_TUNNEL=mCONFIG_NET_IPGRE=mCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=yCONFIG_IP_MROUTE=yCONFIG_IP_MROUTE_MULTIPLE_TABLES=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=mCONFIG_NET_UDP_TUNNEL=mCONFIG_NET_FOU=mCONFIG_NET_FOU_IP_TUNNELS=yCONFIG_INET_AH=mCONFIG_INET_ESP=m
# CONFIG_INET_ESP_OFFLOAD is not setCONFIG_INET_IPCOMP=mCONFIG_INET_XFRM_TUNNEL=mCONFIG_INET_TUNNEL=mCONFIG_INET_DIAG=mCONFIG_INET_TCP_DIAG=mCONFIG_INET_UDP_DIAG=m
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not setCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=mCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=mCONFIG_TCP_CONG_HTCP=mCONFIG_TCP_CONG_HSTCP=mCONFIG_TCP_CONG_HYBLA=mCONFIG_TCP_CONG_VEGAS=m
# CONFIG_TCP_CONG_NV is not setCONFIG_TCP_CONG_SCALABLE=mCONFIG_TCP_CONG_LP=mCONFIG_TCP_CONG_VENO=mCONFIG_TCP_CONG_YEAH=mCONFIG_TCP_CONG_ILLINOIS=mCONFIG_TCP_CONG_DCTCP=m
# CONFIG_TCP_CONG_CDG is not set
# CONFIG_TCP_CONG_BBR is not setCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=yCONFIG_IPV6_ROUTE_INFO=yCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=mCONFIG_INET6_ESP=m
# CONFIG_INET6_ESP_OFFLOAD is not setCONFIG_INET6_IPCOMP=mCONFIG_IPV6_MIP6=m
# CONFIG_IPV6_ILA is not setCONFIG_INET6_XFRM_TUNNEL=mCONFIG_INET6_TUNNEL=mCONFIG_IPV6_VTI=mCONFIG_IPV6_SIT=mCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=mCONFIG_IPV6_GRE=mCONFIG_IPV6_FOU=mCONFIG_IPV6_FOU_TUNNEL=mCONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not setCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=y
# CONFIG_IPV6_SEG6_HMAC is not setCONFIG_IPV6_SEG6_BPF=yCONFIG_NETLABEL=yCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=m
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_NETLINK=mCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=yCONFIG_NETFILTER_NETLINK_ACCT=mCONFIG_NETFILTER_NETLINK_QUEUE=mCONFIG_NETFILTER_NETLINK_LOG=mCONFIG_NETFILTER_NETLINK_OSF=mCONFIG_NF_CONNTRACK=mCONFIG_NF_LOG_COMMON=m
# CONFIG_NF_LOG_NETDEV is not setCONFIG_NETFILTER_CONNCOUNT=mCONFIG_NF_CONNTRACK_MARK=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_ZONES=yCONFIG_NF_CONNTRACK_PROCFS=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_TIMEOUT=yCONFIG_NF_CONNTRACK_TIMESTAMP=yCONFIG_NF_CONNTRACK_LABELS=yCONFIG_NF_CT_PROTO_DCCP=yCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=yCONFIG_NF_CONNTRACK_AMANDA=mCONFIG_NF_CONNTRACK_FTP=mCONFIG_NF_CONNTRACK_H323=mCONFIG_NF_CONNTRACK_IRC=mCONFIG_NF_CONNTRACK_BROADCAST=mCONFIG_NF_CONNTRACK_NETBIOS_NS=mCONFIG_NF_CONNTRACK_SNMP=mCONFIG_NF_CONNTRACK_PPTP=mCONFIG_NF_CONNTRACK_SANE=mCONFIG_NF_CONNTRACK_SIP=mCONFIG_NF_CONNTRACK_TFTP=mCONFIG_NF_CT_NETLINK=mCONFIG_NF_CT_NETLINK_TIMEOUT=m
# CONFIG_NETFILTER_NETLINK_GLUE_CT is not setCONFIG_NF_NAT=mCONFIG_NF_NAT_AMANDA=mCONFIG_NF_NAT_FTP=mCONFIG_NF_NAT_IRC=mCONFIG_NF_NAT_SIP=mCONFIG_NF_NAT_TFTP=mCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=mCONFIG_NF_TABLES=m
# CONFIG_NF_TABLES_SET is not set
# CONFIG_NF_TABLES_INET is not set
# CONFIG_NF_TABLES_NETDEV is not set
# CONFIG_NFT_NUMGEN is not setCONFIG_NFT_CT=mCONFIG_NFT_COUNTER=m
# CONFIG_NFT_CONNLIMIT is not setCONFIG_NFT_LOG=mCONFIG_NFT_LIMIT=mCONFIG_NFT_MASQ=mCONFIG_NFT_REDIR=m
# CONFIG_NFT_TUNNEL is not set
# CONFIG_NFT_OBJREF is not setCONFIG_NFT_QUEUE=m
# CONFIG_NFT_QUOTA is not setCONFIG_NFT_REJECT=mCONFIG_NFT_COMPAT=mCONFIG_NFT_HASH=m
# CONFIG_NFT_XFRM is not set
# CONFIG_NFT_SOCKET is not set
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NF_FLOW_TABLE is not setCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=mCONFIG_NETFILTER_XT_CONNMARK=mCONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=mCONFIG_NETFILTER_XT_TARGET_CHECKSUM=mCONFIG_NETFILTER_XT_TARGET_CLASSIFY=mCONFIG_NETFILTER_XT_TARGET_CONNMARK=mCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=mCONFIG_NETFILTER_XT_TARGET_CT=mCONFIG_NETFILTER_XT_TARGET_DSCP=mCONFIG_NETFILTER_XT_TARGET_HL=mCONFIG_NETFILTER_XT_TARGET_HMARK=mCONFIG_NETFILTER_XT_TARGET_IDLETIMER=mCONFIG_NETFILTER_XT_TARGET_LED=mCONFIG_NETFILTER_XT_TARGET_LOG=mCONFIG_NETFILTER_XT_TARGET_MARK=mCONFIG_NETFILTER_XT_NAT=mCONFIG_NETFILTER_XT_TARGET_NETMAP=mCONFIG_NETFILTER_XT_TARGET_NFLOG=mCONFIG_NETFILTER_XT_TARGET_NFQUEUE=mCONFIG_NETFILTER_XT_TARGET_NOTRACK=mCONFIG_NETFILTER_XT_TARGET_RATEEST=mCONFIG_NETFILTER_XT_TARGET_REDIRECT=mCONFIG_NETFILTER_XT_TARGET_MASQUERADE=mCONFIG_NETFILTER_XT_TARGET_TEE=mCONFIG_NETFILTER_XT_TARGET_TPROXY=mCONFIG_NETFILTER_XT_TARGET_TRACE=mCONFIG_NETFILTER_XT_TARGET_SECMARK=mCONFIG_NETFILTER_XT_TARGET_TCPMSS=mCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=mCONFIG_NETFILTER_XT_MATCH_BPF=mCONFIG_NETFILTER_XT_MATCH_CGROUP=mCONFIG_NETFILTER_XT_MATCH_CLUSTER=mCONFIG_NETFILTER_XT_MATCH_COMMENT=mCONFIG_NETFILTER_XT_MATCH_CONNBYTES=mCONFIG_NETFILTER_XT_MATCH_CONNLABEL=mCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=mCONFIG_NETFILTER_XT_MATCH_CONNMARK=mCONFIG_NETFILTER_XT_MATCH_CONNTRACK=mCONFIG_NETFILTER_XT_MATCH_CPU=mCONFIG_NETFILTER_XT_MATCH_DCCP=mCONFIG_NETFILTER_XT_MATCH_DEVGROUP=mCONFIG_NETFILTER_XT_MATCH_DSCP=mCONFIG_NETFILTER_XT_MATCH_ECN=mCONFIG_NETFILTER_XT_MATCH_ESP=mCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=mCONFIG_NETFILTER_XT_MATCH_HELPER=mCONFIG_NETFILTER_XT_MATCH_HL=m
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not setCONFIG_NETFILTER_XT_MATCH_IPRANGE=mCONFIG_NETFILTER_XT_MATCH_IPVS=mCONFIG_NETFILTER_XT_MATCH_L2TP=mCONFIG_NETFILTER_XT_MATCH_LENGTH=mCONFIG_NETFILTER_XT_MATCH_LIMIT=mCONFIG_NETFILTER_XT_MATCH_MAC=mCONFIG_NETFILTER_XT_MATCH_MARK=mCONFIG_NETFILTER_XT_MATCH_MULTIPORT=mCONFIG_NETFILTER_XT_MATCH_NFACCT=mCONFIG_NETFILTER_XT_MATCH_OSF=mCONFIG_NETFILTER_XT_MATCH_OWNER=mCONFIG_NETFILTER_XT_MATCH_POLICY=mCONFIG_NETFILTER_XT_MATCH_PHYSDEV=mCONFIG_NETFILTER_XT_MATCH_PKTTYPE=mCONFIG_NETFILTER_XT_MATCH_QUOTA=mCONFIG_NETFILTER_XT_MATCH_RATEEST=mCONFIG_NETFILTER_XT_MATCH_REALM=mCONFIG_NETFILTER_XT_MATCH_RECENT=mCONFIG_NETFILTER_XT_MATCH_SCTP=mCONFIG_NETFILTER_XT_MATCH_SOCKET=mCONFIG_NETFILTER_XT_MATCH_STATE=mCONFIG_NETFILTER_XT_MATCH_STATISTIC=mCONFIG_NETFILTER_XT_MATCH_STRING=mCONFIG_NETFILTER_XT_MATCH_TCPMSS=mCONFIG_NETFILTER_XT_MATCH_TIME=mCONFIG_NETFILTER_XT_MATCH_U32=m
# end of Core Netfilter Configuration
CONFIG_IP_SET=mCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=mCONFIG_IP_SET_BITMAP_IPMAC=mCONFIG_IP_SET_BITMAP_PORT=mCONFIG_IP_SET_HASH_IP=mCONFIG_IP_SET_HASH_IPMARK=mCONFIG_IP_SET_HASH_IPPORT=mCONFIG_IP_SET_HASH_IPPORTIP=mCONFIG_IP_SET_HASH_IPPORTNET=mCONFIG_IP_SET_HASH_IPMAC=mCONFIG_IP_SET_HASH_MAC=mCONFIG_IP_SET_HASH_NETPORTNET=mCONFIG_IP_SET_HASH_NET=mCONFIG_IP_SET_HASH_NETNET=mCONFIG_IP_SET_HASH_NETPORT=mCONFIG_IP_SET_HASH_NETIFACE=mCONFIG_IP_SET_LIST_SET=mCONFIG_IP_VS=mCONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not setCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#CONFIG_IP_VS_PROTO_TCP=yCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=yCONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#CONFIG_IP_VS_RR=mCONFIG_IP_VS_WRR=mCONFIG_IP_VS_LC=mCONFIG_IP_VS_WLC=m
# CONFIG_IP_VS_FO is not set
# CONFIG_IP_VS_OVF is not setCONFIG_IP_VS_LBLC=mCONFIG_IP_VS_LBLCR=mCONFIG_IP_VS_DH=mCONFIG_IP_VS_SH=m
# CONFIG_IP_VS_MH is not setCONFIG_IP_VS_SED=mCONFIG_IP_VS_NQ=m
#
# IPVS SH scheduler
#CONFIG_IP_VS_SH_TAB_BITS=8
#
# IPVS MH scheduler
#CONFIG_IP_VS_MH_TAB_INDEX=12
#
# IPVS application helper
#CONFIG_IP_VS_FTP=mCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=m
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=mCONFIG_NF_SOCKET_IPV4=mCONFIG_NF_TPROXY_IPV4=m
# CONFIG_NF_TABLES_IPV4 is not set
# CONFIG_NF_TABLES_ARP is not setCONFIG_NF_DUP_IPV4=m
# CONFIG_NF_LOG_ARP is not setCONFIG_NF_LOG_IPV4=mCONFIG_NF_REJECT_IPV4=mCONFIG_NF_NAT_SNMP_BASIC=mCONFIG_NF_NAT_PPTP=mCONFIG_NF_NAT_H323=mCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_MATCH_AH=mCONFIG_IP_NF_MATCH_ECN=mCONFIG_IP_NF_MATCH_RPFILTER=mCONFIG_IP_NF_MATCH_TTL=mCONFIG_IP_NF_FILTER=mCONFIG_IP_NF_TARGET_REJECT=mCONFIG_IP_NF_TARGET_SYNPROXY=mCONFIG_IP_NF_NAT=mCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_NETMAP=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_MANGLE=mCONFIG_IP_NF_TARGET_CLUSTERIP=mCONFIG_IP_NF_TARGET_ECN=mCONFIG_IP_NF_TARGET_TTL=mCONFIG_IP_NF_RAW=mCONFIG_IP_NF_SECURITY=mCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_IP_NF_ARP_MANGLE=m
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=mCONFIG_NF_TPROXY_IPV6=m
# CONFIG_NF_TABLES_IPV6 is not setCONFIG_NF_DUP_IPV6=mCONFIG_NF_REJECT_IPV6=mCONFIG_NF_LOG_IPV6=mCONFIG_IP6_NF_IPTABLES=mCONFIG_IP6_NF_MATCH_AH=mCONFIG_IP6_NF_MATCH_EUI64=mCONFIG_IP6_NF_MATCH_FRAG=mCONFIG_IP6_NF_MATCH_OPTS=mCONFIG_IP6_NF_MATCH_HL=mCONFIG_IP6_NF_MATCH_IPV6HEADER=mCONFIG_IP6_NF_MATCH_MH=mCONFIG_IP6_NF_MATCH_RPFILTER=mCONFIG_IP6_NF_MATCH_RT=m
# CONFIG_IP6_NF_MATCH_SRH is not setCONFIG_IP6_NF_TARGET_HL=mCONFIG_IP6_NF_FILTER=mCONFIG_IP6_NF_TARGET_REJECT=mCONFIG_IP6_NF_TARGET_SYNPROXY=mCONFIG_IP6_NF_MANGLE=mCONFIG_IP6_NF_RAW=mCONFIG_IP6_NF_SECURITY=mCONFIG_IP6_NF_NAT=mCONFIG_IP6_NF_TARGET_MASQUERADE=mCONFIG_IP6_NF_TARGET_NPT=m
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m
# CONFIG_NF_TABLES_BRIDGE is not setCONFIG_BRIDGE_NF_EBTABLES=mCONFIG_BRIDGE_EBT_BROUTE=mCONFIG_BRIDGE_EBT_T_FILTER=mCONFIG_BRIDGE_EBT_T_NAT=mCONFIG_BRIDGE_EBT_802_3=mCONFIG_BRIDGE_EBT_AMONG=mCONFIG_BRIDGE_EBT_ARP=mCONFIG_BRIDGE_EBT_IP=mCONFIG_BRIDGE_EBT_IP6=mCONFIG_BRIDGE_EBT_LIMIT=mCONFIG_BRIDGE_EBT_MARK=mCONFIG_BRIDGE_EBT_PKTTYPE=mCONFIG_BRIDGE_EBT_STP=mCONFIG_BRIDGE_EBT_VLAN=mCONFIG_BRIDGE_EBT_ARPREPLY=mCONFIG_BRIDGE_EBT_DNAT=mCONFIG_BRIDGE_EBT_MARK_T=mCONFIG_BRIDGE_EBT_REDIRECT=mCONFIG_BRIDGE_EBT_SNAT=mCONFIG_BRIDGE_EBT_LOG=mCONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_BPFILTER is not setCONFIG_IP_DCCP=mCONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not setCONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not setCONFIG_IP_DCCP_TFRC_LIB=y
# end of DCCP CCIDs Configuration
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# end of DCCP Kernel Hacking
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m
# CONFIG_RDS is not set
# CONFIG_TIPC is not setCONFIG_ATM=mCONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=mCONFIG_L2TP_DEBUGFS=mCONFIG_L2TP_V3=yCONFIG_L2TP_IP=mCONFIG_L2TP_ETH=mCONFIG_STP=mCONFIG_GARP=mCONFIG_MRP=mCONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y CONFIG_HAVE_NET_DSA=y
# CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=mCONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not setCONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not setCONFIG_6LOWPAN=m
# CONFIG_6LOWPAN_DEBUGFS is not set CONFIG_6LOWPAN_NHC=m CONFIG_6LOWPAN_NHC_DEST=m CONFIG_6LOWPAN_NHC_FRAGMENT=m CONFIG_6LOWPAN_NHC_HOP=m CONFIG_6LOWPAN_NHC_IPV6=m CONFIG_6LOWPAN_NHC_MOBILITY=m CONFIG_6LOWPAN_NHC_ROUTING=m CONFIG_6LOWPAN_NHC_UDP=m
# CONFIG_6LOWPAN_GHC_EXT_HDR_HOP is not set # CONFIG_6LOWPAN_GHC_UDP is not set
# CONFIG_6LOWPAN_GHC_ICMPV6 is not set
# CONFIG_6LOWPAN_GHC_EXT_HDR_DEST is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE is not set CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=mCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=mCONFIG_NET_SCH_HFSC=mCONFIG_NET_SCH_ATM=mCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_MULTIQ=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFB=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=m
# CONFIG_NET_SCH_CBS is not set
# CONFIG_NET_SCH_ETF is not set
# CONFIG_NET_SCH_TAPRIO is not setCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_SCH_NETEM=mCONFIG_NET_SCH_DRR=mCONFIG_NET_SCH_MQPRIO=m
# CONFIG_NET_SCH_SKBPRIO is not setCONFIG_NET_SCH_CHOKE=mCONFIG_NET_SCH_QFQ=mCONFIG_NET_SCH_CODEL=mCONFIG_NET_SCH_FQ_CODEL=m
# CONFIG_NET_SCH_CAKE is not setCONFIG_NET_SCH_FQ=m
# CONFIG_NET_SCH_HHF is not set
# CONFIG_NET_SCH_PIE is not setCONFIG_NET_SCH_INGRESS=mCONFIG_NET_SCH_PLUG=m
# CONFIG_NET_SCH_DEFAULT is not set
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=mCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=mCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=mCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_FLOW=mCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=mCONFIG_NET_CLS_FLOWER=mCONFIG_NET_CLS_MATCHALL=mCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=mCONFIG_NET_EMATCH_NBYTE=mCONFIG_NET_EMATCH_U32=mCONFIG_NET_EMATCH_META=mCONFIG_NET_EMATCH_TEXT=m
# CONFIG_NET_EMATCH_CANID is not setCONFIG_NET_EMATCH_IPSET=m
# CONFIG_NET_EMATCH_IPT is not setCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=mCONFIG_NET_ACT_GACT=mCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=mCONFIG_NET_ACT_SAMPLE=mCONFIG_NET_ACT_IPT=mCONFIG_NET_ACT_NAT=mCONFIG_NET_ACT_PEDIT=mCONFIG_NET_ACT_SIMP=mCONFIG_NET_ACT_SKBEDIT=mCONFIG_NET_ACT_CSUM=mCONFIG_NET_ACT_VLAN=m
# CONFIG_NET_ACT_BPF is not setCONFIG_NET_ACT_CONNMARK=m
# CONFIG_NET_ACT_CTINFO is not setCONFIG_NET_ACT_SKBMOD=m
# CONFIG_NET_ACT_IFE is not setCONFIG_NET_ACT_TUNNEL_KEY=mCONFIG_NET_CLS_IND=yCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=m
# CONFIG_BATMAN_ADV is not setCONFIG_OPENVSWITCH=mCONFIG_OPENVSWITCH_GRE=mCONFIG_OPENVSWITCH_VXLAN=mCONFIG_OPENVSWITCH_GENEVE=mCONFIG_VSOCKETS=mCONFIG_VSOCKETS_DIAG=mCONFIG_VMWARE_VMCI_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS_COMMON=mCONFIG_HYPERV_VSOCKETS=mCONFIG_NETLINK_DIAG=mCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=y
# CONFIG_MPLS_ROUTING is not setCONFIG_NET_NSH=m
# CONFIG_HSR is not setCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=y
# CONFIG_NET_NCSI is not setCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not setCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_JIT=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=mCONFIG_NET_DROP_MONITOR=y
# end of Network testing # end of Networking options
# CONFIG_HAMRADIO is not setCONFIG_CAN=mCONFIG_CAN_RAW=mCONFIG_CAN_BCM=mCONFIG_CAN_GW=m
#
# CAN Device Drivers
#CONFIG_CAN_VCAN=m
# CONFIG_CAN_VXCAN is not setCONFIG_CAN_SLCAN=mCONFIG_CAN_DEV=mCONFIG_CAN_CALC_BITTIMING=yCONFIG_CAN_C_CAN=mCONFIG_CAN_C_CAN_PLATFORM=mCONFIG_CAN_C_CAN_PCI=mCONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not setCONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not setCONFIG_CAN_SJA1000=m
# CONFIG_CAN_SJA1000_ISA is not setCONFIG_CAN_SJA1000_PLATFORM=mCONFIG_CAN_EMS_PCI=mCONFIG_CAN_PEAK_PCI=mCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_KVASER_PCI=mCONFIG_CAN_PLX_PCI=mCONFIG_CAN_SOFTING=m
#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# end of CAN SPI interfaces
#
# CAN USB interfaces
#CONFIG_CAN_8DEV_USB=mCONFIG_CAN_EMS_USB=mCONFIG_CAN_ESD_USB2=m
# CONFIG_CAN_GS_USB is not setCONFIG_CAN_KVASER_USB=m
# CONFIG_CAN_MCBA_USB is not setCONFIG_CAN_PEAK_USB=m
# CONFIG_CAN_UCAN is not set
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
CONFIG_BT=mCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=mCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=mCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_CMTP=mCONFIG_BT_HIDP=mCONFIG_BT_HS=yCONFIG_BT_LE=y
# CONFIG_BT_6LOWPAN is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_SELFTEST is not setCONFIG_BT_DEBUGFS=y
#
# Bluetooth device drivers
#CONFIG_BT_INTEL=mCONFIG_BT_BCM=mCONFIG_BT_RTL=mCONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTUSB_AUTOSUSPEND is not setCONFIG_BT_HCIBTUSB_BCM=yCONFIG_BT_HCIBTUSB_RTL=yCONFIG_BT_HCIBTSDIO=mCONFIG_BT_HCIUART=mCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_AG6XX is not set
# CONFIG_BT_HCIUART_MRVL is not setCONFIG_BT_HCIBCM203X=mCONFIG_BT_HCIBPA10X=mCONFIG_BT_HCIBFUSB=mCONFIG_BT_HCIVHCI=mCONFIG_BT_MRVL=mCONFIG_BT_MRVL_SDIO=mCONFIG_BT_ATH3K=m
# CONFIG_BT_MTKSDIO is not set
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not setCONFIG_STREAM_PARSER=yCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_WIRELESS_EXT=yCONFIG_WEXT_CORE=yCONFIG_WEXT_PROC=yCONFIG_WEXT_PRIV=yCONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not setCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not setCONFIG_CFG80211_CRDA_SUPPORT=yCONFIG_CFG80211_WEXT=yCONFIG_LIB80211=m
# CONFIG_LIB80211_DEBUG is not setCONFIG_MAC80211=mCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"CONFIG_MAC80211_MESH=yCONFIG_MAC80211_LEDS=yCONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not setCONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not setCONFIG_RFKILL=mCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not setCONFIG_NET_9P=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_XEN is not set
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not setCONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not setCONFIG_CEPH_LIB_USE_DNS_RESOLVER=y
# CONFIG_NFC is not setCONFIG_PSAMPLE=m
# CONFIG_NET_IFE is not setCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_FAILOVER=mCONFIG_HAVE_EBPF_JIT=y
#
# Device Drivers
#CONFIG_HAVE_EISA=y
# CONFIG_EISA is not setCONFIG_HAVE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=mCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not setCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=y
# CONFIG_PCIE_DPC is not set
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_BW is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not setCONFIG_PCI_STUB=y
# CONFIG_PCI_PF_STUB is not set
# CONFIG_XEN_PCIDEV_FRONTEND is not setCONFIG_PCI_ATS=yCONFIG_PCI_LOCKLESS_CONFIG=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not setCONFIG_PCI_LABEL=yCONFIG_PCI_HYPERV=mCONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_ACPI=yCONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not setCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#
#
# Cadence PCIe controllers support
#
# end of Cadence PCIe controllers support
CONFIG_VMD=y
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support # end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
CONFIG_PCCARD=y
# CONFIG_PCMCIA is not setCONFIG_CARDBUS=y
#
# PC-card bridges
#CONFIG_YENTA=mCONFIG_YENTA_O2=yCONFIG_YENTA_RICOH=yCONFIG_YENTA_TI=yCONFIG_YENTA_ENE_TUNE=yCONFIG_YENTA_TOSHIBA=y
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#CONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_EXTRA_FIRMWARE=""CONFIG_FW_LOADER_USER_HELPER=yCONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not setCONFIG_SYS_HYPERVISOR=yCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_IRQ=yCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
# end of Generic Driver Options
#
# Bus devices
#
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
# CONFIG_GNSS is not setCONFIG_MTD=m
# CONFIG_MTD_TESTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_AR7_PARTS is not set
#
# Partition parsers
#
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers
#
# User Modules And Translation Layers
#CONFIG_MTD_BLKDEVS=mCONFIG_MTD_BLOCK=m
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set
#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not setCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not set
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# end of Self-contained MTD device drivers
# CONFIG_MTD_ONENAND is not set
# CONFIG_MTD_RAW_NAND is not set
# CONFIG_MTD_SPI_NAND is not set
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# end of LPDDR & LPDDR2 PCM memory drivers
# CONFIG_MTD_SPI_NOR is not setCONFIG_MTD_UBI=mCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_OF is not setCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AX88796 is not setCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=mCONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=yCONFIG_BLK_DEV_FD=mCONFIG_CDROM=m
# CONFIG_PARIDE is not setCONFIG_BLK_DEV_PCIESSD_MTIP32XX=m
# CONFIG_ZRAM is not set
# CONFIG_BLK_DEV_UMEM is not setCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_LOOP_MIN_COUNT=0
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not setCONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SKD is not setCONFIG_BLK_DEV_SX8=mCONFIG_BLK_DEV_RAM=mCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384CONFIG_CDROM_PKTCDVD=mCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not setCONFIG_ATA_OVER_ETH=mCONFIG_XEN_BLKDEV_FRONTEND=mCONFIG_VIRTIO_BLK=y
# CONFIG_VIRTIO_BLK_SCSI is not setCONFIG_BLK_DEV_RBD=m
# CONFIG_BLK_DEV_RSXX is not set
#
# NVME Support
#CONFIG_NVME_CORE=mCONFIG_BLK_DEV_NVME=mCONFIG_NVME_MULTIPATH=yCONFIG_NVME_FABRICS=mCONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not setCONFIG_NVME_TARGET=mCONFIG_NVME_TARGET_LOOP=mCONFIG_NVME_TARGET_FC=mCONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not setCONFIG_SGI_IOC4=mCONFIG_TIFM_CORE=mCONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=mCONFIG_SGI_XP=mCONFIG_HP_ILO=mCONFIG_SGI_GRU=m
# CONFIG_SGI_GRU_DEBUG is not setCONFIG_APDS9802ALS=mCONFIG_ISL29003=mCONFIG_ISL29020=mCONFIG_SENSORS_TSL2550=mCONFIG_SENSORS_BH1770=mCONFIG_SENSORS_APDS990X=m
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not setCONFIG_VMWARE_BALLOON=m
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_PCI_ENDPOINT_TEST is not setCONFIG_PVPANIC=y
# CONFIG_C2PORT is not set
#
# EEPROM support
#CONFIG_EEPROM_AT24=m
# CONFIG_EEPROM_AT25 is not setCONFIG_EEPROM_LEGACY=mCONFIG_EEPROM_MAX6875=mCONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not setCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_I2C=mCONFIG_ALTERA_STAPL=mCONFIG_INTEL_MEI=mCONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_HDCP is not setCONFIG_VMWARE_VMCI=m
#
# Intel MIC & related support
#
#
# Intel MIC Bus Driver
#
# CONFIG_INTEL_MIC_BUS is not set
#
# SCIF Bus Driver
#
# CONFIG_SCIF_BUS is not set
#
# VOP Bus Driver
#
# CONFIG_VOP_BUS is not set
#
# Intel MIC Host Driver
#
#
# Intel MIC Card Driver
#
#
# SCIF Driver
#
#
# Intel MIC Coprocessor State Management (COSM) Drivers #
#
# VOP Driver
#
# end of Intel MIC & related support
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# end of Misc devices
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=mCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=mCONFIG_CHR_DEV_ST=mCONFIG_CHR_DEV_OSST=mCONFIG_BLK_DEV_SR=mCONFIG_BLK_DEV_SR_VENDOR=yCONFIG_CHR_DEV_SG=mCONFIG_CHR_DEV_SCH=mCONFIG_SCSI_ENCLOSURE=mCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=mCONFIG_SCSI_FC_ATTRS=mCONFIG_SCSI_ISCSI_ATTRS=mCONFIG_SCSI_SAS_ATTRS=mCONFIG_SCSI_SAS_LIBSAS=mCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=m
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=mCONFIG_ISCSI_BOOT_SYSFS=mCONFIG_SCSI_CXGB3_ISCSI=mCONFIG_SCSI_CXGB4_ISCSI=mCONFIG_SCSI_BNX2_ISCSI=mCONFIG_SCSI_BNX2X_FCOE=mCONFIG_BE2ISCSI=m
# CONFIG_BLK_DEV_3W_XXXX_RAID is not setCONFIG_SCSI_HPSA=mCONFIG_SCSI_3W_9XXX=mCONFIG_SCSI_3W_SAS=m
# CONFIG_SCSI_ACARD is not setCONFIG_SCSI_AACRAID=m
# CONFIG_SCSI_AIC7XXX is not setCONFIG_SCSI_AIC79XX=mCONFIG_AIC79XX_CMDS_PER_DEVICE=4CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_DEBUG_ENABLE is not setCONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not setCONFIG_SCSI_MVSAS=m
# CONFIG_SCSI_MVSAS_DEBUG is not setCONFIG_SCSI_MVSAS_TASKLET=yCONFIG_SCSI_MVUMI=m
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not setCONFIG_SCSI_ARCMSR=m
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not setCONFIG_MEGARAID_SAS=mCONFIG_SCSI_MPT3SAS=mCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128CONFIG_SCSI_MPT2SAS=m
# CONFIG_SCSI_SMARTPQI is not setCONFIG_SCSI_UFSHCD=mCONFIG_SCSI_UFSHCD_PCI=m
# CONFIG_SCSI_UFS_DWC_TC_PCI is not set
# CONFIG_SCSI_UFSHCD_PLATFORM is not set
# CONFIG_SCSI_UFS_BSG is not setCONFIG_SCSI_HPTIOP=m
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not setCONFIG_VMWARE_PVSCSI=m
# CONFIG_XEN_SCSI_FRONTEND is not setCONFIG_HYPERV_STORAGE=mCONFIG_LIBFC=mCONFIG_LIBFCOE=mCONFIG_FCOE=mCONFIG_FCOE_FNIC=m
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_GDTH is not setCONFIG_SCSI_ISCI=m
# CONFIG_SCSI_IPS is not setCONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not setCONFIG_SCSI_STEX=m
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not setCONFIG_SCSI_QLA_FC=mCONFIG_TCM_QLA2XXX=m
# CONFIG_TCM_QLA2XXX_DEBUG is not setCONFIG_SCSI_QLA_ISCSI=m
# CONFIG_QEDI is not set
# CONFIG_QEDF is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not setCONFIG_SCSI_DEBUG=mCONFIG_SCSI_PMCRAID=mCONFIG_SCSI_PM8001=m
# CONFIG_SCSI_BFA_FC is not setCONFIG_SCSI_VIRTIO=m
# CONFIG_SCSI_CHELSIO_FCOE is not setCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=yCONFIG_SCSI_DH_HP_SW=yCONFIG_SCSI_DH_EMC=yCONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
CONFIG_ATA=mCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not setCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=mCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not setCONFIG_SATA_ACARD_AHCI=mCONFIG_SATA_SIL24=mCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#CONFIG_PDC_ADMA=mCONFIG_SATA_QSTOR=mCONFIG_SATA_SX4=mCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=m
# CONFIG_SATA_DWC is not setCONFIG_SATA_MV=mCONFIG_SATA_NV=mCONFIG_SATA_PROMISE=mCONFIG_SATA_SIL=mCONFIG_SATA_SIS=mCONFIG_SATA_SVW=mCONFIG_SATA_ULI=mCONFIG_SATA_VIA=mCONFIG_SATA_VITESSE=m
#
# PATA SFF controllers with BMDMA
#CONFIG_PATA_ALI=mCONFIG_PATA_AMD=mCONFIG_PATA_ARTOP=mCONFIG_PATA_ATIIXP=mCONFIG_PATA_ATP867X=mCONFIG_PATA_CMD64X=m
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not setCONFIG_PATA_HPT366=mCONFIG_PATA_HPT37X=mCONFIG_PATA_HPT3X2N=mCONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not setCONFIG_PATA_IT8213=mCONFIG_PATA_IT821X=mCONFIG_PATA_JMICRON=mCONFIG_PATA_MARVELL=mCONFIG_PATA_NETCELL=mCONFIG_PATA_NINJA32=m
# CONFIG_PATA_NS87415 is not setCONFIG_PATA_OLDPIIX=m
# CONFIG_PATA_OPTIDMA is not setCONFIG_PATA_PDC2027X=mCONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not setCONFIG_PATA_RDC=mCONFIG_PATA_SCH=mCONFIG_PATA_SERVERWORKS=mCONFIG_PATA_SIL680=mCONFIG_PATA_SIS=mCONFIG_PATA_TOSHIBA=m
# CONFIG_PATA_TRIFLEX is not setCONFIG_PATA_VIA=m
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#CONFIG_PATA_ACPI=mCONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set CONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=mCONFIG_MD_RAID0=mCONFIG_MD_RAID1=mCONFIG_MD_RAID10=mCONFIG_MD_RAID456=mCONFIG_MD_MULTIPATH=mCONFIG_MD_FAULTY=m
# CONFIG_MD_CLUSTER is not set
# CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=mCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=m
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m
# CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=mCONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=mCONFIG_DM_CACHE_SMQ=m
# CONFIG_DM_WRITECACHE is not set CONFIG_DM_ERA=mCONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=mCONFIG_DM_RAID=mCONFIG_DM_ZERO=mCONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=mCONFIG_DM_DELAY=m
# CONFIG_DM_DUST is not set CONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=mCONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=mCONFIG_DM_LOG_WRITES=m
# CONFIG_DM_INTEGRITY is not set
# CONFIG_DM_ZONED is not set CONFIG_TARGET_CORE=mCONFIG_TCM_IBLOCK=mCONFIG_TCM_FILEIO=mCONFIG_TCM_PSCSI=mCONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=mCONFIG_TCM_FC=mCONFIG_ISCSI_TARGET=m CONFIG_ISCSI_TARGET_CXGB4=m
# CONFIG_SBP_TARGET is not set CONFIG_FUSION=yCONFIG_FUSION_SPI=m
# CONFIG_FUSION_FC is not set CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=m CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=mCONFIG_FIREWIRE_OHCI=mCONFIG_FIREWIRE_SBP2=mCONFIG_FIREWIRE_NET=m
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=yCONFIG_MAC_EMUMOUSEBTN=yCONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=yCONFIG_BONDING=mCONFIG_DUMMY=m
# CONFIG_EQUALIZER is not setCONFIG_NET_FC=yCONFIG_IFB=mCONFIG_NET_TEAM=mCONFIG_NET_TEAM_MODE_BROADCAST=mCONFIG_NET_TEAM_MODE_ROUNDROBIN=mCONFIG_NET_TEAM_MODE_RANDOM=mCONFIG_NET_TEAM_MODE_ACTIVEBACKUP=mCONFIG_NET_TEAM_MODE_LOADBALANCE=mCONFIG_MACVLAN=mCONFIG_MACVTAP=m
# CONFIG_IPVLAN is not setCONFIG_VXLAN=mCONFIG_GENEVE=m
# CONFIG_GTP is not setCONFIG_MACSEC=yCONFIG_NETCONSOLE=mCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_NTB_NETDEV=mCONFIG_TUN=mCONFIG_TAP=m
# CONFIG_TUN_VNET_CROSS_LE is not setCONFIG_VETH=mCONFIG_VIRTIO_NET=mCONFIG_NLMON=mCONFIG_NET_VRF=yCONFIG_VSOCKMON=m
# CONFIG_ARCNET is not set
# CONFIG_ATM_DRIVERS is not set
#
# CAIF transport drivers
#
#
# Distributed Switch Architecture drivers
#
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not setCONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not setCONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_ALTERA_TSE is not setCONFIG_NET_VENDOR_AMAZON=yCONFIG_ENA_ETHERNET=mCONFIG_NET_VENDOR_AMD=yCONFIG_AMD8111_ETH=mCONFIG_PCNET32=mCONFIG_AMD_XGBE=m
# CONFIG_AMD_XGBE_DCB is not setCONFIG_AMD_XGBE_HAVE_ECC=yCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_AQTION=mCONFIG_NET_VENDOR_ARC=yCONFIG_NET_VENDOR_ATHEROS=yCONFIG_ATL2=mCONFIG_ATL1=mCONFIG_ATL1E=mCONFIG_ATL1C=mCONFIG_ALX=mCONFIG_NET_VENDOR_AURORA=y
# CONFIG_AURORA_NB8800 is not setCONFIG_NET_VENDOR_BROADCOM=yCONFIG_B44=mCONFIG_B44_PCI_AUTOSELECT=yCONFIG_B44_PCICORE_AUTOSELECT=yCONFIG_B44_PCI=y
# CONFIG_BCMGENET is not setCONFIG_BNX2=mCONFIG_CNIC=mCONFIG_TIGON3=yCONFIG_TIGON3_HWMON=yCONFIG_BNX2X=mCONFIG_BNX2X_SRIOV=y
# CONFIG_SYSTEMPORT is not setCONFIG_BNXT=mCONFIG_BNXT_SRIOV=yCONFIG_BNXT_FLOWER_OFFLOAD=yCONFIG_BNXT_DCB=yCONFIG_BNXT_HWMON=yCONFIG_NET_VENDOR_BROCADE=yCONFIG_BNA=mCONFIG_NET_VENDOR_CADENCE=yCONFIG_MACB=mCONFIG_MACB_USE_HWSTAMP=y
# CONFIG_MACB_PCI is not setCONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not setCONFIG_CAVIUM_PTP=yCONFIG_LIQUIDIO=mCONFIG_LIQUIDIO_VF=mCONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not setCONFIG_CHELSIO_T3=mCONFIG_CHELSIO_T4=m
# CONFIG_CHELSIO_T4_DCB is not setCONFIG_CHELSIO_T4VF=mCONFIG_CHELSIO_LIB=mCONFIG_NET_VENDOR_CISCO=yCONFIG_ENIC=mCONFIG_NET_VENDOR_CORTINA=y
# CONFIG_CX_ECAT is not setCONFIG_DNET=mCONFIG_NET_VENDOR_DEC=yCONFIG_NET_TULIP=yCONFIG_DE2104X=mCONFIG_DE2104X_DSL=0CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not setCONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not setCONFIG_DE4X5=mCONFIG_WINBOND_840=mCONFIG_DM9102=mCONFIG_ULI526X=mCONFIG_PCMCIA_XIRCOM=m
# CONFIG_NET_VENDOR_DLINK is not setCONFIG_NET_VENDOR_EMULEX=yCONFIG_BE2NET=mCONFIG_BE2NET_HWMON=yCONFIG_BE2NET_BE2=yCONFIG_BE2NET_BE3=yCONFIG_BE2NET_LANCER=yCONFIG_BE2NET_SKYHAWK=yCONFIG_NET_VENDOR_EZCHIP=y
# CONFIG_NET_VENDOR_HP is not setCONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not set
# CONFIG_NET_VENDOR_I825XX is not setCONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not setCONFIG_E1000=yCONFIG_E1000E=yCONFIG_E1000E_HWTS=yCONFIG_IGB=yCONFIG_IGB_HWMON=yCONFIG_IGBVF=mCONFIG_IXGB=yCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=yCONFIG_IXGBE_DCB=yCONFIG_IXGBEVF=mCONFIG_I40E=yCONFIG_I40E_DCB=yCONFIG_IAVF=mCONFIG_I40EVF=m
# CONFIG_ICE is not setCONFIG_FM10K=m
# CONFIG_IGC is not setCONFIG_JME=mCONFIG_NET_VENDOR_MARVELL=yCONFIG_MVMDIO=mCONFIG_SKGE=y
# CONFIG_SKGE_DEBUG is not setCONFIG_SKGE_GENESIS=yCONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not setCONFIG_NET_VENDOR_MELLANOX=yCONFIG_MLX4_EN=mCONFIG_MLX4_EN_DCB=yCONFIG_MLX4_CORE=mCONFIG_MLX4_DEBUG=yCONFIG_MLX4_CORE_GEN2=y
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not setCONFIG_NET_VENDOR_MICROSEMI=y
# CONFIG_MSCC_OCELOT_SWITCH is not setCONFIG_NET_VENDOR_MYRI=yCONFIG_MYRI10GE=mCONFIG_MYRI10GE_DCA=y
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NATSEMI is not setCONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not setCONFIG_NET_VENDOR_NETRONOME=yCONFIG_NFP=mCONFIG_NFP_APP_FLOWER=yCONFIG_NFP_APP_ABM_NIC=y
# CONFIG_NFP_DEBUG is not setCONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not set
# CONFIG_NET_VENDOR_NVIDIA is not setCONFIG_NET_VENDOR_OKI=yCONFIG_ETHOC=mCONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not setCONFIG_YELLOWFIN=mCONFIG_NET_VENDOR_QLOGIC=yCONFIG_QLA3XXX=mCONFIG_QLCNIC=mCONFIG_QLCNIC_SRIOV=yCONFIG_QLCNIC_DCB=yCONFIG_QLCNIC_HWMON=yCONFIG_QLGE=mCONFIG_NETXEN_NIC=mCONFIG_QED=mCONFIG_QED_SRIOV=yCONFIG_QEDE=mCONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not set
# CONFIG_NET_VENDOR_RDC is not setCONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not setCONFIG_8139CP=yCONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not setCONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not setCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_NET_VENDOR_ROCKER=yCONFIG_ROCKER=mCONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
# CONFIG_NET_VENDOR_SEEQ is not setCONFIG_NET_VENDOR_SOLARFLARE=yCONFIG_SFC=mCONFIG_SFC_MTD=yCONFIG_SFC_MCDI_MON=yCONFIG_SFC_SRIOV=yCONFIG_SFC_MCDI_LOGGING=yCONFIG_SFC_FALCON=mCONFIG_SFC_FALCON_MTD=y
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not setCONFIG_NET_VENDOR_SMSC=yCONFIG_EPIC100=m
# CONFIG_SMSC911X is not setCONFIG_SMSC9420=mCONFIG_NET_VENDOR_SOCIONEXT=y
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not set
# CONFIG_NET_VENDOR_TEHUTI is not setCONFIG_NET_VENDOR_TI=y
# CONFIG_TI_CPSW_PHY_SEL is not setCONFIG_TLAN=m
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not setCONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not setCONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=y
# CONFIG_MDIO_BCM_UNIMAC is not setCONFIG_MDIO_BITBANG=m
# CONFIG_MDIO_GPIO is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_THUNDER is not setCONFIG_PHYLIB=yCONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not set
#
# MII PHY device drivers
#CONFIG_AMD_PHY=m
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_ASIX_PHY is not setCONFIG_AT803X_PHY=m
# CONFIG_BCM7XXX_PHY is not setCONFIG_BCM87XX_PHY=mCONFIG_BCM_NET_PHYLIB=mCONFIG_BROADCOM_PHY=mCONFIG_CICADA_PHY=m
# CONFIG_CORTINA_PHY is not setCONFIG_DAVICOM_PHY=m
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not setCONFIG_FIXED_PHY=yCONFIG_ICPLUS_PHY=m
# CONFIG_INTEL_XWAY_PHY is not setCONFIG_LSI_ET1011C_PHY=mCONFIG_LXT_PHY=mCONFIG_MARVELL_PHY=m
# CONFIG_MARVELL_10G_PHY is not setCONFIG_MICREL_PHY=m
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not setCONFIG_NATIONAL_PHY=m
# CONFIG_NXP_TJA11XX_PHY is not setCONFIG_QSEMI_PHY=mCONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not setCONFIG_SMSC_PHY=mCONFIG_STE10XP=m
# CONFIG_TERANETICS_PHY is not setCONFIG_VITESSE_PHY=m
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PLIP is not setCONFIG_PPP=mCONFIG_PPP_BSDCOMP=mCONFIG_PPP_DEFLATE=mCONFIG_PPP_FILTER=yCONFIG_PPP_MPPE=mCONFIG_PPP_MULTILINK=yCONFIG_PPPOATM=mCONFIG_PPPOE=mCONFIG_PPTP=mCONFIG_PPPOL2TP=mCONFIG_PPP_ASYNC=mCONFIG_PPP_SYNC_TTY=mCONFIG_SLIP=mCONFIG_SLHC=mCONFIG_SLIP_COMPRESSED=yCONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not setCONFIG_USB_NET_DRIVERS=yCONFIG_USB_CATC=yCONFIG_USB_KAWETH=yCONFIG_USB_PEGASUS=yCONFIG_USB_RTL8150=yCONFIG_USB_RTL8152=m
# CONFIG_USB_LAN78XX is not setCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=mCONFIG_USB_NET_CDCETHER=yCONFIG_USB_NET_CDC_EEM=yCONFIG_USB_NET_CDC_NCM=mCONFIG_USB_NET_HUAWEI_CDC_NCM=mCONFIG_USB_NET_CDC_MBIM=mCONFIG_USB_NET_DM9601=y
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not setCONFIG_USB_NET_SMSC75XX=yCONFIG_USB_NET_SMSC95XX=yCONFIG_USB_NET_GL620A=yCONFIG_USB_NET_NET1080=yCONFIG_USB_NET_PLUSB=yCONFIG_USB_NET_MCS7830=yCONFIG_USB_NET_RNDIS_HOST=yCONFIG_USB_NET_CDC_SUBSET_ENABLE=yCONFIG_USB_NET_CDC_SUBSET=yCONFIG_USB_ALI_M5632=yCONFIG_USB_AN2720=yCONFIG_USB_BELKIN=yCONFIG_USB_ARMLINUX=yCONFIG_USB_EPSON2888=yCONFIG_USB_KC2190=yCONFIG_USB_NET_ZAURUS=yCONFIG_USB_NET_CX82310_ETH=mCONFIG_USB_NET_KALMIA=mCONFIG_USB_NET_QMI_WWAN=mCONFIG_USB_HSO=mCONFIG_USB_NET_INT51X1=yCONFIG_USB_IPHETH=yCONFIG_USB_SIERRA_NET=yCONFIG_USB_VL600=m
# CONFIG_USB_NET_CH9200 is not set
# CONFIG_USB_NET_AQC111 is not setCONFIG_WLAN=y
# CONFIG_WIRELESS_WDS is not setCONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not setCONFIG_ATH_COMMON=mCONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not setCONFIG_ATH9K_HW=mCONFIG_ATH9K_COMMON=mCONFIG_ATH9K_BTCOEX_SUPPORT=y
# CONFIG_ATH9K is not setCONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not setCONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not setCONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not setCONFIG_WLAN_VENDOR_CISCO=y
# CONFIG_AIRO is not setCONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not setCONFIG_IWLEGACY=mCONFIG_IWL4965=mCONFIG_IWL3945=m
#
# iwl3945 / iwl4965 Debugging Options # CONFIG_IWLEGACY_DEBUG=y CONFIG_IWLEGACY_DEBUGFS=y # end of iwl3945 / iwl4965 Debugging Options
CONFIG_IWLWIFI=mCONFIG_IWLWIFI_LEDS=yCONFIG_IWLDVM=mCONFIG_IWLMVM=mCONFIG_IWLWIFI_OPMODE_MODULAR=y
# CONFIG_IWLWIFI_BCAST_FILTERING is not set
# CONFIG_IWLWIFI_PCIE_RTPM is not set
#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not setCONFIG_IWLWIFI_DEBUGFS=y
# CONFIG_IWLWIFI_DEVICE_TRACING is not set
# end of Debugging Options
CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not setCONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
# CONFIG_MWL8K is not setCONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x0E is not set
# CONFIG_MT76x2E is not set
# CONFIG_MT76x2U is not set
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not setCONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not setCONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_RTL_CARDS is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not setCONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not setCONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not setCONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not setCONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not setCONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not setCONFIG_MAC80211_HWSIM=m
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers #CONFIG_WAN=y
# CONFIG_LANMEDIA is not setCONFIG_HDLC=mCONFIG_HDLC_RAW=m
# CONFIG_HDLC_RAW_ETH is not set CONFIG_HDLC_CISCO=mCONFIG_HDLC_FR=mCONFIG_HDLC_PPP=m
#
# X.25/LAPB support is disabled
#
# CONFIG_PCI200SYN is not set
# CONFIG_WANXL is not set
# CONFIG_PC300TOO is not set
# CONFIG_FARSYNC is not set
# CONFIG_DSCC4 is not setCONFIG_DLCI=mCONFIG_DLCI_MAX=8
# CONFIG_SBNI is not setCONFIG_IEEE802154_DRIVERS=mCONFIG_IEEE802154_FAKELB=m
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
# CONFIG_IEEE802154_ATUSB is not set
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
# CONFIG_IEEE802154_HWSIM is not setCONFIG_XEN_NETDEV_FRONTEND=mCONFIG_VMXNET3=mCONFIG_FUJITSU_ES=mCONFIG_THUNDERBOLT_NET=mCONFIG_HYPERV_NET=mCONFIG_NETDEVSIM=mCONFIG_NET_FAILOVER=mCONFIG_ISDN=yCONFIG_ISDN_I4L=mCONFIG_ISDN_PPP=yCONFIG_ISDN_PPP_VJ=yCONFIG_ISDN_MPP=yCONFIG_IPPP_FILTER=y
# CONFIG_ISDN_PPP_BSDCOMP is not setCONFIG_ISDN_AUDIO=yCONFIG_ISDN_TTY_FAX=y
#
# ISDN feature submodules
#CONFIG_ISDN_DIVERSION=m
# end of ISDN feature submodules
#
# ISDN4Linux hardware drivers
#
#
# Passive cards
#CONFIG_ISDN_DRV_HISAX=m
#
# D-channel protocol features
#CONFIG_HISAX_EURO=yCONFIG_DE_AOC=yCONFIG_HISAX_NO_SENDCOMPLETE=yCONFIG_HISAX_NO_LLC=yCONFIG_HISAX_NO_KEYPAD=yCONFIG_HISAX_1TR6=yCONFIG_HISAX_NI1=yCONFIG_HISAX_MAX_CARDS=8
#
# HiSax supported cards
#CONFIG_HISAX_16_3=yCONFIG_HISAX_TELESPCI=yCONFIG_HISAX_S0BOX=yCONFIG_HISAX_FRITZPCI=yCONFIG_HISAX_AVM_A1_PCMCIA=yCONFIG_HISAX_ELSA=yCONFIG_HISAX_DIEHLDIVA=yCONFIG_HISAX_SEDLBAUER=yCONFIG_HISAX_NETJET=yCONFIG_HISAX_NETJET_U=yCONFIG_HISAX_NICCY=yCONFIG_HISAX_BKM_A4T=yCONFIG_HISAX_SCT_QUADRO=yCONFIG_HISAX_GAZEL=yCONFIG_HISAX_HFC_PCI=yCONFIG_HISAX_W6692=yCONFIG_HISAX_HFC_SX=yCONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set
#
# HiSax PCMCIA card service modules
#
#
# HiSax sub driver modules
#CONFIG_HISAX_ST5481=m
# CONFIG_HISAX_HFCUSB is not setCONFIG_HISAX_HFC4S8S=mCONFIG_HISAX_FRITZ_PCIPNP=m
# end of Passive cards
CONFIG_ISDN_CAPI=m
# CONFIG_CAPI_TRACE is not setCONFIG_ISDN_CAPI_CAPI20=mCONFIG_ISDN_CAPI_MIDDLEWARE=yCONFIG_ISDN_CAPI_CAPIDRV=m
# CONFIG_ISDN_CAPI_CAPIDRV_VERBOSE is not set
#
# CAPI hardware drivers
#CONFIG_CAPI_AVM=yCONFIG_ISDN_DRV_AVMB1_B1PCI=mCONFIG_ISDN_DRV_AVMB1_B1PCIV4=yCONFIG_ISDN_DRV_AVMB1_T1PCI=mCONFIG_ISDN_DRV_AVMB1_C4=mCONFIG_ISDN_DRV_GIGASET=mCONFIG_GIGASET_CAPI=yCONFIG_GIGASET_BASE=mCONFIG_GIGASET_M105=mCONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not setCONFIG_HYSDN=mCONFIG_HYSDN_CAPI=yCONFIG_MISDN=mCONFIG_MISDN_DSP=mCONFIG_MISDN_L1OIP=m
#
# mISDN hardware drivers
#CONFIG_MISDN_HFCPCI=mCONFIG_MISDN_HFCMULTI=mCONFIG_MISDN_HFCUSB=mCONFIG_MISDN_AVMFRITZ=mCONFIG_MISDN_SPEEDFAX=mCONFIG_MISDN_INFINEON=mCONFIG_MISDN_W6692=mCONFIG_MISDN_NETJET=mCONFIG_MISDN_IPAC=mCONFIG_MISDN_ISAR=mCONFIG_ISDN_HDLC=mCONFIG_NVM=y
# CONFIG_NVM_PBLK is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_POLLDEV=mCONFIG_INPUT_SPARSEKMAP=m
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=mCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_VMMOUSE=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=mCONFIG_MOUSE_APPLETOUCH=mCONFIG_MOUSE_BCM5974=mCONFIG_MOUSE_CYAPA=m
# CONFIG_MOUSE_ELAN_I2C is not setCONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_GPIO is not setCONFIG_MOUSE_SYNAPTICS_I2C=mCONFIG_MOUSE_SYNAPTICS_USB=m
# CONFIG_INPUT_JOYSTICK is not setCONFIG_INPUT_TABLET=yCONFIG_TABLET_USB_ACECAD=mCONFIG_TABLET_USB_AIPTEK=mCONFIG_TABLET_USB_GTCO=m
# CONFIG_TABLET_USB_HANWANG is not setCONFIG_TABLET_USB_KBTAB=m
# CONFIG_TABLET_USB_PEGASUS is not set
# CONFIG_TABLET_SERIAL_WACOM4 is not setCONFIG_INPUT_TOUCHSCREEN=yCONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ADC is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8505 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not setCONFIG_TOUCHSCREEN_ELO=mCONFIG_TOUCHSCREEN_WACOM_W8001=mCONFIG_TOUCHSCREEN_WACOM_I2C=m
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_WM97XX is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not setCONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_MSM_VIBRATOR is not setCONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_MMA8450 is not setCONFIG_INPUT_APANEL=mCONFIG_INPUT_GP2A=m
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not setCONFIG_INPUT_ATLAS_BTNS=mCONFIG_INPUT_ATI_REMOTE2=mCONFIG_INPUT_KEYSPAN_REMOTE=m
# CONFIG_INPUT_KXTJ9 is not setCONFIG_INPUT_POWERMATE=mCONFIG_INPUT_YEALINK=mCONFIG_INPUT_CM109=mCONFIG_INPUT_UINPUT=m
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not setCONFIG_INPUT_GPIO_ROTARY_ENCODER=m
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_CMA3000 is not setCONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not setCONFIG_RMI4_CORE=m
# CONFIG_RMI4_I2C is not set
# CONFIG_RMI4_SPI is not setCONFIG_RMI4_SMB=mCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=mCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=y
# CONFIG_RMI4_F34 is not set
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=mCONFIG_SERIO_ALTERA_PS2=m
# CONFIG_SERIO_PS2MULT is not setCONFIG_SERIO_ARC_PS2=mCONFIG_HYPERV_KEYBOARD=m
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_VT_CONSOLE_SLEEP=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not setCONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not setCONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not setCONFIG_SYNCLINK=mCONFIG_SYNCLINKMP=mCONFIG_SYNCLINK_GT=mCONFIG_NOZOMI=m
# CONFIG_ISI is not setCONFIG_N_HDLC=mCONFIG_N_GSM=m
# CONFIG_TRACE_SINK is not set
# CONFIG_NULL_TTY is not setCONFIG_LDISC_AUTOLOAD=yCONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not set
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y
# CONFIG_SERIAL_8250_MOXA is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_JSM=m
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not setCONFIG_SERIAL_ARC=mCONFIG_SERIAL_ARC_NR_PORTS=1
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# end of Serial drivers
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not setCONFIG_PPDEV=mCONFIG_HVC_DRIVER=yCONFIG_HVC_IRQ=yCONFIG_HVC_XEN=yCONFIG_HVC_XEN_FRONTEND=yCONFIG_VIRTIO_CONSOLE=yCONFIG_IPMI_HANDLER=mCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=y
# CONFIG_IPMI_PANIC_EVENT is not setCONFIG_IPMI_DEVICE_INTERFACE=mCONFIG_IPMI_SI=mCONFIG_IPMI_SSIF=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=mCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=mCONFIG_HW_RANDOM_INTEL=mCONFIG_HW_RANDOM_AMD=mCONFIG_HW_RANDOM_VIA=mCONFIG_HW_RANDOM_VIRTIO=yCONFIG_NVRAM=y
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not setCONFIG_RAW_DRIVER=yCONFIG_MAX_RAW_DEVS=8192CONFIG_HPET=yCONFIG_HPET_MMAP=y
# CONFIG_HPET_MMAP_DEFAULT is not setCONFIG_HANGCHECK_TIMER=mCONFIG_UV_MMTIMER=mCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not setCONFIG_TCG_TIS_I2C_ATMEL=mCONFIG_TCG_TIS_I2C_INFINEON=mCONFIG_TCG_TIS_I2C_NUVOTON=mCONFIG_TCG_NSC=mCONFIG_TCG_ATMEL=mCONFIG_TCG_INFINEON=m
# CONFIG_TCG_XEN is not setCONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not setCONFIG_TCG_TIS_ST33ZP24=mCONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not setCONFIG_TELCLOCK=mCONFIG_DEVPORT=y
# CONFIG_XILLYBUS is not set
# end of Character devices
# CONFIG_RANDOM_TRUST_CPU is not set
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=mCONFIG_I2C_MUX=m
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_REG is not set
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=mCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not setCONFIG_I2C_AMD756=mCONFIG_I2C_AMD756_S4882=mCONFIG_I2C_AMD8111=m
# CONFIG_I2C_AMD_MP2 is not setCONFIG_I2C_I801=mCONFIG_I2C_ISCH=mCONFIG_I2C_ISMT=mCONFIG_I2C_PIIX4=mCONFIG_I2C_NFORCE2=mCONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not setCONFIG_I2C_SIS96X=mCONFIG_I2C_VIA=mCONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m CONFIG_I2C_DESIGNWARE_PLATFORM=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=mCONFIG_I2C_SIMTEC=m
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#CONFIG_I2C_DIOLAN_U2C=mCONFIG_I2C_PARPORT=mCONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not setCONFIG_I2C_TINY_USB=mCONFIG_I2C_VIPERBOARD=m
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_MLXCPLD is not set
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=m
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not setCONFIG_SPI=y
# CONFIG_SPI_DEBUG is not setCONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not setCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not setCONFIG_PPS_CLIENT_LDISC=mCONFIG_PPS_CLIENT_PARPORT=mCONFIG_PPS_CLIENT_GPIO=m
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_DP83640_PHY=mCONFIG_PTP_1588_CLOCK_KVM=m
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_PINMUX=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not setCONFIG_PINCTRL_AMD=m
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_BAYTRAIL=y
# CONFIG_PINCTRL_CHERRYVIEW is not setCONFIG_PINCTRL_INTEL=m
# CONFIG_PINCTRL_BROXTON is not setCONFIG_PINCTRL_CANNONLAKE=m
# CONFIG_PINCTRL_CEDARFORK is not setCONFIG_PINCTRL_DENVERTON=mCONFIG_PINCTRL_GEMINILAKE=m
# CONFIG_PINCTRL_ICELAKE is not setCONFIG_PINCTRL_LEWISBURG=mCONFIG_PINCTRL_SUNRISEPOINT=mCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not setCONFIG_GPIO_SYSFS=yCONFIG_GPIO_GENERIC=m
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_AMDPT=m
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not setCONFIG_GPIO_ICH=m
# CONFIG_GPIO_LYNXPOINT is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# Port-mapped I/O GPIO drivers
#
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#CONFIG_GPIO_VIPERBOARD=m
# end of USB GPIO expanders
CONFIG_GPIO_MOCKUP=y
# CONFIG_W1 is not set
# CONFIG_POWER_AVS is not setCONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_RESTART is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ25890 is not setCONFIG_CHARGER_SMB347=m
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_CHARGER_RT9455 is not setCONFIG_HWMON=yCONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_ABITUGURU=mCONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not setCONFIG_SENSORS_AD7414=mCONFIG_SENSORS_AD7418=mCONFIG_SENSORS_ADM1021=mCONFIG_SENSORS_ADM1025=mCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=mCONFIG_SENSORS_ADM1031=mCONFIG_SENSORS_ADM9240=mCONFIG_SENSORS_ADT7X10=m
# CONFIG_SENSORS_ADT7310 is not setCONFIG_SENSORS_ADT7410=mCONFIG_SENSORS_ADT7411=mCONFIG_SENSORS_ADT7462=mCONFIG_SENSORS_ADT7470=mCONFIG_SENSORS_ADT7475=mCONFIG_SENSORS_ASC7621=mCONFIG_SENSORS_K8TEMP=mCONFIG_SENSORS_K10TEMP=mCONFIG_SENSORS_FAM15H_POWER=mCONFIG_SENSORS_APPLESMC=mCONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ASPEED is not setCONFIG_SENSORS_ATXP1=mCONFIG_SENSORS_DS620=mCONFIG_SENSORS_DS1621=mCONFIG_SENSORS_DELL_SMM=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=mCONFIG_SENSORS_F71882FG=mCONFIG_SENSORS_F75375S=mCONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_FTSTEUTATES is not setCONFIG_SENSORS_GL518SM=mCONFIG_SENSORS_GL520SM=mCONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_HIH6130 is not setCONFIG_SENSORS_IBMAEM=mCONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
# CONFIG_SENSORS_I5500 is not setCONFIG_SENSORS_CORETEMP=mCONFIG_SENSORS_IT87=mCONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not setCONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not setCONFIG_SENSORS_LTC4151=mCONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not setCONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not setCONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not setCONFIG_SENSORS_MAX16065=mCONFIG_SENSORS_MAX1619=mCONFIG_SENSORS_MAX1668=mCONFIG_SENSORS_MAX197=m
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX6621 is not setCONFIG_SENSORS_MAX6639=mCONFIG_SENSORS_MAX6642=mCONFIG_SENSORS_MAX6650=mCONFIG_SENSORS_MAX6697=m
# CONFIG_SENSORS_MAX31790 is not setCONFIG_SENSORS_MCP3021=m
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_ADCXX is not setCONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not setCONFIG_SENSORS_LM73=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=mCONFIG_SENSORS_LM78=mCONFIG_SENSORS_LM80=mCONFIG_SENSORS_LM83=mCONFIG_SENSORS_LM85=mCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LM90=mCONFIG_SENSORS_LM92=mCONFIG_SENSORS_LM93=mCONFIG_SENSORS_LM95234=mCONFIG_SENSORS_LM95241=mCONFIG_SENSORS_LM95245=mCONFIG_SENSORS_PC87360=mCONFIG_SENSORS_PC87427=mCONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not setCONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not setCONFIG_SENSORS_PCF8591=mCONFIG_PMBUS=mCONFIG_SENSORS_PMBUS=mCONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_IBM_CFFPS is not set
# CONFIG_SENSORS_IR35221 is not set
# CONFIG_SENSORS_IR38064 is not set
# CONFIG_SENSORS_ISL68137 is not setCONFIG_SENSORS_LM25066=mCONFIG_SENSORS_LTC2978=m
# CONFIG_SENSORS_LTC3815 is not setCONFIG_SENSORS_MAX16064=m
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not setCONFIG_SENSORS_MAX34440=mCONFIG_SENSORS_MAX8688=m
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not setCONFIG_SENSORS_UCD9000=mCONFIG_SENSORS_UCD9200=mCONFIG_SENSORS_ZL6100=mCONFIG_SENSORS_SHT15=mCONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not setCONFIG_SENSORS_SIS5595=mCONFIG_SENSORS_DME1737=mCONFIG_SENSORS_EMC1403=m
# CONFIG_SENSORS_EMC2103 is not setCONFIG_SENSORS_EMC6W201=mCONFIG_SENSORS_SMSC47M1=mCONFIG_SENSORS_SMSC47M192=mCONFIG_SENSORS_SMSC47B397=mCONFIG_SENSORS_SCH56XX_COMMON=mCONFIG_SENSORS_SCH5627=mCONFIG_SENSORS_SCH5636=m
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not setCONFIG_SENSORS_ADS1015=mCONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_ADS7871 is not setCONFIG_SENSORS_AMC6821=mCONFIG_SENSORS_INA209=mCONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not setCONFIG_SENSORS_THMC50=mCONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not setCONFIG_SENSORS_TMP401=mCONFIG_SENSORS_TMP421=mCONFIG_SENSORS_VIA_CPUTEMP=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=mCONFIG_SENSORS_VT8231=m
# CONFIG_SENSORS_W83773G is not setCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83791D=mCONFIG_SENSORS_W83792D=mCONFIG_SENSORS_W83793=mCONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not setCONFIG_SENSORS_W83L785TS=mCONFIG_SENSORS_W83L786NG=mCONFIG_SENSORS_W83627HF=mCONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_XGENE is not set
#
# ACPI drivers
#CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=mCONFIG_THERMAL=y
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set # CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not set # CONFIG_CLOCK_THERMAL is not set
# CONFIG_DEVFREQ_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
#
# Intel thermal drivers
#CONFIG_INTEL_POWERCLAMP=mCONFIG_X86_PKG_TEMP_THERMAL=mCONFIG_INTEL_SOC_DTS_IOSF_CORE=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set
#
# ACPI INT340X thermal drivers
#CONFIG_INT340X_THERMAL=mCONFIG_ACPI_THERMAL_REL=m
# CONFIG_INT3406_THERMAL is not set
# end of ACPI INT340X thermal drivers
# CONFIG_INTEL_PCH_THERMAL is not set
# end of Intel thermal drivers
# CONFIG_GENERIC_ADC_THERMAL is not setCONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not setCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_SYSFS=y
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=mCONFIG_WDAT_WDT=m
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not setCONFIG_ALIM1535_WDT=mCONFIG_ALIM7101_WDT=m
# CONFIG_EBC_C384_WDT is not setCONFIG_F71808E_WDT=mCONFIG_SP5100_TCO=mCONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not setCONFIG_IB700_WDT=mCONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not setCONFIG_I6300ESB_WDT=yCONFIG_IE6XX_WDT=mCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=yCONFIG_IT8712F_WDT=mCONFIG_IT87_WDT=mCONFIG_HP_WATCHDOG=mCONFIG_HPWDT_NMI_DECODING=y
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not setCONFIG_NV_TCO=m
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not setCONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not setCONFIG_VIA_WDT=mCONFIG_W83627HF_WDT=mCONFIG_W83877F_WDT=mCONFIG_W83977F_WDT=mCONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not setCONFIG_INTEL_MEI_WDT=m
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not setCONFIG_XEN_WDT=m
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=mCONFIG_WDTPCI=m
#
# USB-based Watchdog Cards
#CONFIG_USBPCWATCHDOG=mCONFIG_SSB_POSSIBLE=yCONFIG_SSB=mCONFIG_SSB_SPROM=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=yCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=yCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=yCONFIG_SSB_DRIVER_GPIO=yCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not setCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_CROS_EC is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not setCONFIG_LPC_ICH=mCONFIG_LPC_SCH=m
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not setCONFIG_MFD_INTEL_LPSS=yCONFIG_MFD_INTEL_LPSS_ACPI=yCONFIG_MFD_INTEL_LPSS_PCI=y
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not setCONFIG_MFD_VIPERBOARD=m
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_UCB1400_CORE is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not setCONFIG_MFD_SM501=mCONFIG_MFD_SM501_GPIO=y
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_SMSC is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TQMX86 is not setCONFIG_MFD_VX855=m
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not setCONFIG_RC_CORE=mCONFIG_RC_MAP=mCONFIG_LIRC=yCONFIG_RC_DECODERS=yCONFIG_IR_NEC_DECODER=mCONFIG_IR_RC5_DECODER=mCONFIG_IR_RC6_DECODER=mCONFIG_IR_JVC_DECODER=mCONFIG_IR_SONY_DECODER=mCONFIG_IR_SANYO_DECODER=mCONFIG_IR_SHARP_DECODER=mCONFIG_IR_MCE_KBD_DECODER=m
# CONFIG_IR_XMP_DECODER is not set
# CONFIG_IR_IMON_DECODER is not set
# CONFIG_IR_RCMM_DECODER is not setCONFIG_RC_DEVICES=yCONFIG_RC_ATI_REMOTE=mCONFIG_IR_ENE=mCONFIG_IR_IMON=m
# CONFIG_IR_IMON_RAW is not setCONFIG_IR_MCEUSB=mCONFIG_IR_ITE_CIR=mCONFIG_IR_FINTEK=mCONFIG_IR_NUVOTON=mCONFIG_IR_REDRAT3=mCONFIG_IR_STREAMZAP=mCONFIG_IR_WINBOND_CIR=m
# CONFIG_IR_IGORPLUGUSB is not setCONFIG_IR_IGUANA=mCONFIG_IR_TTUSBIR=mCONFIG_RC_LOOPBACK=m
# CONFIG_IR_SERIAL is not set
# CONFIG_IR_SIR is not set
# CONFIG_RC_XBOX_DVD is not setCONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=yCONFIG_MEDIA_DIGITAL_TV_SUPPORT=yCONFIG_MEDIA_RADIO_SUPPORT=y
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_CEC_SUPPORT is not setCONFIG_MEDIA_CONTROLLER=yCONFIG_MEDIA_CONTROLLER_DVB=yCONFIG_VIDEO_DEV=m
# CONFIG_VIDEO_V4L2_SUBDEV_API is not setCONFIG_VIDEO_V4L2=m
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not setCONFIG_VIDEO_TUNER=mCONFIG_VIDEOBUF_GEN=mCONFIG_VIDEOBUF_DMA_SG=mCONFIG_VIDEOBUF_VMALLOC=mCONFIG_DVB_CORE=m
# CONFIG_DVB_MMAP is not setCONFIG_DVB_NET=yCONFIG_TTPCI_EEPROM=mCONFIG_DVB_MAX_ADAPTERS=8CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
#
# Media drivers
#CONFIG_MEDIA_USB_SUPPORT=y
#
# Webcam devices
#CONFIG_USB_VIDEO_CLASS=mCONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=yCONFIG_USB_GSPCA=mCONFIG_USB_M5602=mCONFIG_USB_STV06XX=mCONFIG_USB_GL860=mCONFIG_USB_GSPCA_BENQ=mCONFIG_USB_GSPCA_CONEX=mCONFIG_USB_GSPCA_CPIA1=m
# CONFIG_USB_GSPCA_DTCS033 is not setCONFIG_USB_GSPCA_ETOMS=mCONFIG_USB_GSPCA_FINEPIX=mCONFIG_USB_GSPCA_JEILINJ=mCONFIG_USB_GSPCA_JL2005BCD=m
# CONFIG_USB_GSPCA_KINECT is not setCONFIG_USB_GSPCA_KONICA=mCONFIG_USB_GSPCA_MARS=mCONFIG_USB_GSPCA_MR97310A=mCONFIG_USB_GSPCA_NW80X=mCONFIG_USB_GSPCA_OV519=mCONFIG_USB_GSPCA_OV534=mCONFIG_USB_GSPCA_OV534_9=mCONFIG_USB_GSPCA_PAC207=mCONFIG_USB_GSPCA_PAC7302=mCONFIG_USB_GSPCA_PAC7311=mCONFIG_USB_GSPCA_SE401=mCONFIG_USB_GSPCA_SN9C2028=mCONFIG_USB_GSPCA_SN9C20X=mCONFIG_USB_GSPCA_SONIXB=mCONFIG_USB_GSPCA_SONIXJ=mCONFIG_USB_GSPCA_SPCA500=mCONFIG_USB_GSPCA_SPCA501=mCONFIG_USB_GSPCA_SPCA505=mCONFIG_USB_GSPCA_SPCA506=mCONFIG_USB_GSPCA_SPCA508=mCONFIG_USB_GSPCA_SPCA561=mCONFIG_USB_GSPCA_SPCA1528=mCONFIG_USB_GSPCA_SQ905=mCONFIG_USB_GSPCA_SQ905C=mCONFIG_USB_GSPCA_SQ930X=mCONFIG_USB_GSPCA_STK014=m
# CONFIG_USB_GSPCA_STK1135 is not setCONFIG_USB_GSPCA_STV0680=mCONFIG_USB_GSPCA_SUNPLUS=mCONFIG_USB_GSPCA_T613=mCONFIG_USB_GSPCA_TOPRO=m
# CONFIG_USB_GSPCA_TOUPTEK is not setCONFIG_USB_GSPCA_TV8532=mCONFIG_USB_GSPCA_VC032X=mCONFIG_USB_GSPCA_VICAM=mCONFIG_USB_GSPCA_XIRLINK_CIT=mCONFIG_USB_GSPCA_ZC3XX=mCONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not setCONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_VIDEO_CPIA2 is not setCONFIG_USB_ZR364XX=mCONFIG_USB_STKWEBCAM=mCONFIG_USB_S2255=m
# CONFIG_VIDEO_USBTV is not set
#
# Analog TV USB devices
#CONFIG_VIDEO_PVRUSB2=mCONFIG_VIDEO_PVRUSB2_SYSFS=yCONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not setCONFIG_VIDEO_HDPVR=mCONFIG_VIDEO_USBVISION=m
# CONFIG_VIDEO_STK1160_COMMON is not set
# CONFIG_VIDEO_GO7007 is not set
#
# Analog/digital TV USB devices
#CONFIG_VIDEO_AU0828=mCONFIG_VIDEO_AU0828_V4L2=y
# CONFIG_VIDEO_AU0828_RC is not setCONFIG_VIDEO_CX231XX=mCONFIG_VIDEO_CX231XX_RC=yCONFIG_VIDEO_CX231XX_ALSA=mCONFIG_VIDEO_CX231XX_DVB=mCONFIG_VIDEO_TM6000=mCONFIG_VIDEO_TM6000_ALSA=mCONFIG_VIDEO_TM6000_DVB=m
#
# Digital TV USB devices
#CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not setCONFIG_DVB_USB_DIB3000MC=mCONFIG_DVB_USB_A800=mCONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not setCONFIG_DVB_USB_DIBUSB_MC=mCONFIG_DVB_USB_DIB0700=mCONFIG_DVB_USB_UMT_010=mCONFIG_DVB_USB_CXUSB=mCONFIG_DVB_USB_M920X=mCONFIG_DVB_USB_DIGITV=mCONFIG_DVB_USB_VP7045=mCONFIG_DVB_USB_VP702X=mCONFIG_DVB_USB_GP8PSK=mCONFIG_DVB_USB_NOVA_T_USB2=mCONFIG_DVB_USB_TTUSB2=mCONFIG_DVB_USB_DTT200U=mCONFIG_DVB_USB_OPERA1=mCONFIG_DVB_USB_AF9005=mCONFIG_DVB_USB_AF9005_REMOTE=mCONFIG_DVB_USB_PCTV452E=mCONFIG_DVB_USB_DW2102=mCONFIG_DVB_USB_CINERGY_T2=mCONFIG_DVB_USB_DTV5100=mCONFIG_DVB_USB_AZ6027=mCONFIG_DVB_USB_TECHNISAT_USB2=mCONFIG_DVB_USB_V2=mCONFIG_DVB_USB_AF9015=mCONFIG_DVB_USB_AF9035=mCONFIG_DVB_USB_ANYSEE=mCONFIG_DVB_USB_AU6610=mCONFIG_DVB_USB_AZ6007=mCONFIG_DVB_USB_CE6230=mCONFIG_DVB_USB_EC168=mCONFIG_DVB_USB_GL861=mCONFIG_DVB_USB_LME2510=mCONFIG_DVB_USB_MXL111SF=mCONFIG_DVB_USB_RTL28XXU=m
# CONFIG_DVB_USB_DVBSKY is not set
# CONFIG_DVB_USB_ZD1301 is not setCONFIG_DVB_TTUSB_BUDGET=mCONFIG_DVB_TTUSB_DEC=mCONFIG_SMS_USB_DRV=mCONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set
# CONFIG_DVB_AS102 is not set
#
# Webcam, TV (analog/digital) USB devices
#CONFIG_VIDEO_EM28XX=m
# CONFIG_VIDEO_EM28XX_V4L2 is not setCONFIG_VIDEO_EM28XX_ALSA=mCONFIG_VIDEO_EM28XX_DVB=mCONFIG_VIDEO_EM28XX_RC=mCONFIG_MEDIA_PCI_SUPPORT=y
#
# Media capture support
#
# CONFIG_VIDEO_MEYE is not set
# CONFIG_VIDEO_SOLO6X10 is not set
# CONFIG_VIDEO_TW5864 is not set
# CONFIG_VIDEO_TW68 is not set
# CONFIG_VIDEO_TW686X is not set
#
# Media capture/analog TV support
#CONFIG_VIDEO_IVTV=m
# CONFIG_VIDEO_IVTV_DEPRECATED_IOCTLS is not set
# CONFIG_VIDEO_IVTV_ALSA is not setCONFIG_VIDEO_FB_IVTV=m
# CONFIG_VIDEO_FB_IVTV_FORCE_PAT is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DT3155 is not set
#
# Media capture/analog/hybrid TV support
#CONFIG_VIDEO_CX18=mCONFIG_VIDEO_CX18_ALSA=mCONFIG_VIDEO_CX23885=mCONFIG_MEDIA_ALTERA_CI=m
# CONFIG_VIDEO_CX25821 is not setCONFIG_VIDEO_CX88=mCONFIG_VIDEO_CX88_ALSA=mCONFIG_VIDEO_CX88_BLACKBIRD=mCONFIG_VIDEO_CX88_DVB=mCONFIG_VIDEO_CX88_ENABLE_VP3054=yCONFIG_VIDEO_CX88_VP3054=mCONFIG_VIDEO_CX88_MPEG=mCONFIG_VIDEO_BT848=mCONFIG_DVB_BT8XX=mCONFIG_VIDEO_SAA7134=mCONFIG_VIDEO_SAA7134_ALSA=mCONFIG_VIDEO_SAA7134_RC=yCONFIG_VIDEO_SAA7134_DVB=mCONFIG_VIDEO_SAA7164=m
#
# Media digital TV PCI Adapters
#CONFIG_DVB_AV7110_IR=yCONFIG_DVB_AV7110=mCONFIG_DVB_AV7110_OSD=yCONFIG_DVB_BUDGET_CORE=mCONFIG_DVB_BUDGET=mCONFIG_DVB_BUDGET_CI=mCONFIG_DVB_BUDGET_AV=mCONFIG_DVB_BUDGET_PATCH=mCONFIG_DVB_B2C2_FLEXCOP_PCI=m
# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not setCONFIG_DVB_PLUTO2=mCONFIG_DVB_DM1105=mCONFIG_DVB_PT1=m
# CONFIG_DVB_PT3 is not setCONFIG_MANTIS_CORE=mCONFIG_DVB_MANTIS=mCONFIG_DVB_HOPPER=mCONFIG_DVB_NGENE=mCONFIG_DVB_DDBRIDGE=m
# CONFIG_DVB_DDBRIDGE_MSIENABLE is not set
# CONFIG_DVB_SMIPCIE is not set
# CONFIG_DVB_NETUP_UNIDVB is not set
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_V4L_TEST_DRIVERS is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
#
# Supported MMC/SDIO adapters
#CONFIG_SMS_SDIO_DRV=mCONFIG_RADIO_ADAPTERS=yCONFIG_RADIO_TEA575X=m
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
#
# Texas Instruments WL128x FM driver (ST based)
#
# end of Texas Instruments WL128x FM driver (ST based)
#
# Supported FireWire (IEEE 1394) Adapters
#CONFIG_DVB_FIREDTV=mCONFIG_DVB_FIREDTV_INPUT=yCONFIG_MEDIA_COMMON_OPTIONS=y
#
# common driver options # CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_TVEEPROM=m CONFIG_CYPRESS_FIRMWARE=m CONFIG_VIDEOBUF2_CORE=m CONFIG_VIDEOBUF2_V4L2=m CONFIG_VIDEOBUF2_MEMOPS=m CONFIG_VIDEOBUF2_VMALLOC=m CONFIG_VIDEOBUF2_DMA_SG=m CONFIG_VIDEOBUF2_DVB=m CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_SMS_SIANO_MDTV=m CONFIG_SMS_SIANO_RC=y # CONFIG_SMS_SIANO_DEBUGFS is not set
#
# Media ancillary drivers (tuners, sensors, i2c, spi, frontends) #CONFIG_MEDIA_SUBDRV_AUTOSELECT=yCONFIG_MEDIA_ATTACH=yCONFIG_VIDEO_IR_I2C=m
#
# Audio decoders, processors and mixers
#CONFIG_VIDEO_TVAUDIO=mCONFIG_VIDEO_TDA7432=mCONFIG_VIDEO_MSP3400=mCONFIG_VIDEO_CS3308=mCONFIG_VIDEO_CS5345=mCONFIG_VIDEO_CS53L32A=mCONFIG_VIDEO_WM8775=mCONFIG_VIDEO_WM8739=mCONFIG_VIDEO_VP27SMPX=m
#
# RDS decoders
#CONFIG_VIDEO_SAA6588=m
#
# Video decoders
#CONFIG_VIDEO_SAA711X=m
#
# Video and audio decoders
#CONFIG_VIDEO_SAA717X=mCONFIG_VIDEO_CX25840=m
#
# Video encoders
#CONFIG_VIDEO_SAA7127=m
#
# Camera sensor devices
#
#
# Lens drivers
#
#
# Flash devices
#
#
# Video improvement chips
#CONFIG_VIDEO_UPD64031A=mCONFIG_VIDEO_UPD64083=m
#
# Audio/Video compression chips
#CONFIG_VIDEO_SAA6752HS=m
#
# SDR tuner chips
#
#
# Miscellaneous helper chips
#CONFIG_VIDEO_M52790=m
#
# Media SPI Adapters
#
# CONFIG_CXD2880_SPI_DRV is not set
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=mCONFIG_MEDIA_TUNER_SIMPLE=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA8290=mCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=mCONFIG_MEDIA_TUNER_TEA5761=mCONFIG_MEDIA_TUNER_TEA5767=mCONFIG_MEDIA_TUNER_MT20XX=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=mCONFIG_MEDIA_TUNER_XC5000=mCONFIG_MEDIA_TUNER_XC4000=mCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_MC44S803=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_FC0011=mCONFIG_MEDIA_TUNER_FC0012=mCONFIG_MEDIA_TUNER_FC0013=mCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_E4000=mCONFIG_MEDIA_TUNER_FC2580=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_TUA9001=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_R820T=mCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QM1D1B0004=m
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=mCONFIG_DVB_STV6111=mCONFIG_DVB_MXL5XX=mCONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#CONFIG_DVB_DRXK=mCONFIG_DVB_TDA18271C2DD=mCONFIG_DVB_SI2165=mCONFIG_DVB_MN88472=mCONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_ZL10036=mCONFIG_DVB_ZL10039=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=mCONFIG_DVB_STB6000=mCONFIG_DVB_STV0299=mCONFIG_DVB_STV6110=mCONFIG_DVB_STV0900=mCONFIG_DVB_TDA8083=mCONFIG_DVB_TDA10086=mCONFIG_DVB_TDA8261=mCONFIG_DVB_VES1X93=mCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=mCONFIG_DVB_TUA6100=mCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_SI21XX=mCONFIG_DVB_TS2020=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=mCONFIG_DVB_TDA10071=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP8870=mCONFIG_DVB_SP887X=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_DRXD=mCONFIG_DVB_L64781=mCONFIG_DVB_TDA1004X=mCONFIG_DVB_NXT6000=mCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=mCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=mCONFIG_DVB_TDA10048=mCONFIG_DVB_AF9013=mCONFIG_DVB_EC100=mCONFIG_DVB_STV0367=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=mCONFIG_DVB_RTL2830=mCONFIG_DVB_RTL2832=mCONFIG_DVB_SI2168=mCONFIG_DVB_GP8PSK_FE=m
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=mCONFIG_DVB_TDA10021=mCONFIG_DVB_TDA10023=mCONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=mCONFIG_DVB_OR51132=mCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3305=mCONFIG_DVB_LGDT3306A=mCONFIG_DVB_LG2160=mCONFIG_DVB_S5H1409=mCONFIG_DVB_AU8522=mCONFIG_DVB_AU8522_DTV=mCONFIG_DVB_AU8522_V4L=mCONFIG_DVB_S5H1411=m
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_S921=mCONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_TC90522=m
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=mCONFIG_DVB_TUNER_DIB0070=mCONFIG_DVB_TUNER_DIB0090=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_DRX39XYJ=mCONFIG_DVB_LNBH25=mCONFIG_DVB_LNBP21=mCONFIG_DVB_LNBP22=mCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=mCONFIG_DVB_ISL6423=mCONFIG_DVB_A8293=mCONFIG_DVB_LGS8GXX=mCONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=mCONFIG_DVB_IX2505V=mCONFIG_DVB_M88RS2000=mCONFIG_DVB_AF9033=m
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=m
#
# Tools to develop new frontends
#CONFIG_DVB_DUMMY_FE=m
#
# Graphics support
#CONFIG_AGP=yCONFIG_AGP_AMD64=yCONFIG_AGP_INTEL=yCONFIG_AGP_SIS=yCONFIG_AGP_VIA=yCONFIG_INTEL_GTT=yCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=64CONFIG_VGA_SWITCHEROO=yCONFIG_DRM=mCONFIG_DRM_MIPI_DSI=yCONFIG_DRM_DP_AUX_CHARDEV=yCONFIG_DRM_DEBUG_SELFTEST=mCONFIG_DRM_KMS_HELPER=mCONFIG_DRM_KMS_FB_HELPER=yCONFIG_DRM_FBDEV_EMULATION=yCONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not setCONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not setCONFIG_DRM_TTM=mCONFIG_DRM_GEM_SHMEM_HELPER=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=mCONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
#
# ACP (Audio CoProcessor) Configuration
#
# end of ACP (Audio CoProcessor) Configuration
# CONFIG_DRM_NOUVEAU is not setCONFIG_DRM_I915=m
# CONFIG_DRM_I915_ALPHA_SUPPORT is not setCONFIG_DRM_I915_CAPTURE_ERROR=yCONFIG_DRM_I915_COMPRESS_ERROR=yCONFIG_DRM_I915_USERPTR=yCONFIG_DRM_I915_GVT=yCONFIG_DRM_I915_GVT_KVMGT=m
#
# drm/i915 Debugging # # CONFIG_DRM_I915_WERROR is not set # CONFIG_DRM_I915_DEBUG is not set # CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set # CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set # CONFIG_DRM_I915_DEBUG_GUC is not set # CONFIG_DRM_I915_SELFTEST is not set # CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set # CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set # CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set # end of drm/i915 Debugging
CONFIG_DRM_VGEM=m
# CONFIG_DRM_VKMS is not setCONFIG_DRM_VMWGFX=mCONFIG_DRM_VMWGFX_FBCON=yCONFIG_DRM_GMA500=mCONFIG_DRM_GMA600=yCONFIG_DRM_GMA3600=yCONFIG_DRM_UDL=mCONFIG_DRM_AST=mCONFIG_DRM_MGAG200=mCONFIG_DRM_CIRRUS_QEMU=mCONFIG_DRM_QXL=mCONFIG_DRM_BOCHS=mCONFIG_DRM_VIRTIO_GPU=mCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# end of Display Interface Bridges
# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_HISI_HIBMC is not set
# CONFIG_DRM_TINYDRM is not set
# CONFIG_DRM_XEN is not set
# CONFIG_DRM_VBOXVIDEO is not set
# CONFIG_DRM_LEGACY is not setCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=yCONFIG_DRM_LIB_RANDOM=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=mCONFIG_FB_SYS_COPYAREA=mCONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=mCONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_MODE_HELPERS is not setCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not setCONFIG_FB_VESA=yCONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SM501 is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not setCONFIG_FB_HYPERV=m
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SM712 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not setCONFIG_LCD_PLATFORM=m
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not setCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PWM is not setCONFIG_BACKLIGHT_APPLE=m
# CONFIG_BACKLIGHT_PM8941_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not setCONFIG_BACKLIGHT_LP855X=m
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# end of Backlight & LCD device support
CONFIG_HDMI=y
#
# Console display driver support
#CONFIG_VGA_CONSOLE=yCONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
# CONFIG_VGACON_SOFT_SCROLLBACK_PERSISTENT_ENABLE_BY_DEFAULT is not set CONFIG_DUMMY_CONSOLE=yCONFIG_DUMMY_CONSOLE_COLUMNS=80CONFIG_DUMMY_CONSOLE_ROWS=25CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not setCONFIG_LOGO_LINUX_CLUT224=y
# end of Graphics support
CONFIG_SOUND=mCONFIG_SOUND_OSS_CORE=yCONFIG_SOUND_OSS_CORE_PRECLAIM=yCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_PCM_ELD=yCONFIG_SND_HWDEP=mCONFIG_SND_SEQ_DEVICE=mCONFIG_SND_RAWMIDI=mCONFIG_SND_COMPRESS_OFFLOAD=mCONFIG_SND_JACK=yCONFIG_SND_JACK_INPUT_DEV=yCONFIG_SND_OSSEMUL=y
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not setCONFIG_SND_PCM_TIMER=yCONFIG_SND_HRTIMER=mCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_MAX_CARDS=32
# CONFIG_SND_SUPPORT_OLD_API is not setCONFIG_SND_PROC_FS=yCONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not setCONFIG_SND_VMASTER=yCONFIG_SND_DMA_SGBUF=yCONFIG_SND_SEQUENCER=mCONFIG_SND_SEQ_DUMMY=mCONFIG_SND_SEQUENCER_OSS=mCONFIG_SND_SEQ_HRTIMER_DEFAULT=yCONFIG_SND_SEQ_MIDI_EVENT=mCONFIG_SND_SEQ_MIDI=mCONFIG_SND_SEQ_MIDI_EMUL=mCONFIG_SND_SEQ_VIRMIDI=mCONFIG_SND_MPU401_UART=mCONFIG_SND_OPL3_LIB=mCONFIG_SND_OPL3_LIB_SEQ=mCONFIG_SND_VX_LIB=mCONFIG_SND_AC97_CODEC=mCONFIG_SND_DRIVERS=yCONFIG_SND_PCSP=mCONFIG_SND_DUMMY=mCONFIG_SND_ALOOP=mCONFIG_SND_VIRMIDI=mCONFIG_SND_MTPAV=m
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not setCONFIG_SND_MPU401=m
# CONFIG_SND_PORTMAN2X4 is not setCONFIG_SND_AC97_POWER_SAVE=yCONFIG_SND_AC97_POWER_SAVE_DEFAULT=5CONFIG_SND_PCI=yCONFIG_SND_AD1889=m
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not setCONFIG_SND_ALI5451=mCONFIG_SND_ASIHPI=mCONFIG_SND_ATIIXP=mCONFIG_SND_ATIIXP_MODEM=mCONFIG_SND_AU8810=mCONFIG_SND_AU8820=mCONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not setCONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not setCONFIG_SND_CA0106=mCONFIG_SND_CMIPCI=mCONFIG_SND_OXYGEN_LIB=mCONFIG_SND_OXYGEN=m
# CONFIG_SND_CS4281 is not setCONFIG_SND_CS46XX=mCONFIG_SND_CS46XX_NEW_DSP=yCONFIG_SND_CTXFI=mCONFIG_SND_DARLA20=mCONFIG_SND_GINA20=mCONFIG_SND_LAYLA20=mCONFIG_SND_DARLA24=mCONFIG_SND_GINA24=mCONFIG_SND_LAYLA24=mCONFIG_SND_MONA=mCONFIG_SND_MIA=mCONFIG_SND_ECHO3G=mCONFIG_SND_INDIGO=mCONFIG_SND_INDIGOIO=mCONFIG_SND_INDIGODJ=mCONFIG_SND_INDIGOIOX=mCONFIG_SND_INDIGODJX=mCONFIG_SND_EMU10K1=mCONFIG_SND_EMU10K1_SEQ=mCONFIG_SND_EMU10K1X=mCONFIG_SND_ENS1370=mCONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not setCONFIG_SND_ES1968=mCONFIG_SND_ES1968_INPUT=yCONFIG_SND_ES1968_RADIO=y
# CONFIG_SND_FM801 is not setCONFIG_SND_HDSP=mCONFIG_SND_HDSPM=mCONFIG_SND_ICE1712=mCONFIG_SND_ICE1724=mCONFIG_SND_INTEL8X0=mCONFIG_SND_INTEL8X0M=mCONFIG_SND_KORG1212=mCONFIG_SND_LOLA=mCONFIG_SND_LX6464ES=mCONFIG_SND_MAESTRO3=mCONFIG_SND_MAESTRO3_INPUT=yCONFIG_SND_MIXART=m
# CONFIG_SND_NM256 is not setCONFIG_SND_PCXHR=m
# CONFIG_SND_RIPTIDE is not setCONFIG_SND_RME32=mCONFIG_SND_RME96=mCONFIG_SND_RME9652=m
# CONFIG_SND_SONICVIBES is not setCONFIG_SND_TRIDENT=mCONFIG_SND_VIA82XX=mCONFIG_SND_VIA82XX_MODEM=mCONFIG_SND_VIRTUOSO=mCONFIG_SND_VX222=m
# CONFIG_SND_YMFPCI is not set
#
# HD-Audio
#CONFIG_SND_HDA=mCONFIG_SND_HDA_INTEL=mCONFIG_SND_HDA_HWDEP=yCONFIG_SND_HDA_RECONFIG=yCONFIG_SND_HDA_INPUT_BEEP=yCONFIG_SND_HDA_INPUT_BEEP_MODE=0CONFIG_SND_HDA_PATCH_LOADER=yCONFIG_SND_HDA_CODEC_REALTEK=mCONFIG_SND_HDA_CODEC_ANALOG=mCONFIG_SND_HDA_CODEC_SIGMATEL=mCONFIG_SND_HDA_CODEC_VIA=mCONFIG_SND_HDA_CODEC_HDMI=mCONFIG_SND_HDA_CODEC_CIRRUS=mCONFIG_SND_HDA_CODEC_CONEXANT=mCONFIG_SND_HDA_CODEC_CA0110=mCONFIG_SND_HDA_CODEC_CA0132=mCONFIG_SND_HDA_CODEC_CA0132_DSP=yCONFIG_SND_HDA_CODEC_CMEDIA=mCONFIG_SND_HDA_CODEC_SI3054=mCONFIG_SND_HDA_GENERIC=mCONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# end of HD-Audio
CONFIG_SND_HDA_CORE=mCONFIG_SND_HDA_DSP_LOADER=yCONFIG_SND_HDA_COMPONENT=yCONFIG_SND_HDA_I915=yCONFIG_SND_HDA_EXT_CORE=mCONFIG_SND_HDA_PREALLOC_SIZE=512
# CONFIG_SND_SPI is not setCONFIG_SND_USB=yCONFIG_SND_USB_AUDIO=mCONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=yCONFIG_SND_USB_UA101=mCONFIG_SND_USB_USX2Y=mCONFIG_SND_USB_CAIAQ=mCONFIG_SND_USB_CAIAQ_INPUT=yCONFIG_SND_USB_US122L=mCONFIG_SND_USB_6FIRE=mCONFIG_SND_USB_HIFACE=mCONFIG_SND_BCD2000=mCONFIG_SND_USB_LINE6=mCONFIG_SND_USB_POD=mCONFIG_SND_USB_PODHD=mCONFIG_SND_USB_TONEPORT=mCONFIG_SND_USB_VARIAX=mCONFIG_SND_FIREWIRE=yCONFIG_SND_FIREWIRE_LIB=m
# CONFIG_SND_DICE is not set
# CONFIG_SND_OXFW is not setCONFIG_SND_ISIGHT=m
# CONFIG_SND_FIREWORKS is not set
# CONFIG_SND_BEBOB is not set
# CONFIG_SND_FIREWIRE_DIGI00X is not set
# CONFIG_SND_FIREWIRE_TASCAM is not set
# CONFIG_SND_FIREWIRE_MOTU is not set
# CONFIG_SND_FIREFACE is not setCONFIG_SND_SOC=mCONFIG_SND_SOC_COMPRESS=yCONFIG_SND_SOC_TOPOLOGY=yCONFIG_SND_SOC_ACPI=m
# CONFIG_SND_SOC_AMD_ACP is not set
# CONFIG_SND_SOC_AMD_ACP3x is not set
# CONFIG_SND_ATMEL_SOC is not set
# CONFIG_SND_DESIGNWARE_I2S is not set
#
# SoC Audio for Freescale CPUs
#
#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# end of SoC Audio for Freescale CPUs
# CONFIG_SND_I2S_HI6210_I2S is not set
# CONFIG_SND_SOC_IMG is not set CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SST_IPC=mCONFIG_SND_SST_IPC_ACPI=m CONFIG_SND_SOC_INTEL_SST_ACPI=m CONFIG_SND_SOC_INTEL_SST=m CONFIG_SND_SOC_INTEL_SST_FIRMWARE=m CONFIG_SND_SOC_INTEL_HASWELL=m CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m
# CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m CONFIG_SND_SOC_INTEL_SKYLAKE=m CONFIG_SND_SOC_INTEL_SKL=m CONFIG_SND_SOC_INTEL_APL=m CONFIG_SND_SOC_INTEL_KBL=m CONFIG_SND_SOC_INTEL_GLK=m CONFIG_SND_SOC_INTEL_CNL=m CONFIG_SND_SOC_INTEL_CFL=m CONFIG_SND_SOC_INTEL_SKYLAKE_FAMILY=m CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m
# CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC is not set CONFIG_SND_SOC_INTEL_SKYLAKE_COMMON=m CONFIG_SND_SOC_ACPI_INTEL_MATCH=m CONFIG_SND_SOC_INTEL_MACH=y CONFIG_SND_SOC_INTEL_HASWELL_MACH=m CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m
# CONFIG_SND_SOC_INTEL_CHT_BSW_NAU8824_MACH is not set CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=m CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set # CONFIG_SND_SOC_INTEL_GLK_RT5682_MAX98357A_MACH is not set # CONFIG_SND_SOC_MTK_BTCVSD is not set
# CONFIG_SND_SOC_SOF_TOPLEVEL is not set
#
# STMicroelectronics STM32 SOC audio support
#
# end of STMicroelectronics STM32 SOC audio support
# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set # CONFIG_SND_SOC_XILINX_SPDIF is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# CONFIG_ZX_TDM is not set CONFIG_SND_SOC_I2C_AND_SPI=m
#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS42L42 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS53L30 is not setCONFIG_SND_SOC_DA7213=mCONFIG_SND_SOC_DA7219=mCONFIG_SND_SOC_DMIC=m
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not setCONFIG_SND_SOC_ES8316=m
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_GTM601 is not setCONFIG_SND_SOC_HDAC_HDMI=m
# CONFIG_SND_SOC_INNO_RK3036 is not set
# CONFIG_SND_SOC_MAX98088 is not setCONFIG_SND_SOC_MAX98090=mCONFIG_SND_SOC_MAX98357A=m
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not setCONFIG_SND_SOC_MAX98927=m
# CONFIG_SND_SOC_MAX98373 is not set
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RK3328 is not setCONFIG_SND_SOC_RL6231=mCONFIG_SND_SOC_RL6347A=mCONFIG_SND_SOC_RT286=mCONFIG_SND_SOC_RT298=mCONFIG_SND_SOC_RT5514=mCONFIG_SND_SOC_RT5514_SPI=m
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not setCONFIG_SND_SOC_RT5640=mCONFIG_SND_SOC_RT5645=mCONFIG_SND_SOC_RT5651=mCONFIG_SND_SOC_RT5663=mCONFIG_SND_SOC_RT5670=mCONFIG_SND_SOC_RT5677=mCONFIG_SND_SOC_RT5677_SPI=m
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not setCONFIG_SND_SOC_SSM4567=m
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X is not setCONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8904 is not set
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_WM8985 is not set
# CONFIG_SND_SOC_ZX_AUD96P22 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6358 is not set
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8822 is not setCONFIG_SND_SOC_NAU8824=mCONFIG_SND_SOC_NAU8825=m
# CONFIG_SND_SOC_TPA6130A2 is not set
# end of CODEC drivers
# CONFIG_SND_SIMPLE_CARD is not setCONFIG_SND_X86=yCONFIG_HDMI_LPE_AUDIO=mCONFIG_SND_SYNTH_EMUX=m
# CONFIG_SND_XEN_FRONTEND is not setCONFIG_AC97_BUS=m
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=yCONFIG_HIDRAW=yCONFIG_UHID=mCONFIG_HID_GENERIC=y
#
# Special HID drivers
#CONFIG_HID_A4TECH=y
# CONFIG_HID_ACCUTOUCH is not setCONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=yCONFIG_HID_APPLEIR=m
# CONFIG_HID_ASUS is not setCONFIG_HID_AUREAL=mCONFIG_HID_BELKIN=y
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not setCONFIG_HID_CHERRY=yCONFIG_HID_CHICONY=y
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not setCONFIG_HID_PRODIKEYS=m
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not setCONFIG_HID_CYPRESS=yCONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not setCONFIG_HID_ELECOM=m
# CONFIG_HID_ELO is not setCONFIG_HID_EZKEY=y
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not setCONFIG_HID_HOLTEK=m
# CONFIG_HOLTEK_FF is not set
# CONFIG_HID_GT683R is not setCONFIG_HID_KEYTOUCH=mCONFIG_HID_KYE=mCONFIG_HID_UCLOGIC=mCONFIG_HID_WALTOP=m
# CONFIG_HID_VIEWSONIC is not setCONFIG_HID_GYRATION=mCONFIG_HID_ICADE=mCONFIG_HID_ITE=y
# CONFIG_HID_JABRA is not setCONFIG_HID_TWINHAN=mCONFIG_HID_KENSINGTON=yCONFIG_HID_LCPOWER=mCONFIG_HID_LED=m
# CONFIG_HID_LENOVO is not setCONFIG_HID_LOGITECH=yCONFIG_HID_LOGITECH_DJ=mCONFIG_HID_LOGITECH_HIDPP=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not setCONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not setCONFIG_HID_REDRAGON=yCONFIG_HID_MICROSOFT=yCONFIG_HID_MONTEREY=yCONFIG_HID_MULTITOUCH=m
# CONFIG_HID_NTI is not setCONFIG_HID_NTRIG=yCONFIG_HID_ORTEK=mCONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PENMOUNT is not setCONFIG_HID_PETALYNX=mCONFIG_HID_PICOLCD=mCONFIG_HID_PICOLCD_FB=yCONFIG_HID_PICOLCD_BACKLIGHT=yCONFIG_HID_PICOLCD_LCD=yCONFIG_HID_PICOLCD_LEDS=yCONFIG_HID_PICOLCD_CIR=yCONFIG_HID_PLANTRONICS=yCONFIG_HID_PRIMAX=m
# CONFIG_HID_RETRODE is not setCONFIG_HID_ROCCAT=mCONFIG_HID_SAITEK=mCONFIG_HID_SAMSUNG=mCONFIG_HID_SONY=m
# CONFIG_SONY_FF is not setCONFIG_HID_SPEEDLINK=m
# CONFIG_HID_STEAM is not setCONFIG_HID_STEELSERIES=mCONFIG_HID_SUNPLUS=mCONFIG_HID_RMI=mCONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not setCONFIG_HID_HYPERV_MOUSE=mCONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not setCONFIG_HID_TIVO=mCONFIG_HID_TOPSEED=mCONFIG_HID_THINGM=mCONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not setCONFIG_HID_WACOM=mCONFIG_HID_WIIMOTE=m
# CONFIG_HID_XINMO is not setCONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not setCONFIG_HID_ZYDACRON=mCONFIG_HID_SENSOR_HUB=mCONFIG_HID_SENSOR_CUSTOM_SENSOR=mCONFIG_HID_ALPS=m
# end of Special HID drivers
#
# USB HID support
#CONFIG_USB_HID=yCONFIG_HID_PID=yCONFIG_USB_HIDDEV=y
# end of USB HID support
#
# I2C HID support
#CONFIG_I2C_HID=m
# end of I2C HID support
#
# Intel ISH HID support
#CONFIG_INTEL_ISH_HID=y
# CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER is not set
# end of Intel ISH HID support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_PCI=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not setCONFIG_USB_LEDS_TRIGGER_USBPORT=mCONFIG_USB_AUTOSUSPEND_DELAY=2CONFIG_USB_MON=yCONFIG_USB_WUSB=mCONFIG_USB_WUSB_CBAF=m
# CONFIG_USB_WUSB_CBAF_DEBUG is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not setCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PLATFORM is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not setCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_U132_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not setCONFIG_USB_HWA_HCD=m
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_SSB is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#CONFIG_USB_ACM=mCONFIG_USB_PRINTER=mCONFIG_USB_WDM=mCONFIG_USB_TMC=m
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_REALTEK=m CONFIG_REALTEK_AUTOPM=y CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m CONFIG_USB_STORAGE_ENE_UB6250=m CONFIG_USB_UAS=m
#
# USB Imaging devices
#CONFIG_USB_MDC800=mCONFIG_USB_MICROTEK=mCONFIG_USBIP_CORE=m
# CONFIG_USBIP_VHCI_HCD is not set
# CONFIG_USBIP_HOST is not set
# CONFIG_USBIP_DEBUG is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#CONFIG_USB_USS720=mCONFIG_USB_SERIAL=yCONFIG_USB_SERIAL_CONSOLE=yCONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not setCONFIG_USB_SERIAL_AIRCABLE=mCONFIG_USB_SERIAL_ARK3116=mCONFIG_USB_SERIAL_BELKIN=mCONFIG_USB_SERIAL_CH341=mCONFIG_USB_SERIAL_WHITEHEAT=mCONFIG_USB_SERIAL_DIGI_ACCELEPORT=mCONFIG_USB_SERIAL_CP210X=mCONFIG_USB_SERIAL_CYPRESS_M8=mCONFIG_USB_SERIAL_EMPEG=mCONFIG_USB_SERIAL_FTDI_SIO=mCONFIG_USB_SERIAL_VISOR=mCONFIG_USB_SERIAL_IPAQ=mCONFIG_USB_SERIAL_IR=mCONFIG_USB_SERIAL_EDGEPORT=mCONFIG_USB_SERIAL_EDGEPORT_TI=m
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not setCONFIG_USB_SERIAL_GARMIN=mCONFIG_USB_SERIAL_IPW=mCONFIG_USB_SERIAL_IUU=mCONFIG_USB_SERIAL_KEYSPAN_PDA=mCONFIG_USB_SERIAL_KEYSPAN=mCONFIG_USB_SERIAL_KLSI=mCONFIG_USB_SERIAL_KOBIL_SCT=mCONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_METRO is not setCONFIG_USB_SERIAL_MOS7720=mCONFIG_USB_SERIAL_MOS7715_PARPORT=yCONFIG_USB_SERIAL_MOS7840=m
# CONFIG_USB_SERIAL_MXUPORT is not setCONFIG_USB_SERIAL_NAVMAN=mCONFIG_USB_SERIAL_PL2303=mCONFIG_USB_SERIAL_OTI6858=mCONFIG_USB_SERIAL_QCAUX=mCONFIG_USB_SERIAL_QUALCOMM=mCONFIG_USB_SERIAL_SPCP8X5=mCONFIG_USB_SERIAL_SAFE=mCONFIG_USB_SERIAL_SAFE_PADDED=yCONFIG_USB_SERIAL_SIERRAWIRELESS=mCONFIG_USB_SERIAL_SYMBOL=mCONFIG_USB_SERIAL_TI=mCONFIG_USB_SERIAL_CYBERJACK=mCONFIG_USB_SERIAL_XIRCOM=mCONFIG_USB_SERIAL_WWAN=mCONFIG_USB_SERIAL_OPTION=mCONFIG_USB_SERIAL_OMNINET=mCONFIG_USB_SERIAL_OPTICON=mCONFIG_USB_SERIAL_XSENS_MT=m
# CONFIG_USB_SERIAL_WISHBONE is not setCONFIG_USB_SERIAL_SSU100=mCONFIG_USB_SERIAL_QT2=m
# CONFIG_USB_SERIAL_UPD78F0730 is not setCONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#CONFIG_USB_EMI62=mCONFIG_USB_EMI26=mCONFIG_USB_ADUTUX=mCONFIG_USB_SEVSEG=m
# CONFIG_USB_RIO500 is not setCONFIG_USB_LEGOTOWER=mCONFIG_USB_LCD=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not setCONFIG_USB_IDMOUSE=mCONFIG_USB_FTDI_ELAN=mCONFIG_USB_APPLEDISPLAY=mCONFIG_USB_SISUSBVGA=mCONFIG_USB_SISUSBVGA_CON=yCONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not setCONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not setCONFIG_USB_ISIGHTFW=m
# CONFIG_USB_YUREX is not setCONFIG_USB_EZUSB_FX2=m
# CONFIG_USB_HUB_USB251XB is not setCONFIG_USB_HSIC_USB3503=m
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not setCONFIG_USB_ATM=mCONFIG_USB_SPEEDTOUCH=mCONFIG_USB_CXACRU=mCONFIG_USB_UEAGLEATM=mCONFIG_USB_XUSBATM=m
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not setCONFIG_TYPEC=y
# CONFIG_TYPEC_TCPM is not setCONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not setCONFIG_UCSI_ACPI=y
# CONFIG_TYPEC_TPS6598X is not set
#
# USB Type-C Multiplexer/DeMultiplexer Switch support #
# CONFIG_TYPEC_MUX_PI3USB30532 is not set
# end of USB Type-C Multiplexer/DeMultiplexer Switch support
#
# USB Type-C Alternate Mode drivers
#
# CONFIG_TYPEC_DP_ALTMODE is not set
# end of USB Type-C Alternate Mode drivers
# CONFIG_USB_ROLE_SWITCH is not set
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not setCONFIG_UWB=mCONFIG_UWB_HWA=mCONFIG_UWB_WHCI=mCONFIG_UWB_I1480U=mCONFIG_MMC=mCONFIG_MMC_BLOCK=mCONFIG_MMC_BLOCK_MINORS=8CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not setCONFIG_MMC_SDHCI=mCONFIG_MMC_SDHCI_PCI=mCONFIG_MMC_RICOH_MMC=yCONFIG_MMC_SDHCI_ACPI=mCONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_WBSD is not setCONFIG_MMC_TIFM_SD=m
# CONFIG_MMC_SPI is not setCONFIG_MMC_CB710=mCONFIG_MMC_VIA_SDMMC=mCONFIG_MMC_VUB300=mCONFIG_MMC_USHC=m
# CONFIG_MMC_USDHI6ROL0 is not setCONFIG_MMC_CQHCI=m
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not setCONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set
#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not setCONFIG_MSPRO_BLOCK=m
# CONFIG_MS_BLOCK is not set
#
# MemoryStick Host Controller Drivers
#CONFIG_MEMSTICK_TIFM_MS=mCONFIG_MEMSTICK_JMICRON_38X=mCONFIG_MEMSTICK_R592=mCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#
# CONFIG_LEDS_APU is not setCONFIG_LEDS_LM3530=m
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not setCONFIG_LEDS_LP55XX_COMMON=mCONFIG_LEDS_LP5521=mCONFIG_LEDS_LP5523=mCONFIG_LEDS_LP5562=m
# CONFIG_LEDS_LP8501 is not setCONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not setCONFIG_LEDS_INTEL_SS4200=m
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=m
# CONFIG_LEDS_MLXCPLD is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=yCONFIG_LEDS_TRIGGER_TIMER=mCONFIG_LEDS_TRIGGER_ONESHOT=m
# CONFIG_LEDS_TRIGGER_DISK is not set
# CONFIG_LEDS_TRIGGER_MTD is not setCONFIG_LEDS_TRIGGER_HEARTBEAT=mCONFIG_LEDS_TRIGGER_BACKLIGHT=m
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not setCONFIG_LEDS_TRIGGER_GPIO=mCONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_NETDEV is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_GHES=y CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_IE31200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I7CORE=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_EDAC_I7300=m CONFIG_EDAC_SBRIDGE=m CONFIG_EDAC_SKX=m # CONFIG_EDAC_I10NM is not set CONFIG_EDAC_PND2=m CONFIG_RTC_LIB=y CONFIG_RTC_MC146818_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_SYSTOHC is not set # CONFIG_RTC_DEBUG is not set CONFIG_RTC_NVMEM=y
#
# RTC interfaces
#CONFIG_RTC_INTF_SYSFS=yCONFIG_RTC_INTF_PROC=yCONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not setCONFIG_RTC_DRV_DS1307=m
# CONFIG_RTC_DRV_DS1307_CENTURY is not setCONFIG_RTC_DRV_DS1374=m
# CONFIG_RTC_DRV_DS1374_WDT is not setCONFIG_RTC_DRV_DS1672=mCONFIG_RTC_DRV_MAX6900=mCONFIG_RTC_DRV_RS5C372=mCONFIG_RTC_DRV_ISL1208=mCONFIG_RTC_DRV_ISL12022=mCONFIG_RTC_DRV_X1205=mCONFIG_RTC_DRV_PCF8523=m
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF85363 is not setCONFIG_RTC_DRV_PCF8563=mCONFIG_RTC_DRV_PCF8583=mCONFIG_RTC_DRV_M41T80=mCONFIG_RTC_DRV_M41T80_WDT=yCONFIG_RTC_DRV_BQ32K=m
# CONFIG_RTC_DRV_S35390A is not setCONFIG_RTC_DRV_FM3130=m
# CONFIG_RTC_DRV_RX8010 is not setCONFIG_RTC_DRV_RX8581=mCONFIG_RTC_DRV_RX8025=mCONFIG_RTC_DRV_EM3027=m
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not setCONFIG_RTC_DRV_RX4581=m
# CONFIG_RTC_DRV_RX6110 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not setCONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#CONFIG_RTC_DRV_DS3232=mCONFIG_RTC_DRV_DS3232_HWMON=y
# CONFIG_RTC_DRV_PCF2127 is not setCONFIG_RTC_DRV_RV3029C2=mCONFIG_RTC_DRV_RV3029_HWMON=y
#
# Platform RTC drivers
#CONFIG_RTC_DRV_CMOS=yCONFIG_RTC_DRV_DS1286=mCONFIG_RTC_DRV_DS1511=mCONFIG_RTC_DRV_DS1553=m
# CONFIG_RTC_DRV_DS1685_FAMILY is not setCONFIG_RTC_DRV_DS1742=mCONFIG_RTC_DRV_DS2404=mCONFIG_RTC_DRV_STK17TA8=m
# CONFIG_RTC_DRV_M48T86 is not setCONFIG_RTC_DRV_M48T35=mCONFIG_RTC_DRV_M48T59=mCONFIG_RTC_DRV_MSM6242=mCONFIG_RTC_DRV_BQ4802=mCONFIG_RTC_DRV_RP5C01=mCONFIG_RTC_DRV_V3020=m
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_FTRTC010 is not set
#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_HID_SENSOR_TIME is not setCONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#CONFIG_DMA_ENGINE=yCONFIG_DMA_VIRTUAL_CHANNELS=yCONFIG_DMA_ACPI=y
# CONFIG_ALTERA_MSGDMA is not set
# CONFIG_INTEL_IDMA64 is not setCONFIG_INTEL_IOATDMA=m
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not setCONFIG_DW_DMAC_CORE=yCONFIG_DW_DMAC=mCONFIG_DW_DMAC_PCI=yCONFIG_HSU_DMA=y
#
# DMA Clients
#CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not setCONFIG_DMA_ENGINE_RAID=y
#
# DMABUF options
#CONFIG_SYNC_FILE=yCONFIG_SW_SYNC=y
# CONFIG_UDMABUF is not set
# end of DMABUF options
CONFIG_DCA=mCONFIG_AUXDISPLAY=y
# CONFIG_HD44780 is not setCONFIG_KS0108=mCONFIG_KS0108_PORT=0x378CONFIG_KS0108_DELAY=2CONFIG_CFAG12864B=mCONFIG_CFAG12864B_RATE=20
# CONFIG_IMG_ASCII_LCD is not set
# CONFIG_PARPORT_PANEL is not set
# CONFIG_CHARLCD_BL_OFF is not set
# CONFIG_CHARLCD_BL_ON is not setCONFIG_CHARLCD_BL_FLASH=y
# CONFIG_PANEL is not setCONFIG_UIO=mCONFIG_UIO_CIF=mCONFIG_UIO_PDRV_GENIRQ=m
# CONFIG_UIO_DMEM_GENIRQ is not setCONFIG_UIO_AEC=mCONFIG_UIO_SERCOS3=mCONFIG_UIO_PCI_GENERIC=m
# CONFIG_UIO_NETX is not set
# CONFIG_UIO_PRUSS is not set
# CONFIG_UIO_MF624 is not setCONFIG_UIO_HV_GENERIC=mCONFIG_VFIO_IOMMU_TYPE1=mCONFIG_VFIO_VIRQFD=mCONFIG_VFIO=mCONFIG_VFIO_NOIOMMU=yCONFIG_VFIO_PCI=m
# CONFIG_VFIO_PCI_VGA is not setCONFIG_VFIO_PCI_MMAP=yCONFIG_VFIO_PCI_INTX=y
# CONFIG_VFIO_PCI_IGD is not setCONFIG_VFIO_MDEV=mCONFIG_VFIO_MDEV_DEVICE=mCONFIG_IRQ_BYPASS_MANAGER=m
# CONFIG_VIRT_DRIVERS is not setCONFIG_VIRTIO=yCONFIG_VIRTIO_MENU=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_PCI_LEGACY=yCONFIG_VIRTIO_BALLOON=yCONFIG_VIRTIO_INPUT=m
# CONFIG_VIRTIO_MMIO is not set
#
# Microsoft Hyper-V guest support
#CONFIG_HYPERV=mCONFIG_HYPERV_TSCPAGE=yCONFIG_HYPERV_UTILS=mCONFIG_HYPERV_BALLOON=m
# end of Microsoft Hyper-V guest support
#
# Xen driver support
#CONFIG_XEN_BALLOON=y
# CONFIG_XEN_SELFBALLOONING is not set
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not setCONFIG_XEN_SCRUB_PAGES_DEFAULT=yCONFIG_XEN_DEV_EVTCHN=m
# CONFIG_XEN_BACKEND is not setCONFIG_XENFS=mCONFIG_XEN_COMPAT_XENFS=yCONFIG_XEN_SYS_HYPERVISOR=yCONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_XEN_GRANT_DEV_ALLOC is not set
# CONFIG_XEN_GRANT_DMA_ALLOC is not setCONFIG_SWIOTLB_XEN=yCONFIG_XEN_TMEM=m
# CONFIG_XEN_PVCALLS_FRONTEND is not setCONFIG_XEN_PRIVCMD=mCONFIG_XEN_HAVE_PVMMU=yCONFIG_XEN_EFI=yCONFIG_XEN_AUTO_XLATE=yCONFIG_XEN_ACPI=yCONFIG_XEN_HAVE_VPMU=y
# end of Xen driver support
5,188 lines not shown · raw message
Part of this message is not shown here. View the raw message.