xdp: hints via kfuncs
Subsystems (12)
Martin KaFai Lau
reviewerRe: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Stanislav FomichevQuoted 152 lines · Stanislav Fomichev
Quoted 48 lines · Martin KaFai Lau
Quoted 17 lines · Stanislav Fomichev
include/linux/skbuff.h
Quoted 1 line
include/linux/skbuff.h +0
-0index
59c9fd55699d..dba857f212d7100644include/linux/skbuff.h +4
-0@@ -4217,9 +4217,13 @@ static inline bool skb_metadata_differs(const struct sk_buff *skb_a, true : __skb_metadata_differs(skb_a, skb_b, len_a); } +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len); +static inline void skb_metadata_set (struct sk_buff *skb,u8 meta_len) {skb_shinfo (skb)->meta_len = meta_len; +if (meta_len) +skb_metadata_import_from_xdp (skb, meta_len); }[ ... ]
Quoted 7 lines
include/linux/skbuff.h +7
-0+struct xdp_to_skb_metadata { +u32 magic;/* xdp_metadata_magic */ +u64 rx_timestamp; +} __randomize_layout; + +struct bpf_patch ; +[ ... ]
Quoted 17 lines
include/linux/skbuff.h +17
-0+void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len) +{ +struct xdp_to_skb_metadata *meta = (void *)(skb_mac_header (skb) - len); + +/* Optional SKB info, currently missing: +* - HW checksum info (skb->ip_summed) +* - HW RX hash (skb_set_hash) +* - RX ring dev queue index (skb_record_rx_queue) +*/ + +if (len !=sizeof (struct xdp_to_skb_metadata )) +return ; + +if (meta->magic != xdp_metadata_magic) +return ; + +if (meta->rx_timestamp) {Quoted 8 lines
include/linux/skbuff.h
Quoted 5 lines
include/linux/skbuff.h +5
-0+ *skb_hwtstamps (skb) = (struct skb_shared_hwtstamps ){ + .hwtstamp =ns_to_ktime (meta->rx_timestamp), + }; + } +}Considering the metadata will affect the gro, should the meta be cleared after importing to the skb?
Yeah, good suggestion, will clear it here.
Quoted 79 lines
[ ... ]
Quoted 77 lines
include/linux/skbuff.h +77
-0+/* Since we're not actually doing a call but instead rewriting +* in place, we can only afford to use R0-R5 scratch registers. +* +* We reserve R1 for bpf_xdp_metadata_export_to_skb and let individual +* metadata kfuncs use only R0,R4-R5. +* +* The above also means we _cannot_ easily call any other helper/kfunc +* because there is no place for us to preserve our R1 argument; +* existing R6-R9 belong to the callee. +*/ +void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) +{ +u32 func_id; + +/* +* The code below generates the following: +* +* void bpf_xdp_metadata_export_to_skb(struct xdp_md *ctx) +* { +* struct xdp_to_skb_metadata *meta; +* int ret; +* +* ret = bpf_xdp_adjust_meta(ctx, -sizeof(*meta)); +* if (!ret) +* return; +* +* meta = ctx->data_meta; +* meta->magic = xdp_metadata_magic; +* meta->rx_timestamp = bpf_xdp_metadata_rx_timestamp(ctx); +* } +* +*/ + +bpf_patch_append (patch, +/* r2 = ((struct xdp_buff *)r1)->data_meta; */ +BPF_LDX_MEM (BPF_DW ,BPF_REG_2 ,BPF_REG_1 , + offsetof(struct xdp_buff , data_meta)), +/* r3 = ((struct xdp_buff *)r1)->data; */ +BPF_LDX_MEM (BPF_DW ,BPF_REG_3 ,BPF_REG_1 , + offsetof(struct xdp_buff , data)), +/* if (data_meta != data) return; +* +* data_meta > data: xdp_data_meta_unsupported() +* data_meta < data: already used, no need to touch +*/ +BPF_JMP_REG (BPF_JNE ,BPF_REG_2 ,BPF_REG_3 ,S16_MAX ), + +/* r2 -= sizeof(struct xdp_to_skb_metadata); */ +BPF_ALU64_IMM (BPF_SUB ,BPF_REG_2 , +sizeof (struct xdp_to_skb_metadata )), +/* r3 = ((struct xdp_buff *)r1)->data_hard_start; */ +BPF_LDX_MEM (BPF_DW ,BPF_REG_3 ,BPF_REG_1 , + offsetof(struct xdp_buff , data_hard_start)), +/* r3 += sizeof(struct xdp_frame) */ +BPF_ALU64_IMM (BPF_ADD ,BPF_REG_3 , +sizeof (struct xdp_frame )), +/* if (data-sizeof(struct xdp_to_skb_metadata) < data_hard_start+sizeof(struct xdp_frame)) return; */ +BPF_JMP_REG (BPF_JLT ,BPF_REG_2 ,BPF_REG_3 ,S16_MAX ), + +/* ((struct xdp_buff *)r1)->data_meta = r2; */ +BPF_STX_MEM (BPF_DW ,BPF_REG_1 ,BPF_REG_2 , + offsetof(struct xdp_buff , data_meta)), + +/* *((struct xdp_to_skb_metadata *)r2)->magic = xdp_metadata_magic; */ +BPF_ST_MEM (BPF_W ,BPF_REG_2 , + offsetof(struct xdp_to_skb_metadata , magic), + xdp_metadata_magic), + ); + +/* r0 = bpf_xdp_metadata_rx_timestamp(ctx); */ + func_id =xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP ); + prog->aux->xdp_kfunc_ndo->ndo_unroll_kfunc (prog, func_id, patch); + + bpf_patch_append(patch, + /* r2 = ((struct xdp_buff *)r1)->data_meta; */ + BPF_LDX_MEM(BPF_DW, BPF_REG_2, BPF_REG_1, + offsetof(struct xdp_buff, data_meta)),Quoted 8 lines
include/linux/skbuff.h
Quoted 3 lines
include/linux/skbuff.h +3
-0+/* *((struct xdp_to_skb_metadata *)r2)->rx_timestamp = r0; */ +BPF_STX_MEM (BPF_DW ,BPF_REG_2 ,BPF_REG_0 , + offsetof(struct xdp_to_skb_metadata, rx_timestamp)),Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
I can't think of a use case now for the xdp prog to use the xdp_to_skb_metadata while the xdp prog can directly call the kfunc (eg bpf_xdp_metadata_rx_timestamp) to get individual hint. I was asking if patch 7 is an actual use case because it does test the tstamp in XDP_PASS or it is mostly for selftest purpose? Yeah, may be the xdp prog will be able to change the xdp_to_skb_metadata eventually but that is for later.
My concern is the xdp prog is allowed to change xdp_to_skb_metadata or by-coincident writing metadata that matches the random and the sizeof(struct xdp_to_skb_metadata).
Also, the added opacity of xdp_to_skb_metadata (__randomize_layout + random int) is trying very hard to hide it from xdp prog. Instead, would it be cleaner to have a flag in xdp->flags (to be set by bpf_xdp_metadata_export_to_skb?) to guard this, like one of Jesper's patch. The xdp_convert_ctx_access() and bpf_xdp_adjust_meta() can check this bit to ensure the xdp_to_skb_metadata cannot be read and no metadata can be added/deleted after that. btw, is it possible to keep both xdp_to_skb_metadata and the xdp_prog's metadata? After skb_metadata_import_from_xdp popping the xdp_to_skb_metadata, the remaining xdp_prog's metatdata can still be used by the bpf-tc.
Quoted 13 lines
...
Quoted 2 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.
Quoted 6 lines
In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Yeah, not sure if it can solely depend on BPF_F_XDP_HAS_METADATA but it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by calling bpf_xdp_metadata_export_to_skb() with XDP_PASS and knowing nothing can be changed now.
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
include/linux/skbuff.h +6
-0+ ); + +bpf_patch_resolve_jmp (patch); +} +static int __init xdp_metadata_init (void ) { + xdp_metadata_magic =get_random_u32 () |1 ;return register_btf_kfunc_id_set (BPF_PROG_TYPE_XDP , &xdp_metadata_kfunc_set); }late_initcall (xdp_metadata_init);
Martin KaFai Lau
reviewerRe: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 157 lines · Martin KaFai Lau
Quoted 156 lines · Stanislav Fomichev
Quoted 49 lines · Martin KaFai Lau
Quoted 18 lines · Stanislav Fomichev
include/linux/skbuff.h
Quoted 1 line
include/linux/skbuff.h +0
-0index
59c9fd55699d..dba857f212d7100644include/linux/skbuff.h +4
-0@@ -4217,9 +4217,13 @@ static inline bool skb_metadata_differs(const structsk_buff *skb_a, true : __skb_metadata_differs(skb_a, skb_b, len_a); } +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len); + static inline void skb_metadata_set(struct sk_buff *skb, u8 meta_len) { skb_shinfo(skb)->meta_len = meta_len; + if (meta_len) + skb_metadata_import_from_xdp(skb, meta_len); }[ ... ]
Quoted 7 lines
include/linux/skbuff.h +7
-0+struct xdp_to_skb_metadata { + u32 magic; /* xdp_metadata_magic */ + u64 rx_timestamp; +} __randomize_layout; + +struct bpf_patch ; +[ ... ]
Quoted 17 lines
include/linux/skbuff.h +17
-0+void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len) +{ + struct xdp_to_skb_metadata *meta = (void *)(skb_mac_header(skb) - len); + + /* Optional SKB info, currently missing: + * - HW checksum info (skb->ip_summed) + * - HW RX hash (skb_set_hash) + * - RX ring dev queue index (skb_record_rx_queue) + */ + + if (len != sizeof(struct xdp_to_skb_metadata)) + return; + + if (meta->magic != xdp_metadata_magic) + return; + + if (meta->rx_timestamp) {Quoted 8 lines
Quoted 5 lines
+
*skb_hwtstamps(skb)= (struct skb_shared_hwtstamps){ + .hwtstamp =ns_to_ktime(meta->rx_timestamp), + };
+ }
+}Considering the metadata will affect the gro, should the meta be cleared after importing to the skb?
Yeah, good suggestion, will clear it here.
Quoted 82 lines
[ ... ]
Quoted 80 lines
include/linux/skbuff.h +11
-0+/* Since we're not actually doing a call but instead rewriting +* in place, we can only afford to use R0-R5 scratch registers. +* +* We reserve R1 for bpf_xdp_metadata_export_to_skb and let individual +* metadata kfuncs use only R0,R4-R5. +* +* The above also means we _cannot_ easily call any other helper/kfunc +* because there is no place for us to preserve our R1 argument; +* existing R6-R9 belong to the callee. +*/ +void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct
bpf_patch*patch)include/linux/skbuff.h +46
-0+{ + u32 func_id; + + /* + * The code below generates the following: + * + * void bpf_xdp_metadata_export_to_skb(struct xdp_md *ctx) + * { + * struct xdp_to_skb_metadata *meta; + * int ret; + * + * ret = bpf_xdp_adjust_meta(ctx, -sizeof(*meta)); + * if (!ret) + * return; + * + * meta = ctx->data_meta; + * meta->magic = xdp_metadata_magic; + * meta->rx_timestamp = bpf_xdp_metadata_rx_timestamp(ctx); + * } + * + */ + + bpf_patch_append(patch, + /* r2 = ((struct xdp_buff *)r1)->data_meta; */ + BPF_LDX_MEM(BPF_DW, BPF_REG_2, BPF_REG_1, + offsetof(struct xdp_buff, data_meta)), + /* r3 = ((struct xdp_buff *)r1)->data; */ + BPF_LDX_MEM(BPF_DW, BPF_REG_3, BPF_REG_1, + offsetof(struct xdp_buff, data)), + /* if (data_meta != data) return; + * + * data_meta > data: xdp_data_meta_unsupported() + * data_meta < data: already used, no need to touch + */ + BPF_JMP_REG(BPF_JNE, BPF_REG_2, BPF_REG_3, S16_MAX), + + /* r2 -= sizeof(struct xdp_to_skb_metadata); */ + BPF_ALU64_IMM(BPF_SUB, BPF_REG_2, + sizeof(struct xdp_to_skb_metadata)), + /* r3 = ((struct xdp_buff *)r1)->data_hard_start; */ + BPF_LDX_MEM(BPF_DW, BPF_REG_3, BPF_REG_1, + offsetof(struct xdp_buff, data_hard_start)), + /* r3 += sizeof(struct xdp_frame) */ + BPF_ALU64_IMM(BPF_ADD, BPF_REG_3, + sizeof(struct xdp_frame)), + /* if (data-sizeof(struct xdp_to_skb_metadata) <data_hard_start+sizeof(struct
xdp_frame)) return; */
+BPF_JMP_REG(BPF_JLT, BPF_REG_2, BPF_REG_3, S16_MAX),include/linux/skbuff.h +6
-0+ + /* ((struct xdp_buff *)r1)->data_meta = r2; */ + BPF_STX_MEM(BPF_DW, BPF_REG_1, BPF_REG_2, + offsetof(struct xdp_buff, data_meta)), + + /* *((struct xdp_to_skb_metadata *)r2)->magic =
xdp_metadata_magic; */
+ BPF_ST_MEM(BPF_W,BPF_REG_2,
+offsetof(struct xdp_to_skb_metadata, magic), +xdp_metadata_magic),
+ );include/linux/skbuff.h +9
-0+ + /* r0 = bpf_xdp_metadata_rx_timestamp(ctx); */ + func_id = xdp_metadata_kfunc_id(XDP_METADATA_KFUNC_RX_TIMESTAMP); + prog->aux->xdp_kfunc_ndo->ndo_unroll_kfunc(prog, func_id, patch); + + bpf_patch_append(patch, + /* r2 = ((struct xdp_buff *)r1)->data_meta; */ + BPF_LDX_MEM(BPF_DW, BPF_REG_2, BPF_REG_1, + offsetof(struct xdp_buff, data_meta)),Quoted 8 lines
Quoted 3 lines
+ /* *((struct
xdp_to_skb_metadata*)r2)->rx_timestamp = r0; */ + BPF_STX_MEM(BPF_DW,BPF_REG_2,BPF_REG_0,
+offsetof(struct xdp_to_skb_metadata, rx_timestamp)),Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
After re-reading patch 6, have another question. The 'void bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'struct xdp_to_skb_metadata *' pointer and the xdp prog can directly read (or even write) it? A related question, why 'struct xdp_to_skb_metadata' needs __randomize_layout?
Quoted 45 lines
I can't think of a use case now for the xdp prog to use the
xdp_to_skb_metadatawhile the xdp prog can directly call the kfunc (egbpf_xdp_metadata_rx_timestamp) to get individual hint. I was asking if patch 7 is an actual use case because it does test the tstamp inXDP_PASSor it is mostly for selftest purpose? Yeah, may be the xdp prog will be able to change thexdp_to_skb_metadataeventually but that is for later.My concern is the xdp prog is allowed to change
xdp_to_skb_metadataor by-coincident writing metadata that matches the random and thesizeof(struct xdp_to_skb_metadata).Also, the added opacity of
xdp_to_skb_metadata(__randomize_layout+ random int) is trying very hard to hide it from xdp prog. Instead, would it be cleaner to have a flag inxdp->flags(to be set bybpf_xdp_metadata_export_to_skb?) to guard this, like one of Jesper's patch. Thexdp_convert_ctx_access()andbpf_xdp_adjust_meta()can check this bit to ensure thexdp_to_skb_metadatacannot be read and no metadata can be added/deleted after that. btw, is it possible to keep bothxdp_to_skb_metadataand the xdp_prog's metadata? Afterskb_metadata_import_from_xdppopping thexdp_to_skb_metadata, the remaining xdp_prog's metatdata can still be used by the bpf-tc.Quoted 13 lines
...
Quoted 2 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.Quoted 6 lines
In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).
> WDYT?Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
+ );
include/linux/skbuff.h +4
-0+ + bpf_patch_resolve_jmp(patch); +} +static int
__initxdp_metadata_init(void)
{
+xdp_metadata_magic=get_random_u32()| 1;
returnregister_btf_kfunc_id_set(BPF_PROG_TYPE_XDP, &xdp_metadata_kfunc_set); }
late_initcall(xdp_metadata_init);
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
There are several use cases for needing to access the metadata after calling bpf_xdp_metdata_export_to_skb():
- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata to AF_XDP
- Returning XDP_PASS, but accessing some of the metadata first (whether to read or change it)
The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
We should probably also have a flag set on the xdp_frame so the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.
Quoted 4 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the data_meta pointer, but the verifier could know its size, so the program doesn't have to bounds check it).
Quoted 2 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?
The __randomize_layout thing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and __randomize_layout seemed like a neat trick to enforce CO-RE usage :)
Quoted 19 lines
Quoted 19 lines
Quoted 17 lines
Quoted 2 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).
> WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.
I agree it would be best if the drivers also use the XDP metadata (if present) on XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it on XDP_PASS.
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDP
fwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct xdp_to_skb_metadata'.
Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through data_meta (as a _u8 *).
Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current bpf_xdp_adjust_meta() usage?
Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.
Yeah, I think having a flag is useful. The flag will be set at xdp_buff and then transfer to the xdp_frame?
Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?
Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).
If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing xdp->data_meta with xdp->data as a side effect is not intuitive.
It is more than saving the bound check. With type info of 'struct xdp_to_skb_metadata *', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.
The returning 'struct xdp_to_skb_metadata *' should not be an alias to the xdp->data_meta. They should actually point to different locations in the headroom. bpf_xdp_metadata_export_to_skb() sets a flag in xdp_buff. xdp->data_meta won't be changed and keeps pointing to the last bpf_xdp_adjust_meta() location. The kernel will know if there is xdp_to_skb_metadata before the xdp->data_meta when that bit is set in the xdp_{buff,frame}. Would it work?
Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)
I am not sure if it is necessary or helpful to only enforce __randomize_layout in 'struct xdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.
It is more important for the verifier to see the xdp prog accessing it as a 'struct xdp_to_skb_metadata *' instead of xdp->data_meta which is a __u8 * so that the verifier can enforce the rules of access.
Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).
> WDYT?Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 111 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)
Quoted 46 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Not to derail the discussion (left the last message intact on top, feel free to continue), but to summarize. The proposed changes seem to be:
1. bpf_xdp_metadata_export_to_skb() should return pointer to "struct xdp_to_skb_metadata"
- This should let bpf programs change the metadata passed to the skb
2. "struct xdp_to_skb_metadata" should have its btf_id as the first __u32 member (and remove the magic)
- This is for the redirect case where the end users, includingAF_XDP, can parse this metadata from btf_id
- This, however, is not all the metadata that the device can
support, but a much narrower set that the kernel is expected to use for skb construction
3. __randomize_layout isn't really helping, CO-RE will trigger regardless; maybe only the case where it matters is probably AF_XDP, so still useful?
4. The presence of the metadata generated by bpf_xdp_metadata_export_to_skb should be indicated by a flag in xdp_{buff,frame}->flags
- Assuming exposing it via xdp_md->has_skb_metadata is ok?
- Since the programs probably need to do the following:
if (xdp_md->has_skb_metadata) {
access/change skb metadata by doing struct xdp_to_skb_metadata *p
= data_meta;
} else {
use kfuncs
}
5. Support the case where we keep program's metadata and kernel's xdp_to_skb_metadata
- skb_metadata_import_from_xdp() will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroom
I think the above solves all the cases Toke points to?
a) Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- only a small xdp_to_skb_metadata subset will work out of the box
iff the redirecttor calls bpf_xdp_metadata_export_to_skb; for the rest the progs will have to agree on the layout, right?
b) Transferring the packet+metadata to AF_XDP
- here, again, the AF_XDP consumer will have to either expectxdp_to_skb_metadata with a smaller set of skb-related metadata, or will have to make sure the producer builds a custom layout using kfuncs; there is also no flag to indicate whether xdp_to_skb_metadata is there or not; the consumer will have to test btf_id at the right offset
c) Returning XDP_PASS, but accessing some of the metadata first (whether to read or change it)
- can read via kfuncs, can change viabpf_xdp_metadata_export_to_skb(); m->xyz=abc;
Anything I'm missing?
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 163 lines · Stanislav Fomichev
Quoted 111 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)Quoted 46 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Not to derail the discussion (left the last message intact on top, feel free to continue), but to summarize. The proposed changes seem to be:
Quoted 8 lines
1.
bpf_xdp_metadata_export_to_skb()should return pointer to "structxdp_to_skb_metadata"
- This should let bpf programs change the metadata passed to the skb2. "struct
xdp_to_skb_metadata" should have itsbtf_idas the first__u32member (and remove the magic)
- This is for the redirect case where the end users, includingAF_XDP, can parse this metadata frombtf_id
I think Toke's idea is to put the btf_id at the end of xdp_to_skb_metadata. I can see why the end is needed for the userspace AF_XDP because, afaict, AF_XDP rx_desc currently cannot tell if there is metadata written by the xdp prog or not. However, if the 'has_skb_metadata' bit can also be passed to the AF_XDP rx_desc->options, the btf_id may as well be not needed now. However, the btf_id and other future new members can be added to the xdp_to_skb_metadata later if there is a need.
For the kernel and xdp prog, a bit in the xdp->flags should be enough to get to the xdp_to_skb_metadata. The xdp prog will use CO-RE to access the members in xdp_to_skb_metadata.
Quoted 4 lines
- This, however, is not all the metadata that the device can
support, but a much narrower set that the kernel is expected to use for skb construction
Quoted 8 lines
3.
__randomize_layoutisn't really helping, CO-RE will trigger regardless; maybe only the case where it matters is probablyAF_XDP, so still useful?4. The presence of the metadata generated by
bpf_xdp_metadata_export_to_skbshould be indicated by a flag in xdp_{buff,frame}->flags
- Assuming exposing it viaxdp_md->has_skb_metadatais ok?
probably __bpf_md_ptr(struct xdp_to_skb_metadata *, skb_metadata) and the type will be PTR_TO_BTF_ID_OR_NULL.
Quoted 5 lines
- Since the programs probably need to do the following:
if (
xdp_md->has_skb_metadata) {
access/change skb metadata by doing structxdp_to_skb_metadata*p
=data_meta;
and directly access/change xdp->skb_metadata instead of using xdp->data_meta.
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroom
I was thinking the kernel's xdp_to_skb_metadata is always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, call bpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it is XDP_PASS, the kernel just needs to pop the xdp_to_skb_metadata and pass the remaining program's metadata to the bpf-tc.
For the kernel and xdp prog, I don't think it matters where the xdp_to_skb_metadata is. However, the xdp->data_meta (program's metadata) has to be before xdp->data because of the current data_meta and data comparison usage in the xdp prog.
The order of the kernel's xdp_to_skb_metadata and the program's metadata probably only matters to the userspace AF_XDP. However, I don't see how AF_XDP supports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or the AF_XDP currently does not use the program's metadata. Either way, we can do the mem-moving only for AF_XDP and it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?
Thanks for the summary!
Quoted 24 lines
I think the above solves all the cases Toke points to?
a) Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- only a smallxdp_to_skb_metadatasubset will work out of the box
iff the redirecttor callsbpf_xdp_metadata_export_to_skb; for the rest the progs will have to agree on the layout, right?b) Transferring the packet+metadata to
AF_XDP
- here, again, theAF_XDPconsumer will have to either expectxdp_to_skb_metadatawith a smaller set of skb-related metadata, or will have to make sure the producer builds a custom layout using kfuncs; there is also no flag to indicate whetherxdp_to_skb_metadatais there or not; the consumer will have to testbtf_idat the right offsetc) Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)
- can read via kfuncs, can change viabpf_xdp_metadata_export_to_skb(); m->xyz=abc;Anything I'm missing?
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 182 lines · Martin KaFai Lau
Quoted 163 lines · Stanislav Fomichev
Quoted 111 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)Quoted 46 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Not to derail the discussion (left the last message intact on top, feel free to continue), but to summarize. The proposed changes seem to be:
Quoted 8 lines
1.
bpf_xdp_metadata_export_to_skb()should return pointer to "structxdp_to_skb_metadata"
- This should let bpf programs change the metadata passed to the skb2. "struct
xdp_to_skb_metadata" should have itsbtf_idas the first__u32member (and remove the magic)
- This is for the redirect case where the end users, includingAF_XDP, can parse this metadata frombtf_idI think Toke's idea is to put the
btf_idat the end ofxdp_to_skb_metadata. I can see why the end is needed for the userspaceAF_XDPbecause, afaict,AF_XDPrx_desccurrently cannot tell if there is metadata written by the xdp prog or not. However, if the 'has_skb_metadata' bit can also be passed to theAF_XDPrx_desc->options, thebtf_idmay as well be not needed now. However, thebtf_idand other future new members can be added to thexdp_to_skb_metadatalater if there is a need.
Quoted 3 lines
For the kernel and xdp prog, a bit in the
xdp->flagsshould be enough to get to thexdp_to_skb_metadata. The xdp prog will use CO-RE to access the members inxdp_to_skb_metadata.
Ack, good points on putting it at the end.
Regarding bit in desc->options vs btf_id: since it seems that btf_id is useful anyway, let's start with that? We can add a bit later on if it turns out using metadata is problematic otherwise.
Quoted 8 lines
Quoted 8 lines
- This, however, is not all the metadata that the device can
support, but a much narrower set that the kernel is expected to use for skb construction3.
__randomize_layoutisn't really helping, CO-RE will trigger regardless; maybe only the case where it matters is probablyAF_XDP, so still useful?
Quoted 7 lines
Quoted 4 lines
4. The presence of the metadata generated by
bpf_xdp_metadata_export_to_skbshould be indicated by a flag in xdp_{buff,frame}->flags
- Assuming exposing it viaxdp_md->has_skb_metadatais ok?probably
__bpf_md_ptr(struct xdp_to_skb_metadata *, skb_metadata)and the type will bePTR_TO_BTF_ID_OR_NULL.
Oh, that seems even better than returning it from bpf_xdp_metadata_export_to_skb. bpf_xdp_metadata_export_to_skb can return true/false and the rest goes via default verifier ctx resolution mechanism..
(returning ptr from a kfunc seems to be a bit complicated right now)
Quoted 7 lines
Quoted 5 lines
- Since the programs probably need to do the following:
if (
xdp_md->has_skb_metadata) {
access/change skb metadata by doing structxdp_to_skb_metadata*p
=data_meta;and directly access/change
xdp->skb_metadatainstead of usingxdp->data_meta.
Ack.
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.
Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?
Agreed on all of the above. For now it seems like the safest thing to do is to put xdp_to_skb_metadata last to allow af_xdp to properly locate btf_id.
Let's see if Toke disagrees :-)
Quoted 27 lines
Thanks for the summary!
Quoted 24 lines
I think the above solves all the cases Toke points to?
a) Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- only a smallxdp_to_skb_metadatasubset will work out of the box
iff the redirecttor callsbpf_xdp_metadata_export_to_skb; for the rest the progs will have to agree on the layout, right?b) Transferring the packet+metadata to
AF_XDP
- here, again, theAF_XDPconsumer will have to either expectxdp_to_skb_metadatawith a smaller set of skb-related metadata, or will have to make sure the producer builds a custom layout using kfuncs; there is also no flag to indicate whetherxdp_to_skb_metadatais there or not; the consumer will have to testbtf_idat the right offsetc) Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)
- can read via kfuncs, can change viabpf_xdp_metadata_export_to_skb(); m->xyz=abc;Anything I'm missing?
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 183 lines · Stanislav Fomichev
Quoted 182 lines · Martin KaFai Lau
Quoted 163 lines · Stanislav Fomichev
Quoted 111 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)Quoted 46 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Not to derail the discussion (left the last message intact on top, feel free to continue), but to summarize. The proposed changes seem to be:
Quoted 8 lines
1.
bpf_xdp_metadata_export_to_skb()should return pointer to "structxdp_to_skb_metadata"
- This should let bpf programs change the metadata passed to the skb2. "struct
xdp_to_skb_metadata" should have itsbtf_idas the first__u32member (and remove the magic)
- This is for the redirect case where the end users, includingAF_XDP, can parse this metadata frombtf_idI think Toke's idea is to put the
btf_idat the end ofxdp_to_skb_metadata. I can see why the end is needed for the userspaceAF_XDPbecause, afaict,AF_XDPrx_desccurrently cannot tell if there is metadata written by the xdp prog or not. However, if the 'has_skb_metadata' bit can also be passed to theAF_XDPrx_desc->options, thebtf_idmay as well be not needed now. However, thebtf_idand other future new members can be added to thexdp_to_skb_metadatalater if there is a need.
Quoted 8 lines
Quoted 3 lines
For the kernel and xdp prog, a bit in the
xdp->flagsshould be enough to get to thexdp_to_skb_metadata. The xdp prog will use CO-RE to access the members inxdp_to_skb_metadata.Ack, good points on putting it at the end.
Regarding bit indesc->optionsvsbtf_id: since it seems thatbtf_idis useful anyway, let's start with that? We can add a bit later on if it turns out using metadata is problematic otherwise.
I think the bit is mostly useful so that the stack can know that the metadata has been set before consuming it (to guard against regular xdp_metadata usage accidentally hitting the "right" BTF ID). I don't think it needs to be exposed to the XDP programs themselves.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
- This, however, is not all the metadata that the device can
support, but a much narrower set that the kernel is expected to use for skb construction3.
__randomize_layoutisn't really helping, CO-RE will trigger regardless; maybe only the case where it matters is probablyAF_XDP, so still useful?
Yeah, see my response to Martin, I think the randomisation is useful for AF_XDP transfer.
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
4. The presence of the metadata generated by
bpf_xdp_metadata_export_to_skbshould be indicated by a flag in xdp_{buff,frame}->flags
- Assuming exposing it viaxdp_md->has_skb_metadatais ok?
Quoted 8 lines
Quoted 2 lines
probably
__bpf_md_ptr(struct xdp_to_skb_metadata *, skb_metadata)and the type will bePTR_TO_BTF_ID_OR_NULL.Oh, that seems even better than returning it from
bpf_xdp_metadata_export_to_skb.bpf_xdp_metadata_export_to_skbcan return true/false and the rest goes via default verifier ctx resolution mechanism..
(returning ptr from a kfunc seems to be a bit complicated right now)
See my response to John in the other thread about mixing stable UAPI (in xdp_md) and unstable BTF structures in the xdp_md struct: I think this is confusing and would prefer a kfunc.
Quoted 38 lines
Quoted 7 lines
Quoted 5 lines
- Since the programs probably need to do the following:
if (
xdp_md->has_skb_metadata) {
access/change skb metadata by doing structxdp_to_skb_metadata*p
=data_meta;and directly access/change
xdp->skb_metadatainstead of usingxdp->data_meta.Ack.
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?
Quoted 4 lines
Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing data_meta pointer)?
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
--------------
| skb_metadata
--------------
| data_meta
--------------
| data
--------------
Not sure if that's what you meant? :)
-Toke
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 195 lines · Toke Høiland-Jørgensen
Quoted 183 lines · Stanislav Fomichev
Quoted 182 lines · Martin KaFai Lau
Quoted 163 lines · Stanislav Fomichev
Quoted 111 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Quoted 7 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Quoted 6 lines
Quoted 5 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc. The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)Quoted 46 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.Quoted 37 lines
Quoted 20 lines
Quoted 20 lines
Quoted 18 lines
Quoted 3 lines
Does
xdp_to_skb_metadatahave a use case forXDP_PASS(like patch 7) or thexdp_to_skb_metadatacan be limited toXDP_REDIRECTonly?
XDP_PASScases where we convertxdp_buffinto skb in the drivers right now usually have C code to manually pull out the metadata (out of hw desc) and put it into skb.So, currently, if we're calling
bpf_xdp_metadata_export_to_skb()forXDP_PASS, we're doing a double amount of work:skb_metadata_import_from_xdpfirst, then custom driver code second.In theory, maybe we should completely skip drivers custom parsing when there is a prog with
BPF_F_XDP_HAS_METADATA?
Then bothxdp->skbpaths (XDP_PASS+XDP_REDIRECT) will be bpf-driven and won't require any mental work (plus, the drivers won't have to care either in the future).Quoted 1 line
WDYT?
Quoted 7 lines
Quoted 7 lines
Yeah, not sure if it can solely depend on
BPF_F_XDP_HAS_METADATAbut it makes sense to only use the hints (if ever written) from xdp prog especially if it will eventually support xdp prog changing some of the hints in the future. For now, I think either way is fine since they are the same and the xdp prog is sort of doing extra unnecessary work anyway by callingbpf_xdp_metadata_export_to_skb()withXDP_PASSand knowing nothing can be changed now.I agree it would be best if the drivers also use the XDP metadata (if present) on
XDP_PASS. Longer term my hope is we can make the XDP metadata support the only thing drivers need to implement (i.e., have the stack call into that code even when no XDP program is loaded), but for now just for consistency (and allowing the XDP program to update the metadata), we should probably at least consume it onXDP_PASS.-Toke
Not to derail the discussion (left the last message intact on top, feel free to continue), but to summarize. The proposed changes seem to be:
Quoted 8 lines
1.
bpf_xdp_metadata_export_to_skb()should return pointer to "structxdp_to_skb_metadata"
- This should let bpf programs change the metadata passed to the skb2. "struct
xdp_to_skb_metadata" should have itsbtf_idas the first__u32member (and remove the magic)
- This is for the redirect case where the end users, includingAF_XDP, can parse this metadata frombtf_idI think Toke's idea is to put the
btf_idat the end ofxdp_to_skb_metadata. I can see why the end is needed for the userspaceAF_XDPbecause, afaict,AF_XDPrx_desccurrently cannot tell if there is metadata written by the xdp prog or not. However, if the 'has_skb_metadata' bit can also be passed to theAF_XDPrx_desc->options, thebtf_idmay as well be not needed now. However, thebtf_idand other future new members can be added to thexdp_to_skb_metadatalater if there is a need.Quoted 8 lines
Quoted 3 lines
For the kernel and xdp prog, a bit in the
xdp->flagsshould be enough to get to thexdp_to_skb_metadata. The xdp prog will use CO-RE to access the members inxdp_to_skb_metadata.Ack, good points on putting it at the end.
Regarding bit indesc->optionsvsbtf_id: since it seems thatbtf_idis useful anyway, let's start with that? We can add a bit later on if it turns out using metadata is problematic otherwise.
Quoted 4 lines
I think the bit is mostly useful so that the stack can know that the metadata has been set before consuming it (to guard against regular
xdp_metadatausage accidentally hitting the "right" BTF ID). I don't think it needs to be exposed to the XDP programs themselves.
SG! A flag for xdp_buff/frame and a kfunc to query it for bpf.
Quoted 10 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
- This, however, is not all the metadata that the device can
support, but a much narrower set that the kernel is expected to use for skb construction3.
__randomize_layoutisn't really helping, CO-RE will trigger regardless; maybe only the case where it matters is probablyAF_XDP, so still useful?Yeah, see my response to Martin, I think the randomisation is useful for
AF_XDPtransfer.
SG. Let's keep it for now. Worst case, if it hurts, we can remove it later...
Quoted 14 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
4. The presence of the metadata generated by
bpf_xdp_metadata_export_to_skbshould be indicated by a flag in xdp_{buff,frame}->flags
- Assuming exposing it viaxdp_md->has_skb_metadatais ok?Quoted 8 lines
Quoted 2 lines
probably
__bpf_md_ptr(struct xdp_to_skb_metadata *, skb_metadata)and the type will bePTR_TO_BTF_ID_OR_NULL.Oh, that seems even better than returning it from
bpf_xdp_metadata_export_to_skb.bpf_xdp_metadata_export_to_skbcan return true/false and the rest goes via default verifier ctx resolution mechanism..
(returning ptr from a kfunc seems to be a bit complicated right now)
Quoted 3 lines
See my response to John in the other thread about mixing stable UAPI (in
xdp_md) and unstable BTF structures in thexdp_mdstruct: I think this is confusing and would prefer a kfunc.
SG!
Quoted 38 lines
Quoted 38 lines
Quoted 7 lines
Quoted 5 lines
- Since the programs probably need to do the following:
if (
xdp_md->has_skb_metadata) {
access/change skb metadata by doing structxdp_to_skb_metadata*p
=data_meta;and directly access/change
xdp->skb_metadatainstead of usingxdp->data_meta.Ack.
Quoted 27 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?
Quoted 8 lines
Quoted 4 lines
Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?
I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
Quoted 11 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------
Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming skb_metadata in the kernel becomes messier)
af_xdp can check whether skb_metdata is present by looking at data - offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data - sizeof(skb_metadata)
Otherwise, if it's the other way around, how do we find skb_metadata in a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program find skb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)
Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the skb_metadata would live in the same place at the data_meta pointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.
Quoted 22 lines
Quoted 11 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)
Quoted 5 lines
Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?
Erm, maybe I'm missing something here, but skb_metadata is fixed size, right? So if the "skb_metadata is present" flag is set, we know that the sizeof(skb_metadata) bytes before the data_meta pointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.
For AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).
By this logic, the BTF_ID should be the *first* entry of struct skb_metadata, since that will be the field AF_XDP programs can find right off the bat, no?
-Toke
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 84 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 22 lines
Quoted 11 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Quoted 5 lines
Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.
Quoted 6 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no?
The problem with AF_XDP is that, IIUC, it doesn't have a data_meta pointer in the userspace.
You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |
So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
So if we have the following, we can locate skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata | skb_metadata | data | data - sizeof(skb_metadata) will get you there
But if it's the other way around, the program has to know sizeof(custom metadata) to locate skb_metadata:
| 256-sizeof(skb_metadata) headroom | skb_metadata | custom metadata | data |
Am I missing something here?
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 92 lines · Stanislav Fomichev
Quoted 84 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 22 lines
Quoted 11 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Quoted 5 lines
Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.Quoted 6 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no?
Quoted 5 lines
The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |
Ah, I was missing the bit where the data pointer actually points at data, not the start of the buf. Oops, my bad!
Quoted 8 lines
So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you there
Quoted 5 lines
But if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |Am I missing something here?
Hmm, so one could argue that the only way AF_XDP can consume custom metadata today is if it knows out of band what the size of it is. And if it knows that, it can just skip over it to go back to the skb_metadata, no?
The only problem left then is if there were multiple XDP programs called in sequence (whether before a redirect, or by libxdp chaining or tail calls), and the first one resized the metadata area without the last one knowing about it. For this, we could add a CLOBBER_PROGRAM_META flag to the skb_metadata helper which if set will ensure that the program metadata length is reset to 0?
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 21 lines · Toke Høiland-Jørgensen
Quoted 5 lines
The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |Ah, I was missing the bit where the data pointer actually points at data, not the start of the buf. Oops, my bad!
Quoted 12 lines
So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |
Quoted 6 lines
Quoted 1 line
Am I missing something here?
Hmm, so one could argue that the only way
AF_XDPcan consume custom metadata today is if it knows out of band what the size of it is. And if it knows that, it can just skip over it to go back to theskb_metadata, no?
+1 I replied with a similar point in another email. I also think we can safely assume this.
Quoted 7 lines
The only problem left then is if there were multiple XDP programs called in sequence (whether before a redirect, or by libxdp chaining or tail calls), and the first one resized the metadata area without the last one knowing about it. For this, we could add a
CLOBBER_PROGRAM_METAflag to theskb_metadatahelper which if set will ensure that the program metadata length is reset to 0?
How is it different from the same xdp prog calling bpf_xdp_adjust_meta() and bpf_xdp_metadata_export_to_skb() multiple times. The earlier stored skb_metadata needs to be moved during the latter bpf_xdp_adjust_meta(). The latter bpf_xdp_metadata_export_to_skb() will overwrite the earlier skb_metadata.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 24 lines · Martin KaFai Lau
Quoted 23 lines · Toke Høiland-Jørgensen
Quoted 5 lines
The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |Ah, I was missing the bit where the data pointer actually points at data, not the start of the buf. Oops, my bad!
Quoted 13 lines
So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |Am I missing something here?
Quoted 7 lines
Quoted 4 lines
Hmm, so one could argue that the only way
AF_XDPcan consume custom metadata today is if it knows out of band what the size of it is. And if it knows that, it can just skip over it to go back to theskb_metadata, no?+1 I replied with a similar point in another email. I also think we can safely assume this.
Great!
Quoted 8 lines
Quoted 7 lines
The only problem left then is if there were multiple XDP programs called in sequence (whether before a redirect, or by libxdp chaining or tail calls), and the first one resized the metadata area without the last one knowing about it. For this, we could add a
CLOBBER_PROGRAM_METAflag to theskb_metadatahelper which if set will ensure that the program metadata length is reset to 0?
Quoted 4 lines
How is it different from the same xdp prog calling
bpf_xdp_adjust_meta()andbpf_xdp_metadata_export_to_skb()multiple times. The earlier storedskb_metadataneeds to be moved during the latterbpf_xdp_adjust_meta(). The latterbpf_xdp_metadata_export_to_skb()will overwrite the earlierskb_metadata.
Well, it would just be a convenience flag, so instead of doing:
metalen = ctx->data - ctx->data_meta;
if (metalen)
xdp_adjust_meta(-metalen);bpf_xdp_metadata_export_to_skb(ctx);
you could just do:
bpf_xdp_metadata_export_to_skb(ctx, CLOBBER_PROGRAM_META);
and the kernel would do the check+move for you. But, well, the couple of extra instructions to do the check in BPF is probably fine.
(I'm talking here about a program that wants to make sure that any custom metadata that may have been added by an earlier program is removed before redirecting to an XSK socket; I expect we'd want to do something like this in the default program in libxdp).
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Stanislav FomichevQuoted 54 lines · Stanislav Fomichev
Quoted 53 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 3 lines
Quoted 3 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------
Yeah, for the kernel and xdp prog (ie not AF_XDP), I meant this:
| skb_metadata | custom metadata | data |
Quoted 17 lines
Quoted 17 lines
Quoted 16 lines
Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?
Quoted 5 lines
Quoted 5 lines
Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.
right, so to get to the skb_metadata, it will be data_meta -= sizeof(skb_metadata); /* probably need alignment */
Quoted 9 lines
Quoted 7 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no? >The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.
Yep. It is my understanding also. Missing data_meta pointer in the AF_XDP rx_desc is a potential problem. Having BTF_ID or not won't help.
Quoted 8 lines
You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
Quoted 7 lines
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |
Right, this won't work if the AF_XDP user does not know how big the custom metadata is. The kernel then needs to swap the "skb_metadata" and "custom metadata" + setting a flag in the AF_XDP rx_desc->options to make it looks like this:
| custom metadata | skb_metadata | data |
However, since data_meta is missing from the rx_desc, may be we can safely assume the AF_XDP user always knows the size of the custom metadata or there is usually no "custom metadata" and no swap is needed?
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 130 lines · Martin KaFai Lau
Quoted 54 lines · Stanislav Fomichev
Quoted 53 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 3 lines
Quoted 3 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Yeah, for the kernel and xdp prog (ie not
AF_XDP), I meant this:|
skb_metadata| custom metadata | data |Quoted 17 lines
Quoted 17 lines
Quoted 16 lines
Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?Quoted 5 lines
Quoted 5 lines
Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.right, so to get to the
skb_metadata, it will bedata_meta-=sizeof(skb_metadata); /* probably need alignment */Quoted 9 lines
Quoted 7 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no? >The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.Yep. It is my understanding also. Missing
data_metapointer in theAF_XDPrx_descis a potential problem. HavingBTF_IDor not won't help.Quoted 8 lines
You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
Quoted 7 lines
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |Right, this won't work if the
AF_XDPuser does not know how big the custom metadata is. The kernel then needs to swap the "skb_metadata" and "custom metadata" + setting a flag in theAF_XDPrx_desc->optionsto make it looks like this:
| custom metadata |skb_metadata| data |
Quoted 3 lines
However, since
data_metais missing from therx_desc, may be we can safely assume theAF_XDPuser always knows the size of the custom metadata or there is usually no "custom metadata" and no swap is needed?
If we can assume they can share that info, can they also share more info on what kind of metadata they would prefer to get?
If they can agree on the size, maybe they also can agree on the flows that need skb_metdata vs the flows that need a custom one?
Seems like we can start with supporting either one, but not both and extend in the future once we have more understanding on whether it's actually needed or not?
bpf_xdp_metadata_export_to_skb: adjust data meta, add uses-skb-metadata flagbpf_xdp_adjust_meta: unconditionally reset uses-skb-metadata flag
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 140 lines · Stanislav Fomichev
Quoted 130 lines · Martin KaFai Lau
Quoted 54 lines · Stanislav Fomichev
Quoted 53 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 3 lines
Quoted 3 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Yeah, for the kernel and xdp prog (ie not
AF_XDP), I meant this:|
skb_metadata| custom metadata | data |Quoted 17 lines
Quoted 17 lines
Quoted 16 lines
Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?Quoted 5 lines
Quoted 5 lines
Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.right, so to get to the
skb_metadata, it will bedata_meta-=sizeof(skb_metadata); /* probably need alignment */Quoted 9 lines
Quoted 7 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no? >The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.Yep. It is my understanding also. Missing
data_metapointer in theAF_XDPrx_descis a potential problem. HavingBTF_IDor not won't help.Quoted 8 lines
You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
Quoted 7 lines
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |Right, this won't work if the
AF_XDPuser does not know how big the custom metadata is. The kernel then needs to swap the "skb_metadata" and "custom metadata" + setting a flag in theAF_XDPrx_desc->optionsto make it looks like this:
| custom metadata |skb_metadata| data |Quoted 3 lines
However, since
data_metais missing from therx_desc, may be we can safely assume theAF_XDPuser always knows the size of the custom metadata or there is usually no "custom metadata" and no swap is needed?If we can assume they can share that info, can they also share more info on what kind of metadata they would prefer to get?
If they can agree on the size, maybe they also can agree on the flows that needskb_metdatavs the flows that need a custom one?
Quoted 6 lines
Seems like we can start with supporting either one, but not both and extend in the future once we have more understanding on whether it's actually needed or not?
bpf_xdp_metadata_export_to_skb: adjust data meta, add uses-skb-metadata flagbpf_xdp_adjust_meta: unconditionally reset uses-skb-metadata flag
hmm... I am thinking:
bpf_xdp_adjust_meta: move the existing (if any) skb_metadata and adjust xdp->data_meta.
bpf_xdp_metadata_export_to_skb: If skb_metadata exists, overwrites the existing one. If not exists, gets headroom before xdp->data_meta and writes hints.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 147 lines · Martin KaFai Lau
Quoted 140 lines · Stanislav Fomichev
Quoted 130 lines · Martin KaFai Lau
Quoted 54 lines · Stanislav Fomichev
Quoted 53 lines · Toke Høiland-Jørgensen
Skipping to the last bit:
Quoted 33 lines
Quoted 33 lines
Quoted 32 lines
Quoted 20 lines
Quoted 8 lines
} else { use kfuncs }5. Support the case where we keep program's metadata and kernel's
xdp_to_skb_metadata
-skb_metadata_import_from_xdp()will "consume" it by mem-moving the
rest of the metadata over it and adjusting the headroomI was thinking the kernel's
xdp_to_skb_metadatais always before the program's metadata. xdp prog should usually work in this order also: read/write headers, write its own metadata, callbpf_xdp_metadata_export_to_skb(), and return XDP_PASS/XDP_REDIRECT. When it isXDP_PASS, the kernel just needs to pop thexdp_to_skb_metadataand pass the remaining program's metadata to the bpf-tc.For the kernel and xdp prog, I don't think it matters where the
xdp_to_skb_metadatais. However, thexdp->data_meta(program's metadata) has to be beforexdp->databecause of the currentdata_metaand data comparison usage in the xdp prog.Quoted 7 lines
The order of the kernel's
xdp_to_skb_metadataand the program's metadata probably only matters to the userspaceAF_XDP. However, I don't see howAF_XDPsupports the program's metadata now. afaict, it can only work now if there is some sort of contract between them or theAF_XDPcurrently does not use the program's metadata. Either way, we can do the mem-moving only forAF_XDPand it should be a no op if there is no program's metadata? This behavior could also be configurable through setsockopt?Agreed on all of the above. For now it seems like the safest thing to do is to put
xdp_to_skb_metadatalast to allowaf_xdpto properly locatebtf_id.
Let's see if Toke disagrees :-)Quoted 6 lines
Quoted 3 lines
As I replied to Martin, I'm not sure it's worth the complexity to logically split the SKB metadata from the program's own metadata (as opposed to just reusing the existing
data_metapointer)?I'd gladly keep my current requirement where it's either or, but not both :-) We can relax it later if required?
So the way I've been thinking about it is simply that the
skb_metadatawould live in the same place at thedata_metapointer (including adjusting that pointer to accommodate it), and just overriding the existing program metadata, if any exists. But looking at it now, I guess having the split makes it easier for a program to write its own custom metadata and still use the skb metadata. See below about the ordering.Quoted 3 lines
Quoted 3 lines
However, if we do, the layout that makes most sense to me is putting the skb metadata before the program metadata, like:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
--------------
|skb_metadata
--------------
|data_meta
--------------
| data
--------------Yeah, for the kernel and xdp prog (ie not
AF_XDP), I meant this:|
skb_metadata| custom metadata | data |Quoted 17 lines
Quoted 17 lines
Quoted 16 lines
Quoted 1 line
Not sure if that's what you meant? :)
I was suggesting the other way around: |custom meta|skb_metadata|data| (but, as Martin points out, consuming
skb_metadatain the kernel becomes messier)
af_xdpcan check whetherskb_metdatais present by looking at data -offsetof(struct skb_metadata, btf_id).
progs that know how to handle custom metadata, will look at data -sizeof(skb_metadata)Otherwise, if it's the other way around, how do we find
skb_metadatain a redirected frame?
Let's say we have |skb_metadata|custom meta|data|, how does the final program findskb_metadata?
All the progs have to agree on the sizeof(tc/custom meta), right?Quoted 5 lines
Quoted 5 lines
Erm, maybe I'm missing something here, but
skb_metadatais fixed size, right? So if the "skb_metadatais present" flag is set, we know that thesizeof(skb_metadata)bytes before thedata_metapointer contains the metadata, and if the flag is not set, we know those bytes are not valid metadata.right, so to get to the
skb_metadata, it will bedata_meta-=sizeof(skb_metadata); /* probably need alignment */Quoted 9 lines
Quoted 7 lines
For
AF_XDP, we'd need to transfer the flag as well, and it could apply the same logic (getting the size from the vmlinux BTF).By this logic, the
BTF_IDshould be the *first* entry of structskb_metadata, since that will be the fieldAF_XDPprograms can find right off the bat, no? >The problem with
AF_XDPis that, IIUC, it doesn't have adata_metapointer in the userspace.Yep. It is my understanding also. Missing
data_metapointer in theAF_XDPrx_descis a potential problem. HavingBTF_IDor not won't help.Quoted 8 lines
You get an rx descriptor where the address points to the 'data':
| 256 bytes headroom where metadata can go | data |So you have (at most) 256 bytes of headroom, some of that might be the metadata, but you really don't know where it starts. But you know it definitely ends where the data begins.
Quoted 7 lines
So if we have the following, we can locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom | custom metadata |skb_metadata| data | data -sizeof(skb_metadata)will get you thereBut if it's the other way around, the program has to know sizeof(custom metadata) to locate
skb_metadata:
| 256-sizeof(skb_metadata) headroom |skb_metadata| custom metadata | data |Right, this won't work if the
AF_XDPuser does not know how big the custom metadata is. The kernel then needs to swap the "skb_metadata" and "custom metadata" + setting a flag in theAF_XDPrx_desc->optionsto make it looks like this:
| custom metadata |skb_metadata| data |Quoted 3 lines
However, since
data_metais missing from therx_desc, may be we can safely assume theAF_XDPuser always knows the size of the custom metadata or there is usually no "custom metadata" and no swap is needed?If we can assume they can share that info, can they also share more info on what kind of metadata they would prefer to get?
If they can agree on the size, maybe they also can agree on the flows that needskb_metdatavs the flows that need a custom one?Quoted 6 lines
Seems like we can start with supporting either one, but not both and extend in the future once we have more understanding on whether it's actually needed or not?
bpf_xdp_metadata_export_to_skb: adjust data meta, add uses-skb-metadata flagbpf_xdp_adjust_meta: unconditionally reset uses-skb-metadata flag
Quoted 7 lines
hmm... I am thinking:
bpf_xdp_adjust_meta: move the existing (if any)skb_metadataand adjustxdp->data_meta.
bpf_xdp_metadata_export_to_skb: Ifskb_metadataexists, overwrites the existing one. If not exists, gets headroom beforexdp->data_metaand writes hints.
Yeah, +1 on this. For AF_XDP that means that if you only do bpf_xdp_metadata_export_to_skb() you'll get the skb metadata right before data, and if you add custom metadata yourself, that goes in-between so you'll need to have some way to communicate the length to the AF_XDP consumer. And a default program (like in libxdp) can just check the metadata pointer and make sure to remove any metadata before redirecting to userspace, like in the example from my other reply to Martin.
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Stanislav FomichevQuoted 5 lines · Stanislav Fomichev
Quoted 5 lines
Quoted 5 lines
Oh, that seems even better than returning it from
bpf_xdp_metadata_export_to_skb.bpf_xdp_metadata_export_to_skbcan return true/false and the rest goes via default verifier ctx resolution mechanism..
(returning ptr from a kfunc seems to be a bit complicated right now)
What is the complication in returning ptr from a kfunc? I want to see if it can be solved because it will be an easier API to use instead of calling another kfunc to get the ptr.
Quoted 3 lines
Quoted 3 lines
See my response to John in the other thread about mixing stable UAPI (in
xdp_md) and unstable BTF structures in thexdp_mdstruct: I think this is confusing and would prefer a kfunc.
hmm... right, it will be one of the first considering the current __bpf_md_ptr() usages are only exposing another struct in uapi, eg. __bpf_md_ptr(struct bpf_sock *, sk).
A kfunc will also be fine.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
"
Quoted 11 lines · Martin KaFai Lau
Quoted 5 lines · Stanislav Fomichev
Quoted 5 lines
Quoted 5 lines
Oh, that seems even better than returning it from
bpf_xdp_metadata_export_to_skb.bpf_xdp_metadata_export_to_skbcan return true/false and the rest goes via default verifier ctx resolution mechanism..
(returning ptr from a kfunc seems to be a bit complicated right now)What is the complication in returning ptr from a kfunc? I want to see if it can be solved because it will be an easier API to use instead of calling another kfunc to get the ptr.
At least for returning a pointer to the basic c types like int/long, I was hitting the following:
commit eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae
Author: Benjamin Tissoires <[email protected]> AuthorDate: Tue Sep 6 17:13:02 2022 +0200 Commit: Alexei Starovoitov <[email protected]> CommitDate: Wed Sep 7 11:05:17 2022 -0700
bpf/verifier: allow kfunc to return an allocated mem
Where I had to add an extra "const int rdonly_buf_size" argument to the kfunc to make the verifier happy.
But I haven't really looked at what would happen with the pointers to structs (or why, at all, we have this restriction).
Quoted 10 lines
Quoted 3 lines
Quoted 3 lines
See my response to John in the other thread about mixing stable UAPI (in
xdp_md) and unstable BTF structures in thexdp_mdstruct: I think this is confusing and would prefer a kfunc.hmm... right, it will be one of the first considering the current
__bpf_md_ptr()usages are only exposing another struct in uapi, eg.__bpf_md_ptr(struct bpf_sock *, sk).A kfunc will also be fine.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Martin KaFai LauQuoted 19 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
Quoted 8 lines
Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.
Yup, absolutely! In that sense, reusing the SKB format is mostly a convenience feature. However, lots of people consume AF_XDP through the default program installed by libxdp in the XSK setup code, and including custom metadata there is awkward. So having the metadata consumed by the stack as the "default subset" would enable easy consumption by non-advanced users, while advanced users can still do custom stuff by writing their own XDP program that calls the kfuncs.
Quoted 9 lines
Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).
Yup, totally fine with just keeping that capability :)
Quoted 14 lines
Quoted 6 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
Quoted 3 lines
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?
For the metadata consumed by the stack right now it's a bit hypothetical, yeah. However, there's a bunch of metadata commonly supported by hardware that the stack currently doesn't consume and that hopefully this feature will end up making more accessible. My hope is that the stack can also learn how to use this in the future, in which case we may run out of space. So I think of that bit mostly as future-proofing...
Quoted 7 lines
Quoted 4 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?
Yeah, exactly!
Quoted 14 lines
Quoted 5 lines
Quoted 4 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).
Quoted 2 lines
If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc.
The problem with that is that then we have to spend cycles writing eight bytes of zeroes into the checksum field :)
Quoted 3 lines
The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.
Yeah, hence a flags field so we can just see if setting each field succeeded?
Quoted 5 lines
It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.
Quoted 7 lines
The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?
Hmm, logically splitting the program metadata and the xdp_hints metadata (but having them share the same area) *could* work, I guess, I'm just not sure it's worth the extra complexity?
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)
Quoted 8 lines
I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.
That only works inside the kernel, though. Since the metadata field can be copied wholesale to AF_XDP, having it randomized forces userspace consumers to also write code to deal with the layout being dynamic...
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 68 lines · Toke Høiland-Jørgensen
Quoted 19 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 8 lines
Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Yup, absolutely! In that sense, reusing the SKB format is mostly a convenience feature. However, lots of people consume
AF_XDPthrough the default program installed by libxdp in the XSK setup code, and including custom metadata there is awkward. So having the metadata consumed by the stack as the "default subset" would enable easy consumption by non-advanced users, while advanced users can still do custom stuff by writing their own XDP program that calls the kfuncs.Quoted 9 lines
Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Yup, totally fine with just keeping that capability :)
Quoted 14 lines
Quoted 6 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
Quoted 3 lines
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?
Quoted 7 lines
For the metadata consumed by the stack right now it's a bit hypothetical, yeah. However, there's a bunch of metadata commonly supported by hardware that the stack currently doesn't consume and that hopefully this feature will end up making more accessible. My hope is that the stack can also learn how to use this in the future, in which case we may run out of space. So I think of that bit mostly as future-proofing...
ic. in this case, Can the btf_id be added to 'struct xdp_to_skb_metadata' later if it is indeed needed? The 'struct xdp_to_skb_metadata' is not in UAPI and doing it with CO-RE is to give us flexibility to make this kind of changes in the future.
Quoted 25 lines
Quoted 8 lines
Quoted 5 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Yeah, exactly!
Quoted 14 lines
Quoted 13 lines
Quoted 4 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).
Quoted 5 lines
Quoted 2 lines
If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc.
The problem with that is that then we have to spend cycles writing eight bytes of zeroes into the checksum field :)
With a common 'struct xdp_to_skb_metadata', I am not sure how some of these zero writes can be avoided. If the xdp prog wants to optimize, it can call individual kfunc to get individual hints.
Quoted 7 lines
Quoted 4 lines
The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.Yeah, hence a flags field so we can just see if setting each field succeeded?
How testing a flag is different from checking 0/invalid-value of a field? or some fields just don't have an invalid value to check for like vlan_tci?
You meant a flags field as a return value or in the 'struct xdp_to_skb_metadata' ?
Quoted 14 lines
Quoted 6 lines
It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.Quoted 7 lines
The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?
Quoted 3 lines
Hmm, logically splitting the program metadata and the
xdp_hintsmetadata (but having them share the same area) *could* work, I guess, I'm just not sure it's worth the extra complexity?
It shouldn't stop the existing xdp prog writing its own metadata from using the the new bpf_xdp_metadata_export_to_skb().
Quoted 16 lines
Quoted 16 lines
Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.
Quoted 7 lines
Quoted 3 lines
It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.That only works inside the kernel, though. Since the metadata field can be copied wholesale to
AF_XDP, having it randomized forces userspace consumers to also write code to deal with the layout being dynamic...
hm... I still don't see how useful it is, in particular you mentioned the libxdp will install a xdp prog to write this default format (xdp_to_skb_metadata) and likely libxdp will also provide some helpers to parse the xdp_to_skb_metadata and the libxdp user should not need to know if CO-RE is used or not. Considering it is a kernel internal struct, I think it is fine to keep it and can be revisited later if needed. Lets get on to other things first :)
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 77 lines · Martin KaFai Lau
Quoted 68 lines · Toke Høiland-Jørgensen
Quoted 19 lines · Martin KaFai Lau
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Quoted 8 lines
Quoted 6 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
- Transferring the packet+metadata toAF_XDPfwiw, the xdp prog could also be more selective and only stores one of the hints instead of the whole 'struct
xdp_to_skb_metadata'.Yup, absolutely! In that sense, reusing the SKB format is mostly a convenience feature. However, lots of people consume
AF_XDPthrough the default program installed by libxdp in the XSK setup code, and including custom metadata there is awkward. So having the metadata consumed by the stack as the "default subset" would enable easy consumption by non-advanced users, while advanced users can still do custom stuff by writing their own XDP program that calls the kfuncs.Quoted 9 lines
Quoted 6 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)The last one could be solved by calling additional kfuncs, but that would be less efficient than just directly editing the struct which will be cache-hot after the helper returns.
Yeah, it is more efficient to directly write if possible. I think this set allows the direct reading and writing already through
data_meta(as a_u8*).Yup, totally fine with just keeping that capability :)
Quoted 14 lines
Quoted 6 lines
And yeah, this will allow the XDP program to inject arbitrary metadata into the netstack; but it can already inject arbitrary *packet* data into the stack, so not sure if this is much of an additional risk? If it does lead to trivial crashes, we should probably harden the stack against that?
Quoted 7 lines
As for the random number, Jesper and I discussed replacing this with the same BTF-ID scheme that he was using in his patch series. I.e., instead of just putting in a random number, we insert the BTF ID of the metadata struct at the end of it. This will allow us to support multiple different formats in the future (not just changing the layout, but having multiple simultaneous formats in the same kernel image), in case we run out of space.
Quoted 3 lines
This seems a bit hypothetical. How much headroom does it usually have for the xdp prog? Potentially the hints can use all the remaining space left after the header encap and the current
bpf_xdp_adjust_meta()usage?Quoted 7 lines
For the metadata consumed by the stack right now it's a bit hypothetical, yeah. However, there's a bunch of metadata commonly supported by hardware that the stack currently doesn't consume and that hopefully this feature will end up making more accessible. My hope is that the stack can also learn how to use this in the future, in which case we may run out of space. So I think of that bit mostly as future-proofing...
Quoted 4 lines
ic. in this case, Can the
btf_idbe added to 'structxdp_to_skb_metadata' later if it is indeed needed? The 'structxdp_to_skb_metadata' is not in UAPI and doing it with CO-RE is to give us flexibility to make this kind of changes in the future.
My worry is mostly that it'll be more painful to add it later than just including it from the start, mostly because of AF_XDP users. But if we do the randomisation thing (thus forcing AF_XDP users to deal with the dynamic layout as well), it should be possible to add it later, and I can live with that option as well...
Quoted 27 lines
Quoted 27 lines
Quoted 7 lines
Quoted 4 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Yeah, exactly!
Quoted 16 lines
Quoted 5 lines
Quoted 4 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc.
Quoted 6 lines
Quoted 2 lines
The problem with that is that then we have to spend cycles writing eight bytes of zeroes into the checksum field :)
With a common 'struct
xdp_to_skb_metadata', I am not sure how some of these zero writes can be avoided. If the xdp prog wants to optimize, it can call individual kfunc to get individual hints.
Erm, we just... don't write those fields? Something like:
void write_skb_meta(hw, ctx) {
struct xdp_skb_metadata meta = ctx->data_meta - sizeof(struct xdp_skb_metadata); meta->valid_fields = 0;
if (hw_has_timestamp) {
meta->timestamp = hw->timestamp;
meta->valid_fields |= FIELD_TIMESTAMP;
} /* otherwise meta->timestamp is just uninitialised */ if (hw_has_rxhash) {
meta->rxhash = hw->rxhash;
meta->valid_fields |= FIELD_RXHASH; } /* otherwise meta->rxhash is just uninitialised */ ...etc...
}
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines
The xdp prog needs a direct way to tell hard failure when it cannot write the meta area because of not enough space. Comparing
xdp->data_metawithxdp->dataas a side effect is not intuitive.Yeah, hence a flags field so we can just see if setting each field succeeded?
How testing a flag is different from checking 0/invalid-value of a field?
The flags field is smaller, so we write fewer bytes if not all fields are populated.
Quoted 2 lines
or some fields just don't have an invalid value to check for like
vlan_tci?
Yeah, that could also be an issue.
Quoted 1 line
You meant a flags field as a return value or in the 'struct
xdp_to_skb_metadata' ?
See above.
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
It is more than saving the bound check. With type info of 'struct
xdp_to_skb_metadata*', the verifier can do more checks like reading in the middle of an integer member. The verifier could also limit write access only to a few struct's members if it is needed.The returning 'struct
xdp_to_skb_metadata*' should not be an alias to thexdp->data_meta. They should actually point to different locations in the headroom.bpf_xdp_metadata_export_to_skb()sets a flag inxdp_buff.xdp->data_metawon't be changed and keeps pointing to the lastbpf_xdp_adjust_meta()location. The kernel will know if there isxdp_to_skb_metadatabefore thexdp->data_metawhen that bit is set in the xdp_{buff,frame}. Would it work?
Quoted 6 lines
Quoted 3 lines
Hmm, logically splitting the program metadata and the
xdp_hintsmetadata (but having them share the same area) *could* work, I guess, I'm just not sure it's worth the extra complexity?It shouldn't stop the existing xdp prog writing its own metadata from using the the new
bpf_xdp_metadata_export_to_skb().
Right, I think I see what you mean, and I agree that splitting it internally in the kernel does make sense (see my other reply to Stanislav).
Quoted 24 lines
Quoted 16 lines
Quoted 16 lines
Quoted 10 lines
Quoted 3 lines
A related question, why 'struct
xdp_to_skb_metadata' needs__randomize_layout?The
__randomize_layoutthing is there to force BPF programs to use CO-RE to access the field. This is to avoid the struct layout accidentally ossifying because people in practice rely on a particular layout, even though we tell them to use CO-RE. There are lots of examples of this happening in other domains (IP header options, TCP options, etc), and__randomize_layoutseemed like a neat trick to enforce CO-RE usage :)I am not sure if it is necessary or helpful to only enforce
__randomize_layoutin 'structxdp_to_skb_metadata'. There are other CO-RE use cases (tracing and non tracing) that already have direct access (reading and/or writing) to other kernel structures.Quoted 7 lines
Quoted 3 lines
It is more important for the verifier to see the xdp prog accessing it as a 'struct
xdp_to_skb_metadata*' instead ofxdp->data_metawhich is a__u8* so that the verifier can enforce the rules of access.That only works inside the kernel, though. Since the metadata field can be copied wholesale to
AF_XDP, having it randomized forces userspace consumers to also write code to deal with the layout being dynamic...
Quoted 7 lines
hm... I still don't see how useful it is, in particular you mentioned the libxdp will install a xdp prog to write this default format (
xdp_to_skb_metadata) and likely libxdp will also provide some helpers to parse thexdp_to_skb_metadataand the libxdp user should not need to know if CO-RE is used or not. Considering it is a kernel internal struct, I think it is fine to keep it and can be revisited later if needed. Lets get on to other things first :)
Well, if it was just kernel-internal, sure. But we're also exporting it to userspace (through AF_XDP). Well-behaved users will obviously do the right thing and use CO-RE. I'm trying to guard against users just blindly copy-pasting the struct definition from the kernel and doing a static cast, then complaining about their code breaking the first time we change the struct layout. Which I sadly expect that there absolutely will be people who do unless we actively make sure that doesn't work from the get-go. And since the randomisation is literally just adding __randomize_layout to the struct definition, I'd rather start out with having it, and removing it later if it turns out not to be needed... :)
-Toke
Martin KaFai Lau
reviewerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 13 lines · Toke Høiland-Jørgensen
Quoted 8 lines
Quoted 7 lines
For the metadata consumed by the stack right now it's a bit hypothetical, yeah. However, there's a bunch of metadata commonly supported by hardware that the stack currently doesn't consume and that hopefully this feature will end up making more accessible. My hope is that the stack can also learn how to use this in the future, in which case we may run out of space. So I think of that bit mostly as future-proofing...
Quoted 4 lines
ic. in this case, Can the
btf_idbe added to 'structxdp_to_skb_metadata' later if it is indeed needed? The 'structxdp_to_skb_metadata' is not in UAPI and doing it with CO-RE is to give us flexibility to make this kind of changes in the future.
Quoted 5 lines
My worry is mostly that it'll be more painful to add it later than just including it from the start, mostly because of
AF_XDPusers. But if we do the randomisation thing (thus forcingAF_XDPusers to deal with the dynamic layout as well), it should be possible to add it later, and I can live with that option as well...
imo, considering we are trying to optimize unnecessary field initialization as below, it is sort of wasteful to always initialize the btf_id with the same value. It is better to add it in the future when there is a need.
Quoted 36 lines
Quoted 27 lines
Quoted 27 lines
Quoted 7 lines
Quoted 4 lines
We should probably also have a flag set on the
xdp_frameso the stack knows that the metadata area contains relevant-to-skb data, to guard against an XDP program accidentally hitting the "magic number" (BTF_ID) in unrelated stuff it puts into the metadata area.Yeah, I think having a flag is useful. The flag will be set at
xdp_buffand then transfer to thexdp_frame?Yeah, exactly!
Quoted 16 lines
Quoted 5 lines
Quoted 4 lines
After re-reading patch 6, have another question. The 'void
bpf_xdp_metadata_export_to_skb();' function signature. Should it at least return ok/err? or even return a 'structxdp_to_skb_metadata*' pointer and the xdp prog can directly read (or even write) it?Quoted 8 lines
Hmm, I'm not sure returning a failure makes sense? Failure to read one or more fields just means that those fields will not be populated? We should probably have a flags field inside the metadata struct itself to indicate which fields are set or not, but I'm not sure returning an error value adds anything? Returning a pointer to the metadata field might be convenient for users (it would just be an alias to the
data_metapointer, but the verifier could know its size, so the program doesn't have to bounds check it).If some hints are not available, those hints should be initialized to 0/CHECKSUM_NONE/...etc.
Quoted 6 lines
Quoted 2 lines
The problem with that is that then we have to spend cycles writing eight bytes of zeroes into the checksum field :)
With a common 'struct
xdp_to_skb_metadata', I am not sure how some of these zero writes can be avoided. If the xdp prog wants to optimize, it can call individual kfunc to get individual hints.Erm, we just... don't write those fields? Something like:
Quoted 15 lines
void write_skb_meta(hw, ctx) {
struct xdp_skb_metadata meta = ctx->data_meta - sizeof(struct xdp_skb_metadata);
meta->valid_fields = 0;
if (hw_has_timestamp) {
meta->timestamp = hw->timestamp;
meta->valid_fields |= FIELD_TIMESTAMP;
} /* otherwise meta->timestamp is just uninitialised */
if (hw_has_rxhash) {
meta->rxhash = hw->rxhash;
meta->valid_fields |= FIELD_RXHASH;
} /* otherwise meta->rxhash is just uninitialised */
...etc...
}Ah, got it. Make sense. My mind was stalled in the paradigm that a helper that needs to initialize the result.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 20 lines · Martin KaFai Lau
Quoted 13 lines · Toke Høiland-Jørgensen
Quoted 8 lines
Quoted 7 lines
For the metadata consumed by the stack right now it's a bit hypothetical, yeah. However, there's a bunch of metadata commonly supported by hardware that the stack currently doesn't consume and that hopefully this feature will end up making more accessible. My hope is that the stack can also learn how to use this in the future, in which case we may run out of space. So I think of that bit mostly as future-proofing...
Quoted 4 lines
ic. in this case, Can the
btf_idbe added to 'structxdp_to_skb_metadata' later if it is indeed needed? The 'structxdp_to_skb_metadata' is not in UAPI and doing it with CO-RE is to give us flexibility to make this kind of changes in the future.Quoted 5 lines
My worry is mostly that it'll be more painful to add it later than just including it from the start, mostly because of
AF_XDPusers. But if we do the randomisation thing (thus forcingAF_XDPusers to deal with the dynamic layout as well), it should be possible to add it later, and I can live with that option as well...
Quoted 4 lines
imo, considering we are trying to optimize unnecessary field initialization as below, it is sort of wasteful to always initialize the
btf_idwith the same value. It is better to add it in the future when there is a need.
Okay, let's omit the BTF ID for now, and see what that looks like. I'll try to keep in mind to see if I can find any reasons why we'd need to add it back and make sure to complain before this lands if I find any :)
-Toke
John Fastabend
maintainerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Toke Høiland-JørgensenQuoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);
Hi Toke,
Trying not to bifurcate your thread. Can I start a new one here to elaborate on these use cases. I'm still a bit lost on any use case for this that makes sense to actually deploy on a network.
Quoted 5 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
I think for devmap there are still lots of opens how/where the skb is even built.
For cpumap I'm a bit unsure what the use case is. For ice, mlx and such you should use the hardware RSS if performance is top of mind. And then for specific devices on cpumap (maybe realtime or ptp things?) could we just throw it through the xdp_frame?
Quoted 1 line
- Transferring the packet+metadata to
AF_XDP
In this case we have the metadata and AF_XDP program and XDP program simply need to agree on metadata format. No need to have some magic numbers and driver specific kfuncs.
Quoted 3 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)
I don't get this case? XDP_PASS should go to stack normally through drivers build_skb routines. These will populate timestamp normally. My guess is simply descriptor->skb load/store is cheaper than carrying around this metadata and doing the call in BPF side. Anyways you just built an entire skb and hit the stack I don't think you will notice this noise in any benchmark.
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 26 lines · John Fastabend
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Hi Toke,
Trying not to bifurcate your thread. Can I start a new one here to elaborate on these use cases. I'm still a bit lost on any use case for this that makes sense to actually deploy on a network.
Quoted 8 lines
Quoted 5 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
I think for devmap there are still lots of opens how/where the skb is even built.
For veth it's pretty clear; i.e., when redirecting into containers.
Quoted 2 lines
For cpumap I'm a bit unsure what the use case is. For ice, mlx and such you should use the hardware RSS if performance is top of mind.
Hardware RSS works fine if your hardware supports the hashing you want; many do not. As an example, Jesper wrote this application that uses cpumap to divide out ISP customer traffic among different CPUs (solving an HTB scaling problem):
https://github.com/xdp-project/xdp-cpumap-tc
Quoted 2 lines
And then for specific devices on cpumap (maybe realtime or ptp things?) could we just throw it through the
xdp_frame?
Not sure what you mean here? Throw what through the xdp_frame?
Quoted 5 lines
Quoted 1 line
- Transferring the packet+metadata to
AF_XDPIn this case we have the metadata and
AF_XDPprogram and XDP program simply need to agree on metadata format. No need to have some magic numbers and driver specific kfuncs.
See my other reply to Martin: Yeah, for AF_XDP users that write their own kernel XDP programs, they can just do whatever they want. But many users just rely on the default program in libxdp, so having a standard format to include with that is useful.
Quoted 10 lines
Quoted 3 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)I don't get this case?
XDP_PASSshould go to stack normally through driversbuild_skbroutines. These will populate timestamp normally. My guess is simplydescriptor->skbload/store is cheaper than carrying around this metadata and doing the call in BPF side. Anyways you just built an entire skb and hit the stack I don't think you will notice this noise in any benchmark.
If you modify the packet before calling XDP_PASS you may want to update the metadata as well (for instance the RX hash, or in the future the metadata could also carry transport header offsets).
-Toke
John Fastabend
maintainerRe: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 31 lines · Toke Høiland-Jørgensen
Quoted 29 lines · John Fastabend
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Hi Toke,
Trying not to bifurcate your thread. Can I start a new one here to elaborate on these use cases. I'm still a bit lost on any use case for this that makes sense to actually deploy on a network.
Quoted 3 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
I think for devmap there are still lots of opens how/where the skb is even built.
For veth it's pretty clear; i.e., when redirecting into containers.
Ah but I think XDP on veth is a bit questionable in general. The use case is NFV I guess but its not how I would build out NFV. I've never seen it actually deployed other than in CI. Anyways not necessary to drop into that debate here. It exists so OK.
Quoted 10 lines
Quoted 3 lines
For cpumap I'm a bit unsure what the use case is. For ice, mlx and such you should use the hardware RSS if performance is top of mind.
Hardware RSS works fine if your hardware supports the hashing you want; many do not. As an example, Jesper wrote this application that uses cpumap to divide out ISP customer traffic among different CPUs (solving an HTB scaling problem):
I'm going to argue hw should be able to do this still and we should fix the hw but maybe not easily doable without convincing hardware folks to talk to us.
Also not obvious tto me how linked code works without more studying, its ingress HTB? So you would push the rxhash and timestamp into cpumap and then build the skb here with the correct skb->timestamp?
OK even if I can't exactly find the use case for cpumap if I had a use case I can see how passing metadata through is useful.
Quoted 5 lines
Quoted 3 lines
And then for specific devices on cpumap (maybe realtime or ptp things?) could we just throw it through the
xdp_frame?Not sure what you mean here? Throw what through the
xdp_frame?
Doesn't matter reread patches and figured it out I was slightly confused.
Quoted 12 lines
Quoted 6 lines
Quoted 2 lines
- Transferring the packet+metadata to
AF_XDPIn this case we have the metadata and
AF_XDPprogram and XDP program simply need to agree on metadata format. No need to have some magic numbers and driver specific kfuncs.See my other reply to Martin: Yeah, for
AF_XDPusers that write their own kernel XDP programs, they can just do whatever they want. But many users just rely on the default program in libxdp, so having a standard format to include with that is useful.
I don't think your AF_XDP program is any different than other AF_XDP programs. Your lib can create a standard format if it wants but kernel doesn't need to enforce it anyway.
Quoted 11 lines
Quoted 10 lines
Quoted 3 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)I don't get this case?
XDP_PASSshould go to stack normally through driversbuild_skbroutines. These will populate timestamp normally. My guess is simplydescriptor->skbload/store is cheaper than carrying around this metadata and doing the call in BPF side. Anyways you just built an entire skb and hit the stack I don't think you will notice this noise in any benchmark.
Quoted 3 lines
If you modify the packet before calling
XDP_PASSyou may want to update the metadata as well (for instance the RX hash, or in the future the metadata could also carry transport header offsets).
OK. So when you modify the pkt fixing up the rxhash makes sense. Thanks for the response I can see the argument.
Thanks,
John
Re: [xdp-hints] Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 54 lines · John Fastabend
Quoted 31 lines · Toke Høiland-Jørgensen
Quoted 29 lines · John Fastabend
Quoted 18 lines · Toke Høiland-Jørgensen
Snipping a bit of context to reply to this bit:
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 4 lines
Can the xdp prog still change the metadata through
xdp->data_meta? tbh, I am not sure it is solid enough by asking the xdp prog not to use the same random number in its own metadata + not to change the metadata throughxdp->data_metaafter callingbpf_xdp_metadata_export_to_skb().What do you think the usecase here might be? Or are you suggesting we reject further access to
data_metaafterbpf_xdp_metadata_export_to_skbsomehow?If we want to let the programs override some of this
bpf_xdp_metadata_export_to_skb()metadata, it feels like we can add more kfuncs instead of exposing the layout?
bpf_xdp_metadata_export_to_skb(ctx);bpf_xdp_metadata_export_skb_hash(ctx, 1234);Hi Toke,
Trying not to bifurcate your thread. Can I start a new one here to elaborate on these use cases. I'm still a bit lost on any use case for this that makes sense to actually deploy on a network.
Quoted 3 lines
There are several use cases for needing to access the metadata after calling
bpf_xdp_metdata_export_to_skb():Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
- Accessing the metadata after redirect (in a cpumap or devmap program, or on a veth device)
I think for devmap there are still lots of opens how/where the skb is even built.
For veth it's pretty clear; i.e., when redirecting into containers.
Ah but I think XDP on veth is a bit questionable in general. The use case is NFV I guess but its not how I would build out NFV. I've never seen it actually deployed other than in CI. Anyways not necessary to drop into that debate here. It exists so OK.
Quoted 9 lines
Quoted 3 lines
For cpumap I'm a bit unsure what the use case is. For ice, mlx and such you should use the hardware RSS if performance is top of mind.
Hardware RSS works fine if your hardware supports the hashing you want; many do not. As an example, Jesper wrote this application that uses cpumap to divide out ISP customer traffic among different CPUs (solving an HTB scaling problem):
Quoted 5 lines
Quoted 1 line
I'm going to argue hw should be able to do this still and we should fix the hw but maybe not easily doable without convincing hardware folks to talk to us.
Sure, in the ideal world the hardware should just be able to do this. Unfortunately, we don't live in that ideal world :)
Quoted 3 lines
Also not obvious tto me how linked code works without more studying, its ingress HTB? So you would push the rxhash and timestamp into cpumap and then build the skb here with the correct
skb->timestamp?
No, the HTB tree is on egress. The use case is an ISP middlebox that shapes (say) 1000 customers to their subscribed rate, using a big HTB tree. If you just do this with a single HTB instance on the egress NIC you run into the global qdisc lock and you can't scale beyond a pretty measly bandwidth. Whereas if you use multiple HW TXQs and the mq qdisc, you can partition the HTB tree so you only have a subset of customers on each HWQ/HTB instance. But for this to work, and still guarantee each customer gets shaped to the right rate, you need to ensure that all that customer's traffic hits the same HWQ. The xdp-cpumap-tc tool does this by configuring the TXQs to correspond to individual CPUs, and then runs an XDP program that matches traffic to customers and redirects them to the right CPU (using an LPM map).
This solution runs in production in quite a number of smallish WISPs, BTW, with quite nice results. The software to set it all up is also open
sourced: https://libreqos.io/
Coming back to HW metadata, the LibreQoS system could benefit from the hardware flow hash in particular, since that would save a hash operation when enqueueing the packet into sch_cake.
Quoted 2 lines
OK even if I can't exactly find the use case for cpumap if I had a use case I can see how passing metadata through is useful.
Great!
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
And then for specific devices on cpumap (maybe realtime or ptp things?) could we just throw it through the
xdp_frame?Not sure what you mean here? Throw what through the
xdp_frame?Doesn't matter reread patches and figured it out I was slightly confused.
Right, OK.
Quoted 13 lines
Quoted 12 lines
Quoted 6 lines
Quoted 2 lines
- Transferring the packet+metadata to
AF_XDPIn this case we have the metadata and
AF_XDPprogram and XDP program simply need to agree on metadata format. No need to have some magic numbers and driver specific kfuncs.See my other reply to Martin: Yeah, for
AF_XDPusers that write their own kernel XDP programs, they can just do whatever they want. But many users just rely on the default program in libxdp, so having a standard format to include with that is useful.
Quoted 3 lines
I don't think your
AF_XDPprogram is any different than otherAF_XDPprograms. Your lib can create a standard format if it wants but kernel doesn't need to enforce it anyway.
Yeah, we totally could. But since we're defining a "standard" format for kernel (skb) consumption anyway, making this available to AF_XDP is kinda convenient so we don't have to :)
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 3 lines
- Returning
XDP_PASS, but accessing some of the metadata first (whether to read or change it)I don't get this case?
XDP_PASSshould go to stack normally through driversbuild_skbroutines. These will populate timestamp normally. My guess is simplydescriptor->skbload/store is cheaper than carrying around this metadata and doing the call in BPF side. Anyways you just built an entire skb and hit the stack I don't think you will notice this noise in any benchmark.
Quoted 6 lines
Quoted 3 lines
If you modify the packet before calling
XDP_PASSyou may want to update the metadata as well (for instance the RX hash, or in the future the metadata could also carry transport header offsets).OK. So when you modify the pkt fixing up the rxhash makes sense. Thanks for the response I can see the argument.
Great! You're welcome :)
-Toke
John Fastabend
maintainerRE: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
In reply to Stanislav FomichevQuoted 5 lines · Stanislav Fomichev
Implement new
bpf_xdp_metadata_export_to_skbkfunc which prepares compatible xdp metadata for kernel consumption. This kfunc should be called prior tobpf_redirector (unless already called) when XDP_PASS'ing the frame into the kernel.
Hi,
Had a couple high level questions so starting a new thread thought it would be more confusing than helpful to add to the thread on this patch.
Quoted 5 lines
The implementation currently maintains
xdp_to_skb_metadatalayout by callingbpf_xdp_metadata_rx_timestampand placing small magic number. Fromskb_metdata_set, when we get expected magic number, we interpret metadata accordingly.
From commit message side I'm not able to parse this paragraph without reading code. Maybe expand it a bit for next version or it could just be me.
Quoted 3 lines
Both magic number and struct layout are randomized to make sure it doesn't leak into the userspace.
Are we worried about leaking pointers into XDP program here? We already leak pointers into XDP through helpers so I'm not sure it matters.
Quoted 5 lines
skb_metadata_setis amended withskb_metadata_import_from_xdpwhich tries to parse out the metadata and put it into skb.See the comment for r1 vs r2/r3/r4/r5 conventions.
I think for next version an expanded commit message with use cases would help. I had to follow the thread to get some ideas why this might be useful.
Quoted 85 lines
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- drivers/net/veth.c | 4 +- include/linux/bpf_patch.h | 2 + include/linux/skbuff.h | 4 ++ include/net/xdp.h | 13 +++++ kernel/bpf/bpf_patch.c | 30 +++++++++++ kernel/bpf/verifier.c | 18 +++++++ net/core/skbuff.c | 25 +++++++++ net/core/xdp.c | 104 +++++++++++++++++++++++++++++++++++--- 8 files changed, 193 insertions(+), 7 deletions(-)drivers/net/veth.c +3
-1@@ -1673,7 +1673,9 @@ static int veth_xdp(struct net_device *dev, struct netdev_bpf *xdp)static void veth_unroll_kfunc (const struct bpf_prog *prog,u32 func_id,struct bpf_patch *patch) { -if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) {/* return true; */ bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {include/linux/bpf_patch.h +2
-0@@ -16,6 +16,8 @@ size_t bpf_patch_len(const struct bpf_patch *patch);int bpf_patch_err (const struct bpf_patch *patch);void __bpf_patch_append (struct bpf_patch *patch,struct bpf_insn insn);struct bpf_insn *bpf_patch_data (const struct bpf_patch *patch); +void bpf_patch_resolve_jmp (struct bpf_patch *patch); +u32 bpf_patch_magles_registers (const struct bpf_patch *patch);#define bpf_patch_append (patch, ...) ({ \ struct bpf_insn insn[] = { __VA_ARGS__ }; \include/linux/skbuff.h +4
-0@@ -4217,9 +4217,13 @@ static inline bool skb_metadata_differs(const struct sk_buff *skb_a, true : __skb_metadata_differs(skb_a, skb_b, len_a); } +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len); +static inline void skb_metadata_set (struct sk_buff *skb,u8 meta_len) {skb_shinfo (skb)->meta_len = meta_len; +if (meta_len) +skb_metadata_import_from_xdp (skb, meta_len); }static inline void skb_metadata_clear (struct sk_buff *skb)include/net/xdp.h +2
-0@@ -411,6 +411,8 @@ void xdp_attachment_setup(struct xdp_attachment_info *info,#define DEV_MAP_BULK_SIZE XDP_BULK_QUEUE_SIZE#define XDP_METADATA_KFUNC_xxx \ + XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_EXPORT_TO_SKB, \ + bpf_xdp_metadata_export_to_skb) \ XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED, \ bpf_xdp_metadata_rx_timestamp_supported) \ XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_RX_TIMESTAMP, \
include/net/xdp.h XDP_METADATA_KFUNC_xxx · line 430
Quoted 6 lines
include/net/xdp.h +3
-0@@ -423,14 +425,25 @@ XDP_METADATA_KFUNC_xxx MAX_XDP_METADATA_KFUNC, }; +struct xdp_to_skb_metadata { +u32 magic;/* xdp_metadata_magic */ +u64 rx_timestamp;
Slightly confused. I thought/think most drivers populate the skb timestamp if they can already? So why do we need to bounce these through some xdp metadata? Won't all this cost more than the load/store directly from the descriptor into the skb? Even if drivers are not populating skb now shouldn't an ethtool knob be enough to turn this on?
I don't see the value of getting this in veth side its just a sw timestamp there.
If its specific to cpumap shouldn't we land this in cpumap code paths out of general XDP code paths?
Quoted 27 lines
include/net/xdp.h +8
-0+} __randomize_layout; + +struct bpf_patch ; +#ifdef CONFIG_DEBUG_INFO_BTF +extern u32 xdp_metadata_magic;extern struct btf_id_set8 xdp_metadata_kfunc_ids;static inline u32 xdp_metadata_kfunc_id (int id) {return xdp_metadata_kfunc_ids.pairs[id].id; } +void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch);#else +#define xdp_metadata_magic 0static inline u32 xdp_metadata_kfunc_id (int id) {return 0 ; } +static void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {return 0 ; }#endif #endif /* __LINUX_NET_XDP_H__ */ kernel/bpf/bpf_patch.c +0
-0@@ -49,3 +49,33 @@ struct bpf_insn *bpf_patch_data(const struct bpf_patch *patch) {return patch->insn; }
[...]
Quoted 78 lines
net/core/skbuff.c +25
-0@@ -72,6 +72,7 @@#include <net/mptcp.h> #include <net/mctp.h> #include <net/page_pool.h> +#include <net/xdp.h> #include <linux/uaccess.h> #include <trace/events/skb.h> @@ -6672,3 +6673,27 @@ nodefer: __kfree_skb(skb);if (unlikely (kick) && !cmpxchg (&sd->defer_ipi_scheduled,0 ,1 ))smp_call_function_single_async (cpu, &sd->defer_csd); } + +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len) +{ +struct xdp_to_skb_metadata *meta = (void *)(skb_mac_header (skb) - len); + +/* Optional SKB info, currently missing: +* - HW checksum info (skb->ip_summed) +* - HW RX hash (skb_set_hash) +* - RX ring dev queue index (skb_record_rx_queue) +*/ + +if (len !=sizeof (struct xdp_to_skb_metadata )) +return ; + +if (meta->magic != xdp_metadata_magic) +return ; + +if (meta->rx_timestamp) { + *skb_hwtstamps (skb) = (struct skb_shared_hwtstamps ){ + .hwtstamp =ns_to_ktime (meta->rx_timestamp), + }; + } +} +EXPORT_SYMBOL (skb_metadata_import_from_xdp);net/core/xdp.c +9
-6@@ -653,12 +653,6 @@ struct sk_buff *__xdp_build_skb_from_frame(struct xdp_frame *xdpf,/* Essential SKB info: protocol and skb->dev */ skb->protocol =eth_type_trans (skb, dev); -/* Optional SKB info, currently missing: -* - HW checksum info (skb->ip_summed) -* - HW RX hash (skb_set_hash) -* - RX ring dev queue index (skb_record_rx_queue) -*/ -/* Until page_pool get SKB return path, release DMA here */ xdp_release_frame (xdpf);@@ -712,6 +706,13 @@ struct xdp_frame *xdpf_clone(struct xdp_frame *xdpf)return nxdpf; } +/* For the packets directed to the kernel, this kfunc exports XDP metadata +* into skb context. +*/ +noinline void bpf_xdp_metadata_export_to_skb(const struct xdp_md *ctx) +{ +} +/* Indicates whether particular device supports rx_timestamp metadata. * This is an optional helper to support marking some branches as * "dead code" in the BPF programs. @@ -737,13 +738,104 @@ XDP_METADATA_KFUNC_xxx#undef XDP_METADATA_KFUNCBTF_SET8_END (xdp_metadata_kfunc_ids) +/* Make sure userspace doesn't depend on our layout by using +* different pseudo-generated magic value.
net/core/xdp.c XDP_METADATA_KFUNC_xxx · line 752
Quoted 10 lines
net/core/xdp.c +5
-0+*/ +u32 xdp_metadata_magic; +static const struct btf_kfunc_id_set xdp_metadata_kfunc_set = { .owner =THIS_MODULE , .set = &xdp_metadata_kfunc_ids, }; +/* Since we're not actually doing a call but instead rewriting +* in place, we can only afford to use R0-R5 scratch registers.
Why not just do a call? Its neat to inline this but your going to build an skb next. Thats not cheap and the cost of a call should be complete noise when hitting the entire stack?
Any benchmark to convince us this is worthwhile optimizations?
Quoted 10 lines
net/core/xdp.c +10
-0+* +* We reserve R1 for bpf_xdp_metadata_export_to_skb and let individual +* metadata kfuncs use only R0,R4-R5. +* +* The above also means we _cannot_ easily call any other helper/kfunc +* because there is no place for us to preserve our R1 argument; +* existing R6-R9 belong to the callee. +*/ +void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) +{
[...]
Quoted 2 lines
}
late_initcall(xdp_metadata_init);
Thanks,
John
Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 15 lines · John Fastabend
Quoted 5 lines · Stanislav Fomichev
Implement new
bpf_xdp_metadata_export_to_skbkfunc which prepares compatible xdp metadata for kernel consumption. This kfunc should be called prior tobpf_redirector (unless already called) when XDP_PASS'ing the frame into the kernel.Hi,
Had a couple high level questions so starting a new thread thought it would be more confusing than helpful to add to the thread on this patch.
Quoted 1 line
Quoted 8 lines
Quoted 4 lines
The implementation currently maintains
xdp_to_skb_metadatalayout by callingbpf_xdp_metadata_rx_timestampand placing small magic number. Fromskb_metdata_set, when we get expected magic number, we interpret metadata accordingly.From commit message side I'm not able to parse this paragraph without reading code. Maybe expand it a bit for next version or it could just be me.
Sure, will try to reword. In another thread we've discussed removing the magic number, so I'll have to rewrite this part anyway :-)
Quoted 6 lines
Quoted 3 lines
Both magic number and struct layout are randomized to make sure it doesn't leak into the userspace.
Are we worried about leaking pointers into XDP program here? We already leak pointers into XDP through helpers so I'm not sure it matters.
I wasn't sure here whether we want to have that xdp->skb (redirect) path to be completely opaque or it's ok to expose this to the bpf/af_xdp.
Seems like everybody's on board about exposing, so I'll be most likely removing that randomization part.
(see my recent reply to Martin/Toke)
Quoted 9 lines
Quoted 5 lines
skb_metadata_setis amended withskb_metadata_import_from_xdpwhich tries to parse out the metadata and put it into skb.See the comment for r1 vs r2/r3/r4/r5 conventions.
I think for next version an expanded commit message with use cases would help. I had to follow the thread to get some ideas why this might be useful.
Sure. I was planning to put together Documentation/bpf/xdp_metadata.rst with more details/assumptions/use-cases for the final non-rfc submissions.. Maybe that's better to help build up a full picture?
Quoted 87 lines
Quoted 87 lines
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- drivers/net/veth.c | 4 +- include/linux/bpf_patch.h | 2 + include/linux/skbuff.h | 4 ++ include/net/xdp.h | 13 +++++ kernel/bpf/bpf_patch.c | 30 +++++++++++ kernel/bpf/verifier.c | 18 +++++++ net/core/skbuff.c | 25 +++++++++ net/core/xdp.c | 104 +++++++++++++++++++++++++++++++++++--- 8 files changed, 193 insertions(+), 7 deletions(-)drivers/net/veth.c +3
-1@@ -1673,7 +1673,9 @@ static int veth_xdp(struct net_device *dev, struct netdev_bpf *xdp)static void veth_unroll_kfunc (const struct bpf_prog *prog,u32 func_id,struct bpf_patch *patch) { -if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) {/* return true; */ bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {include/linux/bpf_patch.h +2
-0@@ -16,6 +16,8 @@ size_t bpf_patch_len(const struct bpf_patch *patch);int bpf_patch_err (const struct bpf_patch *patch);void __bpf_patch_append (struct bpf_patch *patch,struct bpf_insn insn);struct bpf_insn *bpf_patch_data (const struct bpf_patch *patch); +void bpf_patch_resolve_jmp (struct bpf_patch *patch); +u32 bpf_patch_magles_registers (const struct bpf_patch *patch);#define bpf_patch_append (patch, ...) ({ \ struct bpf_insn insn[] = { __VA_ARGS__ }; \include/linux/skbuff.h +4
-0@@ -4217,9 +4217,13 @@ static inline bool skb_metadata_differs(const struct sk_buff *skb_a, true : __skb_metadata_differs(skb_a, skb_b, len_a); } +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len); +static inline void skb_metadata_set (struct sk_buff *skb,u8 meta_len) {skb_shinfo (skb)->meta_len = meta_len; +if (meta_len) +skb_metadata_import_from_xdp (skb, meta_len); }static inline void skb_metadata_clear (struct sk_buff *skb)include/net/xdp.h +2
-0@@ -411,6 +411,8 @@ void xdp_attachment_setup(struct xdp_attachment_info *info,#define DEV_MAP_BULK_SIZE XDP_BULK_QUEUE_SIZE#define XDP_METADATA_KFUNC_xxx \ + XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_EXPORT_TO_SKB, \ + bpf_xdp_metadata_export_to_skb) \ XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED, \ bpf_xdp_metadata_rx_timestamp_supported) \ XDP_METADATA_KFUNC(XDP_METADATA_KFUNC_RX_TIMESTAMP, \@@ -423,14 +425,25 @@ XDP_METADATA_KFUNC_xxx MAX_XDP_METADATA_KFUNC, };
Quoted 9 lines
include/net/xdp.h XDP_METADATA_KFUNC_xxx · line 430
Quoted 3 lines
include/net/xdp.h +3
-0+struct xdp_to_skb_metadata { +u32 magic;/* xdp_metadata_magic */ +u64 rx_timestamp;Slightly confused. I thought/think most drivers populate the skb timestamp if they can already? So why do we need to bounce these through some xdp metadata? Won't all this cost more than the load/store directly from the descriptor into the skb? Even if drivers are not populating skb now shouldn't an ethtool knob be enough to turn this on?
dsahern@ pointed out that it might be useful for the program to be able to override some of that metadata.
Or, for example, if there is no rx vlan offload, the program can strip it (as part of parsing) and put the vlan tag into that xdp_to_skb_metadata.
Quoted 2 lines
I don't see the value of getting this in veth side its just a sw timestamp there.
(veth is there so we can have some selftests)
Quoted 2 lines
If its specific to cpumap shouldn't we land this in cpumap code paths out of general XDP code paths?
See above, if we run this at cpumap time it's too late?
Quoted 116 lines
Quoted 27 lines
include/net/xdp.h +8
-0+} __randomize_layout; + +struct bpf_patch ; +#ifdef CONFIG_DEBUG_INFO_BTF +extern u32 xdp_metadata_magic;extern struct btf_id_set8 xdp_metadata_kfunc_ids;static inline u32 xdp_metadata_kfunc_id (int id) {return xdp_metadata_kfunc_ids.pairs[id].id; } +void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch);#else +#define xdp_metadata_magic 0static inline u32 xdp_metadata_kfunc_id (int id) {return 0 ; } +static void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {return 0 ; }#endif #endif /* __LINUX_NET_XDP_H__ */ kernel/bpf/bpf_patch.c +0
-0@@ -49,3 +49,33 @@ struct bpf_insn *bpf_patch_data(const struct bpf_patch *patch) {return patch->insn; }[...]
Quoted 86 lines
net/core/skbuff.c +25
-0@@ -72,6 +72,7 @@#include <net/mptcp.h> #include <net/mctp.h> #include <net/page_pool.h> +#include <net/xdp.h> #include <linux/uaccess.h> #include <trace/events/skb.h> @@ -6672,3 +6673,27 @@ nodefer: __kfree_skb(skb);if (unlikely (kick) && !cmpxchg (&sd->defer_ipi_scheduled,0 ,1 ))smp_call_function_single_async (cpu, &sd->defer_csd); } + +void skb_metadata_import_from_xdp (struct sk_buff *skb,size_t len) +{ +struct xdp_to_skb_metadata *meta = (void *)(skb_mac_header (skb) - len); + +/* Optional SKB info, currently missing: +* - HW checksum info (skb->ip_summed) +* - HW RX hash (skb_set_hash) +* - RX ring dev queue index (skb_record_rx_queue) +*/ + +if (len !=sizeof (struct xdp_to_skb_metadata )) +return ; + +if (meta->magic != xdp_metadata_magic) +return ; + +if (meta->rx_timestamp) { + *skb_hwtstamps (skb) = (struct skb_shared_hwtstamps ){ + .hwtstamp =ns_to_ktime (meta->rx_timestamp), + }; + } +} +EXPORT_SYMBOL (skb_metadata_import_from_xdp);net/core/xdp.c +12
-6@@ -653,12 +653,6 @@ struct sk_buff *__xdp_build_skb_from_frame(struct xdp_frame *xdpf,/* Essential SKB info: protocol and skb->dev */ skb->protocol =eth_type_trans (skb, dev); -/* Optional SKB info, currently missing: -* - HW checksum info (skb->ip_summed) -* - HW RX hash (skb_set_hash) -* - RX ring dev queue index (skb_record_rx_queue) -*/ -/* Until page_pool get SKB return path, release DMA here */ xdp_release_frame (xdpf);@@ -712,6 +706,13 @@ struct xdp_frame *xdpf_clone(struct xdp_frame *xdpf)return nxdpf; } +/* For the packets directed to the kernel, this kfunc exports XDP metadata +* into skb context. +*/ +noinline void bpf_xdp_metadata_export_to_skb(const struct xdp_md *ctx) +{ +} +/* Indicates whether particular device supports rx_timestamp metadata. * This is an optional helper to support marking some branches as * "dead code" in the BPF programs. @@ -737,13 +738,104 @@ XDP_METADATA_KFUNC_xxx#undef XDP_METADATA_KFUNCBTF_SET8_END (xdp_metadata_kfunc_ids) +/* Make sure userspace doesn't depend on our layout by using +* different pseudo-generated magic value. +*/ +u32 xdp_metadata_magic; +static const struct btf_kfunc_id_set xdp_metadata_kfunc_set = { .owner =THIS_MODULE , .set = &xdp_metadata_kfunc_ids, };
Quoted 8 lines
net/core/xdp.c XDP_METADATA_KFUNC_xxx · line 752
Quoted 2 lines
net/core/xdp.c +2
-0+/* Since we're not actually doing a call but instead rewriting +* in place, we can only afford to use R0-R5 scratch registers. Why not just do a call? Its neat to inline this but your going to build an skb next. Thats not cheap and the cost of a call should be complete noise when hitting the entire stack?
Any benchmark to convince us this is worthwhile optimizations?
I do have a suspicion that a non-zero amount of drivers will actually resort to calling kernel instead of writing bpf bytecode (especially since there might be some locks involved).
However if we prefer to go back to calls, there still has to be some translation table.
I'm assuming we want to at least resolve indirect netdev->kfunc_rx_metatada() calls at prog load time.
So we still need a per-netdev map from kfunc_id to real implementation func. And I don't think that it would be more simple than the switch statement that I have?
Quoted 20 lines
Quoted 10 lines
net/core/xdp.c +10
-0+* +* We reserve R1 for bpf_xdp_metadata_export_to_skb and let individual +* metadata kfuncs use only R0,R4-R5. +* +* The above also means we _cannot_ easily call any other helper/kfunc +* because there is no place for us to preserve our R1 argument; +* existing R6-R9 belong to the callee. +*/ +void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) +{[...]
Quoted 2 lines
}
late_initcall(xdp_metadata_init);Thanks,
John
Re: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Quoted 14 lines · Stanislav Fomichev
Quoted 4 lines
Quoted 4 lines
include/net/xdp.h +0
-0@@ -423,14 +425,25 @@ XDP_METADATA_KFUNC_xxx MAX_XDP_METADATA_KFUNC, };Quoted 9 lines
include/net/xdp.h XDP_METADATA_KFUNC_xxx · line 430
Quoted 3 lines
include/net/xdp.h +3
-0+struct xdp_to_skb_metadata { +u32 magic;/* xdp_metadata_magic */ +u64 rx_timestamp;Slightly confused. I thought/think most drivers populate the skb timestamp if they can already? So why do we need to bounce these through some xdp metadata? Won't all this cost more than the load/store directly from the descriptor into the skb? Even if drivers are not populating skb now shouldn't an ethtool knob be enough to turn this on?
Quoted 2 lines
dsahern@ pointed out that it might be useful for the program to be able to override some of that metadata.
Examples that come to mind from previous work:
1. changing vlans on a redirect: Rx on vlan 1 with h/w popping the vlan so it is provided in metadata. Then on a redirect it shifts to vlan 2 for Tx. But this example use case assumes Tx accesses the metadata to ask h/w to insert the header.
2. popping or updating an encap header and wanting to update the checksum
3. changing the h/w provided hash to affect steering of a subsequent skb
RFC v2 7/14 selftests/bpf: Verify xdp_metadata xdp->skb path
In reply to Stanislav Fomichev- divert 9081 UDP traffic to the kernel
- call bpf_xdp_metadata_export_to_skb for such packets
- the kernel should fill in hwtstamp
- verify that the received packet has non-zero hwtstamp
--- .../selftests/bpf/prog_tests/xdp_metadata.c | 92 +++++++++++++++++++ .../selftests/bpf/progs/xdp_metadata.c | 28 ++++++ 2 files changed, 120 insertions(+)
tools/testing/selftests/bpf/prog_tests/xdp_metadata.c +92 -0
@@ -19,6 +19,11 @@#define AF_XDP_SOURCE_PORT 1234#define AF_XDP_CONSUMER_PORT 8080 +#define SOCKET_CONSUMER_PORT 9081 + +#ifndef SOL_UDP +#define SOL_UDP 17 +#endif #define UMEM_NUM 16#define UMEM_FRAME_SIZE XSK_UMEM__DEFAULT_FRAME_SIZE
@@ -221,6 +226,71 @@ int verify_xsk_metadata(struct xsk *xsk)return 0 ; } +static void disable_rx_checksum (int fd) +{ +int ret, val; + + val =1 ; + ret =setsockopt (fd,SOL_UDP ,UDP_NO_CHECK6_RX , &val,sizeof (val)); +ASSERT_OK (ret,"setsockopt(UDP_NO_CHECK6_RX)" ); +} + +static void timestamping_enable (int fd) +{ +int ret, val; + + val =SOF_TIMESTAMPING_SOFTWARE |SOF_TIMESTAMPING_RAW_HARDWARE ; + ret =setsockopt (fd,SOL_SOCKET ,SO_TIMESTAMPING , &val,sizeof (val)); +ASSERT_OK (ret,"setsockopt(SO_TIMESTAMPING)" ); +} + +int verify_skb_metadata (int fd) +{ +char cmsg_buf[1024 ]; +char packet_buf[128 ]; + +struct scm_timestamping *ts; +struct iovec packet_iov; +struct cmsghdr *cmsg; +struct msghdr hdr; +bool found_hwtstamp = false; + +memset (&hdr,0 ,sizeof (hdr)); + hdr.msg_iov = &packet_iov; + hdr.msg_iovlen =1 ; + packet_iov.iov_base = packet_buf; + packet_iov.iov_len =sizeof (packet_buf); + + hdr.msg_control = cmsg_buf; + hdr.msg_controllen =sizeof (cmsg_buf); + +if (ASSERT_GE (recvmsg (fd, &hdr,0 ),0 ,"recvmsg" )) { +for (cmsg =CMSG_FIRSTHDR (&hdr); cmsg !=NULL ; + cmsg =CMSG_NXTHDR (&hdr, cmsg)) { + +if (cmsg->cmsg_level !=SOL_SOCKET ) +continue ; + +switch (cmsg->cmsg_type) { +case SCM_TIMESTAMPING : + ts = (struct scm_timestamping *)CMSG_DATA (cmsg); +if (ts->ts[2 ].tv_sec || ts->ts[2 ].tv_nsec) { + found_hwtstamp = true; +break ; + } +break ; +default : +break ; + } + } + } + +if (!ASSERT_EQ (found_hwtstamp, true,"no hwtstamp!" )) +return -1 ; + +return 0 ; +} +void test_xdp_metadata (void ) {struct xdp_metadata *bpf_obj =NULL ;
@@ -228,6 +298,7 @@ void test_xdp_metadata(void)struct bpf_program *prog;struct xsk tx_xsk = {};struct xsk rx_xsk = {}; +int rx_udp_fd =-1 ;int rx_ifindex;int ret;
@@ -243,6 +314,8 @@ void test_xdp_metadata(void)SYS ("ip link set dev " RX_NAME " up" );SYS ("ip addr add " TX_ADDR "/" PREFIX_LEN " dev " TX_NAME );SYS ("ip addr add " RX_ADDR "/" PREFIX_LEN " dev " RX_NAME ); +SYS ("sysctl -q net.ipv4.ip_forward=1" ); +SYS ("sysctl -q net.ipv4.conf.all.accept_local=1" ); rx_ifindex =if_nametoindex (RX_NAME );
@@ -256,6 +329,14 @@ void test_xdp_metadata(void)if (!ASSERT_OK (ret,"open_xsk(RX_NAME)" )) goto out; +/* Setup UPD listener for RX interface. */ + + rx_udp_fd =start_server (FAMILY ,SOCK_DGRAM ,NULL ,SOCKET_CONSUMER_PORT ,1000 ); +if (!ASSERT_GE (rx_udp_fd,0 ,"start_server" )) + goto out; +disable_rx_checksum (rx_udp_fd); +timestamping_enable (rx_udp_fd); +/* Attach BPF program to RX interface. */ bpf_obj =xdp_metadata__open ();
@@ -291,9 +372,20 @@ void test_xdp_metadata(void) "verify_xsk_metadata")) goto out; +/* Send packet destined to RX UDP socket. */ +if (!ASSERT_GE (generate_packet (&tx_xsk,SOCKET_CONSUMER_PORT ),0 , +"generate SOCKET_CONSUMER_PORT" )) + goto out; + +/* Verify SKB RX packet has proper metadata. */ +if (!ASSERT_GE (verify_skb_metadata (rx_udp_fd),0 , +"verify_skb_metadata" )) + goto out; + out:close_xsk (&rx_xsk);close_xsk (&tx_xsk); +close (rx_udp_fd);if (bpf_obj)xdp_metadata__destroy (bpf_obj);system ("ip netns del xdp_metadata" );
tools/testing/selftests/bpf/progs/xdp_metadata.c +28 -0
@@ -17,6 +17,7 @@ struct {__type (value, __u32); } xsk SEC(".maps"); +extern void bpf_xdp_metadata_export_to_skb(const struct xdp_md *ctx) __ksym; extern int bpf_xdp_metadata_rx_timestamp_supported(const struct xdp_md *ctx) __ksym; extern const __u64 bpf_xdp_metadata_rx_timestamp(const struct xdp_md *ctx) __ksym;
@@ -24,8 +25,35 @@ SEC("xdp")int rx (struct xdp_md *ctx) {void *data, *data_meta; +struct ethhdr *eth =NULL ; +struct udphdr *udp =NULL ; +struct iphdr *iph =NULL ; +void *data_end;int ret; +/* Exercise xdp -> skb metadata path by diverting some traffic +* into the kernel (UDP destination port 9081). +*/ + + data = (void *)(long )ctx->data; + data_end = (void *)(long )ctx->data_end; + eth = data; +if (eth +1 < data_end) { +if (eth->h_proto ==bpf_htons (ETH_P_IP )) { + iph = (void *)(eth +1 ); +if (iph +1 < data_end && iph->protocol ==IPPROTO_UDP ) + udp = (void *)(iph +1 ); + } +if (udp && udp +1 > data_end) + udp =NULL ; + } +if (udp && udp->dest ==bpf_htons (9081 )) { +bpf_xdp_metadata_export_to_skb (ctx); +bpf_printk ("exporting metadata to skb for UDP port 9081" ); +/*return bpf_redirect(ifindex, BPF_F_INGRESS);*/ +return XDP_PASS ; + } +if (bpf_xdp_metadata_rx_timestamp_supported (ctx)) {__u64 rx_timestamp =bpf_xdp_metadata_rx_timestamp (ctx);
Signature · 1 line
2.38.1.431.g37b22c650d-goog
RFC v2 8/14 bpf: Helper to simplify calling kernel routines from unrolled kfuncs
In reply to Stanislav FomichevWhen we need to call the kernel function from the unrolled kfunc, we have to take extra care: r6-r9 belong to the callee, not us, so we can't use these registers to stash our r1.
We use the same trick we use elsewhere: ask the user to provide extra on-stack storage.
Also, note, the program being called has to receive and return the context.
--- include/net/xdp.h | 4 ++++ net/core/xdp.c | 24 +++++++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletion(-)
include/net/xdp.h +4 -0
@@ -440,10 +440,14 @@ static inline u32 xdp_metadata_kfunc_id(int id)return xdp_metadata_kfunc_ids.pairs[id].id; }void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch); +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc);#else #define xdp_metadata_magic 0static inline u32 xdp_metadata_kfunc_id (int id) {return 0 ; }static void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {return 0 ; } +static void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) {}#endif #endif /* __LINUX_NET_XDP_H__ */
net/core/xdp.c +23 -1
@@ -737,6 +737,7 @@ BTF_SET8_START_GLOBAL(xdp_metadata_kfunc_ids) XDP_METADATA_KFUNC_xxx#undef XDP_METADATA_KFUNCBTF_SET8_END (xdp_metadata_kfunc_ids) +EXPORT_SYMBOL (xdp_metadata_kfunc_ids);/* Make sure userspace doesn't depend on our layout by using * different pseudo-generated magic value.
@@ -756,7 +757,8 @@ static const struct btf_kfunc_id_set xdp_metadata_kfunc_set = {* * The above also means we _cannot_ easily call any other helper/kfunc * because there is no place for us to preserve our R1 argument; -* existing R6-R9 belong to the callee. +* existing R6-R9 belong to the callee. For the cases where calling into +* the kernel is the only option, see xdp_kfunc_call_preserving_r1. */ void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {
@@ -832,6 +834,26 @@ void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *pbpf_patch_resolve_jmp (patch); } +EXPORT_SYMBOL (xdp_metadata_export_to_skb); + +/* Helper to generate the bytecode that calls the supplied kfunc. +* The kfunc has to accept a pointer to the context and return the +* same pointer back. The user also has to supply an offset within +* the context to store r0. +*/ +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) +{ +bpf_patch_append (patch, +/* r0 = kfunc(r1); */ +BPF_EMIT_CALL (kfunc), +/* r1 = r0; */ +BPF_MOV64_REG (BPF_REG_1 ,BPF_REG_0 ), +/* r0 = *(r1 + r0_offset); */ + BPF_LDX_MEM(BPF_DW, BPF_REG_0, BPF_REG_1, r0_offset), + ); +} +EXPORT_SYMBOL (xdp_kfunc_call_preserving_r1);static int __init xdp_metadata_init (void ) {
Signature · 1 line
2.38.1.431.g37b22c650d-goog
Re: [RFC bpf-next v2 08/14] bpf: Helper to simplify calling kernel routines from unrolled kfuncs
Quoted 83 lines · Stanislav Fomichev
When we need to call the kernel function from the unrolled kfunc, we have to take extra care: r6-r9 belong to the callee, not us, so we can't use these registers to stash our r1.
We use the same trick we use elsewhere: ask the user to provide extra on-stack storage.
Also, note, the program being called has to receive and return the context.
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- include/net/xdp.h | 4 ++++ net/core/xdp.c | 24 +++++++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletion(-)include/net/xdp.h +4
-0@@ -440,10 +440,14 @@ static inline u32 xdp_metadata_kfunc_id(int id)return xdp_metadata_kfunc_ids.pairs[id].id; }void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch); +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc);#else #define xdp_metadata_magic 0static inline u32 xdp_metadata_kfunc_id (int id) {return 0 ; }static void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {return 0 ; } +static void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) {}#endif #endif /* __LINUX_NET_XDP_H__ */ net/core/xdp.c +13
-1@@ -737,6 +737,7 @@ BTF_SET8_START_GLOBAL(xdp_metadata_kfunc_ids) XDP_METADATA_KFUNC_xxx#undef XDP_METADATA_KFUNCBTF_SET8_END (xdp_metadata_kfunc_ids) +EXPORT_SYMBOL (xdp_metadata_kfunc_ids);/* Make sure userspace doesn't depend on our layout by using * different pseudo-generated magic value. @@ -756,7 +757,8 @@ static const struct btf_kfunc_id_set xdp_metadata_kfunc_set = {* * The above also means we _cannot_ easily call any other helper/kfunc * because there is no place for us to preserve our R1 argument; -* existing R6-R9 belong to the callee. +* existing R6-R9 belong to the callee. For the cases where calling into +* the kernel is the only option, see xdp_kfunc_call_preserving_r1. */ void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {@@ -832,6 +834,26 @@ void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *pbpf_patch_resolve_jmp (patch); } +EXPORT_SYMBOL (xdp_metadata_export_to_skb); + +/* Helper to generate the bytecode that calls the supplied kfunc. +* The kfunc has to accept a pointer to the context and return the +* same pointer back. The user also has to supply an offset within +* the context to store r0. +*/ +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) +{
net/core/xdp.c void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *p · line 856
Quoted 10 lines
net/core/xdp.c +10
-0+bpf_patch_append (patch, +/* r0 = kfunc(r1); */ +BPF_EMIT_CALL (kfunc), +/* r1 = r0; */ +BPF_MOV64_REG (BPF_REG_1 ,BPF_REG_0 ), +/* r0 = *(r1 + r0_offset); */ + BPF_LDX_MEM(BPF_DW, BPF_REG_0, BPF_REG_1, r0_offset), + ); +} +EXPORT_SYMBOL (xdp_kfunc_call_preserving_r1);
That's one twisted logic :)
I guess it works for preserving r1, but r2-r5 are gone and r6-r9 cannot be touched. So it works for the most basic case of returning single value from that additional kfunc while preserving single r1.
I'm afraid that will be very limiting moving forward.
imo we need push/pop insns. It shouldn't difficult to add to the interpreter and JITs. Since this patching is done after verificaiton they will be kernel internal insns. Like we have BPF_REG_AX internal reg.
Re: [RFC bpf-next v2 08/14] bpf: Helper to simplify calling kernel routines from unrolled kfuncs
Quoted 96 lines · Alexei Starovoitov
Quoted 83 lines · Stanislav Fomichev
When we need to call the kernel function from the unrolled kfunc, we have to take extra care: r6-r9 belong to the callee, not us, so we can't use these registers to stash our r1.
We use the same trick we use elsewhere: ask the user to provide extra on-stack storage.
Also, note, the program being called has to receive and return the context.
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- include/net/xdp.h | 4 ++++ net/core/xdp.c | 24 +++++++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletion(-)include/net/xdp.h +4
-0@@ -440,10 +440,14 @@ static inline u32 xdp_metadata_kfunc_id(int id)return xdp_metadata_kfunc_ids.pairs[id].id; }void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch); +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc);#else #define xdp_metadata_magic 0static inline u32 xdp_metadata_kfunc_id (int id) {return 0 ; }static void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {return 0 ; } +static void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) {}#endif #endif /* __LINUX_NET_XDP_H__ */ net/core/xdp.c +13
-1@@ -737,6 +737,7 @@ BTF_SET8_START_GLOBAL(xdp_metadata_kfunc_ids) XDP_METADATA_KFUNC_xxx#undef XDP_METADATA_KFUNCBTF_SET8_END (xdp_metadata_kfunc_ids) +EXPORT_SYMBOL (xdp_metadata_kfunc_ids);/* Make sure userspace doesn't depend on our layout by using * different pseudo-generated magic value. @@ -756,7 +757,8 @@ static const struct btf_kfunc_id_set xdp_metadata_kfunc_set = {* * The above also means we _cannot_ easily call any other helper/kfunc * because there is no place for us to preserve our R1 argument; -* existing R6-R9 belong to the callee. +* existing R6-R9 belong to the callee. For the cases where calling into +* the kernel is the only option, see xdp_kfunc_call_preserving_r1. */ void xdp_metadata_export_to_skb (const struct bpf_prog *prog,struct bpf_patch *patch) {@@ -832,6 +834,26 @@ void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *pbpf_patch_resolve_jmp (patch); } +EXPORT_SYMBOL (xdp_metadata_export_to_skb); + +/* Helper to generate the bytecode that calls the supplied kfunc. +* The kfunc has to accept a pointer to the context and return the +* same pointer back. The user also has to supply an offset within +* the context to store r0. +*/ +void xdp_kfunc_call_preserving_r1 (struct bpf_patch *patch,size_t r0_offset, +void *kfunc) +{net/core/xdp.c void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *p · line 856
Quoted 10 lines
net/core/xdp.c +10
-0+bpf_patch_append (patch, +/* r0 = kfunc(r1); */ +BPF_EMIT_CALL (kfunc), +/* r1 = r0; */ +BPF_MOV64_REG (BPF_REG_1 ,BPF_REG_0 ), +/* r0 = *(r1 + r0_offset); */ + BPF_LDX_MEM(BPF_DW, BPF_REG_0, BPF_REG_1, r0_offset), + ); +} +EXPORT_SYMBOL (xdp_kfunc_call_preserving_r1);
Quoted 8 lines
That's one twisted logic :)
I guess it works for preserving r1, but r2-r5 are gone and r6-r9 cannot be touched. So it works for the most basic case of returning single value from that additional kfunc while preserving single r1.
I'm afraid that will be very limiting moving forward.
imo we need push/pop insns. It shouldn't difficult to add to the interpreter and JITs. Since this patching is done after verificaiton they will be kernel internal insns. Like we haveBPF_REG_AXinternal reg.
Heh, having push/pop would help a lot, agree :-)
Good suggestion, will look into that, thank you!
RFC v2 9/14 ice: Introduce ice_xdp_buff wrapper for xdp_buff
In reply to Stanislav FomichevNo functional changes. Boilerplate to allow stuffing more data after xdp_buff.
--- drivers/net/ethernet/intel/ice/ice_txrx.c | 30 +++++++++++++---------- 1 file changed, 17 insertions(+), 13 deletions(-)
drivers/net/ethernet/intel/ice/ice_txrx.c +17 -13
@@ -1096,6 +1096,10 @@ ice_is_non_eop(struct ice_rx_ring *rx_ring, union ice_32b_rx_flex_desc *rx_desc)return true; } +struct ice_xdp_buff { +struct xdp_buff xdp; +}; +/** * ice_clean_rx_irq - Clean completed descriptors from Rx ring - bounce buf * @rx_ring: Rx descriptor ring to transact packets on
@@ -1117,14 +1121,14 @@ int ice_clean_rx_irq(struct ice_rx_ring *rx_ring, int budget)unsigned int xdp_res, xdp_xmit =0 ;struct sk_buff *skb = rx_ring->skb;struct bpf_prog *xdp_prog =NULL ; -struct xdp_buff xdp; +struct ice_xdp_buff ixbuf;bool failure;/* Frame size depend on rx_ring setup when PAGE_SIZE=4K */ #if (PAGE_SIZE <8192 ) frame_sz =ice_rx_frame_truesize (rx_ring,0 );#endif -xdp_init_buff (&xdp, frame_sz, &rx_ring->xdp_rxq); +xdp_init_buff (&ixbuf.xdp, frame_sz, &rx_ring->xdp_rxq); xdp_prog =READ_ONCE (rx_ring->xdp_prog);if (xdp_prog)
@@ -1178,30 +1182,30 @@ int ice_clean_rx_irq(struct ice_rx_ring *rx_ring, int budget) rx_buf =ice_get_rx_buf (rx_ring, size, &rx_buf_pgcnt);if (!size) { - xdp.data =NULL ; - xdp.data_end =NULL ; - xdp.data_hard_start =NULL ; - xdp.data_meta =NULL ; + ixbuf.xdp.data =NULL ; + ixbuf.xdp.data_end =NULL ; + ixbuf.xdp.data_hard_start =NULL ; + ixbuf.xdp.data_meta =NULL ; goto construct_skb; } hard_start =page_address (rx_buf->page) + rx_buf->page_offset - offset; -xdp_prepare_buff (&xdp, hard_start, offset, size, true); +xdp_prepare_buff (&ixbuf.xdp, hard_start, offset, size, true);#if (PAGE_SIZE >4096 )/* At larger PAGE_SIZE, frame_sz depend on len size */ - xdp.frame_sz =ice_rx_frame_truesize (rx_ring, size); + ixbuf.xdp.frame_sz =ice_rx_frame_truesize (rx_ring, size);#endif if (!xdp_prog) goto construct_skb; - xdp_res =ice_run_xdp (rx_ring, &xdp, xdp_prog, xdp_ring); + xdp_res =ice_run_xdp (rx_ring, &ixbuf.xdp, xdp_prog, xdp_ring);if (!xdp_res) goto construct_skb;if (xdp_res & (ICE_XDP_TX |ICE_XDP_REDIR )) { xdp_xmit |= xdp_res; -ice_rx_buf_adjust_pg_offset (rx_buf, xdp.frame_sz); +ice_rx_buf_adjust_pg_offset (rx_buf, ixbuf.xdp.frame_sz); }else { rx_buf->pagecnt_bias++; }
@@ -1214,11 +1218,11 @@ int ice_clean_rx_irq(struct ice_rx_ring *rx_ring, int budget) construct_skb:if (skb) {ice_add_rx_frag (rx_ring, rx_buf, skb, size); - }else if (likely (xdp.data)) { + }else if (likely (ixbuf.xdp.data)) {if (ice_ring_uses_build_skb (rx_ring)) - skb =ice_build_skb (rx_ring, rx_buf, &xdp); + skb =ice_build_skb (rx_ring, rx_buf, &ixbuf.xdp);else - skb =ice_construct_skb (rx_ring, rx_buf, &xdp); + skb =ice_construct_skb (rx_ring, rx_buf, &ixbuf.xdp); }/* exit if we failed to retrieve a buffer */ if (!skb) {
Signature · 1 line
2.38.1.431.g37b22c650d-goog
RFC v2 10/14 ice: Support rx timestamp metadata for xdp
In reply to Stanislav FomichevCOMPILE-TESTED ONLY!
--- drivers/net/ethernet/intel/ice/ice.h | 5 ++ drivers/net/ethernet/intel/ice/ice_main.c | 1 + drivers/net/ethernet/intel/ice/ice_txrx.c | 75 +++++++++++++++++++++++ 3 files changed, 81 insertions(+)
drivers/net/ethernet/intel/ice/ice.h +5 -0
@@ -925,6 +925,11 @@ int ice_open_internal(struct net_device *netdev);int ice_stop (struct net_device *netdev);void ice_service_task_schedule (struct ice_pf *pf); +struct bpf_insn ; +struct bpf_patch ; +void ice_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch); +/** * ice_set_rdma_cap - enable RDMA support * @pf: PF struct
drivers/net/ethernet/intel/ice/ice_main.c +1 -0
@@ -9109,4 +9109,5 @@ static const struct net_device_ops ice_netdev_ops = { .ndo_xdp_xmit = ice_xdp_xmit, .ndo_xsk_wakeup = ice_xsk_wakeup, .ndo_get_devlink_port = ice_get_devlink_port, + .ndo_unroll_kfunc = ice_unroll_kfunc, };
drivers/net/ethernet/intel/ice/ice_txrx.c +75 -0
95 lines not on this page · raw message
Signature · 1 line
2.38.1.431.g37b22c650d-goog
Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
From: Stanislav Fomichev <[email protected]>
Date: Thu,3 Nov 2022 20:25:28 -0700
Quoted 62 lines
COMPILE-TESTED ONLY!
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- drivers/net/ethernet/intel/ice/ice.h | 5 ++ drivers/net/ethernet/intel/ice/ice_main.c | 1 + drivers/net/ethernet/intel/ice/ice_txrx.c | 75 +++++++++++++++++++++++ 3 files changed, 81 insertions(+)drivers/net/ethernet/intel/ice/ice.h +5
-0@@ -925,6 +925,11 @@ int ice_open_internal(struct net_device *netdev);int ice_stop (struct net_device *netdev);void ice_service_task_schedule (struct ice_pf *pf); +struct bpf_insn ; +struct bpf_patch ; +void ice_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch); +/** * ice_set_rdma_cap - enable RDMA support * @pf: PF struct drivers/net/ethernet/intel/ice/ice_main.c +1
-0@@ -9109,4 +9109,5 @@ static const struct net_device_ops ice_netdev_ops = { .ndo_xdp_xmit = ice_xdp_xmit, .ndo_xsk_wakeup = ice_xsk_wakeup, .ndo_get_devlink_port = ice_get_devlink_port, + .ndo_unroll_kfunc = ice_unroll_kfunc, };drivers/net/ethernet/intel/ice/ice_txrx.c +1
-0@@ -7,6 +7,7 @@#include <linux/netdevice.h> #include <linux/prefetch.h> #include <linux/bpf_trace.h> +#include <linux/bpf_patch.h> #include <net/dsfield.h> #include <net/mpls.h> #include <net/xdp.h> @@ -1098,8 +1099,80 @@ ice_is_non_eop(struct ice_rx_ring *rx_ring, union ice_32b_rx_flex_desc *rx_desc)struct ice_xdp_buff {
drivers/net/ethernet/intel/ice/ice_txrx.c ice_is_non_eop(struct ice_rx_ring *rx_ring, union ice_32b_rx_flex_desc *rx_desc) · line 1110
Quoted 10 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +7
-0struct xdp_buff xdp; +struct ice_rx_ring *rx_ring; +union ice_32b_rx_flex_desc *rx_desc; }; +void ice_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch) +{ +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch);
Hey,
FYI, our team wants to write a follow-up patch with ice support added, not like a draft, more of a mature code. I'm thinking of calling ice C function which would process Rx descriptors from that BPF code from the unrolling callback -- otherwise, implementing a couple hundred C code lines from ice_txrx_lib.c would be a bit too much :D
Quoted 4 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +4
-0+ }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {
[...]
Quoted 2 lines
Signature · 1 line
2.38.1.431.g37b22c650d-goog
Thanks,
Olek
Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
Quoted 79 lines · Alexander Lobakin
From: Stanislav Fomichev <[email protected]>
Date: Thu,3 Nov 2022 20:25:28 -0700Quoted 62 lines
COMPILE-TESTED ONLY!
Cc John Fastabend <[email protected]>Cc David Ahern <[email protected]>Cc Martin KaFai Lau <[email protected]>Cc Jakub Kicinski <[email protected]>Cc Willem de Bruijn <[email protected]>Cc Jesper Dangaard Brouer <[email protected]>Cc Anatoly Burakov <[email protected]>Cc Alexander Lobakin <[email protected]>Cc Magnus Karlsson <[email protected]>Cc Maryam Tahhan <[email protected]>Signed-off-by Stanislav Fomichev <[email protected]>--- drivers/net/ethernet/intel/ice/ice.h | 5 ++ drivers/net/ethernet/intel/ice/ice_main.c | 1 + drivers/net/ethernet/intel/ice/ice_txrx.c | 75 +++++++++++++++++++++++ 3 files changed, 81 insertions(+)drivers/net/ethernet/intel/ice/ice.h +5
-0@@ -925,6 +925,11 @@ int ice_open_internal(struct net_device *netdev);int ice_stop (struct net_device *netdev);void ice_service_task_schedule (struct ice_pf *pf); +struct bpf_insn ; +struct bpf_patch ; +void ice_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch); +/** * ice_set_rdma_cap - enable RDMA support * @pf: PF struct drivers/net/ethernet/intel/ice/ice_main.c +1
-0@@ -9109,4 +9109,5 @@ static const struct net_device_ops ice_netdev_ops = { .ndo_xdp_xmit = ice_xdp_xmit, .ndo_xsk_wakeup = ice_xsk_wakeup, .ndo_get_devlink_port = ice_get_devlink_port, + .ndo_unroll_kfunc = ice_unroll_kfunc, };drivers/net/ethernet/intel/ice/ice_txrx.c +1
-0@@ -7,6 +7,7 @@#include <linux/netdevice.h> #include <linux/prefetch.h> #include <linux/bpf_trace.h> +#include <linux/bpf_patch.h> #include <net/dsfield.h> #include <net/mpls.h> #include <net/xdp.h> @@ -1098,8 +1099,80 @@ ice_is_non_eop(struct ice_rx_ring *rx_ring, union ice_32b_rx_flex_desc *rx_desc)struct ice_xdp_buff {drivers/net/ethernet/intel/ice/ice_txrx.c ice_is_non_eop(struct ice_rx_ring *rx_ring, union ice_32b_rx_flex_desc *rx_desc) · line 1110
Quoted 10 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +7
-0struct xdp_buff xdp; +struct ice_rx_ring *rx_ring; +union ice_32b_rx_flex_desc *rx_desc; }; +void ice_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch) +{ +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch);Hey,
Quoted 6 lines
FYI, our team wants to write a follow-up patch with ice support added, not like a draft, more of a mature code. I'm thinking of calling ice C function which would process Rx descriptors from that BPF code from the unrolling callback -- otherwise, implementing a couple hundred C code lines from
ice_txrx_lib.cwould be a bit too much :D
Sounds good! I would gladly drop all/most of the driver changes for the non-rfc posting :-)
I'll probably have a mlx4 one because there is a chance I might find HW, but the rest I'll drop most likely.
(they are here to show how the driver changes might look like, hence compile-tested only)
Btw, does it make sense to have some small xsk selftest binary that can be used to test the metadata with the real device? The one I'm having right now depends on veth/namespaces; having a similar one for the real hardware to qualify it sounds useful? Something simple that sets up af_xdp for all queues, divers some traffic, and exposes to the userspace consumer all the info about frame metadata...
Or maybe there is something I can reuse already?
Quoted 12 lines
Quoted 4 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +4
-0+ }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {[...]
Quoted 2 lines
--
2.38.1.431.g37b22c650d-googThanks,
Olek
Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
From: Stanislav Fomichev <[email protected]>
Date: Fri, 4 Nov 2022 11:21:47 -0700
Quoted 5 lines
Quoted 3 lines · Alexander Lobakin
From: Stanislav Fomichev <[email protected]>
Date: Thu,3 Nov 2022 20:25:28 -0700
[...]
Quoted 16 lines
Quoted 8 lines
Hey,
FYI, our team wants to write a follow-up patch with ice support added, not like a draft, more of a mature code. I'm thinking of calling ice C function which would process Rx descriptors from that BPF code from the unrolling callback -- otherwise, implementing a couple hundred C code lines from
ice_txrx_lib.cwould be a bit too much :DSounds good! I would gladly drop all/most of the driver changes for the non-rfc posting :-)
I'll probably have a mlx4 one because there is a chance I might find HW, but the rest I'll drop most likely.
(they are here to show how the driver changes might look like, hence compile-tested only)
Quoted 8 lines
Btw, does it make sense to have some small xsk selftest binary that can be used to test the metadata with the real device? The one I'm having right now depends on veth/namespaces; having a similar one for the real hardware to qualify it sounds useful? Something simple that sets up
af_xdpfor all queues, divers some traffic, and exposes to the userspace consumer all the info about frame metadata...
Or maybe there is something I can reuse already?
There's XSk selftest already and recently Maciej added support for executing it on a physical device (via -i <iface> cmdline arg)[0]. I guess the most optimal solution is to expand it to cover metadata cases as it has some sort of useful helper functions / infra? In the set I posted in June, I simply expanded xdp_meta selftest, but there weren't any XSk bits, so I don't think it's a way to go.
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +4
-0+ }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {
Quoted 7 lines
Quoted 7 lines
[...]
Quoted 2 lines
--
2.38.1.431.g37b22c650d-googThanks,
Olek
Thank,
Olek
Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
Quoted 37 lines · Alexander Lobakin
From: Stanislav Fomichev <[email protected]>
Date: Fri, 4 Nov 2022 11:21:47 -0700Quoted 5 lines
Quoted 3 lines · Alexander Lobakin
From: Stanislav Fomichev <[email protected]>
Date: Thu,3 Nov 2022 20:25:28 -0700[...]
Quoted 16 lines
Quoted 8 lines
Hey,
FYI, our team wants to write a follow-up patch with ice support added, not like a draft, more of a mature code. I'm thinking of calling ice C function which would process Rx descriptors from that BPF code from the unrolling callback -- otherwise, implementing a couple hundred C code lines from
ice_txrx_lib.cwould be a bit too much :DSounds good! I would gladly drop all/most of the driver changes for the non-rfc posting :-)
I'll probably have a mlx4 one because there is a chance I might find HW, but the rest I'll drop most likely.
(they are here to show how the driver changes might look like, hence compile-tested only)Quoted 8 lines
Btw, does it make sense to have some small xsk selftest binary that can be used to test the metadata with the real device? The one I'm having right now depends on veth/namespaces; having a similar one for the real hardware to qualify it sounds useful? Something simple that sets up
af_xdpfor all queues, divers some traffic, and exposes to the userspace consumer all the info about frame metadata...
Or maybe there is something I can reuse already?
Quoted 6 lines
There's XSk selftest already and recently Maciej added support for executing it on a physical device (via
-i <iface>cmdline arg)[0]. I guess the most optimal solution is to expand it to cover metadata cases as it has some sort of useful helper functions / infra? In the set I posted in June, I simply expandedxdp_metaselftest, but there weren't any XSk bits, so I don't think it's a way to go.
Yeah, I was also extending xskxceiver initially, but not sure we want to put metadata in there (that test is already too big imo)? Jesper also pointed out [0], so maybe that thing should live out-of-tree?
I got mlx4 working locally with a small xskxceiver-like selftest. I'll probably include it in the next non-rfc submission and we can discuss whether it makes sense to keep it or it's better to extend xskxceiver.
0: https://github.com/xdp-project/bpf-examples/tree/master/AF_XDP-interaction
Quoted 19 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
drivers/net/ethernet/intel/ice/ice_txrx.c +4
-0+ }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) {Quoted 7 lines
Quoted 7 lines
[...]
Quoted 2 lines
--
2.38.1.431.g37b22c650d-googThanks,
OlekThank,
Olek
Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
In reply to Stanislav FomichevReview
Quoted 2 lines · Stanislav Fomichev
(quoted diff) +2
-0+ /* if (r5 == NULL) return; */ + BPF_JMP_IMM(BPF_JNE, BPF_REG_5, 0, S16_MAX),
S16_MAX jump crashes my system and I do not see such jumps used very often in bpf code found in-tree, setting a fixed jump length worked for me. Also, I think BPF_JEQ is a correct condition in this case, not BPF_JNE.
But the main reason for my reply is that I have implemented RX hash hint for ice both as unrolled bpf code and with BPF_EMIT_CALL [0]. Both bpf_xdp_metadata_rx_hash() and bpf_xdp_metadata_rx_hash_supported() are implemented in those 2 ways.
RX hash is the easiest hint to read, so performance difference should be more visible than when reading timestapm.
Counting packets in an rxdrop XDP program on a single queue gave me the following numbers:
- unrolled: 41264360 pps
- BPF_EMIT_CALL: 40370651 pps
So, reading a single hint in an unrolled way instead of calling 2 driver functions in a row, gives us a 2.2% performance boost. Surely, the difference will increase, if we read more than a single hint. Therefore, it would be great to implement at least some simple hints functions as unrolled.
[0] https://github.com/walking-machine/linux/tree/ice-kfunc-hints-clean
Re: [xdp-hints] Re: [RFC bpf-next v2 10/14] ice: Support rx timestamp metadata for xdp
Quoted 22 lines · Larysa Zaremba
Review
Quoted 2 lines · Stanislav Fomichev
(quoted diff) +2
-0+ /* if (r5 == NULL) return; */ + BPF_JMP_IMM(BPF_JNE, BPF_REG_5, 0, S16_MAX),
S16_MAXjump crashes my system and I do not see such jumps used very often in bpf code found in-tree, setting a fixed jump length worked for me. Also, I thinkBPF_JEQis a correct condition in this case, notBPF_JNE.But the main reason for my reply is that I have implemented RX hash hint for ice both as unrolled bpf code and with
BPF_EMIT_CALL[0]. Bothbpf_xdp_metadata_rx_hash()andbpf_xdp_metadata_rx_hash_supported()are implemented in those 2 ways.RX hash is the easiest hint to read, so performance difference should be more visible than when reading timestapm.
Counting packets in an rxdrop XDP program on a single queue gave me the following numbers:
- unrolled: 41264360 pps
-BPF_EMIT_CALL: 40370651 pps
Quoted 7 lines
So, reading a single hint in an unrolled way instead of calling 2 driver functions in a row, gives us a 2.2% performance boost. Surely, the difference will increase, if we read more than a single hint. Therefore, it would be great to implement at least some simple hints functions as unrolled.
[0] https://github.com/walking-machine/linux/tree/ice-kfunc-hints-clean
Right, so this corresponds to ~0.5ns function call overhead, which is a bit less than what I was seeing[0], but you're also getting 41 Mpps where I was getting 25, so I assume your hardware is newer :)
And yeah, I agree that ideally we really should inline these functions. However, seeing as that may be a ways off[1], I suppose we'll have to live with the function call overhead for now. As long as we're reasonably confident that inlining can be added later without disruptive API breaks I am OK with proceeding without inlining for now, though. That way, inlining will just be a nice performance optimisation once it does land, and who knows, maybe this will provide the impetus for someone to land it sooner rather than later...
-Toke
[0] https://lore.kernel.org/r/[email protected]
[1] https://lore.kernel.org/r/CAADnVQ+MyE280Q-7iw2Y-P6qGs4xcDML-tUrXEv_EQTmeESVaQ@mail.gmail.com
RFC v2 11/14 mlx4: Introduce mlx4_xdp_buff wrapper for xdp_buff
In reply to Stanislav FomichevNo functional changes. Boilerplate to allow stuffing more data after xdp_buff.
--- drivers/net/ethernet/mellanox/mlx4/en_rx.c | 26 +++++++++++++--------- 1 file changed, 15 insertions(+), 11 deletions(-)
drivers/net/ethernet/mellanox/mlx4/en_rx.c +15 -11
@@ -661,17 +661,21 @@ static int check_csum(struct mlx4_cqe *cqe, struct sk_buff *skb, void *va,#define MLX4_CQE_STATUS_IP_ANY (MLX4_CQE_STATUS_IPV4)#endif +struct mlx4_xdp_buff { +struct xdp_buff xdp; +}; +int mlx4_en_process_rx_cq (struct net_device *dev,struct mlx4_en_cq *cq,int budget) {struct mlx4_en_priv *priv =netdev_priv (dev);int factor = priv->cqe_factor;struct mlx4_en_rx_ring *ring; +struct mlx4_xdp_buff mxbuf;struct bpf_prog *xdp_prog;int cq_ring = cq->ring;bool doorbell_pending;bool xdp_redir_flush;struct mlx4_cqe *cqe; -struct xdp_buff xdp;int polled =0 ;int index;
@@ -681,7 +685,7 @@ int mlx4_en_process_rx_cq(struct net_device *dev, struct mlx4_en_cq *cq, int bud ring = priv->rx_ring[cq_ring]; xdp_prog =rcu_dereference_bh (ring->xdp_prog); -xdp_init_buff (&xdp, priv->frag_info[0 ].frag_stride, &ring->xdp_rxq); +xdp_init_buff (&mxbuf.xdp, priv->frag_info[0 ].frag_stride, &ring->xdp_rxq); doorbell_pending = false; xdp_redir_flush = false;
@@ -776,24 +780,24 @@ int mlx4_en_process_rx_cq(struct net_device *dev, struct mlx4_en_cq *cq, int bud priv->frag_info[0 ].frag_size, DMA_FROM_DEVICE); -xdp_prepare_buff (&xdp, va - frags[0 ].page_offset, +xdp_prepare_buff (&mxbuf.xdp, va - frags[0 ].page_offset, frags[0 ].page_offset, length, false); - orig_data = xdp.data; + orig_data = mxbuf.xdp.data; - act =bpf_prog_run_xdp (xdp_prog, &xdp); + act =bpf_prog_run_xdp (xdp_prog, &mxbuf.xdp); - length = xdp.data_end - xdp.data; -if (xdp.data != orig_data) { - frags[0 ].page_offset = xdp.data - - xdp.data_hard_start; - va = xdp.data; + length = mxbuf.xdp.data_end - mxbuf.xdp.data; +if (mxbuf.xdp.data != orig_data) { + frags[0 ].page_offset = mxbuf.xdp.data - + mxbuf.xdp.data_hard_start; + va = mxbuf.xdp.data; }switch (act) {case XDP_PASS :break ;case XDP_REDIRECT : -if (likely (!xdp_do_redirect (dev, &xdp, xdp_prog))) { +if (likely (!xdp_do_redirect (dev, &mxbuf.xdp, xdp_prog))) { ring->xdp_redirect++; xdp_redir_flush = true; frags[0 ].page =NULL ;
Signature · 1 line
2.38.1.431.g37b22c650d-goog
RFC v2 12/14 mxl4: Support rx timestamp metadata for xdp
In reply to Stanislav FomichevCOMPILE-TESTED ONLY!
--- .../net/ethernet/mellanox/mlx4/en_netdev.c | 1 + drivers/net/ethernet/mellanox/mlx4/en_rx.c | 40 +++++++++++++++++++ include/linux/mlx4/device.h | 7 ++++ 3 files changed, 48 insertions(+)
drivers/net/ethernet/mellanox/mlx4/en_netdev.c +1 -0
@@ -2890,6 +2890,7 @@ static const struct net_device_ops mlx4_netdev_ops_master = { .ndo_features_check = mlx4_en_features_check, .ndo_set_tx_maxrate = mlx4_en_set_tx_maxrate, .ndo_bpf = mlx4_xdp, + .ndo_unroll_kfunc = mlx4_unroll_kfunc, };struct mlx4_en_bond {
drivers/net/ethernet/mellanox/mlx4/en_rx.c +40 -0
@@ -33,6 +33,7 @@#include <linux/bpf.h> #include <linux/bpf_trace.h> +#include <linux/bpf_patch.h> #include <linux/mlx4/cq.h> #include <linux/slab.h> #include <linux/mlx4/qp.h>
@@ -663,8 +664,43 @@ static int check_csum(struct mlx4_cqe *cqe, struct sk_buff *skb, void *va,struct mlx4_xdp_buff {struct xdp_buff xdp; +struct mlx4_cqe *cqe; +struct mlx4_en_dev *mdev; +u64 r0; }; +struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp (struct mlx4_xdp_buff *ctx) +{ +unsigned int seq; +u64 timestamp; +u64 nsec; + + timestamp =mlx4_en_get_cqe_ts (ctx->cqe); + +do { + seq =read_seqbegin (&ctx->mdev->clock_lock); + nsec =timecounter_cyc2time (&ctx->mdev->clock, timestamp); + }while (read_seqretry (&ctx->mdev->clock_lock, seq)); + + ctx->r0 = (u64 )ns_to_ktime (nsec); +return ctx; +} + +void mlx4_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch) +{ +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) { +xdp_kfunc_call_preserving_r1 (patch, + offsetof(struct mlx4_xdp_buff , r0), + mxl4_xdp_rx_timestamp); + } +} +int mlx4_en_process_rx_cq (struct net_device *dev,struct mlx4_en_cq *cq,int budget) {struct mlx4_en_priv *priv =netdev_priv (dev);
@@ -783,6 +819,10 @@ int mlx4_en_process_rx_cq(struct net_device *dev, struct mlx4_en_cq *cq, int budxdp_prepare_buff (&mxbuf.xdp, va - frags[0 ].page_offset, frags[0 ].page_offset, length, false); orig_data = mxbuf.xdp.data; +if (unlikely (ring->hwtstamp_rx_filter ==HWTSTAMP_FILTER_ALL )) { + mxbuf.cqe = cqe; + mxbuf.mdev = priv->mdev; + } act =bpf_prog_run_xdp (xdp_prog, &mxbuf.xdp);
include/linux/mlx4/device.h +7 -0
@@ -1585,4 +1585,11 @@ static inline int mlx4_get_num_reserved_uar(struct mlx4_dev *dev)/* The first 128 UARs are used for EQ doorbells */ return (128 >> (PAGE_SHIFT - dev->uar_page_shift)); } + +struct bpf_prog ; +struct bpf_insn ; +struct bpf_patch ; + +void mlx4_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch);#endif /* MLX4_DEVICE_H */
Signature · 1 line
2.38.1.431.g37b22c650d-goog
kernel test robot
build botRe: [RFC bpf-next v2 12/14] mxl4: Support rx timestamp metadata for xdp
reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross #…
Hi Stanislav,
[FYI, it's a private test report for your RFC patch.] [auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Stanislav-Fomichev/xdp-hints-via-kfuncs/20221104-113042 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master patch link: https://lore.kernel.org/r/20221104032532.1615099-13-sdf%40google.com patch subject: [RFC bpf-next v2 12/14] mxl4: Support rx timestamp metadata for xdp config: ia64-allyesconfig compiler: ia64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/bb15bd4e2e87117f30c60bbbad15805164454808
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Stanislav-Fomichev/xdp-hints-via-kfuncs/20221104-113042
git checkout bb15bd4e2e87117f30c60bbbad15805164454808
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/net/ethernet/broadcom/bnxt/ drivers/net/ethernet/mellanox/mlx4/
If you fix the issue, kindly add following tag where applicable | Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
In file included from include/linux/netdevice.h:43,
from include/trace/events/xdp.h:8,
from include/linux/bpf_trace.h:5,
from drivers/net/ethernet/mellanox/mlx4/en_rx.c:35:
include/net/xdp.h: In function 'xdp_metadata_export_to_skb':
include/net/xdp.h:448:103: error: 'return' with a value, in function returning void [-Werror=return-type]
448 | static void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *patch) { return 0; }
| ^
include/net/xdp.h:448:13: note: declared here
448 | static void xdp_metadata_export_to_skb(const struct bpf_prog *prog, struct bpf_patch *patch) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx4/en_rx.c: At top level:
>> drivers/net/ethernet/mellanox/mlx4/en_rx.c:672:23: warning: no previous prototype for 'mxl4_xdp_rx_timestamp' [-Wmissing-prototypes] 672 | struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp(struct mlx4_xdp_buff *ctx)
| ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/mxl4_xdp_rx_timestamp +672 drivers/net/ethernet/mellanox/mlx4/en_rx.c
671
> 672 struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp(struct mlx4_xdp_buff *ctx)
673 {
674 unsigned int seq;
675 u64 timestamp;
676 u64 nsec;
677
678 timestamp = mlx4_en_get_cqe_ts(ctx->cqe);
679
680 do {
681 seq = read_seqbegin(&ctx->mdev->clock_lock);
682 nsec = timecounter_cyc2time(&ctx->mdev->clock, timestamp);
683 } while (read_seqretry(&ctx->mdev->clock_lock, seq));
684
685 ctx->r0 = (u64)ns_to_ktime(nsec);
686 return ctx;
687 }
688
Signature · 2 lines
0-DAY CI Kernel Test Service https://01.org/lkp
#
# Automatically generated file; DO NOT EDIT. # Linux/ia64 6.1.0-rc3 Kernel Configuration #CONFIG_CC_VERSION_TEXT="ia64-linux-gcc (GCC) 12.1.0" CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=120100 CONFIG_CLANG_VERSION=0CONFIG_AS_IS_GNU=yCONFIG_AS_VERSION=23800CONFIG_LD_IS_BFD=yCONFIG_LD_VERSION=23800CONFIG_LLD_VERSION=0 CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y CONFIG_PAHOLE_VERSION=123 CONFIG_CONSTRUCTORS=yCONFIG_IRQ_WORK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_COMPILE_TEST=y
# CONFIG_WERROR is not setCONFIG_LOCALVERSION=""CONFIG_BUILD_SALT=""CONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_WATCH_QUEUE=yCONFIG_CROSS_MEMORY_ATTACH=yCONFIG_USELIB=yCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_LEGACY=yCONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_PENDING_IRQ=yCONFIG_GENERIC_IRQ_INJECTION=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_IRQ_FASTEOI_HIERARCHY_HANDLERS=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_IRQ_MSI_IOMMU=yCONFIG_GENERIC_IRQ_DEBUGFS=y
# end of IRQ subsystem
CONFIG_ARCH_CLOCKSOURCE_DATA=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_LEGACY_TIMER_TICK=yCONFIG_TIME_KUNIT_TEST=yCONFIG_CONTEXT_TRACKING=yCONFIG_CONTEXT_TRACKING_IDLE=yCONFIG_BPF=y
#
# BPF subsystem
#CONFIG_BPF_SYSCALL=yCONFIG_BPF_UNPRIV_DEFAULT_OFF=yCONFIG_USERMODE_DRIVER=y
# end of BPF subsystem
CONFIG_PREEMPT_NONE_BUILD=yCONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not setCONFIG_PREEMPT_COUNT=yCONFIG_SCHED_CORE=y
#
# CPU/Task time and stats accounting
#CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is not setCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=yCONFIG_PSI=yCONFIG_PSI_DEFAULT_DISABLED=y
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=yCONFIG_RCU_EXPERT=yCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_FORCE_TASKS_RCU=yCONFIG_TASKS_RCU=yCONFIG_FORCE_TASKS_RUDE_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_FORCE_TASKS_TRACE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16CONFIG_RCU_NOCB_CPU=yCONFIG_RCU_NOCB_CPU_DEFAULT_ALL=yCONFIG_TASKS_TRACE_RCU_READ_MB=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_IKHEADERS=yCONFIG_LOG_BUF_SHIFT=17CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_PRINTK_INDEX=yCONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#
# Scheduler features
#CONFIG_UCLAMP_TASK=yCONFIG_UCLAMP_BUCKETS_COUNT=5
# end of Scheduler features
CONFIG_CC_HAS_INT128=y CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5" CONFIG_GCC12_NO_ARRAY_BOUNDS=y CONFIG_CC_NO_ARRAY_BOUNDS=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=y CONFIG_CGROUP_FAVOR_DYNMODS=yCONFIG_MEMCG=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=yCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=y CONFIG_UCLAMP_TASK_GROUP=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_BPF=yCONFIG_CGROUP_MISC=yCONFIG_CGROUP_DEBUG=yCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_CHECKPOINT_RESTORE=y CONFIG_SCHED_AUTOGROUP=y CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_RD_ZSTD=yCONFIG_BOOT_CONFIG=yCONFIG_BOOT_CONFIG_EMBED=y CONFIG_BOOT_CONFIG_EMBED_FILE="" CONFIG_INITRAMFS_PRESERVE_MTIME=y CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_SYSCTL_ARCH_UNALIGN_NO_WARN=y CONFIG_EXPERT=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=yCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=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_KCMP=yCONFIG_EMBEDDED=yCONFIG_PC104=y
#
# Kernel Performance Events And Counters
#
# end of Kernel Performance Events And Counters
CONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=y
# end of General setup
CONFIG_PGTABLE_LEVELS=3
#
# Processor type and features
#CONFIG_IA64=yCONFIG_64BIT=yCONFIG_MMU=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_DMI=yCONFIG_EFI=yCONFIG_SCHED_OMIT_FRAME_POINTER=yCONFIG_IA64_UNCACHED_ALLOCATOR=yCONFIG_ARCH_USES_PG_UNCACHED=yCONFIG_AUDIT_ARCH=yCONFIG_ITANIUM=y
# CONFIG_MCKINLEY is not set
# CONFIG_IA64_PAGE_SIZE_4KB is not set
# CONFIG_IA64_PAGE_SIZE_8KB is not setCONFIG_IA64_PAGE_SIZE_16KB=y
# CONFIG_HZ_100 is not setCONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=250CONFIG_IA64_BRL_EMU=yCONFIG_IA64_L1_CACHE_SHIFT=6CONFIG_IA64_SGI_UV=yCONFIG_IA64_HP_SBA_IOMMU=yCONFIG_IA64_CYCLONE=yCONFIG_ARCH_FORCE_MAX_ORDER=17CONFIG_SMP=yCONFIG_NR_CPUS=4096CONFIG_HOTPLUG_CPU=yCONFIG_SCHED_SMT=yCONFIG_PERMIT_BSP_REMOVE=yCONFIG_FORCE_CPEI_RETARGET=yCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_ARCH_FLATMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_DEFAULT=yCONFIG_NUMA=yCONFIG_NODES_SHIFT=10CONFIG_HAVE_ARCH_NODEDATA_EXTENSION=yCONFIG_HAVE_MEMORYLESS_NODES=yCONFIG_ARCH_PROC_KCORE_TEXT=yCONFIG_IA64_MCA_RECOVERY=yCONFIG_IA64_PALINFO=yCONFIG_IA64_MC_ERR_INJECT=yCONFIG_IA64_ESI=yCONFIG_IA64_HP_AML_NFW=yCONFIG_KEXEC=yCONFIG_CRASH_DUMP=y
# end of Processor type and features
#
# Power management and ACPI options
#CONFIG_PM=yCONFIG_PM_DEBUG=yCONFIG_PM_ADVANCED_DEBUG=yCONFIG_DPM_WATCHDOG=yCONFIG_DPM_WATCHDOG_TIMEOUT=120CONFIG_PM_CLK=yCONFIG_PM_GENERIC_DOMAINS=yCONFIG_WQ_POWER_EFFICIENT_DEFAULT=yCONFIG_PM_GENERIC_DOMAINS_OF=yCONFIG_ENERGY_MODEL=yCONFIG_ARCH_SUPPORTS_ACPI=yCONFIG_ACPI=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=yCONFIG_ACPI_TABLE_LIB=yCONFIG_ACPI_DEBUGGER=yCONFIG_ACPI_DEBUGGER_USER=yCONFIG_ACPI_SPCR_TABLE=yCONFIG_ACPI_EC_DEBUGFS=yCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=yCONFIG_ACPI_DOCK=yCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_IPMI=yCONFIG_ACPI_HOTPLUG_CPU=yCONFIG_ACPI_THERMAL=yCONFIG_ACPI_PLATFORM_PROFILE=yCONFIG_ACPI_DEBUG=yCONFIG_ACPI_PCI_SLOT=yCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_MEMORY=yCONFIG_ACPI_HED=yCONFIG_ACPI_CUSTOM_METHOD=yCONFIG_ACPI_REDUCED_HARDWARE_ONLY=yCONFIG_ACPI_NUMA=yCONFIG_ACPI_HMAT=yCONFIG_ACPI_WATCHDOG=yCONFIG_ACPI_CONFIGFS=yCONFIG_ACPI_PFRUT=yCONFIG_ACPI_PCC=yCONFIG_PMIC_OPREGION=yCONFIG_BYTCRC_PMIC_OPREGION=yCONFIG_CHTCRC_PMIC_OPREGION=yCONFIG_CHT_WC_PMIC_OPREGION=y
#
# CPU Frequency scaling
#
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # 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=y
#
# CPU frequency scaling drivers
#CONFIG_CPUFREQ_DT=yCONFIG_CPUFREQ_DT_PLATDEV=yCONFIG_IA64_ACPI_CPUFREQ=yCONFIG_QORIQ_CPUFREQ=y
# end of CPU Frequency scaling # end of CPU Frequency scaling # end of Power management and ACPI options
CONFIG_MSPEC=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_KPROBES=yCONFIG_HAVE_64BIT_ALIGNED_ACCESS=yCONFIG_KRETPROBES=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_FUNCTION_DESCRIPTORS=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_TASK_STRUCT_ON_STACK=yCONFIG_ARCH_TASK_STRUCT_ALLOCATOR=yCONFIG_ARCH_THREAD_STACK_ALLOCATOR=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_LTO_NONE=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_PAGE_SIZE_LESS_THAN_64KB=yCONFIG_PAGE_SIZE_LESS_THAN_256KB=yCONFIG_ISA_BUS_API=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_LOCK_EVENT_COUNTS=y
#
# GCOV-based kernel profiling
#CONFIG_GCOV_KERNEL=y
# end of GCOV-based kernel profiling # end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULE_SIG_FORMAT=yCONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=yCONFIG_MODULE_FORCE_UNLOAD=yCONFIG_MODULE_UNLOAD_TAINT_TRACKING=yCONFIG_MODVERSIONS=yCONFIG_ASM_MODVERSIONS=yCONFIG_MODULE_SRCVERSION_ALL=yCONFIG_MODULE_SIG=yCONFIG_MODULE_SIG_FORCE=yCONFIG_MODULE_SIG_ALL=yCONFIG_MODULE_SIG_SHA1=y
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not setCONFIG_MODULE_SIG_HASH="sha1"CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not setCONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS=yCONFIG_MODPROBE_PATH="/sbin/modprobe"CONFIG_BLOCK=yCONFIG_BLOCK_LEGACY_AUTOLOAD=yCONFIG_BLK_RQ_ALLOC_TIME=yCONFIG_BLK_CGROUP_RWSTAT=yCONFIG_BLK_DEV_BSG_COMMON=yCONFIG_BLK_ICQ=yCONFIG_BLK_DEV_BSGLIB=yCONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_DEV_INTEGRITY_T10=yCONFIG_BLK_DEV_ZONED=yCONFIG_BLK_DEV_THROTTLING=yCONFIG_BLK_DEV_THROTTLING_LOW=yCONFIG_BLK_WBT=yCONFIG_BLK_WBT_MQ=yCONFIG_BLK_CGROUP_IOLATENCY=yCONFIG_BLK_CGROUP_FC_APPID=yCONFIG_BLK_CGROUP_IOCOST=yCONFIG_BLK_CGROUP_IOPRIO=yCONFIG_BLK_DEBUG_FS=yCONFIG_BLK_DEBUG_FS_ZONED=yCONFIG_BLK_SED_OPAL=yCONFIG_BLK_INLINE_ENCRYPTION=yCONFIG_BLK_INLINE_ENCRYPTION_FALLBACK=y
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=yCONFIG_ACORN_PARTITION=yCONFIG_ACORN_PARTITION_CUMANA=yCONFIG_ACORN_PARTITION_EESOX=yCONFIG_ACORN_PARTITION_ICS=yCONFIG_ACORN_PARTITION_ADFS=yCONFIG_ACORN_PARTITION_POWERTEC=yCONFIG_ACORN_PARTITION_RISCIX=yCONFIG_AIX_PARTITION=yCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=yCONFIG_ATARI_PARTITION=yCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=yCONFIG_LDM_PARTITION=yCONFIG_LDM_DEBUG=yCONFIG_SGI_PARTITION=yCONFIG_ULTRIX_PARTITION=yCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=yCONFIG_SYSV68_PARTITION=yCONFIG_CMDLINE_PARTITION=y
# end of Partition Types
CONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_MQ_RDMA=yCONFIG_BLK_PM=yCONFIG_BLOCK_HOLDER_DEPRECATED=yCONFIG_BLK_MQ_STACKING=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=yCONFIG_IOSCHED_BFQ=yCONFIG_BFQ_GROUP_IOSCHED=yCONFIG_BFQ_CGROUP_DEBUG=y
# end of IO Schedulers
CONFIG_PADATA=yCONFIG_ASN1=yCONFIG_UNINLINE_SPIN_UNLOCK=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_BINFMT_ELF_KUNIT_TEST=yCONFIG_ARCH_BINFMT_ELF_EXTRA_PHDRS=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=yCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_ZPOOL=yCONFIG_SWAP=yCONFIG_ZSWAP=yCONFIG_ZSWAP_DEFAULT_ON=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT="lzo" CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=y
# CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD is not set # CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set CONFIG_ZSWAP_ZPOOL_DEFAULT="zbud" CONFIG_ZBUD=yCONFIG_Z3FOLD=yCONFIG_ZSMALLOC=yCONFIG_ZSMALLOC_STAT=y
#
# SLAB allocator options
#
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=yCONFIG_SLAB_FREELIST_RANDOM=yCONFIG_SLAB_FREELIST_HARDENED=yCONFIG_SLUB_STATS=yCONFIG_SLUB_CPU_PARTIAL=y
# end of SLAB allocator options
CONFIG_SHUFFLE_PAGE_ALLOCATOR=yCONFIG_COMPAT_BRK=yCONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not setCONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_SPARSEMEM_VMEMMAP_ENABLE=yCONFIG_SPARSEMEM_VMEMMAP=yCONFIG_NUMA_KEEP_MEMINFO=yCONFIG_MEMORY_ISOLATION=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=yCONFIG_MEMORY_HOTREMOVE=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_MEMORY_BALLOON=yCONFIG_BALLOON_COMPACTION=yCONFIG_COMPACTION=yCONFIG_COMPACT_UNEVICTABLE_DEFAULT=1CONFIG_PAGE_REPORTING=yCONFIG_MIGRATION=yCONFIG_HUGETLB_PAGE_SIZE_VARIABLE=yCONFIG_CONTIG_ALLOC=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_USE_PERCPU_NUMA_NODE_ID=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_FRONTSWAP=yCONFIG_CMA=yCONFIG_CMA_DEBUG=yCONFIG_CMA_DEBUGFS=yCONFIG_CMA_SYSFS=yCONFIG_CMA_AREAS=19CONFIG_DEFERRED_STRUCT_PAGE_INIT=yCONFIG_PAGE_IDLE_FLAG=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ZONE_DMA32=yCONFIG_HMM_MIRROR=yCONFIG_GET_FREE_REGION=yCONFIG_VM_EVENT_COUNTERS=yCONFIG_PERCPU_STATS=yCONFIG_GUP_TEST=yCONFIG_ANON_VMA_NAME=yCONFIG_USERFAULTFD=yCONFIG_LRU_GEN=yCONFIG_LRU_GEN_ENABLED=yCONFIG_LRU_GEN_STATS=y
#
# Data Access Monitoring
#CONFIG_DAMON=yCONFIG_DAMON_KUNIT_TEST=yCONFIG_DAMON_VADDR=yCONFIG_DAMON_PADDR=yCONFIG_DAMON_VADDR_KUNIT_TEST=yCONFIG_DAMON_SYSFS=yCONFIG_DAMON_DBGFS=yCONFIG_DAMON_DBGFS_KUNIT_TEST=yCONFIG_DAMON_RECLAIM=yCONFIG_DAMON_LRU_SORT=y
# end of Data Access Monitoring # end of Memory Management options
CONFIG_NET=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_NET_REDIRECT=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=yCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_AF_UNIX_OOB=yCONFIG_UNIX_DIAG=yCONFIG_TLS=yCONFIG_TLS_DEVICE=yCONFIG_TLS_TOE=yCONFIG_XFRM=yCONFIG_XFRM_OFFLOAD=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=yCONFIG_XFRM_INTERFACE=yCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_AH=yCONFIG_XFRM_ESP=yCONFIG_XFRM_IPCOMP=yCONFIG_NET_KEY=yCONFIG_NET_KEY_MIGRATE=yCONFIG_XFRM_ESPINTCP=yCONFIG_SMC=yCONFIG_SMC_DIAG=yCONFIG_XDP_SOCKETS=yCONFIG_XDP_SOCKETS_DIAG=yCONFIG_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=yCONFIG_IP_PNP_BOOTP=yCONFIG_IP_PNP_RARP=yCONFIG_NET_IPIP=yCONFIG_NET_IPGRE_DEMUX=yCONFIG_NET_IP_TUNNEL=yCONFIG_NET_IPGRE=yCONFIG_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=yCONFIG_NET_UDP_TUNNEL=yCONFIG_NET_FOU=yCONFIG_NET_FOU_IP_TUNNELS=yCONFIG_INET_AH=yCONFIG_INET_ESP=yCONFIG_INET_ESP_OFFLOAD=yCONFIG_INET_ESPINTCP=yCONFIG_INET_IPCOMP=yCONFIG_INET_XFRM_TUNNEL=yCONFIG_INET_TUNNEL=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=yCONFIG_INET_UDP_DIAG=yCONFIG_INET_RAW_DIAG=yCONFIG_INET_DIAG_DESTROY=yCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=yCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=yCONFIG_TCP_CONG_HTCP=yCONFIG_TCP_CONG_HSTCP=yCONFIG_TCP_CONG_HYBLA=yCONFIG_TCP_CONG_VEGAS=yCONFIG_TCP_CONG_NV=yCONFIG_TCP_CONG_SCALABLE=yCONFIG_TCP_CONG_LP=yCONFIG_TCP_CONG_VENO=yCONFIG_TCP_CONG_YEAH=yCONFIG_TCP_CONG_ILLINOIS=yCONFIG_TCP_CONG_DCTCP=yCONFIG_TCP_CONG_CDG=yCONFIG_TCP_CONG_BBR=y
# CONFIG_DEFAULT_BIC is not setCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_HYBLA is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_VENO is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_DCTCP is not set
# CONFIG_DEFAULT_CDG is not set
# CONFIG_DEFAULT_BBR is not set
# 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=yCONFIG_INET6_ESP=yCONFIG_INET6_ESP_OFFLOAD=yCONFIG_INET6_ESPINTCP=yCONFIG_INET6_IPCOMP=yCONFIG_IPV6_MIP6=yCONFIG_IPV6_ILA=yCONFIG_INET6_XFRM_TUNNEL=yCONFIG_INET6_TUNNEL=yCONFIG_IPV6_VTI=yCONFIG_IPV6_SIT=yCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=yCONFIG_IPV6_GRE=yCONFIG_IPV6_FOU=yCONFIG_IPV6_FOU_TUNNEL=yCONFIG_IPV6_MULTIPLE_TABLES=yCONFIG_IPV6_SUBTREES=yCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=yCONFIG_IPV6_SEG6_HMAC=yCONFIG_IPV6_SEG6_BPF=yCONFIG_IPV6_RPL_LWTUNNEL=yCONFIG_IPV6_IOAM6_LWTUNNEL=yCONFIG_NETLABEL=yCONFIG_MPTCP=yCONFIG_INET_MPTCP_DIAG=yCONFIG_MPTCP_IPV6=yCONFIG_MPTCP_KUNIT_TEST=yCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_EGRESS=yCONFIG_NETFILTER_SKIP_EGRESS=yCONFIG_NETFILTER_NETLINK=yCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=yCONFIG_NETFILTER_NETLINK_HOOK=yCONFIG_NETFILTER_NETLINK_ACCT=yCONFIG_NETFILTER_NETLINK_QUEUE=yCONFIG_NETFILTER_NETLINK_LOG=yCONFIG_NETFILTER_NETLINK_OSF=yCONFIG_NF_CONNTRACK=yCONFIG_NF_LOG_SYSLOG=yCONFIG_NETFILTER_CONNCOUNT=yCONFIG_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=yCONFIG_NF_CONNTRACK_FTP=yCONFIG_NF_CONNTRACK_H323=yCONFIG_NF_CONNTRACK_IRC=yCONFIG_NF_CONNTRACK_BROADCAST=yCONFIG_NF_CONNTRACK_NETBIOS_NS=yCONFIG_NF_CONNTRACK_SNMP=yCONFIG_NF_CONNTRACK_PPTP=yCONFIG_NF_CONNTRACK_SANE=yCONFIG_NF_CONNTRACK_SIP=yCONFIG_NF_CONNTRACK_TFTP=yCONFIG_NF_CT_NETLINK=yCONFIG_NF_CT_NETLINK_TIMEOUT=yCONFIG_NF_CT_NETLINK_HELPER=yCONFIG_NETFILTER_NETLINK_GLUE_CT=yCONFIG_NF_NAT=yCONFIG_NF_NAT_AMANDA=yCONFIG_NF_NAT_FTP=yCONFIG_NF_NAT_IRC=yCONFIG_NF_NAT_SIP=yCONFIG_NF_NAT_TFTP=yCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=yCONFIG_NF_TABLES=yCONFIG_NF_TABLES_INET=yCONFIG_NF_TABLES_NETDEV=yCONFIG_NFT_NUMGEN=yCONFIG_NFT_CT=yCONFIG_NFT_FLOW_OFFLOAD=yCONFIG_NFT_CONNLIMIT=yCONFIG_NFT_LOG=yCONFIG_NFT_LIMIT=yCONFIG_NFT_MASQ=yCONFIG_NFT_REDIR=yCONFIG_NFT_NAT=yCONFIG_NFT_TUNNEL=yCONFIG_NFT_QUEUE=yCONFIG_NFT_QUOTA=yCONFIG_NFT_REJECT=yCONFIG_NFT_REJECT_INET=yCONFIG_NFT_COMPAT=yCONFIG_NFT_HASH=yCONFIG_NFT_FIB=yCONFIG_NFT_FIB_INET=yCONFIG_NFT_XFRM=yCONFIG_NFT_SOCKET=yCONFIG_NFT_OSF=yCONFIG_NFT_TPROXY=yCONFIG_NFT_SYNPROXY=yCONFIG_NF_DUP_NETDEV=yCONFIG_NFT_DUP_NETDEV=yCONFIG_NFT_FWD_NETDEV=yCONFIG_NFT_FIB_NETDEV=yCONFIG_NFT_REJECT_NETDEV=yCONFIG_NF_FLOW_TABLE_INET=yCONFIG_NF_FLOW_TABLE=yCONFIG_NF_FLOW_TABLE_PROCFS=yCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=yCONFIG_NETFILTER_XT_CONNMARK=yCONFIG_NETFILTER_XT_SET=y
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=yCONFIG_NETFILTER_XT_TARGET_CHECKSUM=yCONFIG_NETFILTER_XT_TARGET_CLASSIFY=yCONFIG_NETFILTER_XT_TARGET_CONNMARK=yCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=yCONFIG_NETFILTER_XT_TARGET_CT=yCONFIG_NETFILTER_XT_TARGET_DSCP=yCONFIG_NETFILTER_XT_TARGET_HL=yCONFIG_NETFILTER_XT_TARGET_HMARK=yCONFIG_NETFILTER_XT_TARGET_IDLETIMER=yCONFIG_NETFILTER_XT_TARGET_LED=yCONFIG_NETFILTER_XT_TARGET_LOG=yCONFIG_NETFILTER_XT_TARGET_MARK=yCONFIG_NETFILTER_XT_NAT=yCONFIG_NETFILTER_XT_TARGET_NETMAP=yCONFIG_NETFILTER_XT_TARGET_NFLOG=yCONFIG_NETFILTER_XT_TARGET_NFQUEUE=yCONFIG_NETFILTER_XT_TARGET_NOTRACK=yCONFIG_NETFILTER_XT_TARGET_RATEEST=yCONFIG_NETFILTER_XT_TARGET_REDIRECT=yCONFIG_NETFILTER_XT_TARGET_MASQUERADE=yCONFIG_NETFILTER_XT_TARGET_TEE=yCONFIG_NETFILTER_XT_TARGET_TPROXY=yCONFIG_NETFILTER_XT_TARGET_TRACE=yCONFIG_NETFILTER_XT_TARGET_SECMARK=yCONFIG_NETFILTER_XT_TARGET_TCPMSS=yCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=y
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=yCONFIG_NETFILTER_XT_MATCH_BPF=yCONFIG_NETFILTER_XT_MATCH_CGROUP=yCONFIG_NETFILTER_XT_MATCH_CLUSTER=yCONFIG_NETFILTER_XT_MATCH_COMMENT=yCONFIG_NETFILTER_XT_MATCH_CONNBYTES=yCONFIG_NETFILTER_XT_MATCH_CONNLABEL=yCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=yCONFIG_NETFILTER_XT_MATCH_CONNMARK=yCONFIG_NETFILTER_XT_MATCH_CONNTRACK=yCONFIG_NETFILTER_XT_MATCH_CPU=yCONFIG_NETFILTER_XT_MATCH_DCCP=yCONFIG_NETFILTER_XT_MATCH_DEVGROUP=yCONFIG_NETFILTER_XT_MATCH_DSCP=yCONFIG_NETFILTER_XT_MATCH_ECN=yCONFIG_NETFILTER_XT_MATCH_ESP=yCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=yCONFIG_NETFILTER_XT_MATCH_HELPER=yCONFIG_NETFILTER_XT_MATCH_HL=yCONFIG_NETFILTER_XT_MATCH_IPCOMP=yCONFIG_NETFILTER_XT_MATCH_IPRANGE=yCONFIG_NETFILTER_XT_MATCH_IPVS=yCONFIG_NETFILTER_XT_MATCH_L2TP=yCONFIG_NETFILTER_XT_MATCH_LENGTH=yCONFIG_NETFILTER_XT_MATCH_LIMIT=yCONFIG_NETFILTER_XT_MATCH_MAC=yCONFIG_NETFILTER_XT_MATCH_MARK=yCONFIG_NETFILTER_XT_MATCH_MULTIPORT=yCONFIG_NETFILTER_XT_MATCH_NFACCT=yCONFIG_NETFILTER_XT_MATCH_OSF=yCONFIG_NETFILTER_XT_MATCH_OWNER=yCONFIG_NETFILTER_XT_MATCH_POLICY=yCONFIG_NETFILTER_XT_MATCH_PHYSDEV=yCONFIG_NETFILTER_XT_MATCH_PKTTYPE=yCONFIG_NETFILTER_XT_MATCH_QUOTA=yCONFIG_NETFILTER_XT_MATCH_RATEEST=yCONFIG_NETFILTER_XT_MATCH_REALM=yCONFIG_NETFILTER_XT_MATCH_RECENT=yCONFIG_NETFILTER_XT_MATCH_SCTP=yCONFIG_NETFILTER_XT_MATCH_SOCKET=yCONFIG_NETFILTER_XT_MATCH_STATE=yCONFIG_NETFILTER_XT_MATCH_STATISTIC=yCONFIG_NETFILTER_XT_MATCH_STRING=yCONFIG_NETFILTER_XT_MATCH_TCPMSS=yCONFIG_NETFILTER_XT_MATCH_TIME=yCONFIG_NETFILTER_XT_MATCH_U32=y
# end of Core Netfilter Configuration
CONFIG_IP_SET=yCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=yCONFIG_IP_SET_BITMAP_IPMAC=yCONFIG_IP_SET_BITMAP_PORT=yCONFIG_IP_SET_HASH_IP=yCONFIG_IP_SET_HASH_IPMARK=yCONFIG_IP_SET_HASH_IPPORT=yCONFIG_IP_SET_HASH_IPPORTIP=yCONFIG_IP_SET_HASH_IPPORTNET=yCONFIG_IP_SET_HASH_IPMAC=yCONFIG_IP_SET_HASH_MAC=yCONFIG_IP_SET_HASH_NETPORTNET=yCONFIG_IP_SET_HASH_NET=yCONFIG_IP_SET_HASH_NETNET=yCONFIG_IP_SET_HASH_NETPORT=yCONFIG_IP_SET_HASH_NETIFACE=yCONFIG_IP_SET_LIST_SET=yCONFIG_IP_VS=yCONFIG_IP_VS_IPV6=yCONFIG_IP_VS_DEBUG=yCONFIG_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=yCONFIG_IP_VS_WRR=yCONFIG_IP_VS_LC=yCONFIG_IP_VS_WLC=yCONFIG_IP_VS_FO=yCONFIG_IP_VS_OVF=yCONFIG_IP_VS_LBLC=yCONFIG_IP_VS_LBLCR=yCONFIG_IP_VS_DH=yCONFIG_IP_VS_SH=yCONFIG_IP_VS_MH=yCONFIG_IP_VS_SED=yCONFIG_IP_VS_NQ=yCONFIG_IP_VS_TWOS=y
#
# 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=yCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=y
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=yCONFIG_NF_SOCKET_IPV4=yCONFIG_NF_TPROXY_IPV4=yCONFIG_NF_TABLES_IPV4=yCONFIG_NFT_REJECT_IPV4=yCONFIG_NFT_DUP_IPV4=yCONFIG_NFT_FIB_IPV4=yCONFIG_NF_TABLES_ARP=yCONFIG_NF_DUP_IPV4=yCONFIG_NF_LOG_ARP=yCONFIG_NF_LOG_IPV4=yCONFIG_NF_REJECT_IPV4=yCONFIG_NF_NAT_SNMP_BASIC=yCONFIG_NF_NAT_PPTP=yCONFIG_NF_NAT_H323=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_MATCH_AH=yCONFIG_IP_NF_MATCH_ECN=yCONFIG_IP_NF_MATCH_RPFILTER=yCONFIG_IP_NF_MATCH_TTL=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_SYNPROXY=yCONFIG_IP_NF_NAT=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_IP_NF_TARGET_NETMAP=yCONFIG_IP_NF_TARGET_REDIRECT=yCONFIG_IP_NF_MANGLE=yCONFIG_IP_NF_TARGET_CLUSTERIP=yCONFIG_IP_NF_TARGET_ECN=yCONFIG_IP_NF_TARGET_TTL=yCONFIG_IP_NF_RAW=yCONFIG_IP_NF_SECURITY=yCONFIG_IP_NF_ARPTABLES=yCONFIG_IP_NF_ARPFILTER=yCONFIG_IP_NF_ARP_MANGLE=y
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=yCONFIG_NF_TPROXY_IPV6=yCONFIG_NF_TABLES_IPV6=yCONFIG_NFT_REJECT_IPV6=yCONFIG_NFT_DUP_IPV6=yCONFIG_NFT_FIB_IPV6=yCONFIG_NF_DUP_IPV6=yCONFIG_NF_REJECT_IPV6=yCONFIG_NF_LOG_IPV6=yCONFIG_IP6_NF_IPTABLES=yCONFIG_IP6_NF_MATCH_AH=yCONFIG_IP6_NF_MATCH_EUI64=yCONFIG_IP6_NF_MATCH_FRAG=yCONFIG_IP6_NF_MATCH_OPTS=yCONFIG_IP6_NF_MATCH_HL=yCONFIG_IP6_NF_MATCH_IPV6HEADER=yCONFIG_IP6_NF_MATCH_MH=yCONFIG_IP6_NF_MATCH_RPFILTER=yCONFIG_IP6_NF_MATCH_RT=yCONFIG_IP6_NF_MATCH_SRH=yCONFIG_IP6_NF_TARGET_HL=yCONFIG_IP6_NF_FILTER=yCONFIG_IP6_NF_TARGET_REJECT=yCONFIG_IP6_NF_TARGET_SYNPROXY=yCONFIG_IP6_NF_MANGLE=yCONFIG_IP6_NF_RAW=yCONFIG_IP6_NF_SECURITY=yCONFIG_IP6_NF_NAT=yCONFIG_IP6_NF_TARGET_MASQUERADE=yCONFIG_IP6_NF_TARGET_NPT=y
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=yCONFIG_NF_TABLES_BRIDGE=yCONFIG_NFT_BRIDGE_META=yCONFIG_NFT_BRIDGE_REJECT=yCONFIG_NF_CONNTRACK_BRIDGE=yCONFIG_BRIDGE_NF_EBTABLES=yCONFIG_BRIDGE_EBT_BROUTE=yCONFIG_BRIDGE_EBT_T_FILTER=yCONFIG_BRIDGE_EBT_T_NAT=yCONFIG_BRIDGE_EBT_802_3=yCONFIG_BRIDGE_EBT_AMONG=yCONFIG_BRIDGE_EBT_ARP=yCONFIG_BRIDGE_EBT_IP=yCONFIG_BRIDGE_EBT_IP6=yCONFIG_BRIDGE_EBT_LIMIT=yCONFIG_BRIDGE_EBT_MARK=yCONFIG_BRIDGE_EBT_PKTTYPE=yCONFIG_BRIDGE_EBT_STP=yCONFIG_BRIDGE_EBT_VLAN=yCONFIG_BRIDGE_EBT_ARPREPLY=yCONFIG_BRIDGE_EBT_DNAT=yCONFIG_BRIDGE_EBT_MARK_T=yCONFIG_BRIDGE_EBT_REDIRECT=yCONFIG_BRIDGE_EBT_SNAT=yCONFIG_BRIDGE_EBT_LOG=yCONFIG_BRIDGE_EBT_NFLOG=yCONFIG_BPFILTER=yCONFIG_IP_DCCP=yCONFIG_INET_DCCP_DIAG=y
#
# DCCP CCIDs Configuration
#CONFIG_IP_DCCP_CCID2_DEBUG=yCONFIG_IP_DCCP_CCID3=yCONFIG_IP_DCCP_CCID3_DEBUG=yCONFIG_IP_DCCP_TFRC_LIB=yCONFIG_IP_DCCP_TFRC_DEBUG=y
# end of DCCP CCIDs Configuration
#
# DCCP Kernel Hacking
#CONFIG_IP_DCCP_DEBUG=y
# end of DCCP Kernel Hacking
CONFIG_IP_SCTP=yCONFIG_SCTP_DBG_OBJCNT=yCONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1 is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not setCONFIG_SCTP_COOKIE_HMAC_MD5=yCONFIG_SCTP_COOKIE_HMAC_SHA1=yCONFIG_INET_SCTP_DIAG=yCONFIG_RDS=yCONFIG_RDS_RDMA=yCONFIG_RDS_TCP=yCONFIG_RDS_DEBUG=yCONFIG_TIPC=yCONFIG_TIPC_MEDIA_IB=yCONFIG_TIPC_MEDIA_UDP=yCONFIG_TIPC_CRYPTO=yCONFIG_TIPC_DIAG=yCONFIG_ATM=yCONFIG_ATM_CLIP=yCONFIG_ATM_CLIP_NO_ICMP=yCONFIG_ATM_LANE=yCONFIG_ATM_MPOA=yCONFIG_ATM_BR2684=yCONFIG_ATM_BR2684_IPFILTER=yCONFIG_L2TP=yCONFIG_L2TP_DEBUGFS=yCONFIG_L2TP_V3=yCONFIG_L2TP_IP=yCONFIG_L2TP_ETH=yCONFIG_STP=yCONFIG_GARP=yCONFIG_MRP=yCONFIG_BRIDGE=yCONFIG_BRIDGE_IGMP_SNOOPING=yCONFIG_BRIDGE_VLAN_FILTERING=yCONFIG_BRIDGE_MRP=yCONFIG_BRIDGE_CFM=yCONFIG_NET_DSA=yCONFIG_NET_DSA_TAG_AR9331=yCONFIG_NET_DSA_TAG_BRCM_COMMON=yCONFIG_NET_DSA_TAG_BRCM=yCONFIG_NET_DSA_TAG_BRCM_LEGACY=yCONFIG_NET_DSA_TAG_BRCM_PREPEND=yCONFIG_NET_DSA_TAG_HELLCREEK=yCONFIG_NET_DSA_TAG_GSWIP=yCONFIG_NET_DSA_TAG_DSA_COMMON=yCONFIG_NET_DSA_TAG_DSA=yCONFIG_NET_DSA_TAG_EDSA=yCONFIG_NET_DSA_TAG_MTK=yCONFIG_NET_DSA_TAG_KSZ=yCONFIG_NET_DSA_TAG_OCELOT=yCONFIG_NET_DSA_TAG_OCELOT_8021Q=yCONFIG_NET_DSA_TAG_QCA=yCONFIG_NET_DSA_TAG_RTL4_A=yCONFIG_NET_DSA_TAG_RTL8_4=yCONFIG_NET_DSA_TAG_RZN1_A5PSW=yCONFIG_NET_DSA_TAG_LAN9303=yCONFIG_NET_DSA_TAG_SJA1105=yCONFIG_NET_DSA_TAG_TRAILER=yCONFIG_NET_DSA_TAG_XRS700X=yCONFIG_VLAN_8021Q=yCONFIG_VLAN_8021Q_GVRP=yCONFIG_VLAN_8021Q_MVRP=yCONFIG_LLC=yCONFIG_LLC2=yCONFIG_ATALK=yCONFIG_DEV_APPLETALK=yCONFIG_IPDDP=yCONFIG_IPDDP_ENCAP=yCONFIG_X25=yCONFIG_LAPB=yCONFIG_PHONET=yCONFIG_6LOWPAN=yCONFIG_6LOWPAN_DEBUGFS=yCONFIG_6LOWPAN_NHC=yCONFIG_6LOWPAN_NHC_DEST=yCONFIG_6LOWPAN_NHC_FRAGMENT=yCONFIG_6LOWPAN_NHC_HOP=yCONFIG_6LOWPAN_NHC_IPV6=yCONFIG_6LOWPAN_NHC_MOBILITY=yCONFIG_6LOWPAN_NHC_ROUTING=yCONFIG_6LOWPAN_NHC_UDP=yCONFIG_6LOWPAN_GHC_EXT_HDR_HOP=yCONFIG_6LOWPAN_GHC_UDP=yCONFIG_6LOWPAN_GHC_ICMPV6=yCONFIG_6LOWPAN_GHC_EXT_HDR_DEST=yCONFIG_6LOWPAN_GHC_EXT_HDR_FRAG=yCONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE=yCONFIG_IEEE802154=yCONFIG_IEEE802154_NL802154_EXPERIMENTAL=yCONFIG_IEEE802154_SOCKET=yCONFIG_IEEE802154_6LOWPAN=yCONFIG_MAC802154=yCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=yCONFIG_NET_SCH_HTB=yCONFIG_NET_SCH_HFSC=yCONFIG_NET_SCH_ATM=yCONFIG_NET_SCH_PRIO=yCONFIG_NET_SCH_MULTIQ=yCONFIG_NET_SCH_RED=yCONFIG_NET_SCH_SFB=yCONFIG_NET_SCH_SFQ=yCONFIG_NET_SCH_TEQL=yCONFIG_NET_SCH_TBF=yCONFIG_NET_SCH_CBS=yCONFIG_NET_SCH_ETF=yCONFIG_NET_SCH_TAPRIO=yCONFIG_NET_SCH_GRED=yCONFIG_NET_SCH_DSMARK=yCONFIG_NET_SCH_NETEM=yCONFIG_NET_SCH_DRR=yCONFIG_NET_SCH_MQPRIO=yCONFIG_NET_SCH_SKBPRIO=yCONFIG_NET_SCH_CHOKE=yCONFIG_NET_SCH_QFQ=yCONFIG_NET_SCH_CODEL=yCONFIG_NET_SCH_FQ_CODEL=yCONFIG_NET_SCH_CAKE=yCONFIG_NET_SCH_FQ=yCONFIG_NET_SCH_HHF=yCONFIG_NET_SCH_PIE=yCONFIG_NET_SCH_FQ_PIE=yCONFIG_NET_SCH_INGRESS=yCONFIG_NET_SCH_PLUG=yCONFIG_NET_SCH_ETS=yCONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
# CONFIG_DEFAULT_CODEL is not set
# CONFIG_DEFAULT_FQ_CODEL is not set
# CONFIG_DEFAULT_FQ_PIE is not set
# CONFIG_DEFAULT_SFQ is not setCONFIG_DEFAULT_PFIFO_FAST=yCONFIG_DEFAULT_NET_SCH="pfifo_fast"
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=yCONFIG_NET_CLS_TCINDEX=yCONFIG_NET_CLS_ROUTE4=yCONFIG_NET_CLS_FW=yCONFIG_NET_CLS_U32=yCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=yCONFIG_NET_CLS_RSVP6=yCONFIG_NET_CLS_FLOW=yCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=yCONFIG_NET_CLS_FLOWER=yCONFIG_NET_CLS_MATCHALL=yCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=yCONFIG_NET_EMATCH_NBYTE=yCONFIG_NET_EMATCH_U32=yCONFIG_NET_EMATCH_META=yCONFIG_NET_EMATCH_TEXT=yCONFIG_NET_EMATCH_CANID=yCONFIG_NET_EMATCH_IPSET=yCONFIG_NET_EMATCH_IPT=yCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=yCONFIG_NET_ACT_GACT=yCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=yCONFIG_NET_ACT_SAMPLE=yCONFIG_NET_ACT_IPT=yCONFIG_NET_ACT_NAT=yCONFIG_NET_ACT_PEDIT=yCONFIG_NET_ACT_SIMP=yCONFIG_NET_ACT_SKBEDIT=yCONFIG_NET_ACT_CSUM=yCONFIG_NET_ACT_MPLS=yCONFIG_NET_ACT_VLAN=yCONFIG_NET_ACT_BPF=yCONFIG_NET_ACT_CONNMARK=yCONFIG_NET_ACT_CTINFO=yCONFIG_NET_ACT_SKBMOD=yCONFIG_NET_ACT_IFE=yCONFIG_NET_ACT_TUNNEL_KEY=yCONFIG_NET_ACT_CT=yCONFIG_NET_ACT_GATE=yCONFIG_NET_IFE_SKBMARK=yCONFIG_NET_IFE_SKBPRIO=yCONFIG_NET_IFE_SKBTCINDEX=yCONFIG_NET_TC_SKB_EXT=yCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=yCONFIG_BATMAN_ADV=yCONFIG_BATMAN_ADV_BATMAN_V=yCONFIG_BATMAN_ADV_BLA=yCONFIG_BATMAN_ADV_DAT=yCONFIG_BATMAN_ADV_NC=yCONFIG_BATMAN_ADV_MCAST=yCONFIG_BATMAN_ADV_DEBUG=yCONFIG_OPENVSWITCH=yCONFIG_OPENVSWITCH_GRE=yCONFIG_OPENVSWITCH_VXLAN=yCONFIG_OPENVSWITCH_GENEVE=yCONFIG_VSOCKETS=yCONFIG_VSOCKETS_DIAG=yCONFIG_VSOCKETS_LOOPBACK=yCONFIG_VIRTIO_VSOCKETS=yCONFIG_VIRTIO_VSOCKETS_COMMON=yCONFIG_NETLINK_DIAG=yCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=yCONFIG_MPLS_ROUTING=yCONFIG_MPLS_IPTUNNEL=yCONFIG_NET_NSH=yCONFIG_HSR=yCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=yCONFIG_QRTR=yCONFIG_QRTR_SMD=yCONFIG_QRTR_TUN=yCONFIG_QRTR_MHI=yCONFIG_NET_NCSI=yCONFIG_NCSI_OEM_CMD_GET_MAC=yCONFIG_NCSI_OEM_CMD_KEEP_PHY=yCONFIG_PCPU_DEV_REFCNT=yCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_SOCK_RX_QUEUE_MAPPING=yCONFIG_XPS=yCONFIG_CGROUP_NET_PRIO=yCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=y
# end of Network testing # end of Networking options
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#CONFIG_AX25=yCONFIG_AX25_DAMA_SLAVE=yCONFIG_NETROM=yCONFIG_ROSE=y
#
# AX.25 network device drivers
#CONFIG_MKISS=yCONFIG_6PACK=yCONFIG_BPQETHER=yCONFIG_BAYCOM_SER_FDX=yCONFIG_BAYCOM_SER_HDX=yCONFIG_BAYCOM_PAR=yCONFIG_YAM=y
# end of AX.25 network device drivers
CONFIG_CAN=yCONFIG_CAN_RAW=yCONFIG_CAN_BCM=yCONFIG_CAN_GW=yCONFIG_CAN_J1939=yCONFIG_CAN_ISOTP=yCONFIG_BT=yCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=yCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=yCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_CMTP=yCONFIG_BT_HIDP=yCONFIG_BT_HS=yCONFIG_BT_LE=yCONFIG_BT_6LOWPAN=yCONFIG_BT_LEDS=yCONFIG_BT_MSFTEXT=yCONFIG_BT_AOSPEXT=yCONFIG_BT_DEBUGFS=yCONFIG_BT_SELFTEST=yCONFIG_BT_SELFTEST_ECDH=yCONFIG_BT_SELFTEST_SMP=y
#
# Bluetooth device drivers
#CONFIG_BT_INTEL=yCONFIG_BT_BCM=yCONFIG_BT_RTL=yCONFIG_BT_QCA=yCONFIG_BT_MTK=yCONFIG_BT_HCIBTUSB=yCONFIG_BT_HCIBTUSB_AUTOSUSPEND=yCONFIG_BT_HCIBTUSB_BCM=yCONFIG_BT_HCIBTUSB_MTK=yCONFIG_BT_HCIBTUSB_RTL=yCONFIG_BT_HCIBTSDIO=yCONFIG_BT_HCIUART=yCONFIG_BT_HCIUART_SERDEV=yCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_NOKIA=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=yCONFIG_BT_HCIUART_LL=yCONFIG_BT_HCIUART_3WIRE=yCONFIG_BT_HCIUART_INTEL=yCONFIG_BT_HCIUART_BCM=yCONFIG_BT_HCIUART_RTL=yCONFIG_BT_HCIUART_QCA=yCONFIG_BT_HCIUART_AG6XX=yCONFIG_BT_HCIUART_MRVL=yCONFIG_BT_HCIBCM203X=yCONFIG_BT_HCIBPA10X=yCONFIG_BT_HCIBFUSB=yCONFIG_BT_HCIDTL1=yCONFIG_BT_HCIBT3C=yCONFIG_BT_HCIBLUECARD=yCONFIG_BT_HCIVHCI=yCONFIG_BT_MRVL=yCONFIG_BT_MRVL_SDIO=yCONFIG_BT_ATH3K=yCONFIG_BT_MTKSDIO=yCONFIG_BT_MTKUART=yCONFIG_BT_QCOMSMD=yCONFIG_BT_HCIRSI=yCONFIG_BT_VIRTIO=y
# end of Bluetooth device drivers
CONFIG_AF_RXRPC=yCONFIG_AF_RXRPC_IPV6=yCONFIG_AF_RXRPC_INJECT_LOSS=yCONFIG_AF_RXRPC_DEBUG=yCONFIG_RXKAD=yCONFIG_AF_KCM=yCONFIG_STREAM_PARSER=yCONFIG_MCTP=yCONFIG_MCTP_TEST=yCONFIG_MCTP_FLOWS=yCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_WIRELESS_EXT=yCONFIG_WEXT_CORE=yCONFIG_WEXT_PROC=yCONFIG_WEXT_SPY=yCONFIG_WEXT_PRIV=yCONFIG_CFG80211=yCONFIG_NL80211_TESTMODE=yCONFIG_CFG80211_DEVELOPER_WARNINGS=yCONFIG_CFG80211_CERTIFICATION_ONUS=yCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_EXTRA_REGDB_KEYDIR=""CONFIG_CFG80211_REG_CELLULAR_HINTS=yCONFIG_CFG80211_REG_RELAX_NO_IR=yCONFIG_CFG80211_DEFAULT_PS=yCONFIG_CFG80211_DEBUGFS=yCONFIG_CFG80211_CRDA_SUPPORT=yCONFIG_CFG80211_WEXT=yCONFIG_CFG80211_WEXT_EXPORT=yCONFIG_LIB80211=yCONFIG_LIB80211_CRYPT_WEP=yCONFIG_LIB80211_CRYPT_CCMP=yCONFIG_LIB80211_CRYPT_TKIP=yCONFIG_LIB80211_DEBUG=yCONFIG_MAC80211=yCONFIG_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=yCONFIG_MAC80211_MESSAGE_TRACING=yCONFIG_MAC80211_DEBUG_MENU=yCONFIG_MAC80211_NOINLINE=yCONFIG_MAC80211_VERBOSE_DEBUG=yCONFIG_MAC80211_MLME_DEBUG=yCONFIG_MAC80211_STA_DEBUG=yCONFIG_MAC80211_HT_DEBUG=yCONFIG_MAC80211_OCB_DEBUG=yCONFIG_MAC80211_IBSS_DEBUG=yCONFIG_MAC80211_PS_DEBUG=yCONFIG_MAC80211_MPL_DEBUG=yCONFIG_MAC80211_MPATH_DEBUG=yCONFIG_MAC80211_MHWMP_DEBUG=yCONFIG_MAC80211_MESH_SYNC_DEBUG=yCONFIG_MAC80211_MESH_CSA_DEBUG=yCONFIG_MAC80211_MESH_PS_DEBUG=yCONFIG_MAC80211_TDLS_DEBUG=yCONFIG_MAC80211_DEBUG_COUNTERS=yCONFIG_MAC80211_STA_HASH_MAX_SIZE=0CONFIG_RFKILL=yCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=yCONFIG_RFKILL_GPIO=yCONFIG_NET_9P=yCONFIG_NET_9P_FD=yCONFIG_NET_9P_VIRTIO=yCONFIG_NET_9P_RDMA=yCONFIG_NET_9P_DEBUG=yCONFIG_CAIF=yCONFIG_CAIF_DEBUG=yCONFIG_CAIF_NETDEV=yCONFIG_CAIF_USB=yCONFIG_CEPH_LIB=yCONFIG_CEPH_LIB_PRETTYDEBUG=yCONFIG_CEPH_LIB_USE_DNS_RESOLVER=yCONFIG_NFC=yCONFIG_NFC_DIGITAL=yCONFIG_NFC_NCI=yCONFIG_NFC_NCI_SPI=yCONFIG_NFC_NCI_UART=yCONFIG_NFC_HCI=yCONFIG_NFC_SHDLC=y
#
# Near Field Communication (NFC) devices
#CONFIG_NFC_TRF7970A=yCONFIG_NFC_SIM=yCONFIG_NFC_PORT100=yCONFIG_NFC_VIRTUAL_NCI=yCONFIG_NFC_FDP=yCONFIG_NFC_FDP_I2C=yCONFIG_NFC_PN544=yCONFIG_NFC_PN544_I2C=yCONFIG_NFC_PN533=yCONFIG_NFC_PN533_USB=yCONFIG_NFC_PN533_I2C=yCONFIG_NFC_PN532_UART=yCONFIG_NFC_MICROREAD=yCONFIG_NFC_MICROREAD_I2C=yCONFIG_NFC_MRVL=yCONFIG_NFC_MRVL_USB=yCONFIG_NFC_MRVL_UART=yCONFIG_NFC_MRVL_I2C=yCONFIG_NFC_MRVL_SPI=yCONFIG_NFC_ST21NFCA=yCONFIG_NFC_ST21NFCA_I2C=yCONFIG_NFC_ST_NCI=yCONFIG_NFC_ST_NCI_I2C=yCONFIG_NFC_ST_NCI_SPI=yCONFIG_NFC_NXP_NCI=yCONFIG_NFC_NXP_NCI_I2C=yCONFIG_NFC_S3FWRN5=yCONFIG_NFC_S3FWRN5_I2C=yCONFIG_NFC_S3FWRN82_UART=yCONFIG_NFC_ST95HF=y
# end of Near Field Communication (NFC) devices
CONFIG_PSAMPLE=yCONFIG_NET_IFE=yCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_SOCK_VALIDATE_XMIT=yCONFIG_NET_SELFTESTS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=yCONFIG_PAGE_POOL_STATS=yCONFIG_FAILOVER=yCONFIG_ETHTOOL_NETLINK=yCONFIG_NETDEV_ADDR_LIST_TEST=y
#
# Device Drivers
#CONFIG_HAVE_PCI=yCONFIG_FORCE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCI_SYSCALL=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=yCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=yCONFIG_PCIE_DPC=yCONFIG_PCIE_PTM=yCONFIG_PCIE_EDR=yCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_MSI_ARCH_FALLBACKS=yCONFIG_PCI_QUIRKS=yCONFIG_PCI_DEBUG=yCONFIG_PCI_REALLOC_ENABLE_AUTO=yCONFIG_PCI_STUB=yCONFIG_PCI_PF_STUB=yCONFIG_PCI_ATS=yCONFIG_PCI_DOE=yCONFIG_PCI_ECAM=yCONFIG_PCI_BRIDGE_EMUL=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=yCONFIG_PCI_LABEL=y
# CONFIG_PCIE_BUS_TUNE_OFF is not setCONFIG_PCIE_BUS_DEFAULT=y
# CONFIG_PCIE_BUS_SAFE is not set
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not setCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=16CONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_ACPI=yCONFIG_HOTPLUG_PCI_ACPI_IBM=yCONFIG_HOTPLUG_PCI_CPCI=yCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#CONFIG_PCI_AARDVARK=yCONFIG_PCIE_XILINX_NWL=yCONFIG_PCI_FTPCI100=yCONFIG_PCI_TEGRA=yCONFIG_PCIE_RCAR_HOST=yCONFIG_PCIE_RCAR_EP=yCONFIG_PCI_HOST_COMMON=yCONFIG_PCI_HOST_GENERIC=yCONFIG_PCIE_XILINX=yCONFIG_PCIE_XILINX_CPM=yCONFIG_PCI_XGENE=yCONFIG_PCI_XGENE_MSI=yCONFIG_PCI_V3_SEMI=yCONFIG_PCI_VERSATILE=yCONFIG_PCIE_ALTERA=yCONFIG_PCIE_ALTERA_MSI=yCONFIG_PCI_HOST_THUNDER_PEM=yCONFIG_PCI_HOST_THUNDER_ECAM=yCONFIG_PCIE_ROCKCHIP=yCONFIG_PCIE_ROCKCHIP_HOST=yCONFIG_PCIE_ROCKCHIP_EP=yCONFIG_PCIE_MEDIATEK=yCONFIG_PCIE_MEDIATEK_GEN3=yCONFIG_PCIE_BRCMSTB=yCONFIG_PCI_LOONGSON=yCONFIG_PCIE_MICROCHIP_HOST=yCONFIG_PCIE_APPLE_MSI_DOORBELL_ADDR=0xfffff000CONFIG_PCIE_APPLE=yCONFIG_PCIE_MT7621=y
#
# DesignWare PCI Core Support
#CONFIG_PCIE_DW=yCONFIG_PCIE_DW_HOST=yCONFIG_PCIE_DW_EP=yCONFIG_PCI_DRA7XX=yCONFIG_PCI_DRA7XX_HOST=yCONFIG_PCI_DRA7XX_EP=yCONFIG_PCIE_DW_PLAT=yCONFIG_PCIE_DW_PLAT_HOST=yCONFIG_PCIE_DW_PLAT_EP=yCONFIG_PCI_EXYNOS=yCONFIG_PCI_IMX6=yCONFIG_PCIE_SPEAR13XX=yCONFIG_PCI_KEYSTONE=yCONFIG_PCI_KEYSTONE_HOST=yCONFIG_PCI_KEYSTONE_EP=yCONFIG_PCI_LAYERSCAPE=yCONFIG_PCI_LAYERSCAPE_EP=yCONFIG_PCI_HISI=yCONFIG_PCIE_QCOM=yCONFIG_PCIE_QCOM_EP=yCONFIG_PCIE_ARMADA_8K=yCONFIG_PCIE_ARTPEC6=yCONFIG_PCIE_ARTPEC6_HOST=yCONFIG_PCIE_ARTPEC6_EP=yCONFIG_PCIE_ROCKCHIP_DW_HOST=yCONFIG_PCIE_INTEL_GW=yCONFIG_PCIE_KEEMBAY=yCONFIG_PCIE_KEEMBAY_HOST=yCONFIG_PCIE_KEEMBAY_EP=yCONFIG_PCIE_KIRIN=yCONFIG_PCIE_HISI_STB=yCONFIG_PCI_MESON=yCONFIG_PCIE_TEGRA194=yCONFIG_PCIE_TEGRA194_HOST=yCONFIG_PCIE_TEGRA194_EP=yCONFIG_PCIE_VISCONTI_HOST=yCONFIG_PCIE_UNIPHIER=yCONFIG_PCIE_UNIPHIER_EP=yCONFIG_PCIE_AL=yCONFIG_PCIE_FU740=y
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#CONFIG_PCIE_MOBIVEIL=yCONFIG_PCIE_MOBIVEIL_HOST=yCONFIG_PCIE_MOBIVEIL_PLAT=yCONFIG_PCIE_LAYERSCAPE_GEN4=y
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#CONFIG_PCIE_CADENCE=yCONFIG_PCIE_CADENCE_HOST=yCONFIG_PCIE_CADENCE_EP=yCONFIG_PCIE_CADENCE_PLAT=yCONFIG_PCIE_CADENCE_PLAT_HOST=yCONFIG_PCIE_CADENCE_PLAT_EP=yCONFIG_PCI_J721E=yCONFIG_PCI_J721E_HOST=yCONFIG_PCI_J721E_EP=y
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#CONFIG_PCI_ENDPOINT=yCONFIG_PCI_ENDPOINT_CONFIGFS=yCONFIG_PCI_EPF_TEST=yCONFIG_PCI_EPF_NTB=yCONFIG_PCI_EPF_VNTB=y
# end of PCI Endpoint
#
# PCI switch controller drivers
#CONFIG_PCI_SW_SWITCHTEC=y
# end of PCI switch controller drivers
CONFIG_CXL_BUS=yCONFIG_CXL_PCI=yCONFIG_CXL_MEM_RAW_COMMANDS=yCONFIG_CXL_ACPI=yCONFIG_CXL_PMEM=yCONFIG_CXL_MEM=yCONFIG_CXL_PORT=yCONFIG_CXL_REGION=yCONFIG_PCCARD=yCONFIG_PCMCIA=yCONFIG_PCMCIA_LOAD_CIS=yCONFIG_CARDBUS=y
#
# PC-card bridges
#CONFIG_YENTA=yCONFIG_YENTA_O2=yCONFIG_YENTA_RICOH=yCONFIG_YENTA_TI=yCONFIG_YENTA_ENE_TUNE=yCONFIG_YENTA_TOSHIBA=yCONFIG_PD6729=yCONFIG_I82092=yCONFIG_PCCARD_NONSTATIC=yCONFIG_RAPIDIO=yCONFIG_RAPIDIO_TSI721=yCONFIG_RAPIDIO_DISC_TIMEOUT=30CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS=yCONFIG_RAPIDIO_DMA_ENGINE=yCONFIG_RAPIDIO_DEBUG=yCONFIG_RAPIDIO_ENUM_BASIC=yCONFIG_RAPIDIO_CHMAN=yCONFIG_RAPIDIO_MPORT_CDEV=y
#
# RapidIO Switch drivers
#CONFIG_RAPIDIO_CPS_XX=yCONFIG_RAPIDIO_CPS_GEN2=yCONFIG_RAPIDIO_RXS_GEN3=y
# end of RapidIO Switch drivers
#
# Generic Driver Options
#CONFIG_AUXILIARY_BUS=yCONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_DEVTMPFS_SAFE=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_FW_LOADER_PAGED_BUF=yCONFIG_FW_LOADER_SYSFS=yCONFIG_EXTRA_FIRMWARE=""CONFIG_FW_LOADER_USER_HELPER=yCONFIG_FW_LOADER_USER_HELPER_FALLBACK=yCONFIG_FW_LOADER_COMPRESS=yCONFIG_FW_LOADER_COMPRESS_XZ=yCONFIG_FW_LOADER_COMPRESS_ZSTD=yCONFIG_FW_UPLOAD=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=yCONFIG_DEBUG_DRIVER=yCONFIG_DEBUG_DEVRES=yCONFIG_DEBUG_TEST_DRIVER_REMOVE=yCONFIG_PM_QOS_KUNIT_TEST=yCONFIG_HMEM_REPORTING=yCONFIG_TEST_ASYNC_DRIVER_PROBE=mCONFIG_DRIVER_PE_KUNIT_TEST=yCONFIG_SOC_BUS=yCONFIG_REGMAP=yCONFIG_REGMAP_AC97=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SLIMBUS=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_SPMI=yCONFIG_REGMAP_W1=yCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_REGMAP_SOUNDWIRE=yCONFIG_REGMAP_SOUNDWIRE_MBQ=yCONFIG_REGMAP_SCCB=yCONFIG_REGMAP_I3C=yCONFIG_REGMAP_SPI_AVMM=yCONFIG_DMA_SHARED_BUFFER=yCONFIG_DMA_FENCE_TRACE=y
# end of Generic Driver Options
#
# Bus devices
#CONFIG_ARM_INTEGRATOR_LM=yCONFIG_BT1_APB=yCONFIG_BT1_AXI=yCONFIG_MOXTET=yCONFIG_HISILICON_LPC=yCONFIG_INTEL_IXP4XX_EB=yCONFIG_QCOM_EBI2=yCONFIG_MHI_BUS=yCONFIG_MHI_BUS_DEBUG=yCONFIG_MHI_BUS_PCI_GENERIC=yCONFIG_MHI_BUS_EP=y
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol #CONFIG_ARM_SCMI_PROTOCOL=y CONFIG_ARM_SCMI_HAVE_TRANSPORT=y CONFIG_ARM_SCMI_HAVE_SHMEM=y CONFIG_ARM_SCMI_HAVE_MSG=y CONFIG_ARM_SCMI_TRANSPORT_MAILBOX=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_VERSION1_COMPLIANCE=y CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_ATOMIC_ENABLE=y CONFIG_ARM_SCMI_POWER_DOMAIN=y CONFIG_ARM_SCMI_POWER_CONTROL=y
# end of ARM System Control and Management Interface Protocol
CONFIG_ARM_SCPI_PROTOCOL=yCONFIG_ARM_SCPI_POWER_DOMAIN=yCONFIG_FIRMWARE_MEMMAP=yCONFIG_EFI_PCDP=yCONFIG_DMIID=yCONFIG_DMI_SYSFS=yCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=yCONFIG_ISCSI_IBFT=yCONFIG_MTK_ADSP_IPC=yCONFIG_QCOM_SCM=yCONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT=yCONFIG_SYSFB=yCONFIG_SYSFB_SIMPLEFB=yCONFIG_TURRIS_MOX_RWTM=yCONFIG_BCM47XX_NVRAM=yCONFIG_BCM47XX_SPROM=yCONFIG_TEE_BNXT_FW=yCONFIG_CS_DSP=yCONFIG_GOOGLE_FIRMWARE=yCONFIG_GOOGLE_COREBOOT_TABLE=yCONFIG_GOOGLE_MEMCONSOLE=yCONFIG_GOOGLE_MEMCONSOLE_COREBOOT=yCONFIG_GOOGLE_VPD=y
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_VARS_PSTORE=yCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=yCONFIG_EFI_BOOTLOADER_CONTROL=yCONFIG_EFI_TEST=yCONFIG_EFI_RCI2_TABLE=yCONFIG_EFI_DISABLE_PCI_DMA=yCONFIG_EFI_CUSTOM_SSDT_OVERLAYS=yCONFIG_EFI_DISABLE_RUNTIME=yCONFIG_EFI_COCO_SECRET=y
# end of EFI (Extensible Firmware Interface) Support
CONFIG_IMX_DSP=yCONFIG_IMX_SCU=yCONFIG_IMX_SCU_PD=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_GNSS=yCONFIG_GNSS_SERIAL=yCONFIG_GNSS_MTK_SERIAL=yCONFIG_GNSS_SIRF_SERIAL=yCONFIG_GNSS_UBX_SERIAL=yCONFIG_GNSS_USB=yCONFIG_MTD=yCONFIG_MTD_TESTS=m
#
# Partition parsers
#CONFIG_MTD_AR7_PARTS=yCONFIG_MTD_BCM63XX_PARTS=yCONFIG_MTD_BRCM_U_BOOT=yCONFIG_MTD_CMDLINE_PARTS=yCONFIG_MTD_OF_PARTS=yCONFIG_MTD_OF_PARTS_BCM4908=yCONFIG_MTD_OF_PARTS_LINKSYS_NS=yCONFIG_MTD_PARSER_IMAGETAG=yCONFIG_MTD_PARSER_TRX=yCONFIG_MTD_SHARPSL_PARTS=yCONFIG_MTD_REDBOOT_PARTS=yCONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED=yCONFIG_MTD_REDBOOT_PARTS_READONLY=yCONFIG_MTD_QCOMSMEM_PARTS=y
# end of Partition parsers
#
# User Modules And Translation Layers
#CONFIG_MTD_BLKDEVS=yCONFIG_MTD_BLOCK=y
#
# Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK. #CONFIG_FTL=yCONFIG_NFTL=yCONFIG_NFTL_RW=yCONFIG_INFTL=yCONFIG_RFD_FTL=yCONFIG_SSFDC=yCONFIG_SM_FTL=yCONFIG_MTD_OOPS=yCONFIG_MTD_PSTORE=yCONFIG_MTD_SWAP=yCONFIG_MTD_PARTITIONED_MASTER=y
#
# RAM/ROM/Flash chip drivers
#CONFIG_MTD_CFI=yCONFIG_MTD_JEDECPROBE=yCONFIG_MTD_GEN_PROBE=yCONFIG_MTD_CFI_ADV_OPTIONS=yCONFIG_MTD_CFI_NOSWAP=y
# CONFIG_MTD_CFI_BE_BYTE_SWAP is not set
# CONFIG_MTD_CFI_LE_BYTE_SWAP is not setCONFIG_MTD_CFI_GEOMETRY=yCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_MAP_BANK_WIDTH_8=yCONFIG_MTD_MAP_BANK_WIDTH_16=yCONFIG_MTD_MAP_BANK_WIDTH_32=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=yCONFIG_MTD_CFI_I4=yCONFIG_MTD_CFI_I8=yCONFIG_MTD_OTP=yCONFIG_MTD_CFI_INTELEXT=yCONFIG_MTD_CFI_AMDSTD=yCONFIG_MTD_CFI_STAA=yCONFIG_MTD_CFI_UTIL=yCONFIG_MTD_RAM=yCONFIG_MTD_ROM=yCONFIG_MTD_ABSENT=y
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#CONFIG_MTD_COMPLEX_MAPPINGS=yCONFIG_MTD_PHYSMAP=yCONFIG_MTD_PHYSMAP_COMPAT=yCONFIG_MTD_PHYSMAP_START=0x8000000CONFIG_MTD_PHYSMAP_LEN=0CONFIG_MTD_PHYSMAP_BANKWIDTH=2CONFIG_MTD_PHYSMAP_OF=yCONFIG_MTD_PHYSMAP_BT1_ROM=yCONFIG_MTD_PHYSMAP_VERSATILE=yCONFIG_MTD_PHYSMAP_GEMINI=yCONFIG_MTD_PHYSMAP_GPIO_ADDR=yCONFIG_MTD_SC520CDP=yCONFIG_MTD_NETSC520=yCONFIG_MTD_TS5500=yCONFIG_MTD_PCI=yCONFIG_MTD_PCMCIA=yCONFIG_MTD_PCMCIA_ANONYMOUS=yCONFIG_MTD_INTEL_VR_NOR=yCONFIG_MTD_PLATRAM=y
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#CONFIG_MTD_PMC551=yCONFIG_MTD_PMC551_BUGFIX=yCONFIG_MTD_PMC551_DEBUG=yCONFIG_MTD_DATAFLASH=yCONFIG_MTD_DATAFLASH_WRITE_VERIFY=yCONFIG_MTD_DATAFLASH_OTP=yCONFIG_MTD_MCHP23K256=yCONFIG_MTD_MCHP48L640=yCONFIG_MTD_SPEAR_SMI=yCONFIG_MTD_SST25L=yCONFIG_MTD_SLRAM=yCONFIG_MTD_PHRAM=yCONFIG_MTD_MTDRAM=yCONFIG_MTDRAM_TOTAL_SIZE=4096CONFIG_MTDRAM_ERASE_SIZE=128CONFIG_MTD_BLOCK2MTD=y
#
# Disk-On-Chip Device Drivers
#CONFIG_MTD_DOCG3=yCONFIG_BCH_CONST_M=14CONFIG_BCH_CONST_T=4
# end of Self-contained MTD device drivers
#
# NAND
#CONFIG_MTD_NAND_CORE=yCONFIG_MTD_ONENAND=yCONFIG_MTD_ONENAND_VERIFY_WRITE=yCONFIG_MTD_ONENAND_GENERIC=yCONFIG_MTD_ONENAND_SAMSUNG=yCONFIG_MTD_ONENAND_OTP=yCONFIG_MTD_ONENAND_2X_PROGRAM=yCONFIG_MTD_RAW_NAND=y
#
# Raw/parallel NAND flash controllers
#CONFIG_MTD_NAND_DENALI=yCONFIG_MTD_NAND_DENALI_PCI=yCONFIG_MTD_NAND_DENALI_DT=yCONFIG_MTD_NAND_AMS_DELTA=yCONFIG_MTD_NAND_OMAP2=yCONFIG_MTD_NAND_OMAP_BCH=yCONFIG_MTD_NAND_OMAP_BCH_BUILD=yCONFIG_MTD_NAND_SHARPSL=yCONFIG_MTD_NAND_CAFE=yCONFIG_MTD_NAND_ATMEL=yCONFIG_MTD_NAND_MARVELL=yCONFIG_MTD_NAND_SLC_LPC32XX=yCONFIG_MTD_NAND_MLC_LPC32XX=yCONFIG_MTD_NAND_BRCMNAND=yCONFIG_MTD_NAND_BRCMNAND_BCM63XX=yCONFIG_MTD_NAND_BRCMNAND_BCMA=yCONFIG_MTD_NAND_BRCMNAND_BCMBCA=yCONFIG_MTD_NAND_BRCMNAND_BRCMSTB=yCONFIG_MTD_NAND_BRCMNAND_IPROC=yCONFIG_MTD_NAND_BCM47XXNFLASH=yCONFIG_MTD_NAND_OXNAS=yCONFIG_MTD_NAND_GPMI_NAND=yCONFIG_MTD_NAND_FSL_IFC=yCONFIG_MTD_NAND_VF610_NFC=yCONFIG_MTD_NAND_MXC=yCONFIG_MTD_NAND_SH_FLCTL=yCONFIG_MTD_NAND_DAVINCI=yCONFIG_MTD_NAND_TXX9NDFMC=yCONFIG_MTD_NAND_JZ4780=yCONFIG_MTD_NAND_INGENIC_ECC=yCONFIG_MTD_NAND_JZ4740_ECC=yCONFIG_MTD_NAND_JZ4725B_BCH=yCONFIG_MTD_NAND_JZ4780_BCH=yCONFIG_MTD_NAND_FSMC=yCONFIG_MTD_NAND_SUNXI=yCONFIG_MTD_NAND_HISI504=yCONFIG_MTD_NAND_QCOM=yCONFIG_MTD_NAND_MTK=yCONFIG_MTD_NAND_MXIC=yCONFIG_MTD_NAND_TEGRA=yCONFIG_MTD_NAND_STM32_FMC2=yCONFIG_MTD_NAND_MESON=yCONFIG_MTD_NAND_GPIO=yCONFIG_MTD_NAND_PLATFORM=yCONFIG_MTD_NAND_CADENCE=yCONFIG_MTD_NAND_ARASAN=yCONFIG_MTD_NAND_INTEL_LGM=yCONFIG_MTD_NAND_RENESAS=y
#
# Misc
#CONFIG_MTD_SM_COMMON=yCONFIG_MTD_NAND_NANDSIM=yCONFIG_MTD_NAND_RICOH=yCONFIG_MTD_NAND_DISKONCHIP=yCONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED=yCONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0CONFIG_MTD_NAND_DISKONCHIP_PROBE_HIGH=yCONFIG_MTD_NAND_DISKONCHIP_BBTWRITE=yCONFIG_MTD_SPI_NAND=y
#
# ECC engine support
#CONFIG_MTD_NAND_ECC=yCONFIG_MTD_NAND_ECC_SW_HAMMING=yCONFIG_MTD_NAND_ECC_SW_HAMMING_SMC=yCONFIG_MTD_NAND_ECC_SW_BCH=yCONFIG_MTD_NAND_ECC_MXIC=yCONFIG_MTD_NAND_ECC_MEDIATEK=y
# end of ECC engine support # end of NAND
#
# LPDDR & LPDDR2 PCM memory drivers
#CONFIG_MTD_LPDDR=yCONFIG_MTD_QINFO_PROBE=y
# end of LPDDR & LPDDR2 PCM memory drivers
CONFIG_MTD_SPI_NOR=yCONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
# CONFIG_MTD_SPI_NOR_SWP_DISABLE is not setCONFIG_MTD_SPI_NOR_SWP_DISABLE_ON_VOLATILE=y
# CONFIG_MTD_SPI_NOR_SWP_KEEP is not setCONFIG_SPI_HISI_SFC=yCONFIG_SPI_NXP_SPIFI=yCONFIG_MTD_UBI=yCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20CONFIG_MTD_UBI_FASTMAP=yCONFIG_MTD_UBI_GLUEBI=yCONFIG_MTD_UBI_BLOCK=yCONFIG_MTD_HYPERBUS=yCONFIG_HBMC_AM654=yCONFIG_DTC=yCONFIG_OF=yCONFIG_OF_UNITTEST=yCONFIG_OF_ALL_DTBS=yCONFIG_OF_FLATTREE=yCONFIG_OF_EARLY_FLATTREE=yCONFIG_OF_KOBJ=yCONFIG_OF_DYNAMIC=yCONFIG_OF_ADDRESS=yCONFIG_OF_IRQ=yCONFIG_OF_RESERVED_MEM=yCONFIG_OF_RESOLVE=yCONFIG_OF_OVERLAY=yCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=yCONFIG_PARPORT_PC=yCONFIG_PARPORT_SERIAL=yCONFIG_PARPORT_PC_FIFO=yCONFIG_PARPORT_PC_SUPERIO=yCONFIG_PARPORT_PC_PCMCIA=yCONFIG_PARPORT_AX88796=yCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#CONFIG_ISAPNP=yCONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=yCONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=yCONFIG_CDROM=yCONFIG_PARIDE=y
#
# Parallel IDE high-level drivers
#CONFIG_PARIDE_PD=yCONFIG_PARIDE_PCD=yCONFIG_PARIDE_PF=yCONFIG_PARIDE_PT=yCONFIG_PARIDE_PG=y
#
# Parallel IDE protocol modules
#CONFIG_PARIDE_ATEN=yCONFIG_PARIDE_BPCK=yCONFIG_PARIDE_COMM=yCONFIG_PARIDE_DSTR=yCONFIG_PARIDE_FIT2=yCONFIG_PARIDE_FIT3=yCONFIG_PARIDE_EPAT=yCONFIG_PARIDE_EPATC8=yCONFIG_PARIDE_EPIA=yCONFIG_PARIDE_FRIQ=yCONFIG_PARIDE_FRPW=yCONFIG_PARIDE_KBIC=yCONFIG_PARIDE_KTTI=yCONFIG_PARIDE_ON20=yCONFIG_PARIDE_ON26=yCONFIG_BLK_DEV_PCIESSD_MTIP32XX=yCONFIG_ZRAM=yCONFIG_ZRAM_DEF_COMP_LZORLE=y
# CONFIG_ZRAM_DEF_COMP_ZSTD is not set
# CONFIG_ZRAM_DEF_COMP_LZ4 is not set
# CONFIG_ZRAM_DEF_COMP_LZO is not set
# CONFIG_ZRAM_DEF_COMP_LZ4HC is not set
# CONFIG_ZRAM_DEF_COMP_842 is not setCONFIG_ZRAM_DEF_COMP="lzo-rle"CONFIG_ZRAM_WRITEBACK=yCONFIG_ZRAM_MEMORY_TRACKING=yCONFIG_BLK_DEV_LOOP=yCONFIG_BLK_DEV_LOOP_MIN_COUNT=8CONFIG_BLK_DEV_DRBD=yCONFIG_DRBD_FAULT_INJECTION=yCONFIG_BLK_DEV_NBD=yCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8CONFIG_CDROM_PKTCDVD_WCACHE=yCONFIG_ATA_OVER_ETH=yCONFIG_VIRTIO_BLK=yCONFIG_BLK_DEV_RBD=yCONFIG_BLK_DEV_UBLK=yCONFIG_BLK_DEV_RNBD=yCONFIG_BLK_DEV_RNBD_CLIENT=yCONFIG_BLK_DEV_RNBD_SERVER=y
#
# NVME Support
#CONFIG_NVME_COMMON=yCONFIG_NVME_CORE=yCONFIG_BLK_DEV_NVME=yCONFIG_NVME_MULTIPATH=yCONFIG_NVME_VERBOSE_ERRORS=yCONFIG_NVME_HWMON=yCONFIG_NVME_FABRICS=yCONFIG_NVME_RDMA=yCONFIG_NVME_FC=yCONFIG_NVME_TCP=yCONFIG_NVME_AUTH=yCONFIG_NVME_APPLE=yCONFIG_NVME_TARGET=yCONFIG_NVME_TARGET_PASSTHRU=yCONFIG_NVME_TARGET_LOOP=yCONFIG_NVME_TARGET_RDMA=yCONFIG_NVME_TARGET_FC=yCONFIG_NVME_TARGET_FCLOOP=yCONFIG_NVME_TARGET_TCP=yCONFIG_NVME_TARGET_AUTH=y
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=yCONFIG_AD525X_DPOT=yCONFIG_AD525X_DPOT_I2C=yCONFIG_AD525X_DPOT_SPI=yCONFIG_DUMMY_IRQ=yCONFIG_PHANTOM=yCONFIG_TIFM_CORE=yCONFIG_TIFM_7XX1=yCONFIG_ICS932S401=yCONFIG_ATMEL_SSC=yCONFIG_ENCLOSURE_SERVICES=yCONFIG_GEHC_ACHC=yCONFIG_HI6421V600_IRQ=yCONFIG_HP_ILO=yCONFIG_QCOM_COINCELL=yCONFIG_QCOM_FASTRPC=yCONFIG_APDS9802ALS=yCONFIG_ISL29003=yCONFIG_ISL29020=yCONFIG_SENSORS_TSL2550=yCONFIG_SENSORS_BH1770=yCONFIG_SENSORS_APDS990X=yCONFIG_HMC6352=yCONFIG_DS1682=yCONFIG_PCH_PHUB=yCONFIG_LATTICE_ECP3_CONFIG=yCONFIG_SRAM=yCONFIG_DW_XDATA_PCIE=yCONFIG_PCI_ENDPOINT_TEST=yCONFIG_XILINX_SDFEC=yCONFIG_MISC_RTSX=yCONFIG_HISI_HIKEY_USB=yCONFIG_OPEN_DICE=yCONFIG_VCPU_STALL_DETECTOR=yCONFIG_C2PORT=y
#
# EEPROM support
#CONFIG_EEPROM_AT24=yCONFIG_EEPROM_AT25=yCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_MAX6875=yCONFIG_EEPROM_93CX6=yCONFIG_EEPROM_93XX46=yCONFIG_EEPROM_IDT_89HPESX=yCONFIG_EEPROM_EE1004=y
# end of EEPROM support
CONFIG_CB710_CORE=yCONFIG_CB710_DEBUG=yCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #CONFIG_TI_ST=y
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_I2C=yCONFIG_ALTERA_STAPL=yCONFIG_GENWQE=yCONFIG_GENWQE_PLATFORM_ERROR_RECOVERY=0CONFIG_ECHO=yCONFIG_BCM_VK=yCONFIG_BCM_VK_TTY=yCONFIG_MISC_ALCOR_PCI=yCONFIG_MISC_RTSX_PCI=yCONFIG_MISC_RTSX_USB=yCONFIG_HABANA_AI=yCONFIG_UACCE=yCONFIG_PVPANIC=yCONFIG_PVPANIC_MMIO=yCONFIG_PVPANIC_PCI=yCONFIG_GP_PCI1XXXX=y
# end of Misc devices
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=yCONFIG_SCSI_COMMON=yCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=yCONFIG_BLK_DEV_SR=yCONFIG_CHR_DEV_SG=yCONFIG_BLK_DEV_BSG=yCONFIG_CHR_DEV_SCH=yCONFIG_SCSI_ENCLOSURE=yCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=yCONFIG_SCSI_FC_ATTRS=yCONFIG_SCSI_ISCSI_ATTRS=yCONFIG_SCSI_SAS_ATTRS=yCONFIG_SCSI_SAS_LIBSAS=yCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=y
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=yCONFIG_ISCSI_BOOT_SYSFS=yCONFIG_SCSI_CXGB3_ISCSI=yCONFIG_SCSI_CXGB4_ISCSI=yCONFIG_SCSI_BNX2_ISCSI=yCONFIG_SCSI_BNX2X_FCOE=yCONFIG_BE2ISCSI=yCONFIG_BLK_DEV_3W_XXXX_RAID=yCONFIG_SCSI_HPSA=yCONFIG_SCSI_3W_9XXX=yCONFIG_SCSI_3W_SAS=yCONFIG_SCSI_ACARD=yCONFIG_SCSI_AACRAID=yCONFIG_SCSI_AIC7XXX=yCONFIG_AIC7XXX_CMDS_PER_DEVICE=32CONFIG_AIC7XXX_RESET_DELAY_MS=5000CONFIG_AIC7XXX_DEBUG_ENABLE=yCONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_AIC7XXX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC79XX=yCONFIG_AIC79XX_CMDS_PER_DEVICE=32CONFIG_AIC79XX_RESET_DELAY_MS=5000CONFIG_AIC79XX_DEBUG_ENABLE=yCONFIG_AIC79XX_DEBUG_MASK=0CONFIG_AIC79XX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC94XX=yCONFIG_AIC94XX_DEBUG=yCONFIG_SCSI_HISI_SAS=yCONFIG_SCSI_HISI_SAS_PCI=yCONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE=yCONFIG_SCSI_MVSAS=yCONFIG_SCSI_MVSAS_DEBUG=yCONFIG_SCSI_MVSAS_TASKLET=yCONFIG_SCSI_MVUMI=yCONFIG_SCSI_ADVANSYS=yCONFIG_SCSI_ARCMSR=yCONFIG_SCSI_ESAS2R=yCONFIG_MEGARAID_NEWGEN=yCONFIG_MEGARAID_MM=yCONFIG_MEGARAID_MAILBOX=yCONFIG_MEGARAID_LEGACY=yCONFIG_MEGARAID_SAS=yCONFIG_SCSI_MPT3SAS=yCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128CONFIG_SCSI_MPT2SAS=yCONFIG_SCSI_MPI3MR=yCONFIG_SCSI_SMARTPQI=yCONFIG_SCSI_HPTIOP=yCONFIG_SCSI_BUSLOGIC=yCONFIG_SCSI_FLASHPOINT=yCONFIG_SCSI_MYRB=yCONFIG_SCSI_MYRS=yCONFIG_LIBFC=yCONFIG_LIBFCOE=yCONFIG_FCOE=yCONFIG_SCSI_SNIC=yCONFIG_SCSI_SNIC_DEBUG_FS=yCONFIG_SCSI_DMX3191D=yCONFIG_SCSI_FDOMAIN=yCONFIG_SCSI_FDOMAIN_PCI=yCONFIG_SCSI_IPS=yCONFIG_SCSI_INITIO=yCONFIG_SCSI_INIA100=yCONFIG_SCSI_PPA=yCONFIG_SCSI_IMM=yCONFIG_SCSI_IZIP_EPP16=yCONFIG_SCSI_IZIP_SLOW_CTR=yCONFIG_SCSI_STEX=yCONFIG_SCSI_SYM53C8XX_2=yCONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64CONFIG_SCSI_SYM53C8XX_MMIO=yCONFIG_SCSI_IPR=yCONFIG_SCSI_IPR_TRACE=yCONFIG_SCSI_IPR_DUMP=yCONFIG_SCSI_QLOGIC_1280=yCONFIG_SCSI_QLA_FC=yCONFIG_TCM_QLA2XXX=yCONFIG_TCM_QLA2XXX_DEBUG=yCONFIG_SCSI_QLA_ISCSI=yCONFIG_QEDI=yCONFIG_QEDF=yCONFIG_SCSI_LPFC=yCONFIG_SCSI_LPFC_DEBUG_FS=yCONFIG_SCSI_EFCT=y
CONFIG_SCSI_DC395x=yCONFIG_SCSI_AM53C974=yCONFIG_SCSI_WD719X=yCONFIG_SCSI_DEBUG=yCONFIG_SCSI_PMCRAID=yCONFIG_SCSI_PM8001=yCONFIG_SCSI_BFA_FC=yCONFIG_SCSI_VIRTIO=yCONFIG_SCSI_CHELSIO_FCOE=yCONFIG_SCSI_LOWLEVEL_PCMCIA=yCONFIG_PCMCIA_AHA152X=mCONFIG_PCMCIA_FDOMAIN=mCONFIG_PCMCIA_NINJA_SCSI=mCONFIG_PCMCIA_QLOGIC=mCONFIG_PCMCIA_SYM53C500=mCONFIG_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=yCONFIG_ATA_NONSTANDARD=yCONFIG_SATA_HOST=yCONFIG_PATA_TIMINGS=yCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_FORCE=yCONFIG_ATA_ACPI=yCONFIG_SATA_ZPODD=yCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=yCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=yCONFIG_AHCI_BRCM=yCONFIG_AHCI_DA850=yCONFIG_AHCI_DM816=yCONFIG_AHCI_DWC=yCONFIG_AHCI_ST=yCONFIG_AHCI_IMX=yCONFIG_AHCI_CEVA=yCONFIG_AHCI_MTK=yCONFIG_AHCI_MVEBU=yCONFIG_AHCI_SUNXI=yCONFIG_AHCI_TEGRA=yCONFIG_AHCI_XGENE=yCONFIG_AHCI_QORIQ=yCONFIG_SATA_FSL=yCONFIG_SATA_GEMINI=yCONFIG_SATA_AHCI_SEATTLE=yCONFIG_SATA_INIC162X=yCONFIG_SATA_ACARD_AHCI=yCONFIG_SATA_SIL24=yCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#CONFIG_PDC_ADMA=yCONFIG_SATA_QSTOR=yCONFIG_SATA_SX4=yCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=yCONFIG_SATA_DWC=yCONFIG_SATA_DWC_OLD_DMA=yCONFIG_SATA_HIGHBANK=yCONFIG_SATA_MV=yCONFIG_SATA_NV=yCONFIG_SATA_PROMISE=yCONFIG_SATA_RCAR=yCONFIG_SATA_SIL=yCONFIG_SATA_SIS=yCONFIG_SATA_SVW=yCONFIG_SATA_ULI=yCONFIG_SATA_VIA=yCONFIG_SATA_VITESSE=y
#
# PATA SFF controllers with BMDMA
#CONFIG_PATA_ALI=yCONFIG_PATA_AMD=yCONFIG_PATA_ARASAN_CF=yCONFIG_PATA_ARTOP=yCONFIG_PATA_ATIIXP=yCONFIG_PATA_ATP867X=yCONFIG_PATA_BK3710=yCONFIG_PATA_CMD64X=yCONFIG_PATA_CS5520=yCONFIG_PATA_CS5530=yCONFIG_PATA_CS5536=yCONFIG_PATA_CYPRESS=yCONFIG_PATA_EFAR=yCONFIG_PATA_FTIDE010=yCONFIG_PATA_HPT366=yCONFIG_PATA_HPT37X=yCONFIG_PATA_HPT3X2N=yCONFIG_PATA_HPT3X3=yCONFIG_PATA_HPT3X3_DMA=yCONFIG_PATA_IMX=yCONFIG_PATA_IT8213=yCONFIG_PATA_IT821X=yCONFIG_PATA_JMICRON=yCONFIG_PATA_MARVELL=yCONFIG_PATA_NETCELL=yCONFIG_PATA_NINJA32=yCONFIG_PATA_NS87415=yCONFIG_PATA_OLDPIIX=yCONFIG_PATA_OPTIDMA=yCONFIG_PATA_PDC2027X=yCONFIG_PATA_PDC_OLD=yCONFIG_PATA_RADISYS=yCONFIG_PATA_RDC=yCONFIG_PATA_SC1200=yCONFIG_PATA_SCH=yCONFIG_PATA_SERVERWORKS=yCONFIG_PATA_SIL680=yCONFIG_PATA_SIS=yCONFIG_PATA_TOSHIBA=yCONFIG_PATA_TRIFLEX=yCONFIG_PATA_VIA=yCONFIG_PATA_PXA=yCONFIG_PATA_WINBOND=y
#
# PIO-only SFF controllers
#CONFIG_PATA_CMD640_PCI=yCONFIG_PATA_ISAPNP=yCONFIG_PATA_IXP4XX_CF=yCONFIG_PATA_MPIIX=yCONFIG_PATA_NS87410=yCONFIG_PATA_OPTI=yCONFIG_PATA_PCMCIA=yCONFIG_PATA_PLATFORM=yCONFIG_PATA_OF_PLATFORM=yCONFIG_PATA_RZ1000=yCONFIG_PATA_SAMSUNG_CF=y
#
# Generic fallback / legacy drivers
#CONFIG_PATA_ACPI=yCONFIG_ATA_GENERIC=yCONFIG_PATA_LEGACY=yCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=yCONFIG_MD_RAID0=yCONFIG_MD_RAID1=yCONFIG_MD_RAID10=yCONFIG_MD_RAID456=yCONFIG_MD_MULTIPATH=yCONFIG_MD_FAULTY=yCONFIG_MD_CLUSTER=yCONFIG_BCACHE=yCONFIG_BCACHE_DEBUG=y CONFIG_BCACHE_CLOSURES_DEBUG=y CONFIG_BCACHE_ASYNC_REGISTRATION=y CONFIG_BLK_DEV_DM_BUILTIN=yCONFIG_BLK_DEV_DM=yCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=y CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING=y CONFIG_DM_DEBUG_BLOCK_STACK_TRACING=y CONFIG_DM_BIO_PRISON=y CONFIG_DM_PERSISTENT_DATA=y CONFIG_DM_UNSTRIPED=yCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=y CONFIG_DM_THIN_PROVISIONING=yCONFIG_DM_CACHE=yCONFIG_DM_CACHE_SMQ=yCONFIG_DM_WRITECACHE=yCONFIG_DM_EBS=yCONFIG_DM_ERA=yCONFIG_DM_CLONE=yCONFIG_DM_MIRROR=yCONFIG_DM_LOG_USERSPACE=yCONFIG_DM_RAID=yCONFIG_DM_ZERO=yCONFIG_DM_MULTIPATH=yCONFIG_DM_MULTIPATH_QL=y CONFIG_DM_MULTIPATH_ST=y CONFIG_DM_MULTIPATH_HST=y CONFIG_DM_MULTIPATH_IOA=yCONFIG_DM_DELAY=yCONFIG_DM_DUST=yCONFIG_DM_INIT=yCONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=yCONFIG_DM_VERITY=y CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y CONFIG_DM_VERITY_FEC=yCONFIG_DM_SWITCH=yCONFIG_DM_LOG_WRITES=yCONFIG_DM_INTEGRITY=yCONFIG_DM_ZONED=yCONFIG_DM_AUDIT=yCONFIG_TARGET_CORE=yCONFIG_TCM_IBLOCK=yCONFIG_TCM_FILEIO=yCONFIG_TCM_PSCSI=yCONFIG_TCM_USER2=yCONFIG_LOOPBACK_TARGET=yCONFIG_TCM_FC=yCONFIG_ISCSI_TARGET=y CONFIG_ISCSI_TARGET_CXGB4=yCONFIG_SBP_TARGET=yCONFIG_FUSION=yCONFIG_FUSION_SPI=yCONFIG_FUSION_FC=yCONFIG_FUSION_SAS=yCONFIG_FUSION_MAX_SGE=128CONFIG_FUSION_CTL=yCONFIG_FUSION_LAN=yCONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=yCONFIG_FIREWIRE_OHCI=yCONFIG_FIREWIRE_SBP2=yCONFIG_FIREWIRE_NET=yCONFIG_FIREWIRE_NOSY=y
# end of IEEE 1394 (FireWire) support
CONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=yCONFIG_BONDING=yCONFIG_DUMMY=yCONFIG_WIREGUARD=yCONFIG_WIREGUARD_DEBUG=yCONFIG_EQUALIZER=yCONFIG_NET_FC=yCONFIG_IFB=yCONFIG_NET_TEAM=yCONFIG_NET_TEAM_MODE_BROADCAST=yCONFIG_NET_TEAM_MODE_ROUNDROBIN=yCONFIG_NET_TEAM_MODE_RANDOM=yCONFIG_NET_TEAM_MODE_ACTIVEBACKUP=yCONFIG_NET_TEAM_MODE_LOADBALANCE=yCONFIG_MACVLAN=yCONFIG_MACVTAP=yCONFIG_IPVLAN_L3S=yCONFIG_IPVLAN=yCONFIG_IPVTAP=yCONFIG_VXLAN=yCONFIG_GENEVE=yCONFIG_BAREUDP=yCONFIG_GTP=yCONFIG_AMT=yCONFIG_MACSEC=yCONFIG_NETCONSOLE=yCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_NTB_NETDEV=yCONFIG_RIONET=yCONFIG_RIONET_TX_SIZE=128CONFIG_RIONET_RX_SIZE=128CONFIG_TUN=yCONFIG_TAP=yCONFIG_TUN_VNET_CROSS_LE=yCONFIG_VETH=yCONFIG_VIRTIO_NET=yCONFIG_NLMON=yCONFIG_NET_VRF=yCONFIG_VSOCKMON=yCONFIG_MHI_NET=yCONFIG_SUNGEM_PHY=yCONFIG_ARCNET=yCONFIG_ARCNET_1201=yCONFIG_ARCNET_1051=yCONFIG_ARCNET_RAW=yCONFIG_ARCNET_CAP=y
CONFIG_ARCNET_COM90xx=y
CONFIG_ARCNET_COM90xxIO=yCONFIG_ARCNET_RIM_I=yCONFIG_ARCNET_COM20020=yCONFIG_ARCNET_COM20020_PCI=yCONFIG_ARCNET_COM20020_CS=yCONFIG_ATM_DRIVERS=yCONFIG_ATM_DUMMY=yCONFIG_ATM_TCP=yCONFIG_ATM_LANAI=yCONFIG_ATM_ENI=yCONFIG_ATM_ENI_DEBUG=yCONFIG_ATM_ENI_TUNE_BURST=yCONFIG_ATM_ENI_BURST_TX_16W=yCONFIG_ATM_ENI_BURST_TX_8W=yCONFIG_ATM_ENI_BURST_TX_4W=yCONFIG_ATM_ENI_BURST_TX_2W=yCONFIG_ATM_ENI_BURST_RX_16W=yCONFIG_ATM_ENI_BURST_RX_8W=yCONFIG_ATM_ENI_BURST_RX_4W=yCONFIG_ATM_ENI_BURST_RX_2W=yCONFIG_ATM_NICSTAR=yCONFIG_ATM_NICSTAR_USE_SUNI=yCONFIG_ATM_NICSTAR_USE_IDT77105=yCONFIG_ATM_IDT77252=yCONFIG_ATM_IDT77252_DEBUG=yCONFIG_ATM_IDT77252_RCV_ALL=yCONFIG_ATM_IDT77252_USE_SUNI=yCONFIG_ATM_IA=yCONFIG_ATM_IA_DEBUG=yCONFIG_ATM_FORE200E=yCONFIG_ATM_FORE200E_USE_TASKLET=yCONFIG_ATM_FORE200E_TX_RETRY=16CONFIG_ATM_FORE200E_DEBUG=0CONFIG_ATM_HE=yCONFIG_ATM_HE_USE_SUNI=yCONFIG_ATM_SOLOS=yCONFIG_CAIF_DRIVERS=yCONFIG_CAIF_TTY=yCONFIG_CAIF_VIRTIO=y
#
# Distributed Switch Architecture drivers
#CONFIG_B53=yCONFIG_B53_SPI_DRIVER=yCONFIG_B53_MDIO_DRIVER=yCONFIG_B53_MMAP_DRIVER=yCONFIG_B53_SRAB_DRIVER=yCONFIG_B53_SERDES=yCONFIG_NET_DSA_BCM_SF2=yCONFIG_NET_DSA_LOOP=yCONFIG_NET_DSA_HIRSCHMANN_HELLCREEK=yCONFIG_NET_DSA_LANTIQ_GSWIP=yCONFIG_NET_DSA_MT7530=yCONFIG_NET_DSA_MV88E6060=yCONFIG_NET_DSA_MICROCHIP_KSZ_COMMON=yCONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=yCONFIG_NET_DSA_MICROCHIP_KSZ_SPI=yCONFIG_NET_DSA_MICROCHIP_KSZ8863_SMI=yCONFIG_NET_DSA_MV88E6XXX=yCONFIG_NET_DSA_MV88E6XXX_PTP=yCONFIG_NET_DSA_MSCC_FELIX=yCONFIG_NET_DSA_MSCC_SEVILLE=yCONFIG_NET_DSA_AR9331=yCONFIG_NET_DSA_QCA8K=yCONFIG_NET_DSA_SJA1105=yCONFIG_NET_DSA_SJA1105_PTP=yCONFIG_NET_DSA_SJA1105_TAS=yCONFIG_NET_DSA_SJA1105_VL=yCONFIG_NET_DSA_XRS700X=yCONFIG_NET_DSA_XRS700X_I2C=yCONFIG_NET_DSA_XRS700X_MDIO=yCONFIG_NET_DSA_REALTEK=yCONFIG_NET_DSA_REALTEK_MDIO=yCONFIG_NET_DSA_REALTEK_SMI=yCONFIG_NET_DSA_REALTEK_RTL8365MB=yCONFIG_NET_DSA_REALTEK_RTL8366RB=yCONFIG_NET_DSA_SMSC_LAN9303=yCONFIG_NET_DSA_SMSC_LAN9303_I2C=yCONFIG_NET_DSA_SMSC_LAN9303_MDIO=yCONFIG_NET_DSA_VITESSE_VSC73XX=yCONFIG_NET_DSA_VITESSE_VSC73XX_SPI=yCONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM=y
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=yCONFIG_NET_VENDOR_3COM=yCONFIG_PCMCIA_3C574=yCONFIG_PCMCIA_3C589=yCONFIG_VORTEX=yCONFIG_TYPHOON=yCONFIG_NET_VENDOR_ACTIONS=yCONFIG_OWL_EMAC=yCONFIG_NET_VENDOR_ADAPTEC=yCONFIG_ADAPTEC_STARFIRE=yCONFIG_NET_VENDOR_AGERE=yCONFIG_ET131X=yCONFIG_NET_VENDOR_ALACRITECH=yCONFIG_SLICOSS=yCONFIG_NET_VENDOR_ALTEON=yCONFIG_ACENIC=yCONFIG_ACENIC_OMIT_TIGON_I=yCONFIG_ALTERA_TSE=yCONFIG_NET_VENDOR_AMAZON=yCONFIG_ENA_ETHERNET=yCONFIG_NET_VENDOR_AMD=yCONFIG_AMD8111_ETH=yCONFIG_PCNET32=yCONFIG_PCMCIA_NMCLAN=yCONFIG_AMD_XGBE=yCONFIG_AMD_XGBE_DCB=yCONFIG_NET_XGENE=yCONFIG_NET_XGENE_V2=yCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_AQTION=yCONFIG_NET_VENDOR_ARC=yCONFIG_ARC_EMAC_CORE=yCONFIG_ARC_EMAC=yCONFIG_EMAC_ROCKCHIP=yCONFIG_NET_VENDOR_ASIX=yCONFIG_SPI_AX88796C=yCONFIG_SPI_AX88796C_COMPRESSION=yCONFIG_NET_VENDOR_ATHEROS=yCONFIG_ATL2=yCONFIG_ATL1=yCONFIG_ATL1E=yCONFIG_ATL1C=yCONFIG_ALX=yCONFIG_CX_ECAT=yCONFIG_NET_VENDOR_BROADCOM=yCONFIG_B44=yCONFIG_B44_PCI_AUTOSELECT=yCONFIG_B44_PCICORE_AUTOSELECT=yCONFIG_B44_PCI=yCONFIG_BCM4908_ENET=yCONFIG_BCMGENET=yCONFIG_BNX2=yCONFIG_CNIC=yCONFIG_TIGON3=yCONFIG_TIGON3_HWMON=yCONFIG_BNX2X=yCONFIG_BNX2X_SRIOV=yCONFIG_BGMAC=yCONFIG_BGMAC_BCMA=yCONFIG_BGMAC_PLATFORM=yCONFIG_SYSTEMPORT=yCONFIG_BNXT=yCONFIG_BNXT_SRIOV=yCONFIG_BNXT_FLOWER_OFFLOAD=yCONFIG_BNXT_DCB=yCONFIG_BNXT_HWMON=yCONFIG_NET_VENDOR_CADENCE=yCONFIG_MACB=yCONFIG_MACB_USE_HWSTAMP=yCONFIG_MACB_PCI=yCONFIG_NET_CALXEDA_XGMAC=yCONFIG_NET_VENDOR_CAVIUM=yCONFIG_THUNDER_NIC_PF=yCONFIG_THUNDER_NIC_VF=yCONFIG_THUNDER_NIC_BGX=yCONFIG_THUNDER_NIC_RGX=yCONFIG_CAVIUM_PTP=yCONFIG_LIQUIDIO=yCONFIG_LIQUIDIO_VF=yCONFIG_NET_VENDOR_CHELSIO=yCONFIG_CHELSIO_T1=yCONFIG_CHELSIO_T1_1G=yCONFIG_CHELSIO_T3=yCONFIG_CHELSIO_T4=yCONFIG_CHELSIO_T4_DCB=yCONFIG_CHELSIO_T4_FCOE=yCONFIG_CHELSIO_T4VF=yCONFIG_CHELSIO_LIB=yCONFIG_CHELSIO_INLINE_CRYPTO=yCONFIG_CRYPTO_DEV_CHELSIO_TLS=yCONFIG_CHELSIO_IPSEC_INLINE=yCONFIG_CHELSIO_TLS_DEVICE=yCONFIG_NET_VENDOR_CIRRUS=y
CONFIG_CS89x0=y
CONFIG_CS89x0_PLATFORM=yCONFIG_EP93XX_ETH=yCONFIG_NET_VENDOR_CISCO=yCONFIG_ENIC=yCONFIG_NET_VENDOR_CORTINA=yCONFIG_GEMINI_ETHERNET=yCONFIG_NET_VENDOR_DAVICOM=yCONFIG_DM9000=yCONFIG_DM9000_FORCE_SIMPLE_PHY_POLL=yCONFIG_DM9051=yCONFIG_DNET=yCONFIG_NET_VENDOR_DEC=yCONFIG_NET_TULIP=yCONFIG_DE2104X=yCONFIG_DE2104X_DSL=0CONFIG_TULIP=yCONFIG_TULIP_MWI=yCONFIG_TULIP_MMIO=yCONFIG_TULIP_NAPI=yCONFIG_TULIP_NAPI_HW_MITIGATION=yCONFIG_WINBOND_840=yCONFIG_DM9102=yCONFIG_ULI526X=yCONFIG_PCMCIA_XIRCOM=yCONFIG_NET_VENDOR_DLINK=yCONFIG_DL2K=yCONFIG_SUNDANCE=yCONFIG_SUNDANCE_MMIO=yCONFIG_NET_VENDOR_EMULEX=yCONFIG_BE2NET=yCONFIG_BE2NET_HWMON=yCONFIG_BE2NET_BE2=yCONFIG_BE2NET_BE3=yCONFIG_BE2NET_LANCER=yCONFIG_BE2NET_SKYHAWK=yCONFIG_NET_VENDOR_ENGLEDER=yCONFIG_TSNEP=yCONFIG_TSNEP_SELFTESTS=yCONFIG_NET_VENDOR_EZCHIP=yCONFIG_EZCHIP_NPS_MANAGEMENT_ENET=yCONFIG_NET_VENDOR_FARADAY=yCONFIG_NET_VENDOR_FREESCALE=yCONFIG_FEC=yCONFIG_FSL_FMAN=yCONFIG_FSL_PQ_MDIO=yCONFIG_FSL_XGMAC_MDIO=yCONFIG_GIANFAR=yCONFIG_FSL_DPAA2_SWITCH=yCONFIG_FSL_ENETC=yCONFIG_FSL_ENETC_VF=yCONFIG_FSL_ENETC_IERB=yCONFIG_FSL_ENETC_MDIO=yCONFIG_FSL_ENETC_PTP_CLOCK=yCONFIG_FSL_ENETC_QOS=yCONFIG_NET_VENDOR_FUJITSU=yCONFIG_PCMCIA_FMVJ18X=yCONFIG_NET_VENDOR_FUNGIBLE=yCONFIG_FUN_CORE=yCONFIG_FUN_ETH=yCONFIG_NET_VENDOR_GOOGLE=yCONFIG_NET_VENDOR_HISILICON=yCONFIG_HIX5HD2_GMAC=yCONFIG_HISI_FEMAC=yCONFIG_HIP04_ETH=yCONFIG_HI13X1_GMAC=yCONFIG_HNS_MDIO=yCONFIG_HNS=yCONFIG_HNS_DSAF=yCONFIG_HNS_ENET=yCONFIG_HNS3=yCONFIG_HNS3_HCLGE=yCONFIG_HNS3_DCB=yCONFIG_HNS3_HCLGEVF=yCONFIG_HNS3_ENET=yCONFIG_NET_VENDOR_HUAWEI=yCONFIG_NET_VENDOR_I825XX=yCONFIG_NET_VENDOR_INTEL=yCONFIG_E100=yCONFIG_E1000=yCONFIG_E1000E=yCONFIG_IGB=yCONFIG_IGB_HWMON=yCONFIG_IGBVF=yCONFIG_IXGB=yCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=yCONFIG_IXGBE_DCB=yCONFIG_IXGBE_IPSEC=yCONFIG_IXGBEVF=yCONFIG_IXGBEVF_IPSEC=yCONFIG_I40E=yCONFIG_I40E_DCB=yCONFIG_IAVF=yCONFIG_I40EVF=yCONFIG_ICE=yCONFIG_ICE_SWITCHDEV=yCONFIG_FM10K=yCONFIG_IGC=yCONFIG_NET_VENDOR_WANGXUN=yCONFIG_LIBWX=yCONFIG_NGBE=yCONFIG_TXGBE=yCONFIG_JME=yCONFIG_KORINA=yCONFIG_NET_VENDOR_ADI=yCONFIG_ADIN1110=yCONFIG_NET_VENDOR_LITEX=yCONFIG_LITEX_LITEETH=yCONFIG_NET_VENDOR_MARVELL=yCONFIG_MV643XX_ETH=yCONFIG_MVMDIO=yCONFIG_MVNETA=yCONFIG_MVPP2=yCONFIG_MVPP2_PTP=yCONFIG_PXA168_ETH=yCONFIG_SKGE=yCONFIG_SKGE_DEBUG=yCONFIG_SKGE_GENESIS=yCONFIG_SKY2=yCONFIG_SKY2_DEBUG=yCONFIG_OCTEONTX2_MBOX=yCONFIG_OCTEONTX2_AF=yCONFIG_NDC_DIS_DYNAMIC_CACHING=yCONFIG_OCTEONTX2_PF=yCONFIG_OCTEONTX2_VF=yCONFIG_OCTEON_EP=yCONFIG_PRESTERA=yCONFIG_PRESTERA_PCI=yCONFIG_NET_VENDOR_MEDIATEK=yCONFIG_NET_MEDIATEK_SOC_WED=yCONFIG_NET_MEDIATEK_SOC=yCONFIG_NET_MEDIATEK_STAR_EMAC=yCONFIG_NET_VENDOR_MELLANOX=yCONFIG_MLX4_EN=yCONFIG_MLX4_EN_DCB=yCONFIG_MLX4_CORE=yCONFIG_MLX4_DEBUG=yCONFIG_MLX4_CORE_GEN2=yCONFIG_MLX5_CORE=yCONFIG_MLX5_FPGA=yCONFIG_MLX5_CORE_EN=yCONFIG_MLX5_EN_ARFS=yCONFIG_MLX5_EN_RXNFC=yCONFIG_MLX5_MPFS=yCONFIG_MLX5_ESWITCH=yCONFIG_MLX5_BRIDGE=yCONFIG_MLX5_CLS_ACT=yCONFIG_MLX5_TC_CT=yCONFIG_MLX5_TC_SAMPLE=yCONFIG_MLX5_CORE_EN_DCB=yCONFIG_MLX5_CORE_IPOIB=yCONFIG_MLX5_EN_MACSEC=yCONFIG_MLX5_EN_IPSEC=yCONFIG_MLX5_EN_TLS=yCONFIG_MLX5_SW_STEERING=yCONFIG_MLX5_SF=yCONFIG_MLX5_SF_MANAGER=yCONFIG_MLXSW_CORE=yCONFIG_MLXSW_CORE_HWMON=yCONFIG_MLXSW_CORE_THERMAL=yCONFIG_MLXSW_PCI=yCONFIG_MLXSW_I2C=yCONFIG_MLXSW_SPECTRUM=yCONFIG_MLXSW_SPECTRUM_DCB=yCONFIG_MLXSW_MINIMAL=yCONFIG_MLXFW=yCONFIG_MLXBF_GIGE=yCONFIG_NET_VENDOR_MICREL=yCONFIG_KS8842=yCONFIG_KS8851=yCONFIG_KS8851_MLL=yCONFIG_KSZ884X_PCI=yCONFIG_NET_VENDOR_MICROCHIP=yCONFIG_ENC28J60=yCONFIG_ENC28J60_WRITEVERIFY=yCONFIG_ENCX24J600=yCONFIG_LAN743X=yCONFIG_LAN966X_SWITCH=yCONFIG_SPARX5_SWITCH=yCONFIG_SPARX5_DCB=yCONFIG_VCAP=yCONFIG_VCAP_KUNIT_TEST=yCONFIG_NET_VENDOR_MICROSEMI=yCONFIG_MSCC_OCELOT_SWITCH_LIB=yCONFIG_MSCC_OCELOT_SWITCH=yCONFIG_NET_VENDOR_MICROSOFT=yCONFIG_NET_VENDOR_MYRI=yCONFIG_MYRI10GE=yCONFIG_NET_VENDOR_NI=yCONFIG_NI_XGE_MANAGEMENT_ENET=yCONFIG_NET_VENDOR_NATSEMI=yCONFIG_NATSEMI=yCONFIG_NS83820=yCONFIG_NET_VENDOR_NETERION=yCONFIG_S2IO=yCONFIG_NET_VENDOR_NETRONOME=yCONFIG_NFP=yCONFIG_NFP_APP_FLOWER=yCONFIG_NFP_APP_ABM_NIC=yCONFIG_NFP_DEBUG=yCONFIG_NET_VENDOR_8390=yCONFIG_PCMCIA_AXNET=yCONFIG_AX88796=yCONFIG_AX88796_93CX6=yCONFIG_NE2K_PCI=yCONFIG_PCMCIA_PCNET=yCONFIG_NET_VENDOR_NVIDIA=yCONFIG_FORCEDETH=yCONFIG_LPC_ENET=yCONFIG_NET_VENDOR_OKI=yCONFIG_PCH_GBE=yCONFIG_ETHOC=yCONFIG_NET_VENDOR_PACKET_ENGINES=yCONFIG_HAMACHI=yCONFIG_YELLOWFIN=yCONFIG_NET_VENDOR_PENSANDO=yCONFIG_IONIC=yCONFIG_NET_VENDOR_QLOGIC=yCONFIG_QLA3XXX=yCONFIG_QLCNIC=yCONFIG_QLCNIC_SRIOV=yCONFIG_QLCNIC_DCB=yCONFIG_QLCNIC_HWMON=yCONFIG_NETXEN_NIC=yCONFIG_QED=yCONFIG_QED_LL2=yCONFIG_QED_SRIOV=yCONFIG_QEDE=yCONFIG_QED_RDMA=yCONFIG_QED_ISCSI=yCONFIG_QED_FCOE=yCONFIG_QED_OOO=yCONFIG_NET_VENDOR_BROCADE=yCONFIG_BNA=yCONFIG_NET_VENDOR_QUALCOMM=yCONFIG_QCA7000=yCONFIG_QCA7000_SPI=yCONFIG_QCA7000_UART=yCONFIG_QCOM_EMAC=yCONFIG_RMNET=yCONFIG_NET_VENDOR_RDC=yCONFIG_R6040=yCONFIG_NET_VENDOR_REALTEK=yCONFIG_8139CP=yCONFIG_8139TOO=yCONFIG_8139TOO_PIO=yCONFIG_8139TOO_TUNE_TWISTER=yCONFIG_8139TOO_8129=yCONFIG_8139_OLD_RX_RESET=yCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_SH_ETH=yCONFIG_RAVB=yCONFIG_RENESAS_ETHER_SWITCH=yCONFIG_NET_VENDOR_ROCKER=yCONFIG_ROCKER=yCONFIG_NET_VENDOR_SAMSUNG=yCONFIG_SXGBE_ETH=yCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SILAN=yCONFIG_SC92031=yCONFIG_NET_VENDOR_SIS=yCONFIG_SIS900=yCONFIG_SIS190=yCONFIG_NET_VENDOR_SOLARFLARE=yCONFIG_SFC=yCONFIG_SFC_MTD=yCONFIG_SFC_MCDI_MON=yCONFIG_SFC_SRIOV=yCONFIG_SFC_MCDI_LOGGING=yCONFIG_SFC_FALCON=yCONFIG_SFC_FALCON_MTD=yCONFIG_SFC_SIENA=yCONFIG_SFC_SIENA_MTD=yCONFIG_SFC_SIENA_MCDI_MON=yCONFIG_SFC_SIENA_SRIOV=yCONFIG_SFC_SIENA_MCDI_LOGGING=yCONFIG_NET_VENDOR_SMSC=yCONFIG_SMC91X=yCONFIG_PCMCIA_SMC91C92=yCONFIG_EPIC100=yCONFIG_SMSC911X=yCONFIG_SMSC9420=yCONFIG_NET_VENDOR_SOCIONEXT=yCONFIG_SNI_AVE=yCONFIG_SNI_NETSEC=yCONFIG_NET_VENDOR_STMICRO=yCONFIG_STMMAC_ETH=yCONFIG_STMMAC_SELFTESTS=yCONFIG_STMMAC_PLATFORM=yCONFIG_DWMAC_DWC_QOS_ETH=yCONFIG_DWMAC_GENERIC=yCONFIG_DWMAC_ANARION=yCONFIG_DWMAC_INGENIC=yCONFIG_DWMAC_IPQ806X=yCONFIG_DWMAC_LPC18XX=yCONFIG_DWMAC_MEDIATEK=yCONFIG_DWMAC_MESON=yCONFIG_DWMAC_OXNAS=yCONFIG_DWMAC_QCOM_ETHQOS=yCONFIG_DWMAC_ROCKCHIP=yCONFIG_DWMAC_SOCFPGA=yCONFIG_DWMAC_STI=yCONFIG_DWMAC_STM32=yCONFIG_DWMAC_SUNXI=yCONFIG_DWMAC_SUN8I=yCONFIG_DWMAC_IMX8=yCONFIG_DWMAC_INTEL_PLAT=yCONFIG_DWMAC_VISCONTI=yCONFIG_DWMAC_LOONGSON=yCONFIG_STMMAC_PCI=yCONFIG_NET_VENDOR_SUN=yCONFIG_HAPPYMEAL=yCONFIG_SUNGEM=yCONFIG_CASSINI=yCONFIG_NIU=yCONFIG_NET_VENDOR_SUNPLUS=yCONFIG_SP7021_EMAC=yCONFIG_NET_VENDOR_SYNOPSYS=yCONFIG_DWC_XLGMAC=yCONFIG_DWC_XLGMAC_PCI=yCONFIG_NET_VENDOR_TEHUTI=yCONFIG_TEHUTI=yCONFIG_NET_VENDOR_TI=yCONFIG_TI_DAVINCI_EMAC=yCONFIG_TI_DAVINCI_MDIO=yCONFIG_TI_CPSW_PHY_SEL=yCONFIG_TI_CPSW=yCONFIG_TI_CPSW_SWITCHDEV=yCONFIG_TI_CPTS=yCONFIG_TLAN=yCONFIG_NET_VENDOR_VERTEXCOM=yCONFIG_MSE102X=yCONFIG_NET_VENDOR_VIA=yCONFIG_VIA_RHINE=yCONFIG_VIA_RHINE_MMIO=yCONFIG_VIA_VELOCITY=yCONFIG_NET_VENDOR_WIZNET=yCONFIG_WIZNET_W5100=yCONFIG_WIZNET_W5300=y
# CONFIG_WIZNET_BUS_DIRECT is not set
# CONFIG_WIZNET_BUS_INDIRECT is not setCONFIG_WIZNET_BUS_ANY=yCONFIG_WIZNET_W5100_SPI=yCONFIG_NET_VENDOR_XILINX=yCONFIG_XILINX_EMACLITE=yCONFIG_XILINX_AXI_EMAC=yCONFIG_XILINX_LL_TEMAC=yCONFIG_NET_VENDOR_XIRCOM=yCONFIG_PCMCIA_XIRC2PS=yCONFIG_FDDI=yCONFIG_DEFXX=yCONFIG_SKFP=yCONFIG_HIPPI=yCONFIG_ROADRUNNER=yCONFIG_ROADRUNNER_LARGE_RINGS=yCONFIG_QCOM_IPA=yCONFIG_NET_SB1000=yCONFIG_PHYLINK=yCONFIG_PHYLIB=yCONFIG_SWPHY=yCONFIG_LED_TRIGGER_PHY=yCONFIG_FIXED_PHY=yCONFIG_SFP=y
#
# MII PHY device drivers
#CONFIG_AMD_PHY=yCONFIG_MESON_GXL_PHY=yCONFIG_ADIN_PHY=yCONFIG_ADIN1100_PHY=yCONFIG_AQUANTIA_PHY=yCONFIG_AX88796B_PHY=yCONFIG_BROADCOM_PHY=yCONFIG_BCM54140_PHY=yCONFIG_BCM63XX_PHY=yCONFIG_BCM7XXX_PHY=yCONFIG_BCM84881_PHY=yCONFIG_BCM87XX_PHY=yCONFIG_BCM_CYGNUS_PHY=yCONFIG_BCM_NET_PHYLIB=yCONFIG_BCM_NET_PHYPTP=yCONFIG_CICADA_PHY=yCONFIG_CORTINA_PHY=yCONFIG_DAVICOM_PHY=yCONFIG_ICPLUS_PHY=yCONFIG_LXT_PHY=yCONFIG_INTEL_XWAY_PHY=yCONFIG_LSI_ET1011C_PHY=yCONFIG_MARVELL_PHY=yCONFIG_MARVELL_10G_PHY=yCONFIG_MARVELL_88X2222_PHY=yCONFIG_MAXLINEAR_GPHY=yCONFIG_MEDIATEK_GE_PHY=yCONFIG_MICREL_PHY=yCONFIG_MICROCHIP_PHY=yCONFIG_MICROCHIP_T1_PHY=yCONFIG_MICROSEMI_PHY=yCONFIG_MOTORCOMM_PHY=yCONFIG_NATIONAL_PHY=yCONFIG_NXP_C45_TJA11XX_PHY=yCONFIG_NXP_TJA11XX_PHY=yCONFIG_AT803X_PHY=yCONFIG_QSEMI_PHY=yCONFIG_REALTEK_PHY=yCONFIG_RENESAS_PHY=yCONFIG_ROCKCHIP_PHY=yCONFIG_SMSC_PHY=yCONFIG_STE10XP=yCONFIG_TERANETICS_PHY=yCONFIG_DP83822_PHY=yCONFIG_DP83TC811_PHY=yCONFIG_DP83848_PHY=yCONFIG_DP83867_PHY=yCONFIG_DP83869_PHY=yCONFIG_DP83TD510_PHY=yCONFIG_VITESSE_PHY=yCONFIG_XILINX_GMII2RGMII=yCONFIG_MICREL_KS8995MA=yCONFIG_PSE_CONTROLLER=yCONFIG_PSE_REGULATOR=yCONFIG_CAN_DEV=yCONFIG_CAN_VCAN=yCONFIG_CAN_VXCAN=yCONFIG_CAN_NETLINK=yCONFIG_CAN_CALC_BITTIMING=yCONFIG_CAN_RX_OFFLOAD=yCONFIG_CAN_AT91=yCONFIG_CAN_CAN327=yCONFIG_CAN_FLEXCAN=yCONFIG_CAN_GRCAN=yCONFIG_CAN_JANZ_ICAN3=yCONFIG_CAN_KVASER_PCIEFD=yCONFIG_CAN_SLCAN=yCONFIG_CAN_SUN4I=yCONFIG_CAN_XILINXCAN=yCONFIG_CAN_C_CAN=yCONFIG_CAN_C_CAN_PLATFORM=yCONFIG_CAN_C_CAN_PCI=yCONFIG_CAN_CC770=yCONFIG_CAN_CC770_ISA=yCONFIG_CAN_CC770_PLATFORM=yCONFIG_CAN_CTUCANFD=yCONFIG_CAN_CTUCANFD_PCI=yCONFIG_CAN_CTUCANFD_PLATFORM=yCONFIG_CAN_IFI_CANFD=yCONFIG_CAN_M_CAN=yCONFIG_CAN_M_CAN_PCI=yCONFIG_CAN_M_CAN_PLATFORM=yCONFIG_CAN_M_CAN_TCAN4X5X=yCONFIG_CAN_PEAK_PCIEFD=yCONFIG_CAN_RCAR=yCONFIG_CAN_RCAR_CANFD=yCONFIG_CAN_SJA1000=yCONFIG_CAN_EMS_PCI=yCONFIG_CAN_EMS_PCMCIA=yCONFIG_CAN_F81601=yCONFIG_CAN_KVASER_PCI=yCONFIG_CAN_PEAK_PCI=yCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_PEAK_PCMCIA=yCONFIG_CAN_PLX_PCI=yCONFIG_CAN_SJA1000_ISA=yCONFIG_CAN_SJA1000_PLATFORM=yCONFIG_CAN_SOFTING=yCONFIG_CAN_SOFTING_CS=y
#
# CAN SPI interfaces
#CONFIG_CAN_HI311X=yCONFIG_CAN_MCP251X=yCONFIG_CAN_MCP251XFD=yCONFIG_CAN_MCP251XFD_SANITY=y
# end of CAN SPI interfaces
#
# CAN USB interfaces
#CONFIG_CAN_8DEV_USB=yCONFIG_CAN_EMS_USB=yCONFIG_CAN_ESD_USB=yCONFIG_CAN_ETAS_ES58X=yCONFIG_CAN_GS_USB=yCONFIG_CAN_KVASER_USB=yCONFIG_CAN_MCBA_USB=yCONFIG_CAN_PEAK_USB=yCONFIG_CAN_UCAN=y
# end of CAN USB interfaces
CONFIG_CAN_DEBUG_DEVICES=y
#
# MCTP Device Drivers
#CONFIG_MCTP_SERIAL=yCONFIG_MCTP_TRANSPORT_I2C=y
# end of MCTP Device Drivers
CONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_FWNODE_MDIO=yCONFIG_OF_MDIO=yCONFIG_ACPI_MDIO=yCONFIG_MDIO_DEVRES=yCONFIG_MDIO_SUN4I=yCONFIG_MDIO_XGENE=yCONFIG_MDIO_ASPEED=yCONFIG_MDIO_BITBANG=yCONFIG_MDIO_BCM_IPROC=yCONFIG_MDIO_BCM_UNIMAC=yCONFIG_MDIO_CAVIUM=yCONFIG_MDIO_GPIO=yCONFIG_MDIO_HISI_FEMAC=yCONFIG_MDIO_I2C=yCONFIG_MDIO_MVUSB=yCONFIG_MDIO_MSCC_MIIM=yCONFIG_MDIO_MOXART=yCONFIG_MDIO_OCTEON=yCONFIG_MDIO_IPQ4019=yCONFIG_MDIO_IPQ8064=yCONFIG_MDIO_THUNDER=y
#
# MDIO Multiplexers
#CONFIG_MDIO_BUS_MUX=yCONFIG_MDIO_BUS_MUX_MESON_G12A=yCONFIG_MDIO_BUS_MUX_BCM6368=yCONFIG_MDIO_BUS_MUX_BCM_IPROC=yCONFIG_MDIO_BUS_MUX_GPIO=yCONFIG_MDIO_BUS_MUX_MULTIPLEXER=yCONFIG_MDIO_BUS_MUX_MMIOREG=y
#
# PCS device drivers
#CONFIG_PCS_XPCS=yCONFIG_PCS_LYNX=yCONFIG_PCS_RZN1_MIIC=yCONFIG_PCS_ALTERA_TSE=y
# end of PCS device drivers
CONFIG_PLIP=yCONFIG_PPP=yCONFIG_PPP_BSDCOMP=yCONFIG_PPP_DEFLATE=yCONFIG_PPP_FILTER=yCONFIG_PPP_MPPE=yCONFIG_PPP_MULTILINK=yCONFIG_PPPOATM=yCONFIG_PPPOE=yCONFIG_PPTP=yCONFIG_PPPOL2TP=yCONFIG_PPP_ASYNC=yCONFIG_PPP_SYNC_TTY=yCONFIG_SLIP=yCONFIG_SLHC=yCONFIG_SLIP_COMPRESSED=yCONFIG_SLIP_SMART=yCONFIG_SLIP_MODE_SLIP6=yCONFIG_USB_NET_DRIVERS=yCONFIG_USB_CATC=yCONFIG_USB_KAWETH=yCONFIG_USB_PEGASUS=yCONFIG_USB_RTL8150=yCONFIG_USB_RTL8152=yCONFIG_USB_LAN78XX=yCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=yCONFIG_USB_NET_CDCETHER=yCONFIG_USB_NET_CDC_EEM=yCONFIG_USB_NET_CDC_NCM=yCONFIG_USB_NET_HUAWEI_CDC_NCM=yCONFIG_USB_NET_CDC_MBIM=yCONFIG_USB_NET_DM9601=yCONFIG_USB_NET_SR9700=yCONFIG_USB_NET_SR9800=yCONFIG_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=yCONFIG_USB_NET_KALMIA=yCONFIG_USB_NET_QMI_WWAN=yCONFIG_USB_HSO=yCONFIG_USB_NET_INT51X1=yCONFIG_USB_CDC_PHONET=yCONFIG_USB_IPHETH=yCONFIG_USB_SIERRA_NET=yCONFIG_USB_VL600=yCONFIG_USB_NET_CH9200=yCONFIG_USB_NET_AQC111=yCONFIG_USB_RTL8153_ECM=yCONFIG_WLAN=yCONFIG_WLAN_VENDOR_ADMTEK=yCONFIG_ADM8211=yCONFIG_ATH_COMMON=yCONFIG_WLAN_VENDOR_ATH=yCONFIG_ATH_DEBUG=yCONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS=yCONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING=yCONFIG_ATH5K=yCONFIG_ATH5K_DEBUG=yCONFIG_ATH5K_PCI=yCONFIG_ATH5K_TEST_CHANNELS=yCONFIG_ATH9K_HW=yCONFIG_ATH9K_COMMON=yCONFIG_ATH9K_COMMON_DEBUG=yCONFIG_ATH9K_DFS_DEBUGFS=yCONFIG_ATH9K_BTCOEX_SUPPORT=yCONFIG_ATH9K=yCONFIG_ATH9K_PCI=yCONFIG_ATH9K_AHB=yCONFIG_ATH9K_DEBUGFS=yCONFIG_ATH9K_STATION_STATISTICS=yCONFIG_ATH9K_TX99=yCONFIG_ATH9K_DFS_CERTIFIED=yCONFIG_ATH9K_DYNACK=yCONFIG_ATH9K_WOW=yCONFIG_ATH9K_RFKILL=yCONFIG_ATH9K_CHANNEL_CONTEXT=yCONFIG_ATH9K_PCOEM=yCONFIG_ATH9K_PCI_NO_EEPROM=yCONFIG_ATH9K_HTC=yCONFIG_ATH9K_HTC_DEBUGFS=yCONFIG_ATH9K_HWRNG=yCONFIG_ATH9K_COMMON_SPECTRAL=yCONFIG_CARL9170=yCONFIG_CARL9170_LEDS=yCONFIG_CARL9170_DEBUGFS=yCONFIG_CARL9170_WPC=yCONFIG_CARL9170_HWRNG=yCONFIG_ATH6KL=yCONFIG_ATH6KL_SDIO=yCONFIG_ATH6KL_USB=yCONFIG_ATH6KL_DEBUG=yCONFIG_ATH6KL_REGDOMAIN=yCONFIG_AR5523=yCONFIG_WIL6210=yCONFIG_WIL6210_ISR_COR=yCONFIG_WIL6210_DEBUGFS=yCONFIG_ATH10K=yCONFIG_ATH10K_CE=yCONFIG_ATH10K_PCI=yCONFIG_ATH10K_AHB=yCONFIG_ATH10K_SDIO=yCONFIG_ATH10K_USB=yCONFIG_ATH10K_SNOC=yCONFIG_ATH10K_DEBUG=yCONFIG_ATH10K_DEBUGFS=yCONFIG_ATH10K_SPECTRAL=yCONFIG_ATH10K_DFS_CERTIFIED=yCONFIG_WCN36XX=yCONFIG_WCN36XX_DEBUGFS=yCONFIG_ATH11K=yCONFIG_ATH11K_AHB=yCONFIG_ATH11K_PCI=yCONFIG_ATH11K_DEBUG=yCONFIG_ATH11K_DEBUGFS=yCONFIG_ATH11K_SPECTRAL=yCONFIG_WLAN_VENDOR_ATMEL=yCONFIG_ATMEL=yCONFIG_PCI_ATMEL=yCONFIG_PCMCIA_ATMEL=yCONFIG_AT76C50X_USB=yCONFIG_WLAN_VENDOR_BROADCOM=yCONFIG_B43=yCONFIG_B43_BCMA=yCONFIG_B43_SSB=yCONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not setCONFIG_B43_PCI_AUTOSELECT=yCONFIG_B43_PCICORE_AUTOSELECT=yCONFIG_B43_SDIO=yCONFIG_B43_BCMA_PIO=yCONFIG_B43_PIO=yCONFIG_B43_PHY_G=yCONFIG_B43_PHY_N=yCONFIG_B43_PHY_LP=yCONFIG_B43_PHY_HT=yCONFIG_B43_LEDS=yCONFIG_B43_HWRNG=yCONFIG_B43_DEBUG=yCONFIG_B43LEGACY=yCONFIG_B43LEGACY_PCI_AUTOSELECT=yCONFIG_B43LEGACY_PCICORE_AUTOSELECT=yCONFIG_B43LEGACY_LEDS=yCONFIG_B43LEGACY_HWRNG=yCONFIG_B43LEGACY_DEBUG=yCONFIG_B43LEGACY_DMA=yCONFIG_B43LEGACY_PIO=yCONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not setCONFIG_BRCMUTIL=yCONFIG_BRCMSMAC=yCONFIG_BRCMSMAC_LEDS=yCONFIG_BRCMFMAC=yCONFIG_BRCMFMAC_PROTO_BCDC=yCONFIG_BRCMFMAC_PROTO_MSGBUF=yCONFIG_BRCMFMAC_SDIO=yCONFIG_BRCMFMAC_USB=yCONFIG_BRCMFMAC_PCIE=yCONFIG_BRCM_TRACING=yCONFIG_BRCMDBG=yCONFIG_WLAN_VENDOR_CISCO=yCONFIG_AIRO_CS=yCONFIG_WLAN_VENDOR_INTEL=yCONFIG_IPW2100=yCONFIG_IPW2100_MONITOR=yCONFIG_IPW2100_DEBUG=yCONFIG_IPW2200=yCONFIG_IPW2200_MONITOR=yCONFIG_IPW2200_RADIOTAP=yCONFIG_IPW2200_PROMISCUOUS=yCONFIG_IPW2200_QOS=yCONFIG_IPW2200_DEBUG=yCONFIG_LIBIPW=yCONFIG_LIBIPW_DEBUG=yCONFIG_IWLEGACY=yCONFIG_IWL4965=yCONFIG_IWL3945=y
#
# iwl3945 / iwl4965 Debugging Options # CONFIG_IWLEGACY_DEBUG=y CONFIG_IWLEGACY_DEBUGFS=y # end of iwl3945 / iwl4965 Debugging Options
CONFIG_IWLWIFI=yCONFIG_IWLWIFI_LEDS=yCONFIG_IWLDVM=yCONFIG_IWLMVM=y
#
# Debugging Options
#CONFIG_IWLWIFI_DEBUG=yCONFIG_IWLWIFI_DEBUGFS=y
# end of Debugging Options
CONFIG_WLAN_VENDOR_INTERSIL=yCONFIG_HOSTAP=yCONFIG_HOSTAP_FIRMWARE=yCONFIG_HOSTAP_FIRMWARE_NVRAM=yCONFIG_HOSTAP_PLX=yCONFIG_HOSTAP_PCI=yCONFIG_HOSTAP_CS=yCONFIG_HERMES=yCONFIG_HERMES_PRISM=yCONFIG_HERMES_CACHE_FW_ON_INIT=yCONFIG_PLX_HERMES=yCONFIG_TMD_HERMES=yCONFIG_NORTEL_HERMES=yCONFIG_PCI_HERMES=yCONFIG_PCMCIA_HERMES=yCONFIG_PCMCIA_SPECTRUM=yCONFIG_ORINOCO_USB=yCONFIG_P54_COMMON=yCONFIG_P54_USB=yCONFIG_P54_PCI=yCONFIG_P54_SPI=yCONFIG_P54_SPI_DEFAULT_EEPROM=yCONFIG_P54_LEDS=yCONFIG_WLAN_VENDOR_MARVELL=yCONFIG_LIBERTAS=yCONFIG_LIBERTAS_USB=yCONFIG_LIBERTAS_CS=yCONFIG_LIBERTAS_SDIO=yCONFIG_LIBERTAS_SPI=yCONFIG_LIBERTAS_DEBUG=yCONFIG_LIBERTAS_MESH=yCONFIG_LIBERTAS_THINFIRM=yCONFIG_LIBERTAS_THINFIRM_DEBUG=yCONFIG_LIBERTAS_THINFIRM_USB=yCONFIG_MWIFIEX=yCONFIG_MWIFIEX_SDIO=yCONFIG_MWIFIEX_PCIE=yCONFIG_MWIFIEX_USB=yCONFIG_MWL8K=yCONFIG_WLAN_VENDOR_MEDIATEK=yCONFIG_MT7601U=yCONFIG_MT76_CORE=yCONFIG_MT76_LEDS=yCONFIG_MT76_USB=yCONFIG_MT76_SDIO=y
CONFIG_MT76x02_LIB=y
CONFIG_MT76x02_USB=yCONFIG_MT76_CONNAC_LIB=y
CONFIG_MT76x0_COMMON=y
CONFIG_MT76x0U=y
CONFIG_MT76x0E=y
CONFIG_MT76x2_COMMON=y
CONFIG_MT76x2E=y
CONFIG_MT76x2U=yCONFIG_MT7603E=yCONFIG_MT7615_COMMON=yCONFIG_MT7615E=yCONFIG_MT7622_WMAC=yCONFIG_MT7663_USB_SDIO_COMMON=yCONFIG_MT7663U=yCONFIG_MT7663S=yCONFIG_MT7915E=yCONFIG_MT7986_WMAC=yCONFIG_MT7921_COMMON=yCONFIG_MT7921E=yCONFIG_MT7921S=yCONFIG_MT7921U=yCONFIG_WLAN_VENDOR_MICROCHIP=yCONFIG_WILC1000=yCONFIG_WILC1000_SDIO=yCONFIG_WILC1000_SPI=yCONFIG_WILC1000_HW_OOB_INTR=yCONFIG_WLAN_VENDOR_PURELIFI=yCONFIG_PLFXLC=yCONFIG_WLAN_VENDOR_RALINK=yCONFIG_RT2X00=yCONFIG_RT2400PCI=yCONFIG_RT2500PCI=yCONFIG_RT61PCI=yCONFIG_RT2800PCI=yCONFIG_RT2800PCI_RT33XX=yCONFIG_RT2800PCI_RT35XX=yCONFIG_RT2800PCI_RT53XX=yCONFIG_RT2800PCI_RT3290=yCONFIG_RT2500USB=yCONFIG_RT73USB=yCONFIG_RT2800USB=yCONFIG_RT2800USB_RT33XX=yCONFIG_RT2800USB_RT35XX=yCONFIG_RT2800USB_RT3573=yCONFIG_RT2800USB_RT53XX=yCONFIG_RT2800USB_RT55XX=yCONFIG_RT2800USB_UNKNOWN=yCONFIG_RT2800_LIB=yCONFIG_RT2800_LIB_MMIO=yCONFIG_RT2X00_LIB_MMIO=yCONFIG_RT2X00_LIB_PCI=yCONFIG_RT2X00_LIB_USB=yCONFIG_RT2X00_LIB=yCONFIG_RT2X00_LIB_FIRMWARE=yCONFIG_RT2X00_LIB_CRYPTO=yCONFIG_RT2X00_LIB_LEDS=yCONFIG_RT2X00_LIB_DEBUGFS=yCONFIG_RT2X00_DEBUG=yCONFIG_WLAN_VENDOR_REALTEK=yCONFIG_RTL8180=yCONFIG_RTL8187=yCONFIG_RTL8187_LEDS=yCONFIG_RTL_CARDS=yCONFIG_RTL8192CE=yCONFIG_RTL8192SE=yCONFIG_RTL8192DE=yCONFIG_RTL8723AE=yCONFIG_RTL8723BE=yCONFIG_RTL8188EE=yCONFIG_RTL8192EE=yCONFIG_RTL8821AE=yCONFIG_RTL8192CU=yCONFIG_RTLWIFI=yCONFIG_RTLWIFI_PCI=yCONFIG_RTLWIFI_USB=yCONFIG_RTLWIFI_DEBUG=yCONFIG_RTL8192C_COMMON=yCONFIG_RTL8723_COMMON=yCONFIG_RTLBTCOEXIST=yCONFIG_RTL8XXXU=yCONFIG_RTL8XXXU_UNTESTED=yCONFIG_RTW88=yCONFIG_RTW88_CORE=yCONFIG_RTW88_PCI=yCONFIG_RTW88_8822B=yCONFIG_RTW88_8822C=yCONFIG_RTW88_8723D=yCONFIG_RTW88_8821C=yCONFIG_RTW88_8822BE=yCONFIG_RTW88_8822CE=yCONFIG_RTW88_8723DE=yCONFIG_RTW88_8821CE=yCONFIG_RTW88_DEBUG=yCONFIG_RTW88_DEBUGFS=yCONFIG_RTW89=yCONFIG_RTW89_CORE=yCONFIG_RTW89_PCI=yCONFIG_RTW89_8852A=yCONFIG_RTW89_8852B=yCONFIG_RTW89_8852C=yCONFIG_RTW89_8852AE=yCONFIG_RTW89_8852BE=yCONFIG_RTW89_8852CE=yCONFIG_RTW89_DEBUG=yCONFIG_RTW89_DEBUGMSG=yCONFIG_RTW89_DEBUGFS=yCONFIG_WLAN_VENDOR_RSI=yCONFIG_RSI_91X=yCONFIG_RSI_DEBUGFS=yCONFIG_RSI_SDIO=yCONFIG_RSI_USB=yCONFIG_RSI_COEX=yCONFIG_WLAN_VENDOR_SILABS=yCONFIG_WFX=yCONFIG_WLAN_VENDOR_ST=yCONFIG_CW1200=yCONFIG_CW1200_WLAN_SDIO=yCONFIG_CW1200_WLAN_SPI=yCONFIG_WLAN_VENDOR_TI=yCONFIG_WL1251=yCONFIG_WL1251_SPI=yCONFIG_WL1251_SDIO=yCONFIG_WL12XX=yCONFIG_WL18XX=yCONFIG_WLCORE=yCONFIG_WLCORE_SPI=yCONFIG_WLCORE_SDIO=yCONFIG_WILINK_PLATFORM_DATA=yCONFIG_WLAN_VENDOR_ZYDAS=yCONFIG_USB_ZD1201=yCONFIG_ZD1211RW=yCONFIG_ZD1211RW_DEBUG=yCONFIG_WLAN_VENDOR_QUANTENNA=yCONFIG_QTNFMAC=yCONFIG_QTNFMAC_PCIE=yCONFIG_PCMCIA_RAYCS=yCONFIG_PCMCIA_WL3501=yCONFIG_MAC80211_HWSIM=yCONFIG_USB_NET_RNDIS_WLAN=yCONFIG_VIRT_WIFI=yCONFIG_WAN=yCONFIG_HDLC=yCONFIG_HDLC_RAW=yCONFIG_HDLC_RAW_ETH=yCONFIG_HDLC_CISCO=yCONFIG_HDLC_FR=yCONFIG_HDLC_PPP=yCONFIG_HDLC_X25=yCONFIG_PCI200SYN=yCONFIG_WANXL=yCONFIG_PC300TOO=yCONFIG_FARSYNC=yCONFIG_FSL_UCC_HDLC=yCONFIG_SLIC_DS26522=yCONFIG_LAPBETHER=yCONFIG_IEEE802154_DRIVERS=yCONFIG_IEEE802154_FAKELB=yCONFIG_IEEE802154_AT86RF230=yCONFIG_IEEE802154_MRF24J40=yCONFIG_IEEE802154_CC2520=yCONFIG_IEEE802154_ATUSB=yCONFIG_IEEE802154_ADF7242=yCONFIG_IEEE802154_CA8210=yCONFIG_IEEE802154_CA8210_DEBUGFS=yCONFIG_IEEE802154_MCR20A=yCONFIG_IEEE802154_HWSIM=y
#
# Wireless WAN
#CONFIG_WWAN=yCONFIG_WWAN_DEBUGFS=yCONFIG_WWAN_HWSIM=yCONFIG_MHI_WWAN_CTRL=yCONFIG_MHI_WWAN_MBIM=yCONFIG_QCOM_BAM_DMUX=yCONFIG_RPMSG_WWAN_CTRL=yCONFIG_IOSM=yCONFIG_MTK_T7XX=y
# end of Wireless WAN
CONFIG_VMXNET3=yCONFIG_FUJITSU_ES=yCONFIG_USB4_NET=yCONFIG_NETDEVSIM=yCONFIG_NET_FAILOVER=yCONFIG_ISDN=yCONFIG_ISDN_CAPI=yCONFIG_CAPI_TRACE=yCONFIG_ISDN_CAPI_MIDDLEWARE=yCONFIG_MISDN=yCONFIG_MISDN_DSP=yCONFIG_MISDN_L1OIP=y
#
# mISDN hardware drivers
#CONFIG_MISDN_HFCPCI=yCONFIG_MISDN_HFCMULTI=yCONFIG_MISDN_HFCUSB=yCONFIG_MISDN_AVMFRITZ=yCONFIG_MISDN_SPEEDFAX=yCONFIG_MISDN_INFINEON=yCONFIG_MISDN_W6692=yCONFIG_MISDN_NETJET=yCONFIG_MISDN_HDLC=yCONFIG_MISDN_IPAC=yCONFIG_MISDN_ISAR=y
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_SPARSEKMAP=yCONFIG_INPUT_MATRIXKMAP=yCONFIG_INPUT_VIVALDIFMAP=y
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=yCONFIG_INPUT_EVDEV=yCONFIG_INPUT_EVBUG=y
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ADC=yCONFIG_KEYBOARD_ADP5520=yCONFIG_KEYBOARD_ADP5588=yCONFIG_KEYBOARD_ADP5589=yCONFIG_KEYBOARD_APPLESPI=yCONFIG_KEYBOARD_ATKBD=yCONFIG_KEYBOARD_QT1050=yCONFIG_KEYBOARD_QT1070=yCONFIG_KEYBOARD_QT2160=yCONFIG_KEYBOARD_CLPS711X=yCONFIG_KEYBOARD_DLINK_DIR685=yCONFIG_KEYBOARD_LKKBD=yCONFIG_KEYBOARD_EP93XX=yCONFIG_KEYBOARD_GPIO=yCONFIG_KEYBOARD_GPIO_POLLED=yCONFIG_KEYBOARD_TCA6416=yCONFIG_KEYBOARD_TCA8418=yCONFIG_KEYBOARD_MATRIX=yCONFIG_KEYBOARD_LM8323=yCONFIG_KEYBOARD_LM8333=yCONFIG_KEYBOARD_MAX7359=yCONFIG_KEYBOARD_MCS=yCONFIG_KEYBOARD_MPR121=yCONFIG_KEYBOARD_SNVS_PWRKEY=yCONFIG_KEYBOARD_IMX=yCONFIG_KEYBOARD_IMX_SC_KEY=yCONFIG_KEYBOARD_NEWTON=yCONFIG_KEYBOARD_OPENCORES=yCONFIG_KEYBOARD_PINEPHONE=yCONFIG_KEYBOARD_PMIC8XXX=yCONFIG_KEYBOARD_SAMSUNG=yCONFIG_KEYBOARD_GOLDFISH_EVENTS=yCONFIG_KEYBOARD_STOWAWAY=yCONFIG_KEYBOARD_ST_KEYSCAN=yCONFIG_KEYBOARD_SUNKBD=yCONFIG_KEYBOARD_SH_KEYSC=yCONFIG_KEYBOARD_STMPE=yCONFIG_KEYBOARD_IQS62X=yCONFIG_KEYBOARD_OMAP4=yCONFIG_KEYBOARD_TC3589X=yCONFIG_KEYBOARD_TM2_TOUCHKEY=yCONFIG_KEYBOARD_TWL4030=yCONFIG_KEYBOARD_XTKBD=yCONFIG_KEYBOARD_CROS_EC=yCONFIG_KEYBOARD_CAP11XX=yCONFIG_KEYBOARD_BCM=yCONFIG_KEYBOARD_MT6779=yCONFIG_KEYBOARD_MTK_PMIC=yCONFIG_KEYBOARD_CYPRESS_SF=yCONFIG_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_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=yCONFIG_MOUSE_PS2_TOUCHKIT=yCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=yCONFIG_MOUSE_APPLETOUCH=yCONFIG_MOUSE_BCM5974=yCONFIG_MOUSE_CYAPA=yCONFIG_MOUSE_ELAN_I2C=yCONFIG_MOUSE_ELAN_I2C_I2C=yCONFIG_MOUSE_ELAN_I2C_SMBUS=yCONFIG_MOUSE_VSXXXAA=yCONFIG_MOUSE_GPIO=yCONFIG_MOUSE_SYNAPTICS_I2C=yCONFIG_MOUSE_SYNAPTICS_USB=yCONFIG_INPUT_JOYSTICK=yCONFIG_JOYSTICK_ANALOG=yCONFIG_JOYSTICK_A3D=yCONFIG_JOYSTICK_ADC=yCONFIG_JOYSTICK_ADI=yCONFIG_JOYSTICK_COBRA=yCONFIG_JOYSTICK_GF2K=yCONFIG_JOYSTICK_GRIP=yCONFIG_JOYSTICK_GRIP_MP=yCONFIG_JOYSTICK_GUILLEMOT=yCONFIG_JOYSTICK_INTERACT=yCONFIG_JOYSTICK_SIDEWINDER=yCONFIG_JOYSTICK_TMDC=yCONFIG_JOYSTICK_IFORCE=yCONFIG_JOYSTICK_IFORCE_USB=yCONFIG_JOYSTICK_IFORCE_232=yCONFIG_JOYSTICK_WARRIOR=yCONFIG_JOYSTICK_MAGELLAN=yCONFIG_JOYSTICK_SPACEORB=yCONFIG_JOYSTICK_SPACEBALL=yCONFIG_JOYSTICK_STINGER=yCONFIG_JOYSTICK_TWIDJOY=yCONFIG_JOYSTICK_ZHENHUA=yCONFIG_JOYSTICK_DB9=yCONFIG_JOYSTICK_GAMECON=yCONFIG_JOYSTICK_TURBOGRAFX=yCONFIG_JOYSTICK_AS5011=yCONFIG_JOYSTICK_JOYDUMP=yCONFIG_JOYSTICK_XPAD=yCONFIG_JOYSTICK_XPAD_FF=yCONFIG_JOYSTICK_XPAD_LEDS=yCONFIG_JOYSTICK_PSXPAD_SPI=yCONFIG_JOYSTICK_PSXPAD_SPI_FF=yCONFIG_JOYSTICK_PXRC=yCONFIG_JOYSTICK_QWIIC=yCONFIG_JOYSTICK_FSIA6B=yCONFIG_JOYSTICK_SENSEHAT=yCONFIG_INPUT_TABLET=yCONFIG_TABLET_USB_ACECAD=yCONFIG_TABLET_USB_AIPTEK=yCONFIG_TABLET_USB_HANWANG=yCONFIG_TABLET_USB_KBTAB=yCONFIG_TABLET_USB_PEGASUS=yCONFIG_TABLET_SERIAL_WACOM4=yCONFIG_INPUT_TOUCHSCREEN=yCONFIG_TOUCHSCREEN_88PM860X=yCONFIG_TOUCHSCREEN_ADS7846=yCONFIG_TOUCHSCREEN_AD7877=yCONFIG_TOUCHSCREEN_AD7879=yCONFIG_TOUCHSCREEN_AD7879_I2C=yCONFIG_TOUCHSCREEN_AD7879_SPI=yCONFIG_TOUCHSCREEN_ADC=yCONFIG_TOUCHSCREEN_AR1021_I2C=yCONFIG_TOUCHSCREEN_ATMEL_MXT=yCONFIG_TOUCHSCREEN_ATMEL_MXT_T37=yCONFIG_TOUCHSCREEN_AUO_PIXCIR=yCONFIG_TOUCHSCREEN_BU21013=yCONFIG_TOUCHSCREEN_BU21029=yCONFIG_TOUCHSCREEN_CHIPONE_ICN8318=yCONFIG_TOUCHSCREEN_CHIPONE_ICN8505=yCONFIG_TOUCHSCREEN_CY8CTMA140=yCONFIG_TOUCHSCREEN_CY8CTMG110=yCONFIG_TOUCHSCREEN_CYTTSP_CORE=yCONFIG_TOUCHSCREEN_CYTTSP_I2C=yCONFIG_TOUCHSCREEN_CYTTSP_SPI=yCONFIG_TOUCHSCREEN_CYTTSP4_CORE=yCONFIG_TOUCHSCREEN_CYTTSP4_I2C=yCONFIG_TOUCHSCREEN_CYTTSP4_SPI=yCONFIG_TOUCHSCREEN_DA9034=yCONFIG_TOUCHSCREEN_DA9052=yCONFIG_TOUCHSCREEN_DYNAPRO=yCONFIG_TOUCHSCREEN_HAMPSHIRE=yCONFIG_TOUCHSCREEN_EETI=yCONFIG_TOUCHSCREEN_EGALAX=yCONFIG_TOUCHSCREEN_EGALAX_SERIAL=yCONFIG_TOUCHSCREEN_EXC3000=yCONFIG_TOUCHSCREEN_FUJITSU=yCONFIG_TOUCHSCREEN_GOODIX=yCONFIG_TOUCHSCREEN_HIDEEP=yCONFIG_TOUCHSCREEN_HYCON_HY46XX=yCONFIG_TOUCHSCREEN_ILI210X=yCONFIG_TOUCHSCREEN_ILITEK=yCONFIG_TOUCHSCREEN_IPROC=yCONFIG_TOUCHSCREEN_S6SY761=yCONFIG_TOUCHSCREEN_GUNZE=yCONFIG_TOUCHSCREEN_EKTF2127=yCONFIG_TOUCHSCREEN_ELAN=yCONFIG_TOUCHSCREEN_ELO=yCONFIG_TOUCHSCREEN_WACOM_W8001=yCONFIG_TOUCHSCREEN_WACOM_I2C=yCONFIG_TOUCHSCREEN_MAX11801=yCONFIG_TOUCHSCREEN_MCS5000=yCONFIG_TOUCHSCREEN_MMS114=yCONFIG_TOUCHSCREEN_MELFAS_MIP4=yCONFIG_TOUCHSCREEN_MSG2638=yCONFIG_TOUCHSCREEN_MTOUCH=yCONFIG_TOUCHSCREEN_IMAGIS=yCONFIG_TOUCHSCREEN_IMX6UL_TSC=yCONFIG_TOUCHSCREEN_INEXIO=yCONFIG_TOUCHSCREEN_MK712=yCONFIG_TOUCHSCREEN_PENMOUNT=yCONFIG_TOUCHSCREEN_EDT_FT5X06=yCONFIG_TOUCHSCREEN_RASPBERRYPI_FW=yCONFIG_TOUCHSCREEN_MIGOR=yCONFIG_TOUCHSCREEN_TOUCHRIGHT=yCONFIG_TOUCHSCREEN_TOUCHWIN=yCONFIG_TOUCHSCREEN_TI_AM335X_TSC=yCONFIG_TOUCHSCREEN_UCB1400=yCONFIG_TOUCHSCREEN_PIXCIR=yCONFIG_TOUCHSCREEN_WDT87XX_I2C=yCONFIG_TOUCHSCREEN_WM831X=yCONFIG_TOUCHSCREEN_WM97XX=yCONFIG_TOUCHSCREEN_WM9705=yCONFIG_TOUCHSCREEN_WM9712=yCONFIG_TOUCHSCREEN_WM9713=yCONFIG_TOUCHSCREEN_USB_COMPOSITE=yCONFIG_TOUCHSCREEN_MXS_LRADC=yCONFIG_TOUCHSCREEN_MX25=yCONFIG_TOUCHSCREEN_MC13783=yCONFIG_TOUCHSCREEN_USB_EGALAX=yCONFIG_TOUCHSCREEN_USB_PANJIT=yCONFIG_TOUCHSCREEN_USB_3M=yCONFIG_TOUCHSCREEN_USB_ITM=yCONFIG_TOUCHSCREEN_USB_ETURBO=yCONFIG_TOUCHSCREEN_USB_GUNZE=yCONFIG_TOUCHSCREEN_USB_DMC_TSC10=yCONFIG_TOUCHSCREEN_USB_IRTOUCH=yCONFIG_TOUCHSCREEN_USB_IDEALTEK=yCONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=yCONFIG_TOUCHSCREEN_USB_GOTOP=yCONFIG_TOUCHSCREEN_USB_JASTEC=yCONFIG_TOUCHSCREEN_USB_ELO=yCONFIG_TOUCHSCREEN_USB_E2I=yCONFIG_TOUCHSCREEN_USB_ZYTRONIC=yCONFIG_TOUCHSCREEN_USB_ETT_TC45USB=yCONFIG_TOUCHSCREEN_USB_NEXIO=yCONFIG_TOUCHSCREEN_USB_EASYTOUCH=yCONFIG_TOUCHSCREEN_TOUCHIT213=yCONFIG_TOUCHSCREEN_TS4800=yCONFIG_TOUCHSCREEN_TSC_SERIO=yCONFIG_TOUCHSCREEN_TSC200X_CORE=yCONFIG_TOUCHSCREEN_TSC2004=yCONFIG_TOUCHSCREEN_TSC2005=yCONFIG_TOUCHSCREEN_TSC2007=yCONFIG_TOUCHSCREEN_TSC2007_IIO=yCONFIG_TOUCHSCREEN_PCAP=yCONFIG_TOUCHSCREEN_RM_TS=yCONFIG_TOUCHSCREEN_SILEAD=yCONFIG_TOUCHSCREEN_SIS_I2C=yCONFIG_TOUCHSCREEN_ST1232=yCONFIG_TOUCHSCREEN_STMFTS=yCONFIG_TOUCHSCREEN_STMPE=yCONFIG_TOUCHSCREEN_SUN4I=yCONFIG_TOUCHSCREEN_SUR40=yCONFIG_TOUCHSCREEN_SURFACE3_SPI=yCONFIG_TOUCHSCREEN_SX8654=yCONFIG_TOUCHSCREEN_TPS6507X=yCONFIG_TOUCHSCREEN_ZET6223=yCONFIG_TOUCHSCREEN_ZFORCE=yCONFIG_TOUCHSCREEN_COLIBRI_VF50=yCONFIG_TOUCHSCREEN_ROHM_BU21023=yCONFIG_TOUCHSCREEN_IQS5XX=yCONFIG_TOUCHSCREEN_ZINITIX=yCONFIG_INPUT_MISC=yCONFIG_INPUT_88PM860X_ONKEY=yCONFIG_INPUT_88PM80X_ONKEY=yCONFIG_INPUT_AD714X=yCONFIG_INPUT_AD714X_I2C=yCONFIG_INPUT_AD714X_SPI=yCONFIG_INPUT_ARIEL_PWRBUTTON=yCONFIG_INPUT_ARIZONA_HAPTICS=yCONFIG_INPUT_ATC260X_ONKEY=yCONFIG_INPUT_ATMEL_CAPTOUCH=yCONFIG_INPUT_BMA150=yCONFIG_INPUT_E3X0_BUTTON=yCONFIG_INPUT_PM8941_PWRKEY=yCONFIG_INPUT_PM8XXX_VIBRATOR=yCONFIG_INPUT_PMIC8XXX_PWRKEY=yCONFIG_INPUT_MAX77650_ONKEY=yCONFIG_INPUT_MAX77693_HAPTIC=yCONFIG_INPUT_MAX8925_ONKEY=yCONFIG_INPUT_MAX8997_HAPTIC=yCONFIG_INPUT_MC13783_PWRBUTTON=yCONFIG_INPUT_MMA8450=yCONFIG_INPUT_GPIO_BEEPER=yCONFIG_INPUT_GPIO_DECODER=yCONFIG_INPUT_GPIO_VIBRA=yCONFIG_INPUT_CPCAP_PWRBUTTON=yCONFIG_INPUT_ATI_REMOTE2=yCONFIG_INPUT_KEYSPAN_REMOTE=yCONFIG_INPUT_KXTJ9=yCONFIG_INPUT_POWERMATE=yCONFIG_INPUT_YEALINK=yCONFIG_INPUT_CM109=yCONFIG_INPUT_REGULATOR_HAPTIC=yCONFIG_INPUT_RETU_PWRBUTTON=yCONFIG_INPUT_TPS65218_PWRBUTTON=yCONFIG_INPUT_AXP20X_PEK=yCONFIG_INPUT_TWL4030_PWRBUTTON=yCONFIG_INPUT_TWL4030_VIBRA=yCONFIG_INPUT_TWL6040_VIBRA=yCONFIG_INPUT_UINPUT=yCONFIG_INPUT_PALMAS_PWRBUTTON=yCONFIG_INPUT_PCF50633_PMU=yCONFIG_INPUT_PCF8574=yCONFIG_INPUT_PWM_BEEPER=yCONFIG_INPUT_PWM_VIBRA=yCONFIG_INPUT_RK805_PWRKEY=yCONFIG_INPUT_GPIO_ROTARY_ENCODER=yCONFIG_INPUT_DA7280_HAPTICS=yCONFIG_INPUT_DA9052_ONKEY=yCONFIG_INPUT_DA9055_ONKEY=yCONFIG_INPUT_DA9063_ONKEY=yCONFIG_INPUT_WM831X_ON=yCONFIG_INPUT_PCAP=yCONFIG_INPUT_ADXL34X=yCONFIG_INPUT_ADXL34X_I2C=yCONFIG_INPUT_ADXL34X_SPI=yCONFIG_INPUT_IBM_PANEL=yCONFIG_INPUT_IMS_PCU=yCONFIG_INPUT_IQS269A=yCONFIG_INPUT_IQS626A=yCONFIG_INPUT_IQS7222=yCONFIG_INPUT_CMA3000=yCONFIG_INPUT_CMA3000_I2C=yCONFIG_INPUT_IDEAPAD_SLIDEBAR=yCONFIG_INPUT_SOC_BUTTON_ARRAY=yCONFIG_INPUT_DRV260X_HAPTICS=yCONFIG_INPUT_DRV2665_HAPTICS=yCONFIG_INPUT_DRV2667_HAPTICS=yCONFIG_INPUT_HISI_POWERKEY=yCONFIG_INPUT_RAVE_SP_PWRBUTTON=yCONFIG_INPUT_SC27XX_VIBRA=yCONFIG_INPUT_RT5120_PWRKEY=yCONFIG_INPUT_STPMIC1_ONKEY=yCONFIG_RMI4_CORE=yCONFIG_RMI4_I2C=yCONFIG_RMI4_SPI=yCONFIG_RMI4_SMB=yCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=yCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=yCONFIG_RMI4_F34=yCONFIG_RMI4_F3A=yCONFIG_RMI4_F54=yCONFIG_RMI4_F55=y
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_PARKBD=yCONFIG_SERIO_PCIPS2=yCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=yCONFIG_SERIO_ALTERA_PS2=yCONFIG_SERIO_PS2MULT=yCONFIG_SERIO_ARC_PS2=yCONFIG_SERIO_APBPS2=yCONFIG_SERIO_OLPC_APSP=yCONFIG_SERIO_SUN4I_PS2=yCONFIG_SERIO_GPIO_PS2=yCONFIG_USERIO=yCONFIG_GAMEPORT=yCONFIG_GAMEPORT_NS558=yCONFIG_GAMEPORT_L4=yCONFIG_GAMEPORT_EMU10K1=yCONFIG_GAMEPORT_FM801=y
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_PNP=yCONFIG_SERIAL_8250_16550A_VARIANTS=yCONFIG_SERIAL_8250_FINTEK=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_DMA=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_EXAR=yCONFIG_SERIAL_8250_CS=yCONFIG_SERIAL_8250_MEN_MCB=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_ASPEED_VUART=yCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=yCONFIG_SERIAL_8250_DWLIB=yCONFIG_SERIAL_8250_BCM2835AUX=yCONFIG_SERIAL_8250_FSL=yCONFIG_SERIAL_8250_DW=yCONFIG_SERIAL_8250_EM=yCONFIG_SERIAL_8250_IOC3=yCONFIG_SERIAL_8250_RT288X=yCONFIG_SERIAL_8250_OMAP=yCONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=yCONFIG_SERIAL_8250_LPC18XX=yCONFIG_SERIAL_8250_MT6577=yCONFIG_SERIAL_8250_UNIPHIER=yCONFIG_SERIAL_8250_INGENIC=yCONFIG_SERIAL_8250_LPSS=yCONFIG_SERIAL_8250_MID=yCONFIG_SERIAL_8250_PERICOM=yCONFIG_SERIAL_8250_PXA=yCONFIG_SERIAL_8250_TEGRA=yCONFIG_SERIAL_8250_BCM7271=yCONFIG_SERIAL_OF_PLATFORM=y
#
# Non-8250 serial port support
#CONFIG_SERIAL_AMBA_PL010=yCONFIG_SERIAL_AMBA_PL010_CONSOLE=yCONFIG_SERIAL_ATMEL=yCONFIG_SERIAL_ATMEL_CONSOLE=yCONFIG_SERIAL_ATMEL_PDC=yCONFIG_SERIAL_ATMEL_TTYAT=yCONFIG_SERIAL_MESON=yCONFIG_SERIAL_MESON_CONSOLE=yCONFIG_SERIAL_CLPS711X=yCONFIG_SERIAL_CLPS711X_CONSOLE=yCONFIG_SERIAL_SAMSUNG=yCONFIG_SERIAL_SAMSUNG_UARTS_4=yCONFIG_SERIAL_SAMSUNG_UARTS=4CONFIG_SERIAL_SAMSUNG_CONSOLE=yCONFIG_SERIAL_TEGRA=yCONFIG_SERIAL_TEGRA_TCU=yCONFIG_SERIAL_TEGRA_TCU_CONSOLE=yCONFIG_SERIAL_MAX3100=yCONFIG_SERIAL_MAX310X=yCONFIG_SERIAL_IMX=yCONFIG_SERIAL_IMX_CONSOLE=yCONFIG_SERIAL_IMX_EARLYCON=yCONFIG_SERIAL_UARTLITE=yCONFIG_SERIAL_UARTLITE_CONSOLE=yCONFIG_SERIAL_UARTLITE_NR_UARTS=1CONFIG_SERIAL_SH_SCI=yCONFIG_SERIAL_SH_SCI_NR_UARTS=2CONFIG_SERIAL_SH_SCI_CONSOLE=yCONFIG_SERIAL_SH_SCI_EARLYCON=yCONFIG_SERIAL_SH_SCI_DMA=yCONFIG_SERIAL_HS_LPC32XX=yCONFIG_SERIAL_HS_LPC32XX_CONSOLE=yCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_ICOM=yCONFIG_SERIAL_JSM=yCONFIG_SERIAL_MSM=yCONFIG_SERIAL_MSM_CONSOLE=yCONFIG_SERIAL_QCOM_GENI=yCONFIG_SERIAL_QCOM_GENI_CONSOLE=yCONFIG_SERIAL_VT8500=yCONFIG_SERIAL_VT8500_CONSOLE=yCONFIG_SERIAL_OMAP=yCONFIG_SERIAL_OMAP_CONSOLE=yCONFIG_SERIAL_SIFIVE=yCONFIG_SERIAL_SIFIVE_CONSOLE=yCONFIG_SERIAL_LANTIQ=yCONFIG_SERIAL_LANTIQ_CONSOLE=yCONFIG_SERIAL_QE=yCONFIG_SERIAL_SCCNXP=yCONFIG_SERIAL_SCCNXP_CONSOLE=yCONFIG_SERIAL_SC16IS7XX_CORE=yCONFIG_SERIAL_SC16IS7XX=yCONFIG_SERIAL_SC16IS7XX_I2C=yCONFIG_SERIAL_SC16IS7XX_SPI=yCONFIG_SERIAL_TIMBERDALE=yCONFIG_SERIAL_BCM63XX=yCONFIG_SERIAL_BCM63XX_CONSOLE=yCONFIG_SERIAL_ALTERA_JTAGUART=yCONFIG_SERIAL_ALTERA_JTAGUART_CONSOLE=yCONFIG_SERIAL_ALTERA_JTAGUART_CONSOLE_BYPASS=yCONFIG_SERIAL_ALTERA_UART=yCONFIG_SERIAL_ALTERA_UART_MAXPORTS=4CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200CONFIG_SERIAL_ALTERA_UART_CONSOLE=yCONFIG_SERIAL_PCH_UART=yCONFIG_SERIAL_PCH_UART_CONSOLE=yCONFIG_SERIAL_MXS_AUART=yCONFIG_SERIAL_MXS_AUART_CONSOLE=yCONFIG_SERIAL_XILINX_PS_UART=yCONFIG_SERIAL_XILINX_PS_UART_CONSOLE=yCONFIG_SERIAL_MPS2_UART_CONSOLE=yCONFIG_SERIAL_MPS2_UART=yCONFIG_SERIAL_ARC=yCONFIG_SERIAL_ARC_CONSOLE=yCONFIG_SERIAL_ARC_NR_PORTS=1CONFIG_SERIAL_RP2=yCONFIG_SERIAL_RP2_NR_UARTS=32CONFIG_SERIAL_FSL_LPUART=yCONFIG_SERIAL_FSL_LPUART_CONSOLE=yCONFIG_SERIAL_FSL_LINFLEXUART=yCONFIG_SERIAL_FSL_LINFLEXUART_CONSOLE=yCONFIG_SERIAL_CONEXANT_DIGICOLOR=yCONFIG_SERIAL_CONEXANT_DIGICOLOR_CONSOLE=yCONFIG_SERIAL_ST_ASC=yCONFIG_SERIAL_ST_ASC_CONSOLE=yCONFIG_SERIAL_MEN_Z135=yCONFIG_SERIAL_SPRD=yCONFIG_SERIAL_SPRD_CONSOLE=yCONFIG_SERIAL_STM32=yCONFIG_SERIAL_STM32_CONSOLE=yCONFIG_SERIAL_MVEBU_UART=yCONFIG_SERIAL_MVEBU_CONSOLE=yCONFIG_SERIAL_OWL=yCONFIG_SERIAL_OWL_CONSOLE=yCONFIG_SERIAL_RDA=yCONFIG_SERIAL_RDA_CONSOLE=yCONFIG_SERIAL_MILBEAUT_USIO=yCONFIG_SERIAL_MILBEAUT_USIO_PORTS=4CONFIG_SERIAL_MILBEAUT_USIO_CONSOLE=yCONFIG_SERIAL_LITEUART=yCONFIG_SERIAL_LITEUART_MAX_PORTS=1CONFIG_SERIAL_LITEUART_CONSOLE=yCONFIG_SERIAL_SUNPLUS=yCONFIG_SERIAL_SUNPLUS_CONSOLE=y
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=yCONFIG_SERIAL_NONSTANDARD=yCONFIG_MOXA_INTELLIO=yCONFIG_MOXA_SMARTIO=yCONFIG_SYNCLINK_GT=yCONFIG_N_HDLC=yCONFIG_GOLDFISH_TTY=yCONFIG_GOLDFISH_TTY_EARLY_CONSOLE=yCONFIG_N_GSM=yCONFIG_NOZOMI=yCONFIG_NULL_TTY=yCONFIG_HVC_DRIVER=yCONFIG_RPMSG_TTY=yCONFIG_SERIAL_DEV_BUS=yCONFIG_SERIAL_DEV_CTRL_TTYPORT=yCONFIG_TTY_PRINTK=yCONFIG_TTY_PRINTK_LEVEL=6CONFIG_PRINTER=yCONFIG_LP_CONSOLE=yCONFIG_PPDEV=yCONFIG_VIRTIO_CONSOLE=yCONFIG_IPMI_HANDLER=yCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=yCONFIG_IPMI_DEVICE_INTERFACE=yCONFIG_IPMI_SI=yCONFIG_IPMI_SSIF=yCONFIG_IPMI_IPMB=yCONFIG_IPMI_WATCHDOG=yCONFIG_IPMI_POWEROFF=yCONFIG_IPMI_KCS_BMC=yCONFIG_ASPEED_KCS_IPMI_BMC=yCONFIG_NPCM7XX_KCS_IPMI_BMC=yCONFIG_IPMI_KCS_BMC_CDEV_IPMI=yCONFIG_IPMI_KCS_BMC_SERIO=yCONFIG_ASPEED_BT_IPMI_BMC=yCONFIG_IPMB_DEVICE_INTERFACE=yCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=yCONFIG_HW_RANDOM_INTEL=yCONFIG_HW_RANDOM_ATMEL=yCONFIG_HW_RANDOM_BA431=yCONFIG_HW_RANDOM_BCM2835=yCONFIG_HW_RANDOM_IPROC_RNG200=yCONFIG_HW_RANDOM_IXP4XX=yCONFIG_HW_RANDOM_OMAP=yCONFIG_HW_RANDOM_OMAP3_ROM=yCONFIG_HW_RANDOM_VIRTIO=yCONFIG_HW_RANDOM_IMX_RNGC=yCONFIG_HW_RANDOM_NOMADIK=yCONFIG_HW_RANDOM_STM32=yCONFIG_HW_RANDOM_POLARFIRE_SOC=yCONFIG_HW_RANDOM_MESON=yCONFIG_HW_RANDOM_MTK=yCONFIG_HW_RANDOM_EXYNOS=yCONFIG_HW_RANDOM_NPCM=yCONFIG_HW_RANDOM_KEYSTONE=yCONFIG_HW_RANDOM_CCTRNG=yCONFIG_HW_RANDOM_XIPHERA=yCONFIG_HW_RANDOM_CN10K=yCONFIG_APPLICOM=y
#
# PCMCIA character devices
#CONFIG_SYNCLINK_CS=yCONFIG_CARDMAN_4000=yCONFIG_CARDMAN_4040=yCONFIG_SCR24X=yCONFIG_IPWIRELESS=y
# end of PCMCIA character devices
CONFIG_DEVMEM=yCONFIG_DEVPORT=yCONFIG_HPET=yCONFIG_HPET_MMAP=yCONFIG_HPET_MMAP_DEFAULT=yCONFIG_HANGCHECK_TIMER=yCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=yCONFIG_TCG_TIS_SPI=yCONFIG_TCG_TIS_SPI_CR50=yCONFIG_TCG_TIS_I2C=yCONFIG_TCG_TIS_SYNQUACER=yCONFIG_TCG_TIS_I2C_CR50=yCONFIG_TCG_TIS_I2C_ATMEL=yCONFIG_TCG_TIS_I2C_INFINEON=yCONFIG_TCG_TIS_I2C_NUVOTON=yCONFIG_TCG_ATMEL=yCONFIG_TCG_INFINEON=yCONFIG_TCG_CRB=yCONFIG_TCG_VTPM_PROXY=yCONFIG_TCG_TIS_ST33ZP24=yCONFIG_TCG_TIS_ST33ZP24_I2C=yCONFIG_TCG_TIS_ST33ZP24_SPI=yCONFIG_XILLYBUS_CLASS=yCONFIG_XILLYBUS=yCONFIG_XILLYBUS_PCIE=yCONFIG_XILLYBUS_OF=yCONFIG_XILLYUSB=yCONFIG_RANDOM_TRUST_CPU=yCONFIG_RANDOM_TRUST_BOOTLOADER=y
# end of Character devices
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_ARB_GPIO_CHALLENGE=yCONFIG_I2C_MUX_GPIO=yCONFIG_I2C_MUX_GPMUX=yCONFIG_I2C_MUX_LTC4306=yCONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=yCONFIG_I2C_MUX_PINCTRL=yCONFIG_I2C_MUX_REG=yCONFIG_I2C_DEMUX_PINCTRL=yCONFIG_I2C_MUX_MLXCPLD=y
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_CCGX_UCSI=yCONFIG_I2C_ALI1535=yCONFIG_I2C_ALI1563=yCONFIG_I2C_ALI15X3=yCONFIG_I2C_AMD756=yCONFIG_I2C_AMD8111=yCONFIG_I2C_AMD_MP2=yCONFIG_I2C_HIX5HD2=yCONFIG_I2C_I801=yCONFIG_I2C_ISCH=yCONFIG_I2C_PIIX4=yCONFIG_I2C_CHT_WC=yCONFIG_I2C_NFORCE2=yCONFIG_I2C_NVIDIA_GPU=yCONFIG_I2C_SIS5595=yCONFIG_I2C_SIS630=yCONFIG_I2C_SIS96X=yCONFIG_I2C_VIA=yCONFIG_I2C_VIAPRO=y
#
# ACPI drivers
#CONFIG_I2C_SCMI=y
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_ALTERA=yCONFIG_I2C_ASPEED=yCONFIG_I2C_AT91=y CONFIG_I2C_AT91_SLAVE_EXPERIMENTAL=y CONFIG_I2C_AXXIA=yCONFIG_I2C_BCM2835=yCONFIG_I2C_BCM_IPROC=yCONFIG_I2C_BCM_KONA=yCONFIG_I2C_BRCMSTB=yCONFIG_I2C_CADENCE=yCONFIG_I2C_CBUS_GPIO=yCONFIG_I2C_DAVINCI=yCONFIG_I2C_DESIGNWARE_CORE=y CONFIG_I2C_DESIGNWARE_SLAVE=y CONFIG_I2C_DESIGNWARE_PLATFORM=y CONFIG_I2C_DESIGNWARE_PCI=yCONFIG_I2C_DIGICOLOR=yCONFIG_I2C_EG20T=yCONFIG_I2C_EMEV2=yCONFIG_I2C_EXYNOS5=yCONFIG_I2C_GPIO=yCONFIG_I2C_GPIO_FAULT_INJECTOR=y CONFIG_I2C_HIGHLANDER=yCONFIG_I2C_HISI=yCONFIG_I2C_IMG=yCONFIG_I2C_IMX=yCONFIG_I2C_IMX_LPI2C=yCONFIG_I2C_IOP3XX=yCONFIG_I2C_JZ4780=yCONFIG_I2C_KEMPLD=yCONFIG_I2C_LPC2K=yCONFIG_I2C_MESON=yCONFIG_I2C_MICROCHIP_CORE=yCONFIG_I2C_MT65XX=yCONFIG_I2C_MT7621=yCONFIG_I2C_MV64XXX=yCONFIG_I2C_MXS=yCONFIG_I2C_NPCM=yCONFIG_I2C_OCORES=yCONFIG_I2C_OMAP=yCONFIG_I2C_OWL=yCONFIG_I2C_APPLE=yCONFIG_I2C_PCA_PLATFORM=yCONFIG_I2C_PNX=yCONFIG_I2C_PXA=yCONFIG_I2C_PXA_SLAVE=yCONFIG_I2C_QCOM_CCI=yCONFIG_I2C_QCOM_GENI=yCONFIG_I2C_QUP=yCONFIG_I2C_RIIC=yCONFIG_I2C_RK3X=yCONFIG_I2C_RZV2M=yCONFIG_I2C_S3C2410=yCONFIG_I2C_SH_MOBILE=yCONFIG_I2C_SIMTEC=yCONFIG_I2C_SPRD=yCONFIG_I2C_ST=yCONFIG_I2C_STM32F4=yCONFIG_I2C_STM32F7=yCONFIG_I2C_SUN6I_P2WI=yCONFIG_I2C_SYNQUACER=yCONFIG_I2C_TEGRA_BPMP=yCONFIG_I2C_UNIPHIER=yCONFIG_I2C_UNIPHIER_F=yCONFIG_I2C_VERSATILE=yCONFIG_I2C_WMT=yCONFIG_I2C_THUNDERX=yCONFIG_I2C_XILINX=yCONFIG_I2C_XLP9XX=yCONFIG_I2C_RCAR=y
#
# External I2C/SMBus adapter drivers
#CONFIG_I2C_DIOLAN_U2C=yCONFIG_I2C_DLN2=yCONFIG_I2C_CP2615=yCONFIG_I2C_PARPORT=yCONFIG_I2C_PCI1XXXX=yCONFIG_I2C_ROBOTFUZZ_OSIF=yCONFIG_I2C_TAOS_EVM=yCONFIG_I2C_TINY_USB=yCONFIG_I2C_VIPERBOARD=y
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_MLXCPLD=yCONFIG_I2C_CROS_EC_TUNNEL=yCONFIG_I2C_FSI=yCONFIG_I2C_VIRTIO=y
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=mCONFIG_I2C_SLAVE=yCONFIG_I2C_SLAVE_EEPROM=yCONFIG_I2C_SLAVE_TESTUNIT=yCONFIG_I2C_DEBUG_CORE=yCONFIG_I2C_DEBUG_ALGO=yCONFIG_I2C_DEBUG_BUS=y
# end of I2C support
CONFIG_I3C=yCONFIG_CDNS_I3C_MASTER=yCONFIG_DW_I3C_MASTER=yCONFIG_SVC_I3C_MASTER=yCONFIG_MIPI_I3C_HCI=yCONFIG_SPI=yCONFIG_SPI_DEBUG=yCONFIG_SPI_MASTER=yCONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#CONFIG_SPI_ALTERA=yCONFIG_SPI_ALTERA_CORE=yCONFIG_SPI_ALTERA_DFL=yCONFIG_SPI_AR934X=yCONFIG_SPI_ATH79=yCONFIG_SPI_ARMADA_3700=yCONFIG_SPI_ASPEED_SMC=yCONFIG_SPI_ATMEL=yCONFIG_SPI_AT91_USART=yCONFIG_SPI_ATMEL_QUADSPI=yCONFIG_SPI_AXI_SPI_ENGINE=yCONFIG_SPI_BCM2835=yCONFIG_SPI_BCM2835AUX=yCONFIG_SPI_BCM63XX=yCONFIG_SPI_BCM63XX_HSSPI=yCONFIG_SPI_BCM_QSPI=yCONFIG_SPI_BITBANG=yCONFIG_SPI_BUTTERFLY=yCONFIG_SPI_CADENCE=yCONFIG_SPI_CADENCE_QUADSPI=yCONFIG_SPI_CADENCE_XSPI=yCONFIG_SPI_CLPS711X=yCONFIG_SPI_DESIGNWARE=yCONFIG_SPI_DW_DMA=yCONFIG_SPI_DW_PCI=yCONFIG_SPI_DW_MMIO=yCONFIG_SPI_DW_BT1=yCONFIG_SPI_DW_BT1_DIRMAP=yCONFIG_SPI_DLN2=yCONFIG_SPI_EP93XX=yCONFIG_SPI_FSI=yCONFIG_SPI_FSL_LPSPI=yCONFIG_SPI_FSL_QUADSPI=yCONFIG_SPI_GXP=yCONFIG_SPI_HISI_KUNPENG=yCONFIG_SPI_HISI_SFC_V3XX=yCONFIG_SPI_NXP_FLEXSPI=yCONFIG_SPI_GPIO=yCONFIG_SPI_IMG_SPFI=yCONFIG_SPI_IMX=yCONFIG_SPI_INGENIC=yCONFIG_SPI_INTEL=yCONFIG_SPI_INTEL_PCI=yCONFIG_SPI_INTEL_PLATFORM=yCONFIG_SPI_JCORE=yCONFIG_SPI_LM70_LLP=yCONFIG_SPI_LP8841_RTC=yCONFIG_SPI_FSL_LIB=yCONFIG_SPI_FSL_SPI=yCONFIG_SPI_FSL_DSPI=yCONFIG_SPI_MESON_SPICC=yCONFIG_SPI_MESON_SPIFC=yCONFIG_SPI_MICROCHIP_CORE=yCONFIG_SPI_MICROCHIP_CORE_QSPI=yCONFIG_SPI_MT65XX=yCONFIG_SPI_MT7621=yCONFIG_SPI_MTK_NOR=yCONFIG_SPI_MTK_SNFI=yCONFIG_SPI_NPCM_FIU=yCONFIG_SPI_NPCM_PSPI=yCONFIG_SPI_LANTIQ_SSC=yCONFIG_SPI_OC_TINY=yCONFIG_SPI_OMAP24XX=yCONFIG_SPI_TI_QSPI=yCONFIG_SPI_OMAP_100K=yCONFIG_SPI_ORION=yCONFIG_SPI_PIC32=yCONFIG_SPI_PIC32_SQI=yCONFIG_SPI_PXA2XX=yCONFIG_SPI_PXA2XX_PCI=yCONFIG_SPI_ROCKCHIP=yCONFIG_SPI_ROCKCHIP_SFC=yCONFIG_SPI_RPCIF=yCONFIG_SPI_RSPI=yCONFIG_SPI_QUP=yCONFIG_SPI_QCOM_GENI=yCONFIG_SPI_S3C64XX=yCONFIG_SPI_SC18IS602=yCONFIG_SPI_SH_MSIOF=yCONFIG_SPI_SH=yCONFIG_SPI_SH_HSPI=yCONFIG_SPI_SIFIVE=yCONFIG_SPI_SLAVE_MT27XX=yCONFIG_SPI_SPRD=yCONFIG_SPI_SPRD_ADI=yCONFIG_SPI_STM32=yCONFIG_SPI_STM32_QSPI=yCONFIG_SPI_ST_SSC4=yCONFIG_SPI_SUN4I=yCONFIG_SPI_SUN6I=yCONFIG_SPI_SUNPLUS_SP7021=yCONFIG_SPI_SYNQUACER=yCONFIG_SPI_MXIC=yCONFIG_SPI_TEGRA210_QUAD=yCONFIG_SPI_TEGRA114=yCONFIG_SPI_TEGRA20_SFLASH=yCONFIG_SPI_TEGRA20_SLINK=yCONFIG_SPI_THUNDERX=yCONFIG_SPI_TOPCLIFF_PCH=yCONFIG_SPI_UNIPHIER=yCONFIG_SPI_XCOMM=yCONFIG_SPI_XILINX=yCONFIG_SPI_XLP=yCONFIG_SPI_XTENSA_XTFPGA=yCONFIG_SPI_ZYNQ_QSPI=yCONFIG_SPI_ZYNQMP_GQSPI=yCONFIG_SPI_AMD=y
#
# SPI Multiplexer support
#CONFIG_SPI_MUX=y
#
# SPI Protocol Masters
#CONFIG_SPI_SPIDEV=yCONFIG_SPI_LOOPBACK_TEST=mCONFIG_SPI_TLE62X0=yCONFIG_SPI_SLAVE=yCONFIG_SPI_SLAVE_TIME=yCONFIG_SPI_SLAVE_SYSTEM_CONTROL=yCONFIG_SPI_DYNAMIC=yCONFIG_SPMI=yCONFIG_SPMI_HISI3670=yCONFIG_SPMI_MSM_PMIC_ARB=yCONFIG_SPMI_MTK_PMIF=yCONFIG_HSI=yCONFIG_HSI_BOARDINFO=y
#
# HSI controllers
#
#
# HSI clients
#CONFIG_HSI_CHAR=yCONFIG_PPS=yCONFIG_PPS_DEBUG=yCONFIG_NTP_PPS=y
#
# PPS clients support
#CONFIG_PPS_CLIENT_KTIMER=yCONFIG_PPS_CLIENT_LDISC=yCONFIG_PPS_CLIENT_PARPORT=yCONFIG_PPS_CLIENT_GPIO=y
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_PTP_1588_CLOCK_OPTIONAL=yCONFIG_PTP_1588_CLOCK_DTE=yCONFIG_PTP_1588_CLOCK_QORIQ=yCONFIG_DP83640_PHY=yCONFIG_PTP_1588_CLOCK_INES=yCONFIG_PTP_1588_CLOCK_PCH=yCONFIG_PTP_1588_CLOCK_IDT82P33=yCONFIG_PTP_1588_CLOCK_IDTCM=yCONFIG_PTP_1588_CLOCK_OCP=y
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_GENERIC_PINCTRL_GROUPS=yCONFIG_PINMUX=yCONFIG_GENERIC_PINMUX_FUNCTIONS=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=yCONFIG_DEBUG_PINCTRL=yCONFIG_PINCTRL_AMD=yCONFIG_PINCTRL_AS3722=yCONFIG_PINCTRL_AT91PIO4=yCONFIG_PINCTRL_AXP209=yCONFIG_PINCTRL_BM1880=yCONFIG_PINCTRL_CY8C95X0=yCONFIG_PINCTRL_DA850_PUPD=yCONFIG_PINCTRL_DA9062=yCONFIG_PINCTRL_EQUILIBRIUM=yCONFIG_PINCTRL_INGENIC=yCONFIG_PINCTRL_LPC18XX=yCONFIG_PINCTRL_MAX77620=yCONFIG_PINCTRL_MCP23S08_I2C=yCONFIG_PINCTRL_MCP23S08_SPI=yCONFIG_PINCTRL_MCP23S08=yCONFIG_PINCTRL_MICROCHIP_SGPIO=yCONFIG_PINCTRL_OCELOT=yCONFIG_PINCTRL_PALMAS=yCONFIG_PINCTRL_PISTACHIO=yCONFIG_PINCTRL_RK805=yCONFIG_PINCTRL_ROCKCHIP=yCONFIG_PINCTRL_SINGLE=yCONFIG_PINCTRL_STMFX=yCONFIG_PINCTRL_SX150X=yCONFIG_PINCTRL_OWL=yCONFIG_PINCTRL_S500=yCONFIG_PINCTRL_S700=yCONFIG_PINCTRL_S900=yCONFIG_PINCTRL_ASPEED=yCONFIG_PINCTRL_ASPEED_G4=yCONFIG_PINCTRL_ASPEED_G5=yCONFIG_PINCTRL_ASPEED_G6=yCONFIG_PINCTRL_BCM281XX=yCONFIG_PINCTRL_BCM2835=yCONFIG_PINCTRL_BCM4908=yCONFIG_PINCTRL_BCM63XX=yCONFIG_PINCTRL_BCM6318=yCONFIG_PINCTRL_BCM6328=yCONFIG_PINCTRL_BCM6358=yCONFIG_PINCTRL_BCM6362=yCONFIG_PINCTRL_BCM6368=yCONFIG_PINCTRL_BCM63268=yCONFIG_PINCTRL_IPROC_GPIO=yCONFIG_PINCTRL_CYGNUS_MUX=yCONFIG_PINCTRL_NS=yCONFIG_PINCTRL_NSP_GPIO=yCONFIG_PINCTRL_NS2_MUX=yCONFIG_PINCTRL_NSP_MUX=yCONFIG_PINCTRL_BERLIN=yCONFIG_PINCTRL_AS370=yCONFIG_PINCTRL_BERLIN_BG4CT=yCONFIG_PINCTRL_LOCHNAGAR=yCONFIG_PINCTRL_MADERA=yCONFIG_PINCTRL_CS47L15=yCONFIG_PINCTRL_CS47L35=yCONFIG_PINCTRL_CS47L85=yCONFIG_PINCTRL_CS47L90=yCONFIG_PINCTRL_CS47L92=yCONFIG_PINCTRL_IMX=yCONFIG_PINCTRL_IMX8MM=yCONFIG_PINCTRL_IMX8MN=yCONFIG_PINCTRL_IMX8MP=yCONFIG_PINCTRL_IMX8MQ=y
#
# Intel pinctrl drivers
#CONFIG_PINCTRL_BAYTRAIL=yCONFIG_PINCTRL_CHERRYVIEW=yCONFIG_PINCTRL_LYNXPOINT=yCONFIG_PINCTRL_INTEL=yCONFIG_PINCTRL_ALDERLAKE=yCONFIG_PINCTRL_BROXTON=yCONFIG_PINCTRL_CANNONLAKE=yCONFIG_PINCTRL_CEDARFORK=yCONFIG_PINCTRL_DENVERTON=yCONFIG_PINCTRL_ELKHARTLAKE=yCONFIG_PINCTRL_EMMITSBURG=yCONFIG_PINCTRL_GEMINILAKE=yCONFIG_PINCTRL_ICELAKE=yCONFIG_PINCTRL_JASPERLAKE=yCONFIG_PINCTRL_LAKEFIELD=yCONFIG_PINCTRL_LEWISBURG=yCONFIG_PINCTRL_METEORLAKE=yCONFIG_PINCTRL_SUNRISEPOINT=yCONFIG_PINCTRL_TIGERLAKE=y
# end of Intel pinctrl drivers
#
# MediaTek pinctrl drivers
#CONFIG_EINT_MTK=yCONFIG_PINCTRL_MTK=yCONFIG_PINCTRL_MTK_V2=yCONFIG_PINCTRL_MTK_MOORE=yCONFIG_PINCTRL_MTK_PARIS=yCONFIG_PINCTRL_MT2701=yCONFIG_PINCTRL_MT7623=yCONFIG_PINCTRL_MT7629=yCONFIG_PINCTRL_MT8135=yCONFIG_PINCTRL_MT8127=yCONFIG_PINCTRL_MT2712=yCONFIG_PINCTRL_MT6765=yCONFIG_PINCTRL_MT6779=yCONFIG_PINCTRL_MT6795=yCONFIG_PINCTRL_MT6797=yCONFIG_PINCTRL_MT7622=yCONFIG_PINCTRL_MT7986=yCONFIG_PINCTRL_MT8167=yCONFIG_PINCTRL_MT8173=yCONFIG_PINCTRL_MT8183=yCONFIG_PINCTRL_MT8186=yCONFIG_PINCTRL_MT8188=yCONFIG_PINCTRL_MT8192=yCONFIG_PINCTRL_MT8195=yCONFIG_PINCTRL_MT8365=yCONFIG_PINCTRL_MT8516=yCONFIG_PINCTRL_MT6397=y
# end of MediaTek pinctrl drivers
CONFIG_PINCTRL_MESON=yCONFIG_PINCTRL_WPCM450=yCONFIG_PINCTRL_NPCM7XX=yCONFIG_PINCTRL_PXA=yCONFIG_PINCTRL_PXA25X=yCONFIG_PINCTRL_PXA27X=yCONFIG_PINCTRL_MSM=yCONFIG_PINCTRL_APQ8064=yCONFIG_PINCTRL_APQ8084=yCONFIG_PINCTRL_IPQ4019=yCONFIG_PINCTRL_IPQ8064=yCONFIG_PINCTRL_IPQ8074=yCONFIG_PINCTRL_IPQ6018=yCONFIG_PINCTRL_MSM8226=yCONFIG_PINCTRL_MSM8660=yCONFIG_PINCTRL_MSM8960=yCONFIG_PINCTRL_MDM9607=yCONFIG_PINCTRL_MDM9615=yCONFIG_PINCTRL_MSM8X74=yCONFIG_PINCTRL_MSM8909=yCONFIG_PINCTRL_MSM8916=yCONFIG_PINCTRL_MSM8953=yCONFIG_PINCTRL_MSM8976=yCONFIG_PINCTRL_MSM8994=yCONFIG_PINCTRL_MSM8996=yCONFIG_PINCTRL_MSM8998=yCONFIG_PINCTRL_QCM2290=yCONFIG_PINCTRL_QCS404=yCONFIG_PINCTRL_QDF2XXX=yCONFIG_PINCTRL_QCOM_SPMI_PMIC=yCONFIG_PINCTRL_QCOM_SSBI_PMIC=yCONFIG_PINCTRL_SC7180=yCONFIG_PINCTRL_SC7280=yCONFIG_PINCTRL_SC7280_LPASS_LPI=yCONFIG_PINCTRL_SC8180X=yCONFIG_PINCTRL_SC8280XP=yCONFIG_PINCTRL_SDM660=yCONFIG_PINCTRL_SDM845=yCONFIG_PINCTRL_SDX55=yCONFIG_PINCTRL_SM6115=yCONFIG_PINCTRL_SM6125=yCONFIG_PINCTRL_SM6350=yCONFIG_PINCTRL_SM6375=yCONFIG_PINCTRL_SDX65=yCONFIG_PINCTRL_SM8150=yCONFIG_PINCTRL_SM8250=yCONFIG_PINCTRL_SM8250_LPASS_LPI=yCONFIG_PINCTRL_SM8350=yCONFIG_PINCTRL_SM8450=yCONFIG_PINCTRL_SM8450_LPASS_LPI=yCONFIG_PINCTRL_SC8280XP_LPASS_LPI=yCONFIG_PINCTRL_LPASS_LPI=y
#
# Renesas pinctrl drivers
#CONFIG_PINCTRL_RENESAS=yCONFIG_PINCTRL_SH_PFC=yCONFIG_PINCTRL_SH_PFC_GPIO=yCONFIG_PINCTRL_SH_FUNC_GPIO=yCONFIG_PINCTRL_PFC_EMEV2=yCONFIG_PINCTRL_PFC_R8A77995=yCONFIG_PINCTRL_PFC_R8A7794=yCONFIG_PINCTRL_PFC_R8A77990=yCONFIG_PINCTRL_PFC_R8A7779=yCONFIG_PINCTRL_PFC_R8A7790=yCONFIG_PINCTRL_PFC_R8A77950=yCONFIG_PINCTRL_PFC_R8A77951=yCONFIG_PINCTRL_PFC_R8A7778=yCONFIG_PINCTRL_PFC_R8A7793=yCONFIG_PINCTRL_PFC_R8A7791=yCONFIG_PINCTRL_PFC_R8A77965=yCONFIG_PINCTRL_PFC_R8A77960=yCONFIG_PINCTRL_PFC_R8A77961=yCONFIG_PINCTRL_PFC_R8A779F0=yCONFIG_PINCTRL_PFC_R8A7792=yCONFIG_PINCTRL_PFC_R8A77980=yCONFIG_PINCTRL_PFC_R8A77970=yCONFIG_PINCTRL_PFC_R8A779A0=yCONFIG_PINCTRL_PFC_R8A779G0=yCONFIG_PINCTRL_PFC_R8A7740=yCONFIG_PINCTRL_PFC_R8A73A4=yCONFIG_PINCTRL_RZA1=yCONFIG_PINCTRL_RZA2=yCONFIG_PINCTRL_RZG2L=yCONFIG_PINCTRL_PFC_R8A77470=yCONFIG_PINCTRL_PFC_R8A7745=yCONFIG_PINCTRL_PFC_R8A7742=yCONFIG_PINCTRL_PFC_R8A7743=yCONFIG_PINCTRL_PFC_R8A7744=yCONFIG_PINCTRL_PFC_R8A774C0=yCONFIG_PINCTRL_PFC_R8A774E1=yCONFIG_PINCTRL_PFC_R8A774A1=yCONFIG_PINCTRL_PFC_R8A774B1=yCONFIG_PINCTRL_RZN1=yCONFIG_PINCTRL_RZV2M=yCONFIG_PINCTRL_PFC_SH7203=yCONFIG_PINCTRL_PFC_SH7264=yCONFIG_PINCTRL_PFC_SH7269=yCONFIG_PINCTRL_PFC_SH7720=yCONFIG_PINCTRL_PFC_SH7722=yCONFIG_PINCTRL_PFC_SH7734=yCONFIG_PINCTRL_PFC_SH7757=yCONFIG_PINCTRL_PFC_SH7785=yCONFIG_PINCTRL_PFC_SH7786=yCONFIG_PINCTRL_PFC_SH73A0=yCONFIG_PINCTRL_PFC_SH7723=yCONFIG_PINCTRL_PFC_SH7724=yCONFIG_PINCTRL_PFC_SHX3=y
# end of Renesas pinctrl drivers
CONFIG_PINCTRL_SAMSUNG=yCONFIG_PINCTRL_EXYNOS=yCONFIG_PINCTRL_EXYNOS_ARM=yCONFIG_PINCTRL_EXYNOS_ARM64=yCONFIG_PINCTRL_S3C24XX=yCONFIG_PINCTRL_S3C64XX=yCONFIG_PINCTRL_SPRD=yCONFIG_PINCTRL_SPRD_SC9860=yCONFIG_PINCTRL_STARFIVE_JH7100=yCONFIG_PINCTRL_STM32=yCONFIG_PINCTRL_STM32F429=yCONFIG_PINCTRL_STM32F469=yCONFIG_PINCTRL_STM32F746=yCONFIG_PINCTRL_STM32F769=yCONFIG_PINCTRL_STM32H743=yCONFIG_PINCTRL_STM32MP135=yCONFIG_PINCTRL_STM32MP157=yCONFIG_PINCTRL_TI_IODELAY=yCONFIG_PINCTRL_UNIPHIER=yCONFIG_PINCTRL_UNIPHIER_LD4=yCONFIG_PINCTRL_UNIPHIER_PRO4=yCONFIG_PINCTRL_UNIPHIER_SLD8=yCONFIG_PINCTRL_UNIPHIER_PRO5=yCONFIG_PINCTRL_UNIPHIER_PXS2=yCONFIG_PINCTRL_UNIPHIER_LD6B=yCONFIG_PINCTRL_UNIPHIER_LD11=yCONFIG_PINCTRL_UNIPHIER_LD20=yCONFIG_PINCTRL_UNIPHIER_PXS3=yCONFIG_PINCTRL_UNIPHIER_NX1=yCONFIG_PINCTRL_VISCONTI=yCONFIG_PINCTRL_TMPV7700=yCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_OF_GPIO=yCONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=yCONFIG_DEBUG_GPIO=yCONFIG_GPIO_SYSFS=yCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=yCONFIG_GPIO_REGMAP=yCONFIG_GPIO_MAX730X=y
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_74XX_MMIO=yCONFIG_GPIO_ALTERA=yCONFIG_GPIO_AMDPT=yCONFIG_GPIO_ASPEED=yCONFIG_GPIO_ASPEED_SGPIO=yCONFIG_GPIO_ATH79=yCONFIG_GPIO_RASPBERRYPI_EXP=yCONFIG_GPIO_BCM_KONA=yCONFIG_GPIO_BCM_XGS_IPROC=yCONFIG_GPIO_BRCMSTB=yCONFIG_GPIO_CADENCE=yCONFIG_GPIO_CLPS711X=yCONFIG_GPIO_DWAPB=yCONFIG_GPIO_EIC_SPRD=yCONFIG_GPIO_EM=yCONFIG_GPIO_EXAR=yCONFIG_GPIO_FTGPIO010=yCONFIG_GPIO_GENERIC_PLATFORM=yCONFIG_GPIO_GRGPIO=yCONFIG_GPIO_HISI=yCONFIG_GPIO_HLWD=yCONFIG_GPIO_IMX_SCU=yCONFIG_GPIO_IOP=yCONFIG_GPIO_LOGICVC=yCONFIG_GPIO_LPC18XX=yCONFIG_GPIO_LPC32XX=yCONFIG_GPIO_MB86S7X=yCONFIG_GPIO_MENZ127=yCONFIG_GPIO_MPC8XXX=yCONFIG_GPIO_MT7621=yCONFIG_GPIO_MXC=yCONFIG_GPIO_MXS=yCONFIG_GPIO_PMIC_EIC_SPRD=yCONFIG_GPIO_PXA=yCONFIG_GPIO_RCAR=yCONFIG_GPIO_RDA=yCONFIG_GPIO_ROCKCHIP=yCONFIG_GPIO_SAMA5D2_PIOBU=yCONFIG_GPIO_SIFIVE=yCONFIG_GPIO_SIOX=yCONFIG_GPIO_SNPS_CREG=yCONFIG_GPIO_SPRD=yCONFIG_GPIO_STP_XWAY=yCONFIG_GPIO_SYSCON=yCONFIG_GPIO_TEGRA=yCONFIG_GPIO_TEGRA186=yCONFIG_GPIO_TS4800=yCONFIG_GPIO_THUNDERX=yCONFIG_GPIO_UNIPHIER=yCONFIG_GPIO_VISCONTI=yCONFIG_GPIO_VX855=yCONFIG_GPIO_WCD934X=yCONFIG_GPIO_XGENE_SB=yCONFIG_GPIO_XILINX=yCONFIG_GPIO_XLP=yCONFIG_GPIO_AMD_FCH=yCONFIG_GPIO_IDT3243X=y
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#CONFIG_GPIO_ADNP=yCONFIG_GPIO_GW_PLD=yCONFIG_GPIO_MAX7300=yCONFIG_GPIO_MAX732X=yCONFIG_GPIO_MAX732X_IRQ=yCONFIG_GPIO_PCA953X=yCONFIG_GPIO_PCA953X_IRQ=yCONFIG_GPIO_PCA9570=yCONFIG_GPIO_PCF857X=yCONFIG_GPIO_TPIC2810=yCONFIG_GPIO_TS4900=y
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#CONFIG_GPIO_ADP5520=yCONFIG_GPIO_ARIZONA=yCONFIG_GPIO_BD71815=yCONFIG_GPIO_BD71828=yCONFIG_GPIO_BD9571MWV=yCONFIG_GPIO_CRYSTAL_COVE=yCONFIG_GPIO_DA9052=yCONFIG_GPIO_DA9055=yCONFIG_GPIO_DLN2=yCONFIG_GPIO_JANZ_TTL=yCONFIG_GPIO_KEMPLD=yCONFIG_GPIO_LP3943=yCONFIG_GPIO_LP873X=yCONFIG_GPIO_LP87565=yCONFIG_GPIO_MADERA=yCONFIG_GPIO_MAX77620=yCONFIG_GPIO_MAX77650=yCONFIG_GPIO_PALMAS=yCONFIG_GPIO_RC5T583=yCONFIG_GPIO_SL28CPLD=yCONFIG_GPIO_STMPE=yCONFIG_GPIO_TC3589X=yCONFIG_GPIO_TIMBERDALE=yCONFIG_GPIO_TPS65086=yCONFIG_GPIO_TPS65218=yCONFIG_GPIO_TPS6586X=yCONFIG_GPIO_TPS65910=yCONFIG_GPIO_TPS65912=yCONFIG_GPIO_TQMX86=yCONFIG_GPIO_TWL4030=yCONFIG_GPIO_TWL6040=yCONFIG_GPIO_UCB1400=yCONFIG_GPIO_WM831X=yCONFIG_GPIO_WM8350=yCONFIG_GPIO_WM8994=y
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#CONFIG_GPIO_AMD8111=yCONFIG_GPIO_MLXBF=yCONFIG_GPIO_MLXBF2=yCONFIG_GPIO_ML_IOH=yCONFIG_GPIO_PCH=yCONFIG_GPIO_PCI_IDIO_16=yCONFIG_GPIO_PCIE_IDIO_24=yCONFIG_GPIO_RDC321X=y
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#CONFIG_GPIO_74X164=yCONFIG_GPIO_MAX3191X=yCONFIG_GPIO_MAX7301=yCONFIG_GPIO_MC33880=yCONFIG_GPIO_PISOSR=yCONFIG_GPIO_XRA1403=yCONFIG_GPIO_MOXTET=y
# end of SPI GPIO expanders
#
# USB GPIO expanders
#CONFIG_GPIO_VIPERBOARD=y
# end of USB GPIO expanders
#
# Virtual GPIO drivers
#CONFIG_GPIO_AGGREGATOR=yCONFIG_GPIO_MOCKUP=yCONFIG_GPIO_VIRTIO=yCONFIG_GPIO_SIM=y
# end of Virtual GPIO drivers
CONFIG_W1=yCONFIG_W1_CON=y
#
# 1-wire Bus Masters
#CONFIG_W1_MASTER_MATROX=yCONFIG_W1_MASTER_DS2490=yCONFIG_W1_MASTER_DS2482=yCONFIG_W1_MASTER_MXC=yCONFIG_W1_MASTER_DS1WM=yCONFIG_W1_MASTER_GPIO=yCONFIG_W1_MASTER_SGI=y
# end of 1-wire Bus Masters
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=yCONFIG_W1_SLAVE_SMEM=yCONFIG_W1_SLAVE_DS2405=yCONFIG_W1_SLAVE_DS2408=yCONFIG_W1_SLAVE_DS2408_READBACK=yCONFIG_W1_SLAVE_DS2413=yCONFIG_W1_SLAVE_DS2406=yCONFIG_W1_SLAVE_DS2423=yCONFIG_W1_SLAVE_DS2805=yCONFIG_W1_SLAVE_DS2430=yCONFIG_W1_SLAVE_DS2431=yCONFIG_W1_SLAVE_DS2433=yCONFIG_W1_SLAVE_DS2433_CRC=yCONFIG_W1_SLAVE_DS2438=yCONFIG_W1_SLAVE_DS250X=yCONFIG_W1_SLAVE_DS2780=yCONFIG_W1_SLAVE_DS2781=yCONFIG_W1_SLAVE_DS28E04=yCONFIG_W1_SLAVE_DS28E17=y
# end of 1-wire Slaves
CONFIG_POWER_RESET=yCONFIG_POWER_RESET_AS3722=yCONFIG_POWER_RESET_ATC260X=yCONFIG_POWER_RESET_BRCMKONA=yCONFIG_POWER_RESET_BRCMSTB=yCONFIG_POWER_RESET_GEMINI_POWEROFF=yCONFIG_POWER_RESET_GPIO=yCONFIG_POWER_RESET_GPIO_RESTART=yCONFIG_POWER_RESET_LINKSTATION=yCONFIG_POWER_RESET_OCELOT_RESET=yCONFIG_POWER_RESET_PIIX4_POWEROFF=yCONFIG_POWER_RESET_LTC2952=yCONFIG_POWER_RESET_MT6323=yCONFIG_POWER_RESET_REGULATOR=yCONFIG_POWER_RESET_RESTART=yCONFIG_POWER_RESET_TPS65086=yCONFIG_POWER_RESET_KEYSTONE=yCONFIG_POWER_RESET_SYSCON=yCONFIG_POWER_RESET_SYSCON_POWEROFF=yCONFIG_POWER_RESET_RMOBILE=yCONFIG_REBOOT_MODE=yCONFIG_SYSCON_REBOOT_MODE=yCONFIG_POWER_RESET_SC27XX=yCONFIG_NVMEM_REBOOT_MODE=yCONFIG_POWER_MLXBF=yCONFIG_POWER_SUPPLY=yCONFIG_POWER_SUPPLY_DEBUG=yCONFIG_POWER_SUPPLY_HWMON=yCONFIG_PDA_POWER=yCONFIG_GENERIC_ADC_BATTERY=yCONFIG_IP5XXX_POWER=yCONFIG_MAX8925_POWER=yCONFIG_WM831X_BACKUP=yCONFIG_WM831X_POWER=yCONFIG_WM8350_POWER=yCONFIG_TEST_POWER=yCONFIG_BATTERY_88PM860X=yCONFIG_CHARGER_ADP5061=yCONFIG_BATTERY_ACT8945A=yCONFIG_BATTERY_CPCAP=yCONFIG_BATTERY_CW2015=yCONFIG_BATTERY_DS2760=yCONFIG_BATTERY_DS2780=yCONFIG_BATTERY_DS2781=yCONFIG_BATTERY_DS2782=yCONFIG_BATTERY_LEGO_EV3=yCONFIG_BATTERY_OLPC=yCONFIG_BATTERY_SAMSUNG_SDI=yCONFIG_BATTERY_INGENIC=yCONFIG_BATTERY_WM97XX=yCONFIG_BATTERY_SBS=yCONFIG_CHARGER_SBS=yCONFIG_MANAGER_SBS=yCONFIG_BATTERY_BQ27XXX=yCONFIG_BATTERY_BQ27XXX_I2C=yCONFIG_BATTERY_BQ27XXX_HDQ=yCONFIG_BATTERY_BQ27XXX_DT_UPDATES_NVM=yCONFIG_BATTERY_DA9030=yCONFIG_BATTERY_DA9052=yCONFIG_CHARGER_DA9150=yCONFIG_BATTERY_DA9150=yCONFIG_CHARGER_AXP20X=yCONFIG_BATTERY_AXP20X=yCONFIG_AXP20X_POWER=yCONFIG_BATTERY_MAX17040=yCONFIG_BATTERY_MAX17042=yCONFIG_BATTERY_MAX1721X=yCONFIG_BATTERY_TWL4030_MADC=yCONFIG_CHARGER_88PM860X=yCONFIG_CHARGER_PCF50633=yCONFIG_BATTERY_RX51=yCONFIG_CHARGER_CPCAP=yCONFIG_CHARGER_ISP1704=yCONFIG_CHARGER_MAX8903=yCONFIG_CHARGER_TWL4030=yCONFIG_CHARGER_LP8727=yCONFIG_CHARGER_LP8788=yCONFIG_CHARGER_GPIO=yCONFIG_CHARGER_MANAGER=yCONFIG_CHARGER_LT3651=yCONFIG_CHARGER_LTC4162L=yCONFIG_CHARGER_MAX14577=yCONFIG_CHARGER_DETECTOR_MAX14656=yCONFIG_CHARGER_MAX77650=yCONFIG_CHARGER_MAX77693=yCONFIG_CHARGER_MAX77976=yCONFIG_CHARGER_MAX8997=yCONFIG_CHARGER_MAX8998=yCONFIG_CHARGER_MP2629=yCONFIG_CHARGER_MT6360=yCONFIG_CHARGER_MT6370=yCONFIG_CHARGER_QCOM_SMBB=yCONFIG_CHARGER_BQ2415X=yCONFIG_CHARGER_BQ24190=yCONFIG_CHARGER_BQ24257=yCONFIG_CHARGER_BQ24735=yCONFIG_CHARGER_BQ2515X=yCONFIG_CHARGER_BQ25890=yCONFIG_CHARGER_BQ25980=yCONFIG_CHARGER_BQ256XX=yCONFIG_CHARGER_RK817=yCONFIG_CHARGER_SMB347=yCONFIG_CHARGER_TPS65090=yCONFIG_CHARGER_TPS65217=yCONFIG_BATTERY_GAUGE_LTC2941=yCONFIG_BATTERY_GOLDFISH=yCONFIG_BATTERY_RT5033=yCONFIG_CHARGER_RT9455=yCONFIG_CHARGER_CROS_USBPD=yCONFIG_CHARGER_CROS_PCHG=yCONFIG_CHARGER_SC2731=yCONFIG_FUEL_GAUGE_SC27XX=yCONFIG_CHARGER_UCS1002=yCONFIG_CHARGER_BD99954=yCONFIG_CHARGER_WILCO=yCONFIG_RN5T618_POWER=yCONFIG_BATTERY_ACER_A500=yCONFIG_BATTERY_SURFACE=yCONFIG_CHARGER_SURFACE=yCONFIG_BATTERY_UG3105=yCONFIG_HWMON=yCONFIG_HWMON_VID=yCONFIG_HWMON_DEBUG_CHIP=y
#
# Native drivers
#CONFIG_SENSORS_AD7314=yCONFIG_SENSORS_AD7414=yCONFIG_SENSORS_AD7418=yCONFIG_SENSORS_ADM1025=yCONFIG_SENSORS_ADM1026=yCONFIG_SENSORS_ADM1029=yCONFIG_SENSORS_ADM1031=yCONFIG_SENSORS_ADM1177=yCONFIG_SENSORS_ADM9240=yCONFIG_SENSORS_ADT7X10=yCONFIG_SENSORS_ADT7310=yCONFIG_SENSORS_ADT7410=yCONFIG_SENSORS_ADT7411=yCONFIG_SENSORS_ADT7462=yCONFIG_SENSORS_ADT7470=yCONFIG_SENSORS_ADT7475=yCONFIG_SENSORS_AHT10=yCONFIG_SENSORS_AQUACOMPUTER_D5NEXT=yCONFIG_SENSORS_AS370=yCONFIG_SENSORS_ASC7621=yCONFIG_SENSORS_AXI_FAN_CONTROL=yCONFIG_SENSORS_ARM_SCMI=yCONFIG_SENSORS_ARM_SCPI=yCONFIG_SENSORS_ASB100=yCONFIG_SENSORS_ASPEED=yCONFIG_SENSORS_ATXP1=yCONFIG_SENSORS_BT1_PVT=yCONFIG_SENSORS_BT1_PVT_ALARMS=yCONFIG_SENSORS_CORSAIR_CPRO=yCONFIG_SENSORS_CORSAIR_PSU=yCONFIG_SENSORS_DRIVETEMP=yCONFIG_SENSORS_DS620=yCONFIG_SENSORS_DS1621=yCONFIG_SENSORS_DA9052_ADC=yCONFIG_SENSORS_DA9055=yCONFIG_SENSORS_I5K_AMB=yCONFIG_SENSORS_SPARX5=yCONFIG_SENSORS_F71805F=yCONFIG_SENSORS_F71882FG=yCONFIG_SENSORS_F75375S=yCONFIG_SENSORS_GSC=yCONFIG_SENSORS_MC13783_ADC=yCONFIG_SENSORS_FSCHMD=yCONFIG_SENSORS_FTSTEUTATES=yCONFIG_SENSORS_GL518SM=yCONFIG_SENSORS_GL520SM=yCONFIG_SENSORS_G760A=yCONFIG_SENSORS_G762=yCONFIG_SENSORS_GPIO_FAN=yCONFIG_SENSORS_HIH6130=yCONFIG_SENSORS_IBMAEM=yCONFIG_SENSORS_IBMPEX=yCONFIG_SENSORS_IIO_HWMON=yCONFIG_SENSORS_IT87=yCONFIG_SENSORS_JC42=yCONFIG_SENSORS_POWR1220=yCONFIG_SENSORS_LAN966X=yCONFIG_SENSORS_LINEAGE=yCONFIG_SENSORS_LOCHNAGAR=yCONFIG_SENSORS_LTC2945=yCONFIG_SENSORS_LTC2947=yCONFIG_SENSORS_LTC2947_I2C=yCONFIG_SENSORS_LTC2947_SPI=yCONFIG_SENSORS_LTC2990=yCONFIG_SENSORS_LTC2992=yCONFIG_SENSORS_LTC4151=yCONFIG_SENSORS_LTC4215=yCONFIG_SENSORS_LTC4222=yCONFIG_SENSORS_LTC4245=yCONFIG_SENSORS_LTC4260=yCONFIG_SENSORS_LTC4261=yCONFIG_SENSORS_MAX1111=yCONFIG_SENSORS_MAX127=yCONFIG_SENSORS_MAX16065=yCONFIG_SENSORS_MAX1619=yCONFIG_SENSORS_MAX1668=yCONFIG_SENSORS_MAX197=yCONFIG_SENSORS_MAX31722=yCONFIG_SENSORS_MAX31730=yCONFIG_SENSORS_MAX31760=yCONFIG_SENSORS_MAX6620=yCONFIG_SENSORS_MAX6621=yCONFIG_SENSORS_MAX6639=yCONFIG_SENSORS_MAX6650=yCONFIG_SENSORS_MAX6697=yCONFIG_SENSORS_MAX31790=yCONFIG_SENSORS_MCP3021=yCONFIG_SENSORS_MLXREG_FAN=yCONFIG_SENSORS_TC654=yCONFIG_SENSORS_TPS23861=yCONFIG_SENSORS_MENF21BMC_HWMON=yCONFIG_SENSORS_MR75203=yCONFIG_SENSORS_ADCXX=yCONFIG_SENSORS_LM63=yCONFIG_SENSORS_LM70=yCONFIG_SENSORS_LM73=yCONFIG_SENSORS_LM75=yCONFIG_SENSORS_LM77=yCONFIG_SENSORS_LM78=yCONFIG_SENSORS_LM80=yCONFIG_SENSORS_LM83=yCONFIG_SENSORS_LM85=yCONFIG_SENSORS_LM87=yCONFIG_SENSORS_LM90=yCONFIG_SENSORS_LM92=yCONFIG_SENSORS_LM93=yCONFIG_SENSORS_LM95234=yCONFIG_SENSORS_LM95241=yCONFIG_SENSORS_LM95245=yCONFIG_SENSORS_PC87360=yCONFIG_SENSORS_PC87427=yCONFIG_SENSORS_NTC_THERMISTOR=yCONFIG_SENSORS_NCT6683=yCONFIG_SENSORS_NCT6775_CORE=yCONFIG_SENSORS_NCT6775=yCONFIG_SENSORS_NCT6775_I2C=yCONFIG_SENSORS_NCT7802=yCONFIG_SENSORS_NCT7904=yCONFIG_SENSORS_NPCM7XX=yCONFIG_SENSORS_NSA320=yCONFIG_SENSORS_NZXT_KRAKEN2=yCONFIG_SENSORS_NZXT_SMART2=yCONFIG_SENSORS_OCC_P8_I2C=yCONFIG_SENSORS_OCC_P9_SBE=yCONFIG_SENSORS_OCC=yCONFIG_SENSORS_PCF8591=yCONFIG_SENSORS_PECI_CPUTEMP=yCONFIG_SENSORS_PECI_DIMMTEMP=yCONFIG_SENSORS_PECI=yCONFIG_PMBUS=yCONFIG_SENSORS_PMBUS=yCONFIG_SENSORS_ADM1266=yCONFIG_SENSORS_ADM1275=yCONFIG_SENSORS_BEL_PFE=yCONFIG_SENSORS_BPA_RS600=yCONFIG_SENSORS_DELTA_AHE50DC_FAN=yCONFIG_SENSORS_FSP_3Y=yCONFIG_SENSORS_IBM_CFFPS=yCONFIG_SENSORS_DPS920AB=yCONFIG_SENSORS_INSPUR_IPSPS=yCONFIG_SENSORS_IR35221=yCONFIG_SENSORS_IR36021=yCONFIG_SENSORS_IR38064=yCONFIG_SENSORS_IR38064_REGULATOR=yCONFIG_SENSORS_IRPS5401=yCONFIG_SENSORS_ISL68137=yCONFIG_SENSORS_LM25066=yCONFIG_SENSORS_LM25066_REGULATOR=yCONFIG_SENSORS_LT7182S=yCONFIG_SENSORS_LTC2978=yCONFIG_SENSORS_LTC2978_REGULATOR=yCONFIG_SENSORS_LTC3815=yCONFIG_SENSORS_MAX15301=yCONFIG_SENSORS_MAX16064=yCONFIG_SENSORS_MAX16601=yCONFIG_SENSORS_MAX20730=yCONFIG_SENSORS_MAX20751=yCONFIG_SENSORS_MAX31785=yCONFIG_SENSORS_MAX34440=yCONFIG_SENSORS_MAX8688=yCONFIG_SENSORS_MP2888=yCONFIG_SENSORS_MP2975=yCONFIG_SENSORS_MP5023=yCONFIG_SENSORS_PIM4328=yCONFIG_SENSORS_PLI1209BC=yCONFIG_SENSORS_PLI1209BC_REGULATOR=yCONFIG_SENSORS_PM6764TR=yCONFIG_SENSORS_PXE1610=yCONFIG_SENSORS_Q54SJ108A2=yCONFIG_SENSORS_STPDDC60=yCONFIG_SENSORS_TPS40422=yCONFIG_SENSORS_TPS53679=yCONFIG_SENSORS_TPS546D24=yCONFIG_SENSORS_UCD9000=yCONFIG_SENSORS_UCD9200=yCONFIG_SENSORS_XDPE152=yCONFIG_SENSORS_XDPE122=yCONFIG_SENSORS_XDPE122_REGULATOR=yCONFIG_SENSORS_ZL6100=yCONFIG_SENSORS_PWM_FAN=yCONFIG_SENSORS_RASPBERRYPI_HWMON=yCONFIG_SENSORS_SL28CPLD=yCONFIG_SENSORS_SBTSI=yCONFIG_SENSORS_SBRMI=yCONFIG_SENSORS_SHT15=yCONFIG_SENSORS_SHT21=y
CONFIG_SENSORS_SHT3x=y
CONFIG_SENSORS_SHT4x=yCONFIG_SENSORS_SHTC1=yCONFIG_SENSORS_SIS5595=yCONFIG_SENSORS_SY7636A=yCONFIG_SENSORS_DME1737=yCONFIG_SENSORS_EMC1403=yCONFIG_SENSORS_EMC2103=yCONFIG_SENSORS_EMC2305=yCONFIG_SENSORS_EMC6W201=yCONFIG_SENSORS_SMSC47M1=yCONFIG_SENSORS_SMSC47M192=yCONFIG_SENSORS_SMSC47B397=yCONFIG_SENSORS_SCH56XX_COMMON=yCONFIG_SENSORS_SCH5627=yCONFIG_SENSORS_SCH5636=yCONFIG_SENSORS_STTS751=yCONFIG_SENSORS_SMM665=yCONFIG_SENSORS_ADC128D818=yCONFIG_SENSORS_ADS7828=yCONFIG_SENSORS_ADS7871=yCONFIG_SENSORS_AMC6821=yCONFIG_SENSORS_INA209=yCONFIG_SENSORS_INA2XX=yCONFIG_SENSORS_INA238=yCONFIG_SENSORS_INA3221=yCONFIG_SENSORS_TC74=yCONFIG_SENSORS_THMC50=yCONFIG_SENSORS_TMP102=yCONFIG_SENSORS_TMP103=yCONFIG_SENSORS_TMP108=yCONFIG_SENSORS_TMP401=yCONFIG_SENSORS_TMP421=yCONFIG_SENSORS_TMP464=yCONFIG_SENSORS_TMP513=yCONFIG_SENSORS_VIA686A=yCONFIG_SENSORS_VT1211=yCONFIG_SENSORS_VT8231=yCONFIG_SENSORS_W83773G=yCONFIG_SENSORS_W83781D=yCONFIG_SENSORS_W83791D=yCONFIG_SENSORS_W83792D=yCONFIG_SENSORS_W83793=yCONFIG_SENSORS_W83795=yCONFIG_SENSORS_W83795_FANCTRL=yCONFIG_SENSORS_W83L785TS=yCONFIG_SENSORS_W83L786NG=yCONFIG_SENSORS_W83627HF=yCONFIG_SENSORS_W83627EHF=yCONFIG_SENSORS_WM831X=yCONFIG_SENSORS_WM8350=yCONFIG_SENSORS_XGENE=yCONFIG_SENSORS_INTEL_M10_BMC_HWMON=y
#
# ACPI drivers
#CONFIG_SENSORS_ACPI_POWER=yCONFIG_THERMAL=yCONFIG_THERMAL_NETLINK=y CONFIG_THERMAL_STATISTICS=y CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=yCONFIG_THERMAL_OF=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=y CONFIG_CPU_THERMAL=yCONFIG_CPU_FREQ_THERMAL=y CONFIG_DEVFREQ_THERMAL=y CONFIG_THERMAL_EMULATION=y CONFIG_THERMAL_MMIO=yCONFIG_HISI_THERMAL=yCONFIG_IMX_THERMAL=yCONFIG_IMX_SC_THERMAL=y CONFIG_IMX8MM_THERMAL=yCONFIG_K3_THERMAL=yCONFIG_MAX77620_THERMAL=y CONFIG_QORIQ_THERMAL=yCONFIG_SPEAR_THERMAL=yCONFIG_SUN8I_THERMAL=y CONFIG_ROCKCHIP_THERMAL=y CONFIG_RCAR_THERMAL=y CONFIG_RCAR_GEN3_THERMAL=y CONFIG_RZG2L_THERMAL=y CONFIG_KIRKWOOD_THERMAL=y CONFIG_DOVE_THERMAL=yCONFIG_ARMADA_THERMAL=y CONFIG_DA9062_THERMAL=yCONFIG_MTK_THERMAL=y
#
# Intel thermal drivers
#
#
# ACPI INT340X thermal drivers
#
# end of ACPI INT340X thermal drivers
CONFIG_INTEL_MENLOW=y
# end of Intel thermal drivers
#
# Broadcom thermal drivers
#CONFIG_BCM2711_THERMAL=yCONFIG_BCM2835_THERMAL=yCONFIG_BRCMSTB_THERMAL=yCONFIG_BCM_NS_THERMAL=yCONFIG_BCM_SR_THERMAL=y
# end of Broadcom thermal drivers
#
# Texas Instruments thermal drivers
#CONFIG_TI_SOC_THERMAL=yCONFIG_TI_THERMAL=yCONFIG_OMAP3_THERMAL=yCONFIG_OMAP4_THERMAL=yCONFIG_OMAP5_THERMAL=yCONFIG_DRA752_THERMAL=y
# end of Texas Instruments thermal drivers
#
# Samsung thermal drivers
#CONFIG_EXYNOS_THERMAL=y
# end of Samsung thermal drivers
#
# NVIDIA Tegra thermal drivers
#CONFIG_TEGRA_SOCTHERM=yCONFIG_TEGRA_BPMP_THERMAL=yCONFIG_TEGRA30_TSENSOR=y
# end of NVIDIA Tegra thermal drivers
CONFIG_GENERIC_ADC_THERMAL=y
#
# Qualcomm thermal drivers
#CONFIG_QCOM_TSENS=yCONFIG_QCOM_SPMI_ADC_TM5=yCONFIG_QCOM_SPMI_TEMP_ALARM=y
# end of Qualcomm thermal drivers
CONFIG_UNIPHIER_THERMAL=yCONFIG_SPRD_THERMAL=yCONFIG_KHADAS_MCU_FAN_THERMAL=yCONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=yCONFIG_WATCHDOG_NOWAYOUT=yCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0CONFIG_WATCHDOG_SYSFS=yCONFIG_WATCHDOG_HRTIMER_PRETIMEOUT=y
#
# Watchdog Pretimeout Governors
#CONFIG_WATCHDOG_PRETIMEOUT_GOV=y CONFIG_WATCHDOG_PRETIMEOUT_GOV_SEL=m CONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP=y CONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC=y
# CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP is not set CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC=y
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=yCONFIG_SOFT_WATCHDOG_PRETIMEOUT=yCONFIG_BD957XMUF_WATCHDOG=yCONFIG_DA9052_WATCHDOG=yCONFIG_DA9055_WATCHDOG=yCONFIG_DA9063_WATCHDOG=yCONFIG_DA9062_WATCHDOG=yCONFIG_GPIO_WATCHDOG=yCONFIG_GPIO_WATCHDOG_ARCH_INITCALL=yCONFIG_MENF21BMC_WATCHDOG=yCONFIG_MENZ069_WATCHDOG=yCONFIG_WDAT_WDT=yCONFIG_WM831X_WATCHDOG=yCONFIG_WM8350_WATCHDOG=yCONFIG_XILINX_WATCHDOG=yCONFIG_ZIIRAVE_WATCHDOG=yCONFIG_RAVE_SP_WATCHDOG=yCONFIG_MLX_WDT=yCONFIG_SL28CPLD_WATCHDOG=yCONFIG_ARMADA_37XX_WATCHDOG=yCONFIG_ASM9260_WATCHDOG=yCONFIG_AT91RM9200_WATCHDOG=yCONFIG_AT91SAM9X_WATCHDOG=yCONFIG_SAMA5D4_WATCHDOG=yCONFIG_CADENCE_WATCHDOG=yCONFIG_FTWDT010_WATCHDOG=yCONFIG_S3C2410_WATCHDOG=yCONFIG_DW_WATCHDOG=yCONFIG_EP93XX_WATCHDOG=yCONFIG_OMAP_WATCHDOG=yCONFIG_PNX4008_WATCHDOG=yCONFIG_DAVINCI_WATCHDOG=yCONFIG_K3_RTI_WATCHDOG=yCONFIG_RN5T618_WATCHDOG=yCONFIG_SUNXI_WATCHDOG=yCONFIG_NPCM7XX_WATCHDOG=yCONFIG_TWL4030_WATCHDOG=yCONFIG_STMP3XXX_RTC_WATCHDOG=yCONFIG_TS4800_WATCHDOG=yCONFIG_TS72XX_WATCHDOG=yCONFIG_MAX63XX_WATCHDOG=yCONFIG_MAX77620_WATCHDOG=yCONFIG_IMX2_WDT=yCONFIG_IMX7ULP_WDT=yCONFIG_RETU_WATCHDOG=yCONFIG_MOXART_WDT=yCONFIG_ST_LPC_WATCHDOG=yCONFIG_TEGRA_WATCHDOG=yCONFIG_QCOM_WDT=yCONFIG_MESON_GXBB_WATCHDOG=yCONFIG_MESON_WATCHDOG=yCONFIG_MEDIATEK_WATCHDOG=yCONFIG_DIGICOLOR_WATCHDOG=yCONFIG_LPC18XX_WATCHDOG=yCONFIG_RENESAS_WDT=yCONFIG_RENESAS_RZAWDT=yCONFIG_RENESAS_RZN1WDT=yCONFIG_RENESAS_RZG2LWDT=yCONFIG_ASPEED_WATCHDOG=yCONFIG_STPMIC1_WATCHDOG=yCONFIG_UNIPHIER_WATCHDOG=yCONFIG_RTD119X_WATCHDOG=yCONFIG_REALTEK_OTTO_WDT=yCONFIG_SPRD_WATCHDOG=yCONFIG_PM8916_WATCHDOG=yCONFIG_VISCONTI_WATCHDOG=yCONFIG_MSC313E_WATCHDOG=yCONFIG_APPLE_WATCHDOG=yCONFIG_SUNPLUS_WATCHDOG=yCONFIG_ALIM7101_WDT=yCONFIG_SC520_WDT=yCONFIG_I6300ESB_WDT=yCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=yCONFIG_KEMPLD_WDT=yCONFIG_RDC321X_WDT=yCONFIG_BCM47XX_WDT=yCONFIG_BCM2835_WDT=yCONFIG_BCM_KONA_WDT=yCONFIG_BCM_KONA_WDT_DEBUG=yCONFIG_BCM7038_WDT=yCONFIG_IMGPDC_WDT=yCONFIG_MPC5200_WDT=yCONFIG_MEN_A21_WDT=yCONFIG_UML_WATCHDOG=y
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=yCONFIG_WDTPCI=y
#
# USB-based Watchdog Cards
#CONFIG_USBPCWATCHDOG=yCONFIG_SSB_POSSIBLE=yCONFIG_SSB=yCONFIG_SSB_SPROM=yCONFIG_SSB_BLOCKIO=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=yCONFIG_SSB_B43_PCI_BRIDGE=yCONFIG_SSB_PCMCIAHOST_POSSIBLE=yCONFIG_SSB_PCMCIAHOST=yCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=yCONFIG_SSB_HOST_SOC=yCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=yCONFIG_SSB_DRIVER_GPIO=yCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=yCONFIG_BCMA_BLOCKIO=yCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=yCONFIG_BCMA_HOST_SOC=yCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_MIPS=yCONFIG_BCMA_PFLASH=yCONFIG_BCMA_SFLASH=yCONFIG_BCMA_NFLASH=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=yCONFIG_BCMA_DEBUG=y
7,674 lines not shown · raw message
Part of this message is not shown here. View the raw message.
kernel test robot
build botRe: [RFC bpf-next v2 12/14] mxl4: Support rx timestamp metadata for xdp
In reply to Stanislav Fomichevreproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross #…
Hi Stanislav,
[FYI, it's a private test report for your RFC patch.] [auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Stanislav-Fomichev/xdp-hints-via-kfuncs/20221104-113042 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master patch link: https://lore.kernel.org/r/20221104032532.1615099-13-sdf%40google.com patch subject: [RFC bpf-next v2 12/14] mxl4: Support rx timestamp metadata for xdp config: i386-randconfig-a013 compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/bb15bd4e2e87117f30c60bbbad15805164454808
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Stanislav-Fomichev/xdp-hints-via-kfuncs/20221104-113042
git checkout bb15bd4e2e87117f30c60bbbad15805164454808
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/net/ethernet/broadcom/bnxt/ drivers/net/ethernet/mellanox/mlx4/
If you fix the issue, kindly add following tag where applicable | Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/mellanox/mlx4/en_rx.c:672:23: warning: no previous prototype for function 'mxl4_xdp_rx_timestamp' [-Wmissing-prototypes]
struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp(struct mlx4_xdp_buff *ctx)
^ drivers/net/ethernet/mellanox/mlx4/en_rx.c:672:1: note: declare 'static' if the function is not intended to be used outside of this translation unit struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp(struct mlx4_xdp_buff *ctx)
^
static
1 warning generated.
vim +/mxl4_xdp_rx_timestamp +672 drivers/net/ethernet/mellanox/mlx4/en_rx.c
671
> 672 struct mlx4_xdp_buff *mxl4_xdp_rx_timestamp(struct mlx4_xdp_buff *ctx)
673 {
674 unsigned int seq;
675 u64 timestamp;
676 u64 nsec;
677
678 timestamp = mlx4_en_get_cqe_ts(ctx->cqe);
679
680 do {
681 seq = read_seqbegin(&ctx->mdev->clock_lock);
682 nsec = timecounter_cyc2time(&ctx->mdev->clock, timestamp);
683 } while (read_seqretry(&ctx->mdev->clock_lock, seq));
684
685 ctx->r0 = (u64)ns_to_ktime(nsec);
686 return ctx;
687 }
688
Signature · 2 lines
0-DAY CI Kernel Test Service https://01.org/lkp
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 6.1.0-rc3 Kernel Configuration
#CONFIG_CC_VERSION_TEXT="clang version 14.0.6 (git://gitmirror/llvm_project f28c006a5895fc0e329fe15fead81e37457cb1d1)" CONFIG_GCC_VERSION=0CONFIG_CC_IS_CLANG=yCONFIG_CLANG_VERSION=140006CONFIG_AS_IS_LLVM=yCONFIG_AS_VERSION=140006CONFIG_LD_VERSION=0CONFIG_LD_IS_LLD=yCONFIG_LLD_VERSION=140006CONFIG_RUST_IS_AVAILABLE=yCONFIG_CC_CAN_LINK=yCONFIG_CC_CAN_LINK_STATIC=yCONFIG_CC_HAS_ASM_GOTO_OUTPUT=yCONFIG_TOOLS_SUPPORT_RELR=yCONFIG_CC_HAS_ASM_INLINE=yCONFIG_CC_HAS_NO_PROFILE_FN_ATTR=yCONFIG_PAHOLE_VERSION=123CONFIG_IRQ_WORK=yCONFIG_BUILDTIME_TABLE_SORT=yCONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_WERROR is not setCONFIG_UAPI_HEADER_TEST=yCONFIG_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_HAVE_KERNEL_ZSTD=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not setCONFIG_KERNEL_LZ4=y
# CONFIG_KERNEL_ZSTD is not setCONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_WATCH_QUEUE is not set
# CONFIG_CROSS_MEMORY_ATTACH is not set
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not setCONFIG_HAVE_ARCH_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_GENERIC_IRQ_INJECTION=yCONFIG_HARDIRQS_SW_RESEND=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_IRQ_MSI_IOMMU=yCONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=yCONFIG_GENERIC_IRQ_RESERVATION_MODE=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=yCONFIG_GENERIC_IRQ_DEBUGFS=y
# end of IRQ subsystem
CONFIG_CLOCKSOURCE_WATCHDOG=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=yCONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=yCONFIG_POSIX_CPU_TIMERS_TASK_WORK=yCONFIG_CONTEXT_TRACKING=yCONFIG_CONTEXT_TRACKING_IDLE=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ is not setCONFIG_HIGH_RES_TIMERS=yCONFIG_CLOCKSOURCE_WATCHDOG_MAX_SKEW_US=100
# end of Timers subsystem
CONFIG_BPF=yCONFIG_HAVE_EBPF_JIT=y
#
# BPF subsystem
#CONFIG_BPF_SYSCALL=y
# CONFIG_BPF_JIT is not setCONFIG_BPF_UNPRIV_DEFAULT_OFF=yCONFIG_USERMODE_DRIVER=y
# CONFIG_BPF_PRELOAD is not set
# end of BPF subsystem
CONFIG_PREEMPT_VOLUNTARY_BUILD=y
# CONFIG_PREEMPT_NONE is not setCONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not setCONFIG_PREEMPT_COUNT=y
# CONFIG_PREEMPT_DYNAMIC is not set
# CONFIG_SCHED_CORE is not set
#
# CPU/Task time and stats accounting
#CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
# CONFIG_CPU_ISOLATION is not set
#
# RCU Subsystem
#CONFIG_TREE_RCU=yCONFIG_RCU_EXPERT=yCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_FORCE_TASKS_RCU=yCONFIG_TASKS_RCU=yCONFIG_FORCE_TASKS_RUDE_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_FORCE_TASKS_TRACE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_FANOUT=32CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_NOCB_CPU is not set
# CONFIG_TASKS_TRACE_RCU_READ_MB is not set
# end of RCU Subsystem
CONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_IKHEADERS=mCONFIG_LOG_BUF_SHIFT=20CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
# CONFIG_PRINTK_INDEX is not setCONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough" CONFIG_GCC12_NO_ARRAY_BOUNDS=y CONFIG_CGROUPS=y
# CONFIG_CGROUP_FAVOR_DYNMODS is not set
# CONFIG_MEMCG is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_RDMA is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CGROUP_HUGETLB is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_BPF is not set
# CONFIG_CGROUP_MISC is not set
# CONFIG_CGROUP_DEBUG is not set CONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_TIME_NS=y
# CONFIG_USER_NS is not setCONFIG_PID_NS=y
# CONFIG_NET_NS is not set
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=y
# CONFIG_RD_LZMA is not set
# CONFIG_RD_XZ is not set
# CONFIG_RD_LZO is not set
# CONFIG_RD_LZ4 is not setCONFIG_RD_ZSTD=yCONFIG_BOOT_CONFIG=y
# CONFIG_BOOT_CONFIG_EMBED is not set CONFIG_INITRAMFS_PRESERVE_MTIME=y CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_LD_ORPHAN_WARN=yCONFIG_SYSCTL=yCONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=y
# CONFIG_SYSFS_SYSCALL is not set CONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_BUG=y
# CONFIG_ELF_CORE is not set
# CONFIG_PCSPKR_PLATFORM is not set
# CONFIG_BASE_FULL is not setCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=y
# CONFIG_EVENTFD is not setCONFIG_SHMEM=yCONFIG_AIO=y
# CONFIG_IO_URING is not set CONFIG_ADVISE_SYSCALLS=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_KCMP=yCONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not set
# CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=yCONFIG_PC104=y
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=yCONFIG_DEBUG_PERF_USE_VMALLOC=y
# end of Kernel Performance Events And Counters
# CONFIG_PROFILING is not setCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_X86_32=yCONFIG_FORCE_DYNAMIC_FTRACE=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=yCONFIG_OUTPUT_FORMAT="elf32-i386"CONFIG_LOCKDEP_SUPPORT=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=8CONFIG_ARCH_MMAP_RND_BITS_MAX=16CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=yCONFIG_ARCH_MAY_HAVE_PC_FDC=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_ARCH_HAS_CPU_RELAX=yCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_NR_GPIO=512CONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_X86_32_SMP=yCONFIG_ARCH_SUPPORTS_UPROBES=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_PGTABLE_LEVELS=2
#
# Processor type and features
#CONFIG_SMP=yCONFIG_X86_FEATURE_NAMES=yCONFIG_X86_MPPARSE=yCONFIG_GOLDFISH=y
# CONFIG_X86_CPU_RESCTRL is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_EXTENDED_PLATFORM is not set
# CONFIG_X86_INTEL_LPSS is not set
# CONFIG_X86_AMD_PLATFORM_DEVICE is not setCONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not setCONFIG_X86_32_IRIS=m
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_DEBUG is not set
# CONFIG_PARAVIRT_SPINLOCKS is not setCONFIG_X86_HV_CALLBACK_VECTOR=yCONFIG_KVM_GUEST=yCONFIG_ARCH_CPUIDLE_HALTPOLL=y
# CONFIG_PVH is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not setCONFIG_PARAVIRT_CLOCK=y
# CONFIG_M486SX is not set
# CONFIG_M486 is not setCONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MELAN is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not setCONFIG_X86_GENERIC=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_F00F_BUG=yCONFIG_X86_ALIGNMENT_16=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_MINIMUM_CPU_FAMILY=4CONFIG_IA32_FEAT_CTL=yCONFIG_X86_VMX_FEATURE_NAMES=yCONFIG_PROCESSOR_SELECT=yCONFIG_CPU_SUP_INTEL=y
# CONFIG_CPU_SUP_CYRIX_32 is not set
# CONFIG_CPU_SUP_AMD is not set
# CONFIG_CPU_SUP_HYGON is not set
# CONFIG_CPU_SUP_CENTAUR is not setCONFIG_CPU_SUP_TRANSMETA_32=yCONFIG_CPU_SUP_UMC_32=y
# CONFIG_CPU_SUP_ZHAOXIN is not setCONFIG_CPU_SUP_VORTEX_32=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_BOOT_VESA_SUPPORT=yCONFIG_NR_CPUS_RANGE_BEGIN=2CONFIG_NR_CPUS_RANGE_END=8CONFIG_NR_CPUS_DEFAULT=8CONFIG_NR_CPUS=8CONFIG_SCHED_CLUSTER=yCONFIG_SCHED_SMT=yCONFIG_SCHED_MC=y
# CONFIG_SCHED_MC_PRIO is not setCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
# CONFIG_X86_MCE is not set
#
# Performance monitoring
#CONFIG_PERF_EVENTS_INTEL_UNCORE=y
# CONFIG_PERF_EVENTS_INTEL_RAPL is not set
# CONFIG_PERF_EVENTS_INTEL_CSTATE is not set
# end of Performance monitoring
# CONFIG_X86_LEGACY_VM86 is not set
# CONFIG_X86_16BIT is not setCONFIG_X86_IOPL_IOPERM=y
# CONFIG_TOSHIBA is not setCONFIG_X86_REBOOTFIXUPS=yCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_LATE_LOADING is not setCONFIG_X86_MSR=mCONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not setCONFIG_HIGHMEM4G=y
# CONFIG_VMSPLIT_3G is not set
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not setCONFIG_VMSPLIT_1G=yCONFIG_PAGE_OFFSET=0x40000000CONFIG_HIGHMEM=yCONFIG_X86_CPA_STATISTICS=yCONFIG_ARCH_FLATMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_ILLEGAL_POINTER_VALUE=0
# CONFIG_HIGHPTE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
# CONFIG_MTRR is not setCONFIG_X86_UMIP=yCONFIG_CC_HAS_IBT=y
# CONFIG_X86_INTEL_TSX_MODE_OFF is not set
# CONFIG_X86_INTEL_TSX_MODE_ON is not setCONFIG_X86_INTEL_TSX_MODE_AUTO=y
# CONFIG_EFI is not set
# 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=y
# CONFIG_CRASH_DUMP is not setCONFIG_PHYSICAL_START=0x1000000CONFIG_RELOCATABLE=y
# CONFIG_RANDOMIZE_BASE is not setCONFIG_X86_NEED_RELOCS=yCONFIG_PHYSICAL_ALIGN=0x200000CONFIG_HOTPLUG_CPU=yCONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not setCONFIG_MODIFY_LDT_SYSCALL=yCONFIG_STRICT_SIGALTSTACK_SIZE=y
# end of Processor type and features
CONFIG_SPECULATION_MITIGATIONS=yCONFIG_RETPOLINE=yCONFIG_ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE=y
#
# Power management and ACPI options
#CONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not set
# CONFIG_HIBERNATION is not setCONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_USERSPACE_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=y
# CONFIG_PM_DEBUG is not setCONFIG_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=yCONFIG_ACPI_TABLE_LIB=y
# CONFIG_ACPI_DEBUGGER is not setCONFIG_ACPI_SPCR_TABLE=yCONFIG_ACPI_SLEEP=yCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y
# CONFIG_ACPI_EC_DEBUGFS is not setCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=y
# CONFIG_ACPI_TAD is not set
# CONFIG_ACPI_DOCK is not setCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_PROCESSOR=y
# CONFIG_ACPI_IPMI is not setCONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not setCONFIG_ACPI_THERMAL=yCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not setCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_IOAPIC=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_CUSTOM_METHOD is not set
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not setCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=y
# CONFIG_ACPI_APEI is not set
# CONFIG_ACPI_DPTF is not set
# CONFIG_ACPI_CONFIGFS is not set
# CONFIG_PMIC_OPREGION is not setCONFIG_ACPI_VIOT=yCONFIG_X86_PM_TIMER=y
# CONFIG_APM is not set
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=m CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#CONFIG_CPUFREQ_DT=yCONFIG_CPUFREQ_DT_PLATDEV=y
# CONFIG_X86_INTEL_PSTATE is not set
# CONFIG_X86_PCC_CPUFREQ is not set
# CONFIG_X86_AMD_PSTATE is not set
# CONFIG_X86_AMD_PSTATE_UT is not set
# CONFIG_X86_ACPI_CPUFREQ is not setCONFIG_X86_POWERNOW_K6=mCONFIG_X86_POWERNOW_K7=mCONFIG_X86_POWERNOW_K7_ACPI=yCONFIG_X86_GX_SUSPMOD=yCONFIG_X86_SPEEDSTEP_CENTRINO=mCONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=yCONFIG_X86_SPEEDSTEP_ICH=m
# CONFIG_X86_SPEEDSTEP_SMI is not setCONFIG_X86_P4_CLOCKMOD=yCONFIG_X86_CPUFREQ_NFORCE2=mCONFIG_X86_LONGRUN=y
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=y # CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set # end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_GOV_LADDER=y
# CONFIG_CPU_IDLE_GOV_MENU is not set
# CONFIG_CPU_IDLE_GOV_TEO is not set
# CONFIG_CPU_IDLE_GOV_HALTPOLL is not setCONFIG_HALTPOLL_CPUIDLE=y
# end of CPU Idle
# CONFIG_INTEL_IDLE is not set
# end of Power management and ACPI options
#
# Bus options (PCI etc.)
#
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not setCONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not setCONFIG_PCI_DIRECT=yCONFIG_PCI_CNB20LE_QUIRK=yCONFIG_ISA_BUS=yCONFIG_ISA_DMA_API=yCONFIG_ISA=y
CONFIG_SCx200=y
CONFIG_SCx200HR_TIMER=m
# CONFIG_OLPC is not set
# CONFIG_ALIX is not set
# CONFIG_NET5501 is not set
# CONFIG_GEOS is not set
# end of Bus options (PCI etc.)
#
# Binary Emulations
#CONFIG_COMPAT_32=y
# end of Binary Emulations
CONFIG_HAVE_ATOMIC_IOMAP=yCONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not setCONFIG_AS_AVX512=yCONFIG_AS_SHA1_NI=yCONFIG_AS_SHA256_NI=yCONFIG_AS_TPAUSE=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_HOTPLUG_SMT=yCONFIG_GENERIC_ENTRY=yCONFIG_KPROBES=y
# CONFIG_JUMP_LABEL is not set
# CONFIG_STATIC_CALL_SELFTEST is not setCONFIG_OPTPROBES=yCONFIG_KPROBES_ON_FTRACE=yCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_KRETPROBES=yCONFIG_KRETPROBE_ON_RETHOOK=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_ARCH_CORRECT_STACKTRACE_ON_KRETPROBE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_TRACE_IRQFLAGS_NMI_SUPPORT=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_ARCH_WANTS_NO_INSTR=yCONFIG_ARCH_32BIT_OFF_T=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_FUNCTION_ARG_ACCESS_API=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_MMU_GATHER_TABLE_FREE=yCONFIG_MMU_GATHER_RCU_TABLE_FREE=yCONFIG_MMU_GATHER_MERGE_VMAS=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_IPC_PARSE_VERSION=yCONFIG_HAVE_ARCH_SECCOMP=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=y
# CONFIG_SECCOMP is not setCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_ARCH_SUPPORTS_LTO_CLANG=yCONFIG_ARCH_SUPPORTS_LTO_CLANG_THIN=yCONFIG_LTO_NONE=yCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOVE_PUD=yCONFIG_HAVE_MOVE_PMD=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_ARCH_WANT_HUGE_PMD_SHARE=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_REL=yCONFIG_HAVE_SOFTIRQ_ON_OWN_STACK=yCONFIG_SOFTIRQ_ON_OWN_STACK=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=8CONFIG_PAGE_SIZE_LESS_THAN_64KB=yCONFIG_PAGE_SIZE_LESS_THAN_256KB=yCONFIG_ISA_BUS_API=yCONFIG_CLONE_BACKWARDS=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_OLD_SIGACTION=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=yCONFIG_RANDOMIZE_KSTACK_OFFSET=yCONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=y
# CONFIG_LOCK_EVENT_COUNTS is not setCONFIG_ARCH_HAS_MEM_ENCRYPT=yCONFIG_HAVE_STATIC_CALL=yCONFIG_HAVE_PREEMPT_DYNAMIC=yCONFIG_HAVE_PREEMPT_DYNAMIC_CALL=yCONFIG_ARCH_WANT_LD_ORPHAN_WARN=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_ARCH_SPLIT_ARG64=yCONFIG_ARCH_HAS_PARANOID_L1D_FLUSH=yCONFIG_DYNAMIC_SIGFRAME=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=1CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODULE_UNLOAD_TAINT_TRACKING is not set # CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set CONFIG_MODPROBE_PATH="/sbin/modprobe"
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLOCK_LEGACY_AUTOLOAD=y CONFIG_BLK_DEV_BSG_COMMON=y CONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_INTEGRITY_T10=y
# CONFIG_BLK_DEV_ZONED is not set
# CONFIG_BLK_WBT is not setCONFIG_BLK_DEBUG_FS=yCONFIG_BLK_SED_OPAL=y CONFIG_BLK_INLINE_ENCRYPTION=y CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK=y
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=yCONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
# CONFIG_ACORN_PARTITION_ICS is not set
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
# CONFIG_ACORN_PARTITION_RISCIX is not setCONFIG_AIX_PARTITION=yCONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not setCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=y
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=yCONFIG_ULTRIX_PARTITION=y
# CONFIG_SUN_PARTITION is not setCONFIG_KARMA_PARTITION=y
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_MQ_RDMA=yCONFIG_BLK_PM=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=mCONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_PADATA=yCONFIG_ASN1=yCONFIG_UNINLINE_SPIN_UNLOCK=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_NON_OVERLAPPING_ADDRESS_SPACE=yCONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=yCONFIG_ARCH_HAS_SYSCALL_WRAPPER=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=mCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SWAP=y
# CONFIG_ZSWAP is not set
#
# SLAB allocator options
#
# CONFIG_SLAB is not set
# CONFIG_SLUB is not setCONFIG_SLOB=y
# end of SLAB allocator options
CONFIG_SHUFFLE_PAGE_ALLOCATOR=y
# CONFIG_COMPAT_BRK is not setCONFIG_SELECT_MEMORY_MODEL=yCONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not setCONFIG_FLATMEM=yCONFIG_SPARSEMEM_STATIC=yCONFIG_HAVE_FAST_GUP=yCONFIG_MEMORY_ISOLATION=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_COMPACTION=yCONFIG_COMPACT_UNEVICTABLE_DEFAULT=1
# CONFIG_PAGE_REPORTING is not setCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_BOUNCE=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_ARCH_WANT_GENERAL_HUGETLB=yCONFIG_TRANSPARENT_HUGEPAGE=yCONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not setCONFIG_READ_ONLY_THP_FOR_FS=yCONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=yCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_CMA=yCONFIG_CMA_DEBUG=y
# CONFIG_CMA_DEBUGFS is not setCONFIG_CMA_SYSFS=yCONFIG_CMA_AREAS=7CONFIG_GENERIC_EARLY_IOREMAP=yCONFIG_PAGE_IDLE_FLAG=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ARCH_HAS_CACHE_LINE_SIZE=yCONFIG_ARCH_HAS_CURRENT_STACK_POINTER=yCONFIG_ARCH_HAS_ZONE_DMA_SET=y
# CONFIG_ZONE_DMA is not setCONFIG_VMAP_PFN=y
# CONFIG_VM_EVENT_COUNTERS is not set
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_TEST is not setCONFIG_ARCH_HAS_PTE_SPECIAL=yCONFIG_MAPPING_DIRTY_HELPERS=yCONFIG_KMAP_LOCAL=yCONFIG_SECRETMEM=y
# CONFIG_ANON_VMA_NAME is not set
# CONFIG_USERFAULTFD is not set
# CONFIG_LRU_GEN is not set
#
# Data Access Monitoring
#CONFIG_DAMON=y
# CONFIG_DAMON_VADDR is not set
# CONFIG_DAMON_PADDR is not set
# CONFIG_DAMON_SYSFS is not set
# end of Data Access Monitoring # end of Memory Management options
CONFIG_NET=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=mCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_AF_UNIX_OOB=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not setCONFIG_XFRM=yCONFIG_XFRM_OFFLOAD=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=yCONFIG_XFRM_INTERFACE=m
# CONFIG_XFRM_SUB_POLICY is not setCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_AH=mCONFIG_XFRM_ESP=mCONFIG_XFRM_IPCOMP=mCONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not setCONFIG_XFRM_ESPINTCP=yCONFIG_SMC=mCONFIG_SMC_DIAG=mCONFIG_XDP_SOCKETS=yCONFIG_XDP_SOCKETS_DIAG=mCONFIG_INET=yCONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not setCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not setCONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not setCONFIG_NET_IPGRE_DEMUX=mCONFIG_NET_IP_TUNNEL=mCONFIG_NET_IPGRE=mCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=y
# CONFIG_IP_MROUTE is not setCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=mCONFIG_NET_UDP_TUNNEL=mCONFIG_NET_FOU=m
# CONFIG_NET_FOU_IP_TUNNELS is not set
# CONFIG_INET_AH is not setCONFIG_INET_ESP=mCONFIG_INET_ESP_OFFLOAD=mCONFIG_INET_ESPINTCP=yCONFIG_INET_IPCOMP=mCONFIG_INET_XFRM_TUNNEL=mCONFIG_INET_TUNNEL=mCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=yCONFIG_INET_UDP_DIAG=m
# CONFIG_INET_RAW_DIAG is not setCONFIG_INET_DIAG_DESTROY=y
# CONFIG_TCP_CONG_ADVANCED is not setCONFIG_TCP_CONG_CUBIC=yCONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not setCONFIG_IPV6=m
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not setCONFIG_INET6_AH=m
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not setCONFIG_IPV6_ILA=mCONFIG_INET6_TUNNEL=mCONFIG_IPV6_VTI=m
# CONFIG_IPV6_SIT is not setCONFIG_IPV6_TUNNEL=m
# CONFIG_IPV6_GRE is not setCONFIG_IPV6_FOU=mCONFIG_IPV6_MULTIPLE_TABLES=yCONFIG_IPV6_SUBTREES=yCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=y
# CONFIG_IPV6_SEG6_HMAC is not set
# CONFIG_IPV6_RPL_LWTUNNEL is not set
# CONFIG_IPV6_IOAM6_LWTUNNEL is not set
# CONFIG_NETLABEL is not set
# CONFIG_MPTCP is not setCONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not setCONFIG_NETFILTER=y
# CONFIG_NETFILTER_ADVANCED is not set
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_INGRESS is not set
# CONFIG_NETFILTER_EGRESS is not setCONFIG_NETFILTER_NETLINK=yCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_NETLINK_LOG=yCONFIG_NF_CONNTRACK=mCONFIG_NF_LOG_SYSLOG=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_PROCFS=y
# CONFIG_NF_CONNTRACK_LABELS is not set
# CONFIG_NF_CONNTRACK_FTP is not setCONFIG_NF_CONNTRACK_IRC=mCONFIG_NF_CONNTRACK_BROADCAST=mCONFIG_NF_CONNTRACK_NETBIOS_NS=mCONFIG_NF_CONNTRACK_SIP=mCONFIG_NF_CT_NETLINK=mCONFIG_NETFILTER_NETLINK_GLUE_CT=yCONFIG_NF_NAT=mCONFIG_NF_NAT_IRC=mCONFIG_NF_NAT_SIP=mCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_TABLES=m
# CONFIG_NF_TABLES_INET is not set
# CONFIG_NF_TABLES_NETDEV is not set
# CONFIG_NFT_NUMGEN is not set
# CONFIG_NFT_CT is not setCONFIG_NFT_LOG=m
# CONFIG_NFT_LIMIT is not set
# CONFIG_NFT_MASQ is not setCONFIG_NFT_REDIR=mCONFIG_NFT_NAT=mCONFIG_NFT_TUNNEL=m
# CONFIG_NFT_QUOTA is not setCONFIG_NFT_REJECT=mCONFIG_NFT_COMPAT=mCONFIG_NFT_HASH=mCONFIG_NFT_FIB=m
# CONFIG_NFT_XFRM is not setCONFIG_NFT_SOCKET=m
# CONFIG_NFT_TPROXY is not setCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=y
#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_CONNSECMARK is not set # CONFIG_NETFILTER_XT_TARGET_LOG is not set CONFIG_NETFILTER_XT_NAT=m CONFIG_NETFILTER_XT_TARGET_NETMAP=m
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set CONFIG_NETFILTER_XT_TARGET_REDIRECT=m
# CONFIG_NETFILTER_XT_TARGET_MASQUERADE is not set CONFIG_NETFILTER_XT_TARGET_SECMARK=m
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
# CONFIG_NETFILTER_XT_MATCH_CONNTRACK is not setCONFIG_NETFILTER_XT_MATCH_POLICY=mCONFIG_NETFILTER_XT_MATCH_STATE=m
# end of Core Netfilter Configuration
CONFIG_IP_SET=mCONFIG_IP_SET_MAX=256
# CONFIG_IP_SET_BITMAP_IP is not setCONFIG_IP_SET_BITMAP_IPMAC=m
# CONFIG_IP_SET_BITMAP_PORT is not set
# CONFIG_IP_SET_HASH_IP is not setCONFIG_IP_SET_HASH_IPMARK=mCONFIG_IP_SET_HASH_IPPORT=mCONFIG_IP_SET_HASH_IPPORTIP=m
# CONFIG_IP_SET_HASH_IPPORTNET is not setCONFIG_IP_SET_HASH_IPMAC=mCONFIG_IP_SET_HASH_MAC=m
# CONFIG_IP_SET_HASH_NETPORTNET is not setCONFIG_IP_SET_HASH_NET=m
# CONFIG_IP_SET_HASH_NETNET is not setCONFIG_IP_SET_HASH_NETPORT=mCONFIG_IP_SET_HASH_NETIFACE=mCONFIG_IP_SET_LIST_SET=mCONFIG_IP_VS=m
# CONFIG_IP_VS_IPV6 is not setCONFIG_IP_VS_DEBUG=yCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
# CONFIG_IP_VS_PROTO_TCP is not set
# CONFIG_IP_VS_PROTO_UDP is not setCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=y
# CONFIG_IP_VS_PROTO_SCTP is not set
#
# IPVS scheduler
#
# CONFIG_IP_VS_RR is not setCONFIG_IP_VS_WRR=mCONFIG_IP_VS_LC=mCONFIG_IP_VS_WLC=mCONFIG_IP_VS_FO=m
# CONFIG_IP_VS_OVF is not setCONFIG_IP_VS_LBLC=mCONFIG_IP_VS_LBLCR=mCONFIG_IP_VS_DH=mCONFIG_IP_VS_SH=mCONFIG_IP_VS_MH=mCONFIG_IP_VS_SED=m
# CONFIG_IP_VS_NQ is not set
# CONFIG_IP_VS_TWOS is not set
#
# 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_NFCT=y
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=mCONFIG_NF_SOCKET_IPV4=yCONFIG_NF_TPROXY_IPV4=m
# CONFIG_NF_TABLES_IPV4 is not set
# CONFIG_NF_TABLES_ARP is not set
# CONFIG_NF_DUP_IPV4 is not setCONFIG_NF_LOG_ARP=y
# CONFIG_NF_LOG_IPV4 is not setCONFIG_NF_REJECT_IPV4=yCONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_FILTER is not set
# CONFIG_IP_NF_NAT is not setCONFIG_IP_NF_MANGLE=yCONFIG_IP_NF_RAW=m
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=mCONFIG_NF_TPROXY_IPV6=mCONFIG_NF_TABLES_IPV6=yCONFIG_NFT_REJECT_IPV6=m
# CONFIG_NFT_DUP_IPV6 is not setCONFIG_NFT_FIB_IPV6=mCONFIG_NF_DUP_IPV6=mCONFIG_NF_REJECT_IPV6=m
# CONFIG_NF_LOG_IPV6 is not set
# CONFIG_IP6_NF_IPTABLES is not set
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=mCONFIG_NF_TABLES_BRIDGE=m
# CONFIG_NFT_BRIDGE_META is not setCONFIG_NFT_BRIDGE_REJECT=mCONFIG_NF_CONNTRACK_BRIDGE=mCONFIG_BRIDGE_NF_EBTABLES=mCONFIG_BRIDGE_EBT_BROUTE=mCONFIG_BRIDGE_EBT_T_FILTER=mCONFIG_BRIDGE_EBT_T_NAT=m
# CONFIG_BRIDGE_EBT_802_3 is not setCONFIG_BRIDGE_EBT_AMONG=mCONFIG_BRIDGE_EBT_ARP=mCONFIG_BRIDGE_EBT_IP=mCONFIG_BRIDGE_EBT_IP6=m
# CONFIG_BRIDGE_EBT_LIMIT is not set
# CONFIG_BRIDGE_EBT_MARK is not setCONFIG_BRIDGE_EBT_PKTTYPE=mCONFIG_BRIDGE_EBT_STP=mCONFIG_BRIDGE_EBT_VLAN=mCONFIG_BRIDGE_EBT_ARPREPLY=mCONFIG_BRIDGE_EBT_DNAT=mCONFIG_BRIDGE_EBT_MARK_T=m
# CONFIG_BRIDGE_EBT_REDIRECT is not setCONFIG_BRIDGE_EBT_SNAT=mCONFIG_BRIDGE_EBT_LOG=mCONFIG_BRIDGE_EBT_NFLOG=mCONFIG_BPFILTER=yCONFIG_BPFILTER_UMH=yCONFIG_IP_DCCP=mCONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration
#CONFIG_IP_DCCP_CCID2_DEBUG=y
# CONFIG_IP_DCCP_CCID3 is not set
# end of DCCP CCIDs Configuration
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# end of DCCP Kernel Hacking
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not setCONFIG_ATM=mCONFIG_ATM_CLIP=mCONFIG_ATM_CLIP_NO_ICMP=yCONFIG_ATM_LANE=mCONFIG_ATM_MPOA=mCONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=mCONFIG_L2TP_DEBUGFS=mCONFIG_L2TP_V3=yCONFIG_L2TP_IP=y
# CONFIG_L2TP_ETH is not setCONFIG_STP=yCONFIG_GARP=yCONFIG_MRP=yCONFIG_BRIDGE=m
# CONFIG_BRIDGE_IGMP_SNOOPING is not set CONFIG_BRIDGE_VLAN_FILTERING=y
# CONFIG_BRIDGE_MRP is not set
# CONFIG_BRIDGE_CFM is not set CONFIG_NET_DSA=mCONFIG_NET_DSA_TAG_AR9331=m CONFIG_NET_DSA_TAG_BRCM_COMMON=m CONFIG_NET_DSA_TAG_BRCM=m CONFIG_NET_DSA_TAG_BRCM_LEGACY=m CONFIG_NET_DSA_TAG_BRCM_PREPEND=m CONFIG_NET_DSA_TAG_HELLCREEK=m
# CONFIG_NET_DSA_TAG_GSWIP is not set CONFIG_NET_DSA_TAG_DSA_COMMON=m CONFIG_NET_DSA_TAG_DSA=m CONFIG_NET_DSA_TAG_EDSA=m CONFIG_NET_DSA_TAG_MTK=m CONFIG_NET_DSA_TAG_KSZ=m CONFIG_NET_DSA_TAG_OCELOT=m CONFIG_NET_DSA_TAG_OCELOT_8021Q=m CONFIG_NET_DSA_TAG_QCA=m CONFIG_NET_DSA_TAG_RTL4_A=m CONFIG_NET_DSA_TAG_RTL8_4=m
# CONFIG_NET_DSA_TAG_RZN1_A5PSW is not set CONFIG_NET_DSA_TAG_LAN9303=m CONFIG_NET_DSA_TAG_SJA1105=m CONFIG_NET_DSA_TAG_TRAILER=m CONFIG_NET_DSA_TAG_XRS700X=m CONFIG_VLAN_8021Q=yCONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=yCONFIG_LLC=yCONFIG_LLC2=mCONFIG_ATALK=mCONFIG_DEV_APPLETALK=m
# CONFIG_COPS is not setCONFIG_IPDDP=mCONFIG_IPDDP_ENCAP=yCONFIG_X25=yCONFIG_LAPB=m
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set CONFIG_IEEE802154=y
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=y CONFIG_MAC802154=y
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_DNS_RESOLVER is not set CONFIG_BATMAN_ADV=m
# CONFIG_BATMAN_ADV_BATMAN_V is not set CONFIG_BATMAN_ADV_BLA=y CONFIG_BATMAN_ADV_DAT=y
# CONFIG_BATMAN_ADV_NC is not set CONFIG_BATMAN_ADV_MCAST=y CONFIG_BATMAN_ADV_DEBUG=y CONFIG_BATMAN_ADV_TRACING=y
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set CONFIG_NETLINK_DIAG=mCONFIG_MPLS=y
# CONFIG_NET_MPLS_GSO is not set
# CONFIG_MPLS_ROUTING is not set CONFIG_NET_NSH=yCONFIG_HSR=mCONFIG_NET_SWITCHDEV=y CONFIG_NET_L3_MASTER_DEV=y
# CONFIG_QRTR is not setCONFIG_NET_NCSI=y CONFIG_NCSI_OEM_CMD_GET_MAC=y CONFIG_NCSI_OEM_CMD_KEEP_PHY=y CONFIG_PCPU_DEV_REFCNT=yCONFIG_RPS=yCONFIG_RFS_ACCEL=y CONFIG_SOCK_RX_QUEUE_MAPPING=yCONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set CONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not setCONFIG_NET_DROP_MONITOR=y
# end of Network testing # end of Networking options
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not setCONFIG_BT=y
# CONFIG_BT_BREDR is not set
# CONFIG_BT_LE is not set
# CONFIG_BT_LEDS is not setCONFIG_BT_MSFTEXT=yCONFIG_BT_AOSPEXT=yCONFIG_BT_DEBUGFS=y
# CONFIG_BT_SELFTEST is not set
# CONFIG_BT_FEATURE_DEBUG is not set
#
# Bluetooth device drivers
#CONFIG_BT_MTK=y
# CONFIG_BT_HCIUART is not setCONFIG_BT_HCIVHCI=mCONFIG_BT_MRVL=yCONFIG_BT_MTKUART=y
# CONFIG_BT_VIRTIO is not set
# end of Bluetooth device drivers
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_IPV6 is not set
# CONFIG_AF_RXRPC_INJECT_LOSS is not setCONFIG_AF_RXRPC_DEBUG=y
# CONFIG_RXKAD is not setCONFIG_AF_KCM=mCONFIG_STREAM_PARSER=yCONFIG_MCTP=yCONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not setCONFIG_RFKILL=yCONFIG_RFKILL_LEDS=y
# CONFIG_RFKILL_INPUT is not setCONFIG_RFKILL_GPIO=yCONFIG_NET_9P=yCONFIG_NET_9P_FD=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_RDMA is not set
# CONFIG_NET_9P_DEBUG is not setCONFIG_CAIF=yCONFIG_CAIF_DEBUG=y
# CONFIG_CAIF_NETDEV is not setCONFIG_CAIF_USB=m
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
# CONFIG_PSAMPLE is not setCONFIG_NET_IFE=mCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_NET_SELFTESTS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=y
# CONFIG_PAGE_POOL_STATS is not set
# CONFIG_FAILOVER is not setCONFIG_ETHTOOL_NETLINK=y
#
# Device Drivers
#CONFIG_HAVE_EISA=y
# CONFIG_EISA is not setCONFIG_HAVE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCIEASPM is not set
# CONFIG_PCIE_PTM is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not setCONFIG_PCI_STUB=yCONFIG_PCI_ATS=yCONFIG_PCI_DOE=yCONFIG_PCI_LOCKLESS_CONFIG=y
# CONFIG_PCI_IOV is not set
# CONFIG_PCI_PRI is not setCONFIG_PCI_PASID=yCONFIG_PCI_LABEL=y
# CONFIG_PCIE_BUS_TUNE_OFF is not set
# CONFIG_PCIE_BUS_DEFAULT is not setCONFIG_PCIE_BUS_SAFE=y
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not set
# CONFIG_VGA_ARB is not set
# CONFIG_HOTPLUG_PCI is not set
#
# PCI controller drivers
#
# CONFIG_PCI_FTPCI100 is not set
# CONFIG_PCI_HOST_GENERIC is not setCONFIG_PCIE_XILINX=y
# CONFIG_PCIE_MICROCHIP_HOST is not set
#
# DesignWare PCI Core Support
#CONFIG_PCIE_DW=yCONFIG_PCIE_DW_HOST=yCONFIG_PCIE_DW_PLAT=yCONFIG_PCIE_DW_PLAT_HOST=y
# CONFIG_PCIE_DW_PLAT_EP is not setCONFIG_PCIE_INTEL_GW=yCONFIG_PCI_MESON=m
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# CONFIG_PCIE_CADENCE_PLAT_HOST is not set
# CONFIG_PCIE_CADENCE_PLAT_EP is not set
# CONFIG_PCI_J721E_HOST is not set
# CONFIG_PCI_J721E_EP is not set
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#CONFIG_PCI_ENDPOINT=y
# CONFIG_PCI_ENDPOINT_CONFIGFS is not set
# CONFIG_PCI_EPF_TEST is not set
# CONFIG_PCI_EPF_NTB is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#CONFIG_PCI_SW_SWITCHTEC=y
# end of PCI switch controller drivers
CONFIG_CXL_BUS=yCONFIG_CXL_PCI=yCONFIG_CXL_MEM_RAW_COMMANDS=yCONFIG_CXL_ACPI=yCONFIG_CXL_MEM=mCONFIG_CXL_PORT=yCONFIG_CXL_SUSPEND=y
# CONFIG_PCCARD is not setCONFIG_RAPIDIO=yCONFIG_RAPIDIO_DISC_TIMEOUT=30CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS=yCONFIG_RAPIDIO_DEBUG=yCONFIG_RAPIDIO_ENUM_BASIC=mCONFIG_RAPIDIO_CHMAN=mCONFIG_RAPIDIO_MPORT_CDEV=m
#
# RapidIO Switch drivers
#CONFIG_RAPIDIO_CPS_XX=yCONFIG_RAPIDIO_CPS_GEN2=yCONFIG_RAPIDIO_RXS_GEN3=m
# end of RapidIO Switch drivers
#
# Generic Driver Options
#CONFIG_AUXILIARY_BUS=yCONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
# CONFIG_DEVTMPFS_SAFE is not setCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_FW_LOADER_PAGED_BUF=yCONFIG_FW_LOADER_SYSFS=yCONFIG_EXTRA_FIRMWARE=""CONFIG_FW_LOADER_USER_HELPER=yCONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
# CONFIG_FW_LOADER_COMPRESS is not setCONFIG_FW_CACHE=y
# CONFIG_FW_UPLOAD is not set
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=y
# CONFIG_ALLOW_DEV_COREDUMP is not set
# 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_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_SPMI=mCONFIG_REGMAP_W1=mCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_REGMAP_SCCB=mCONFIG_DMA_SHARED_BUFFER=yCONFIG_DMA_FENCE_TRACE=y
# end of Generic Driver Options
#
# Bus devices
#CONFIG_MOXTET=mCONFIG_MHI_BUS=yCONFIG_MHI_BUS_DEBUG=yCONFIG_MHI_BUS_PCI_GENERIC=m
# CONFIG_MHI_BUS_EP is not set
# end of Bus devices
CONFIG_CONNECTOR=m
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol #
# end of ARM System Control and Management Interface Protocol
# CONFIG_EDD is not set
# CONFIG_FIRMWARE_MEMMAP is not setCONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not setCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
# CONFIG_ISCSI_IBFT is not set
# CONFIG_FW_CFG_SYSFS is not setCONFIG_SYSFB=y
# CONFIG_SYSFB_SIMPLEFB is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_GNSS=mCONFIG_GNSS_SERIAL=m
# CONFIG_GNSS_MTK_SERIAL is not setCONFIG_GNSS_SIRF_SERIAL=mCONFIG_GNSS_UBX_SERIAL=m
# CONFIG_MTD is not setCONFIG_DTC=yCONFIG_OF=y
# CONFIG_OF_UNITTEST is not setCONFIG_OF_FLATTREE=yCONFIG_OF_KOBJ=yCONFIG_OF_DYNAMIC=yCONFIG_OF_ADDRESS=yCONFIG_OF_IRQ=yCONFIG_OF_RESOLVE=yCONFIG_OF_OVERLAY=yCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=yCONFIG_PARPORT_PC=m
# CONFIG_PARPORT_SERIAL is not setCONFIG_PARPORT_PC_FIFO=yCONFIG_PARPORT_PC_SUPERIO=yCONFIG_PARPORT_AX88796=y
# CONFIG_PARPORT_1284 is not setCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not setCONFIG_PNPACPI=yCONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_ZRAM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_BLK_DEV_UBLK is not set
# CONFIG_BLK_DEV_RNBD_CLIENT is not set
# CONFIG_BLK_DEV_RNBD_SERVER is not set
#
# NVME Support
#CONFIG_NVME_CORE=yCONFIG_BLK_DEV_NVME=y
# CONFIG_NVME_MULTIPATH is not set
# CONFIG_NVME_VERBOSE_ERRORS is not set
# CONFIG_NVME_HWMON is not setCONFIG_NVME_FABRICS=yCONFIG_NVME_RDMA=m
# CONFIG_NVME_FC is not setCONFIG_NVME_TCP=y
# CONFIG_NVME_AUTH is not set
# CONFIG_NVME_TARGET is not set
# end of NVME Support
#
# Misc devices
#CONFIG_AD525X_DPOT=yCONFIG_AD525X_DPOT_I2C=yCONFIG_AD525X_DPOT_SPI=m
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not setCONFIG_PHANTOM=yCONFIG_TIFM_CORE=mCONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=yCONFIG_CS5535_MFGPT=yCONFIG_CS5535_MFGPT_DEFAULT_IRQ=7CONFIG_CS5535_CLOCK_EVENT_SRC=mCONFIG_HI6421V600_IRQ=m
# CONFIG_HP_ILO is not setCONFIG_APDS9802ALS=yCONFIG_ISL29003=y
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not setCONFIG_SENSORS_BH1770=y
# CONFIG_SENSORS_APDS990X is not setCONFIG_HMC6352=yCONFIG_DS1682=yCONFIG_PCH_PHUB=yCONFIG_LATTICE_ECP3_CONFIG=mCONFIG_SRAM=yCONFIG_DW_XDATA_PCIE=m
# CONFIG_PCI_ENDPOINT_TEST is not setCONFIG_XILINX_SDFEC=yCONFIG_MISC_RTSX=m
# CONFIG_VCPU_STALL_DETECTOR is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#CONFIG_EEPROM_AT24=yCONFIG_EEPROM_AT25=mCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_MAX6875=yCONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not setCONFIG_EEPROM_IDT_89HPESX=m
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
CONFIG_CB710_CORE=mCONFIG_CB710_DEBUG=yCONFIG_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 is not set
# CONFIG_ALTERA_STAPL is not setCONFIG_INTEL_MEI=mCONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_GSC is not setCONFIG_INTEL_MEI_HDCP=m
# CONFIG_INTEL_MEI_PXP is not set
# CONFIG_VMWARE_VMCI is not setCONFIG_ECHO=yCONFIG_BCM_VK=m
# CONFIG_BCM_VK_TTY is not set
# CONFIG_MISC_ALCOR_PCI is not setCONFIG_MISC_RTSX_PCI=mCONFIG_HABANA_AI=y
# CONFIG_UACCE is not set
# CONFIG_PVPANIC is not set
# CONFIG_GP_PCI1XXXX is not set
# end of Misc devices
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=yCONFIG_SCSI_COMMON=yCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_BLK_DEV_SR is not setCONFIG_CHR_DEV_SG=yCONFIG_BLK_DEV_BSG=yCONFIG_CHR_DEV_SCH=m
# CONFIG_SCSI_ENCLOSURE is not setCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=y
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not setCONFIG_SCSI_ISCSI_ATTRS=yCONFIG_SCSI_SAS_ATTRS=yCONFIG_SCSI_SAS_LIBSAS=yCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=y
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=yCONFIG_ISCSI_BOOT_SYSFS=yCONFIG_SCSI_CXGB3_ISCSI=m
# CONFIG_SCSI_CXGB4_ISCSI is not setCONFIG_SCSI_BNX2_ISCSI=mCONFIG_BE2ISCSI=yCONFIG_BLK_DEV_3W_XXXX_RAID=mCONFIG_SCSI_HPSA=m
# CONFIG_SCSI_3W_9XXX is not setCONFIG_SCSI_3W_SAS=yCONFIG_SCSI_ACARD=m
# CONFIG_SCSI_AHA152X is not setCONFIG_SCSI_AHA1542=mCONFIG_SCSI_AACRAID=mCONFIG_SCSI_AIC7XXX=mCONFIG_AIC7XXX_CMDS_PER_DEVICE=32CONFIG_AIC7XXX_RESET_DELAY_MS=5000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not setCONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_AIC7XXX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC79XX=mCONFIG_AIC79XX_CMDS_PER_DEVICE=32CONFIG_AIC79XX_RESET_DELAY_MS=5000
# CONFIG_AIC79XX_DEBUG_ENABLE is not setCONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not setCONFIG_SCSI_AIC94XX=mCONFIG_AIC94XX_DEBUG=yCONFIG_SCSI_MVSAS=mCONFIG_SCSI_MVSAS_DEBUG=y
# CONFIG_SCSI_MVSAS_TASKLET is not setCONFIG_SCSI_MVUMI=yCONFIG_SCSI_ADVANSYS=yCONFIG_SCSI_ARCMSR=yCONFIG_SCSI_ESAS2R=y
# CONFIG_MEGARAID_NEWGEN is not setCONFIG_MEGARAID_LEGACY=m
# CONFIG_MEGARAID_SAS is not setCONFIG_SCSI_MPT3SAS=mCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128CONFIG_SCSI_MPT2SAS=mCONFIG_SCSI_MPI3MR=yCONFIG_SCSI_SMARTPQI=yCONFIG_SCSI_HPTIOP=m
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not setCONFIG_SCSI_MYRS=yCONFIG_VMWARE_PVSCSI=yCONFIG_SCSI_SNIC=y
# CONFIG_SCSI_SNIC_DEBUG_FS is not set
# CONFIG_SCSI_DMX3191D is not setCONFIG_SCSI_FDOMAIN=mCONFIG_SCSI_FDOMAIN_PCI=m
# CONFIG_SCSI_FDOMAIN_ISA is not setCONFIG_SCSI_ISCI=yCONFIG_SCSI_GENERIC_NCR5380=yCONFIG_SCSI_IPS=mCONFIG_SCSI_INITIO=yCONFIG_SCSI_INIA100=mCONFIG_SCSI_PPA=m
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_IZIP_EPP16 is not setCONFIG_SCSI_IZIP_SLOW_CTR=y
# CONFIG_SCSI_STEX is not setCONFIG_SCSI_SYM53C8XX_2=mCONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_MMIO is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_ISCSI is not set
CONFIG_SCSI_DC395x=yCONFIG_SCSI_AM53C974=y
# CONFIG_SCSI_NSP32 is not setCONFIG_SCSI_WD719X=m
# CONFIG_SCSI_DEBUG is not setCONFIG_SCSI_PMCRAID=mCONFIG_SCSI_PM8001=m
# CONFIG_SCSI_VIRTIO is not setCONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not setCONFIG_SCSI_DH_HP_SW=y
# CONFIG_SCSI_DH_EMC is not set
# CONFIG_SCSI_DH_ALUA is not set
# end of SCSI device support
CONFIG_ATA=yCONFIG_SATA_HOST=yCONFIG_PATA_TIMINGS=yCONFIG_ATA_VERBOSE_ERROR=y
# CONFIG_ATA_FORCE is not setCONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not setCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=yCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_AHCI_DWC is not setCONFIG_AHCI_CEVA=mCONFIG_AHCI_QORIQ=m
# CONFIG_SATA_INIC162X is not setCONFIG_SATA_ACARD_AHCI=mCONFIG_SATA_SIL24=y
# CONFIG_ATA_SFF is not set
# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=yCONFIG_FIREWIRE_OHCI=m
# CONFIG_FIREWIRE_SBP2 is not setCONFIG_FIREWIRE_NET=yCONFIG_FIREWIRE_NOSY=y
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=y
# CONFIG_MAC_EMUMOUSEBTN is not setCONFIG_NETDEVICES=yCONFIG_MII=y
# CONFIG_NET_CORE is not set
# CONFIG_ARCNET is not setCONFIG_ATM_DRIVERS=yCONFIG_ATM_DUMMY=m
# CONFIG_ATM_TCP is not setCONFIG_ATM_LANAI=m
# CONFIG_ATM_ENI is not setCONFIG_ATM_NICSTAR=mCONFIG_ATM_NICSTAR_USE_SUNI=yCONFIG_ATM_NICSTAR_USE_IDT77105=yCONFIG_ATM_IDT77252=mCONFIG_ATM_IDT77252_DEBUG=yCONFIG_ATM_IDT77252_RCV_ALL=yCONFIG_ATM_IDT77252_USE_SUNI=y
# CONFIG_ATM_IA is not setCONFIG_ATM_FORE200E=mCONFIG_ATM_FORE200E_USE_TASKLET=yCONFIG_ATM_FORE200E_TX_RETRY=16CONFIG_ATM_FORE200E_DEBUG=0
# CONFIG_ATM_HE is not setCONFIG_ATM_SOLOS=mCONFIG_CAIF_DRIVERS=y
# CONFIG_CAIF_TTY is not setCONFIG_CAIF_VIRTIO=y
#
# Distributed Switch Architecture drivers
#CONFIG_B53=mCONFIG_B53_SPI_DRIVER=m
# CONFIG_B53_MDIO_DRIVER is not setCONFIG_B53_MMAP_DRIVER=mCONFIG_B53_SRAB_DRIVER=mCONFIG_B53_SERDES=mCONFIG_NET_DSA_BCM_SF2=mCONFIG_NET_DSA_LOOP=m
# CONFIG_NET_DSA_LANTIQ_GSWIP is not set
# CONFIG_NET_DSA_MT7530 is not setCONFIG_NET_DSA_MV88E6060=mCONFIG_NET_DSA_MICROCHIP_KSZ_COMMON=mCONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=m
# CONFIG_NET_DSA_MICROCHIP_KSZ_SPI is not setCONFIG_NET_DSA_MICROCHIP_KSZ8863_SMI=mCONFIG_NET_DSA_MV88E6XXX=m
# CONFIG_NET_DSA_MSCC_SEVILLE is not setCONFIG_NET_DSA_AR9331=mCONFIG_NET_DSA_QCA8K=mCONFIG_NET_DSA_SJA1105=mCONFIG_NET_DSA_XRS700X=mCONFIG_NET_DSA_XRS700X_I2C=mCONFIG_NET_DSA_XRS700X_MDIO=m
# CONFIG_NET_DSA_REALTEK is not setCONFIG_NET_DSA_SMSC_LAN9303=m
# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not setCONFIG_NET_DSA_SMSC_LAN9303_MDIO=mCONFIG_NET_DSA_VITESSE_VSC73XX=m
# CONFIG_NET_DSA_VITESSE_VSC73XX_SPI is not setCONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM=m
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=yCONFIG_NET_VENDOR_3COM=yCONFIG_EL3=mCONFIG_3C515=yCONFIG_VORTEX=yCONFIG_TYPHOON=y
# CONFIG_NET_VENDOR_ADAPTEC is not setCONFIG_NET_VENDOR_AGERE=yCONFIG_ET131X=mCONFIG_NET_VENDOR_ALACRITECH=yCONFIG_SLICOSS=m
# CONFIG_NET_VENDOR_ALTEON is not setCONFIG_ALTERA_TSE=m
# CONFIG_NET_VENDOR_AMAZON is not set
# CONFIG_NET_VENDOR_AMD is not setCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_AQTION=y
# CONFIG_NET_VENDOR_ARC is not set
# CONFIG_NET_VENDOR_ASIX is not setCONFIG_NET_VENDOR_ATHEROS=yCONFIG_ATL2=y
# CONFIG_ATL1 is not setCONFIG_ATL1E=m
# CONFIG_ATL1C is not set
# CONFIG_ALX is not set
# CONFIG_CX_ECAT is not setCONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not setCONFIG_BNX2=yCONFIG_CNIC=mCONFIG_TIGON3=mCONFIG_TIGON3_HWMON=y
# CONFIG_BNX2X is not set
# CONFIG_SYSTEMPORT is not setCONFIG_BNXT=mCONFIG_BNXT_FLOWER_OFFLOAD=y
# CONFIG_BNXT_HWMON is not setCONFIG_NET_VENDOR_CADENCE=y
# CONFIG_MACB is not setCONFIG_NET_VENDOR_CAVIUM=yCONFIG_NET_VENDOR_CHELSIO=yCONFIG_CHELSIO_T1=yCONFIG_CHELSIO_T1_1G=yCONFIG_CHELSIO_T3=y
# CONFIG_CHELSIO_T4 is not setCONFIG_CHELSIO_T4VF=yCONFIG_CHELSIO_LIB=m
# CONFIG_NET_VENDOR_CIRRUS is not setCONFIG_NET_VENDOR_CISCO=yCONFIG_ENIC=m
# CONFIG_NET_VENDOR_CORTINA is not setCONFIG_NET_VENDOR_DAVICOM=y
# CONFIG_DM9051 is not setCONFIG_DNET=y
# CONFIG_NET_VENDOR_DEC is not setCONFIG_NET_VENDOR_DLINK=yCONFIG_DL2K=y
# CONFIG_SUNDANCE is not setCONFIG_NET_VENDOR_EMULEX=yCONFIG_BE2NET=y
# CONFIG_BE2NET_HWMON is not set
# CONFIG_BE2NET_BE2 is not set
# CONFIG_BE2NET_BE3 is not setCONFIG_BE2NET_LANCER=yCONFIG_BE2NET_SKYHAWK=yCONFIG_NET_VENDOR_ENGLEDER=y
# CONFIG_TSNEP is not set
# CONFIG_NET_VENDOR_EZCHIP is not setCONFIG_NET_VENDOR_FUNGIBLE=y
# CONFIG_FUN_ETH is not set
# CONFIG_NET_VENDOR_GOOGLE is not setCONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not set
# CONFIG_NET_VENDOR_I825XX is not setCONFIG_NET_VENDOR_INTEL=yCONFIG_E100=yCONFIG_E1000=yCONFIG_E1000E=yCONFIG_E1000E_HWTS=yCONFIG_IGB=m
# CONFIG_IGB_HWMON is not setCONFIG_IGBVF=yCONFIG_IXGB=mCONFIG_IXGBE=y
# CONFIG_IXGBE_HWMON is not set
# CONFIG_IXGBE_IPSEC is not setCONFIG_IXGBEVF=mCONFIG_IXGBEVF_IPSEC=yCONFIG_I40E=y
# CONFIG_I40EVF is not setCONFIG_ICE=m
# CONFIG_ICE_SWITCHDEV is not setCONFIG_ICE_HWTS=yCONFIG_FM10K=yCONFIG_IGC=mCONFIG_NET_VENDOR_WANGXUN=y
# CONFIG_NGBE is not set
# CONFIG_TXGBE is not set
# CONFIG_JME is not setCONFIG_NET_VENDOR_ADI=y
# CONFIG_ADIN1110 is not setCONFIG_NET_VENDOR_LITEX=y
# CONFIG_LITEX_LITEETH is not set
# CONFIG_NET_VENDOR_MARVELL is not setCONFIG_NET_VENDOR_MELLANOX=yCONFIG_MLX4_EN=yCONFIG_MLX4_CORE=y
# CONFIG_MLX4_DEBUG is not set
# CONFIG_MLX4_CORE_GEN2 is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not setCONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not setCONFIG_KSZ884X_PCI=mCONFIG_NET_VENDOR_MICROCHIP=yCONFIG_ENC28J60=yCONFIG_ENC28J60_WRITEVERIFY=yCONFIG_ENCX24J600=y
# CONFIG_LAN743X is not set
# CONFIG_LAN966X_SWITCH is not set
# CONFIG_VCAP is not setCONFIG_NET_VENDOR_MICROSEMI=y
# CONFIG_MSCC_OCELOT_SWITCH is not setCONFIG_NET_VENDOR_MICROSOFT=y
# CONFIG_NET_VENDOR_MYRI is not setCONFIG_NET_VENDOR_NI=yCONFIG_NI_XGE_MANAGEMENT_ENET=yCONFIG_NET_VENDOR_NATSEMI=yCONFIG_NATSEMI=m
# CONFIG_NS83820 is not setCONFIG_NET_VENDOR_NETERION=yCONFIG_S2IO=y
# CONFIG_NET_VENDOR_NETRONOME is not set
# CONFIG_NET_VENDOR_8390 is not setCONFIG_NET_VENDOR_NVIDIA=yCONFIG_FORCEDETH=mCONFIG_NET_VENDOR_OKI=yCONFIG_ETHOC=y
# CONFIG_NET_VENDOR_PACKET_ENGINES is not setCONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_NET_VENDOR_QLOGIC is not set
# CONFIG_NET_VENDOR_BROCADE is not setCONFIG_NET_VENDOR_QUALCOMM=yCONFIG_QCA7000=yCONFIG_QCA7000_SPI=yCONFIG_QCA7000_UART=m
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not set
# CONFIG_NET_VENDOR_RDC is not setCONFIG_NET_VENDOR_REALTEK=yCONFIG_ATP=mCONFIG_8139CP=m
# CONFIG_8139TOO is not set
# CONFIG_R8169 is not set
# CONFIG_NET_VENDOR_RENESAS is not setCONFIG_NET_VENDOR_ROCKER=y
# CONFIG_ROCKER is not set
# CONFIG_NET_VENDOR_SAMSUNG is not setCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SILAN=yCONFIG_SC92031=m
# CONFIG_NET_VENDOR_SIS is not setCONFIG_NET_VENDOR_SOLARFLARE=y
# CONFIG_SFC is not setCONFIG_SFC_FALCON=mCONFIG_NET_VENDOR_SMSC=yCONFIG_SMC9194=mCONFIG_EPIC100=m
# CONFIG_SMSC911X is not setCONFIG_SMSC9420=y
# CONFIG_NET_VENDOR_SOCIONEXT is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not setCONFIG_NET_VENDOR_TEHUTI=yCONFIG_TEHUTI=yCONFIG_NET_VENDOR_TI=yCONFIG_TI_CPSW_PHY_SEL=y
# CONFIG_TLAN is not setCONFIG_NET_VENDOR_VERTEXCOM=y
# CONFIG_MSE102X is not setCONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not setCONFIG_VIA_VELOCITY=y
# CONFIG_NET_VENDOR_WIZNET is not set
# CONFIG_NET_VENDOR_XILINX is not setCONFIG_FDDI=m
# CONFIG_DEFXX is not setCONFIG_SKFP=mCONFIG_HIPPI=yCONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
# CONFIG_NET_SB1000 is not setCONFIG_PHYLINK=mCONFIG_PHYLIB=yCONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not setCONFIG_FIXED_PHY=y
# CONFIG_SFP is not set
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not setCONFIG_ADIN_PHY=m
# CONFIG_ADIN1100_PHY is not setCONFIG_AQUANTIA_PHY=y
# CONFIG_AX88796B_PHY is not setCONFIG_BROADCOM_PHY=y
# CONFIG_BCM54140_PHY is not setCONFIG_BCM7XXX_PHY=mCONFIG_BCM84881_PHY=y
# CONFIG_BCM87XX_PHY is not setCONFIG_BCM_NET_PHYLIB=y
# CONFIG_CICADA_PHY is not setCONFIG_CORTINA_PHY=mCONFIG_DAVICOM_PHY=y
# CONFIG_ICPLUS_PHY is not setCONFIG_LXT_PHY=mCONFIG_INTEL_XWAY_PHY=y
# CONFIG_LSI_ET1011C_PHY is not setCONFIG_MARVELL_PHY=mCONFIG_MARVELL_10G_PHY=yCONFIG_MARVELL_88X2222_PHY=y
# CONFIG_MAXLINEAR_GPHY is not setCONFIG_MEDIATEK_GE_PHY=yCONFIG_MICREL_PHY=y
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not setCONFIG_MICROSEMI_PHY=mCONFIG_MOTORCOMM_PHY=y
# CONFIG_NATIONAL_PHY is not setCONFIG_NXP_C45_TJA11XX_PHY=yCONFIG_NXP_TJA11XX_PHY=y
# CONFIG_AT803X_PHY is not setCONFIG_QSEMI_PHY=yCONFIG_REALTEK_PHY=mCONFIG_RENESAS_PHY=y
# CONFIG_ROCKCHIP_PHY is not setCONFIG_SMSC_PHY=y
# CONFIG_STE10XP is not setCONFIG_TERANETICS_PHY=y
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not setCONFIG_DP83867_PHY=mCONFIG_DP83869_PHY=y
# CONFIG_DP83TD510_PHY is not setCONFIG_VITESSE_PHY=y
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PSE_CONTROLLER is not set
#
# MCTP Device Drivers
#
# CONFIG_MCTP_SERIAL is not set
# CONFIG_MCTP_TRANSPORT_I2C is not set
# end of MCTP Device Drivers
CONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_FWNODE_MDIO=yCONFIG_OF_MDIO=yCONFIG_ACPI_MDIO=yCONFIG_MDIO_DEVRES=yCONFIG_MDIO_BITBANG=yCONFIG_MDIO_BCM_UNIMAC=y
# CONFIG_MDIO_GPIO is not setCONFIG_MDIO_HISI_FEMAC=mCONFIG_MDIO_MSCC_MIIM=m
# CONFIG_MDIO_IPQ4019 is not setCONFIG_MDIO_IPQ8064=y
#
# MDIO Multiplexers
#CONFIG_MDIO_BUS_MUX=yCONFIG_MDIO_BUS_MUX_GPIO=yCONFIG_MDIO_BUS_MUX_MULTIPLEXER=mCONFIG_MDIO_BUS_MUX_MMIOREG=y
#
# PCS device drivers
#CONFIG_PCS_XPCS=mCONFIG_PCS_ALTERA_TSE=m
# end of PCS device drivers
CONFIG_PLIP=yCONFIG_PPP=yCONFIG_PPP_BSDCOMP=yCONFIG_PPP_DEFLATE=yCONFIG_PPP_FILTER=yCONFIG_PPP_MPPE=yCONFIG_PPP_MULTILINK=yCONFIG_PPPOATM=mCONFIG_PPPOE=yCONFIG_PPTP=mCONFIG_PPPOL2TP=m
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_SLIP is not setCONFIG_SLHC=y
#
# Host-side USB support is needed for USB Network Adapter support #
# CONFIG_WLAN is not set
# CONFIG_WAN is not setCONFIG_IEEE802154_DRIVERS=mCONFIG_IEEE802154_FAKELB=m
# CONFIG_IEEE802154_AT86RF230 is not set CONFIG_IEEE802154_MRF24J40=mCONFIG_IEEE802154_CC2520=mCONFIG_IEEE802154_ADF7242=mCONFIG_IEEE802154_CA8210=m
# CONFIG_IEEE802154_CA8210_DEBUGFS is not set CONFIG_IEEE802154_MCR20A=mCONFIG_IEEE802154_HWSIM=m
#
# Wireless WAN
#
# CONFIG_WWAN is not set
# end of Wireless WAN
CONFIG_VMXNET3=y
# CONFIG_FUJITSU_ES is not set
# CONFIG_NETDEVSIM is not set
# CONFIG_NET_FAILOVER is not setCONFIG_NETDEV_LEGACY_INIT=yCONFIG_ISDN=yCONFIG_ISDN_CAPI=yCONFIG_MISDN=yCONFIG_MISDN_DSP=yCONFIG_MISDN_L1OIP=y
#
# mISDN hardware drivers
#CONFIG_MISDN_HFCPCI=yCONFIG_MISDN_HFCMULTI=m
# CONFIG_MISDN_AVMFRITZ is not setCONFIG_MISDN_SPEEDFAX=mCONFIG_MISDN_INFINEON=m
# CONFIG_MISDN_W6692 is not set
# CONFIG_MISDN_NETJET is not setCONFIG_MISDN_IPAC=mCONFIG_MISDN_ISAR=m
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not setCONFIG_INPUT_VIVALDIFMAP=y
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5520 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_PINEPHONE is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_GOLDFISH_EVENTS is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_IQS62X is not set
# CONFIG_KEYBOARD_OMAP4 is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CROS_EC is not set
# CONFIG_KEYBOARD_CAP11XX is not set
# CONFIG_KEYBOARD_BCM is not set
# CONFIG_KEYBOARD_MTK_PMIC is not set
# CONFIG_KEYBOARD_CYPRESS_SF 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=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=y
# CONFIG_MOUSE_PS2_VMMOUSE is not setCONFIG_MOUSE_PS2_SMBUS=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
# CONFIG_RMI4_CORE 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=mCONFIG_SERIO_PS2MULT=m
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not setCONFIG_SERIO_GPIO_PS2=m
# CONFIG_USERIO is not setCONFIG_GAMEPORT=mCONFIG_GAMEPORT_NS558=m
# CONFIG_GAMEPORT_L4 is not setCONFIG_GAMEPORT_EMU10K1=mCONFIG_GAMEPORT_FM801=m
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=y
# CONFIG_VT is not setCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_16550A_VARIANTS is not set
# CONFIG_SERIAL_8250_FINTEK is not setCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_EXAR=y
# CONFIG_SERIAL_8250_MEN_MCB is not setCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not setCONFIG_SERIAL_8250_DWLIB=y
# CONFIG_SERIAL_8250_DW is not set
# CONFIG_SERIAL_8250_RT288X is not setCONFIG_SERIAL_8250_LPSS=yCONFIG_SERIAL_8250_MID=yCONFIG_SERIAL_8250_PERICOM=y
# CONFIG_SERIAL_OF_PLATFORM 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=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_LANTIQ is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# CONFIG_SERIAL_MEN_Z135 is not set
# CONFIG_SERIAL_SPRD is not set
# CONFIG_SERIAL_LITEUART is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_GOLDFISH_TTY is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
# CONFIG_NULL_TTY is not set
# CONFIG_RPMSG_TTY is not setCONFIG_SERIAL_DEV_BUS=yCONFIG_SERIAL_DEV_CTRL_TTYPORT=y
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=mCONFIG_LP_CONSOLE=y
# CONFIG_PPDEV is not set
# CONFIG_VIRTIO_CONSOLE is not setCONFIG_IPMI_HANDLER=mCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=y
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not setCONFIG_IPMI_SI=m
# CONFIG_IPMI_SSIF is not setCONFIG_IPMI_IPMB=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=m
# CONFIG_IPMB_DEVICE_INTERFACE is not setCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=m
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not setCONFIG_HW_RANDOM_BA431=mCONFIG_HW_RANDOM_GEODE=mCONFIG_HW_RANDOM_VIA=yCONFIG_HW_RANDOM_VIRTIO=mCONFIG_HW_RANDOM_CCTRNG=mCONFIG_HW_RANDOM_XIPHERA=yCONFIG_DTLK=m
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
CONFIG_SCx200_GPIO=m
# CONFIG_PC8736x_GPIO is not setCONFIG_NSC_GPIO=mCONFIG_DEVMEM=yCONFIG_NVRAM=mCONFIG_DEVPORT=y
# CONFIG_HPET is not setCONFIG_HANGCHECK_TIMER=yCONFIG_TCG_TPM=y
# CONFIG_HW_RANDOM_TPM is not setCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=yCONFIG_TCG_TIS_SPI=m
# CONFIG_TCG_TIS_SPI_CR50 is not set
# CONFIG_TCG_TIS_I2C is not setCONFIG_TCG_TIS_I2C_CR50=y
# CONFIG_TCG_TIS_I2C_ATMEL is not set
# CONFIG_TCG_TIS_I2C_INFINEON is not set
# CONFIG_TCG_TIS_I2C_NUVOTON is not setCONFIG_TCG_NSC=yCONFIG_TCG_ATMEL=y
# CONFIG_TCG_INFINEON is not set
# CONFIG_TCG_CRB is not setCONFIG_TCG_VTPM_PROXY=mCONFIG_TCG_TIS_ST33ZP24=yCONFIG_TCG_TIS_ST33ZP24_I2C=y
# CONFIG_TCG_TIS_ST33ZP24_SPI is not setCONFIG_TELCLOCK=y
# CONFIG_XILLYBUS is not setCONFIG_RANDOM_TRUST_CPU=y
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
# end of Character devices
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_COMPAT is not setCONFIG_I2C_CHARDEV=yCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_ARB_GPIO_CHALLENGE=m
# CONFIG_I2C_MUX_GPIO is not setCONFIG_I2C_MUX_GPMUX=yCONFIG_I2C_MUX_LTC4306=yCONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=y
# CONFIG_I2C_MUX_PINCTRL is not set
# CONFIG_I2C_MUX_REG is not setCONFIG_I2C_DEMUX_PINCTRL=y
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
# CONFIG_I2C_HELPER_AUTO is not setCONFIG_I2C_SMBUS=y
#
# I2C Algorithms
#CONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCF=mCONFIG_I2C_ALGOPCA=y
# end of I2C Algorithms
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_CCGX_UCSI=yCONFIG_I2C_ALI1535=m
# CONFIG_I2C_ALI1563 is not setCONFIG_I2C_ALI15X3=y
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_AMD_MP2 is not setCONFIG_I2C_I801=y
# CONFIG_I2C_ISCH is not setCONFIG_I2C_ISMT=y
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not setCONFIG_I2C_NVIDIA_GPU=yCONFIG_I2C_SIS5595=y
# CONFIG_I2C_SIS630 is not setCONFIG_I2C_SIS96X=m
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_CBUS_GPIO=y CONFIG_I2C_DESIGNWARE_CORE=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m
# CONFIG_I2C_DESIGNWARE_AMDPSP is not set
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set CONFIG_I2C_EG20T=m
# CONFIG_I2C_EMEV2 is not setCONFIG_I2C_GPIO=yCONFIG_I2C_GPIO_FAULT_INJECTOR=y CONFIG_I2C_OCORES=m
# CONFIG_I2C_PCA_PLATFORM is not set CONFIG_I2C_PXA=yCONFIG_I2C_PXA_PCI=yCONFIG_I2C_RK3X=y
# CONFIG_I2C_SIMTEC is not setCONFIG_I2C_XILINX=m
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PCI1XXXX is not set
# CONFIG_I2C_TAOS_EVM is not set
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_PCA_ISA=yCONFIG_I2C_CROS_EC_TUNNEL=m
# CONFIG_SCx200_ACB is not setCONFIG_I2C_VIRTIO=y
# end of I2C Hardware Bus support
# CONFIG_I2C_STUB is not setCONFIG_I2C_SLAVE=y
# CONFIG_I2C_SLAVE_EEPROM is not set
# CONFIG_I2C_SLAVE_TESTUNIT 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=m
# CONFIG_CDNS_I3C_MASTER is not setCONFIG_DW_I3C_MASTER=mCONFIG_SVC_I3C_MASTER=m
# CONFIG_MIPI_I3C_HCI 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=mCONFIG_SPI_ALTERA_CORE=m
# CONFIG_SPI_AXI_SPI_ENGINE is not setCONFIG_SPI_BITBANG=y
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_CADENCE_QUADSPI is not setCONFIG_SPI_DESIGNWARE=m
# CONFIG_SPI_DW_DMA is not set
# CONFIG_SPI_DW_PCI is not setCONFIG_SPI_DW_MMIO=m
# CONFIG_SPI_NXP_FLEXSPI is not setCONFIG_SPI_GPIO=yCONFIG_SPI_LM70_LLP=y
# CONFIG_SPI_FSL_SPI is not set
# CONFIG_SPI_MICROCHIP_CORE is not set
# CONFIG_SPI_MICROCHIP_CORE_QSPI is not setCONFIG_SPI_LANTIQ_SSC=yCONFIG_SPI_OC_TINY=y
# CONFIG_SPI_PXA2XX is not setCONFIG_SPI_ROCKCHIP=mCONFIG_SPI_SC18IS602=y
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_TOPCLIFF_PCH is not setCONFIG_SPI_XCOMM=mCONFIG_SPI_XILINX=mCONFIG_SPI_ZYNQMP_GQSPI=y
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#CONFIG_SPI_MUX=m
#
# SPI Protocol Masters
#CONFIG_SPI_SPIDEV=y
# CONFIG_SPI_LOOPBACK_TEST is not setCONFIG_SPI_TLE62X0=mCONFIG_SPI_SLAVE=yCONFIG_SPI_SLAVE_TIME=yCONFIG_SPI_SLAVE_SYSTEM_CONTROL=yCONFIG_SPI_DYNAMIC=yCONFIG_SPMI=mCONFIG_SPMI_HISI3670=mCONFIG_HSI=yCONFIG_HSI_BOARDINFO=y
#
# HSI controllers
#
#
# HSI clients
#CONFIG_HSI_CHAR=mCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not setCONFIG_NTP_PPS=y
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not setCONFIG_PPS_CLIENT_PARPORT=mCONFIG_PPS_CLIENT_GPIO=m
#
# PPS generators support
#
#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not setCONFIG_PTP_1588_CLOCK_OPTIONAL=y
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. #
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_GENERIC_PINCTRL_GROUPS=yCONFIG_PINMUX=yCONFIG_GENERIC_PINMUX_FUNCTIONS=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=yCONFIG_DEBUG_PINCTRL=y
# CONFIG_PINCTRL_AMD is not set
# CONFIG_PINCTRL_CY8C95X0 is not setCONFIG_PINCTRL_DA9062=mCONFIG_PINCTRL_EQUILIBRIUM=yCONFIG_PINCTRL_MCP23S08_I2C=mCONFIG_PINCTRL_MCP23S08_SPI=mCONFIG_PINCTRL_MCP23S08=mCONFIG_PINCTRL_MICROCHIP_SGPIO=y
# CONFIG_PINCTRL_OCELOT is not set
# CONFIG_PINCTRL_PALMAS is not set
# CONFIG_PINCTRL_RK805 is not setCONFIG_PINCTRL_SINGLE=yCONFIG_PINCTRL_STMFX=m
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_MADERA=yCONFIG_PINCTRL_CS47L35=y
#
# Intel pinctrl drivers
#
# CONFIG_PINCTRL_BAYTRAIL is not set
# CONFIG_PINCTRL_CHERRYVIEW is not set
# CONFIG_PINCTRL_LYNXPOINT is not set
# CONFIG_PINCTRL_ALDERLAKE is not set
# CONFIG_PINCTRL_BROXTON is not set
# CONFIG_PINCTRL_CANNONLAKE is not set
# CONFIG_PINCTRL_CEDARFORK is not set
# CONFIG_PINCTRL_DENVERTON is not set
# CONFIG_PINCTRL_ELKHARTLAKE is not set
# CONFIG_PINCTRL_EMMITSBURG is not set
# CONFIG_PINCTRL_GEMINILAKE is not set
# CONFIG_PINCTRL_ICELAKE is not set
# CONFIG_PINCTRL_JASPERLAKE is not set
# CONFIG_PINCTRL_LAKEFIELD is not set
# CONFIG_PINCTRL_LEWISBURG is not set
# CONFIG_PINCTRL_METEORLAKE is not set
# CONFIG_PINCTRL_SUNRISEPOINT is not set
# CONFIG_PINCTRL_TIGERLAKE is not set
# end of Intel pinctrl drivers
#
# Renesas pinctrl drivers
#
# end of Renesas pinctrl drivers
CONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_OF_GPIO=yCONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not setCONFIG_GPIO_CDEV=y
# CONFIG_GPIO_CDEV_V1 is not setCONFIG_GPIO_GENERIC=yCONFIG_GPIO_MAX730X=m
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_74XX_MMIO=mCONFIG_GPIO_ALTERA=m
# CONFIG_GPIO_AMDPT is not setCONFIG_GPIO_CADENCE=yCONFIG_GPIO_DWAPB=m
# CONFIG_GPIO_EXAR is not setCONFIG_GPIO_FTGPIO010=y
# CONFIG_GPIO_GENERIC_PLATFORM is not setCONFIG_GPIO_GRGPIO=yCONFIG_GPIO_HLWD=yCONFIG_GPIO_LOGICVC=yCONFIG_GPIO_MB86S7X=m
# CONFIG_GPIO_MENZ127 is not set
# CONFIG_GPIO_SIFIVE is not set
# CONFIG_GPIO_SIOX is not set
# CONFIG_GPIO_SYSCON is not setCONFIG_GPIO_VX855=m
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# Port-mapped I/O GPIO drivers
#CONFIG_GPIO_I8255=yCONFIG_GPIO_104_DIO_48E=y
# CONFIG_GPIO_104_IDIO_16 is not setCONFIG_GPIO_104_IDI_48=y
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_GPIO_MM is not setCONFIG_GPIO_IT87=m
# CONFIG_GPIO_SCH311X is not setCONFIG_GPIO_WINBOND=m
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers
#
# I2C GPIO expanders
#CONFIG_GPIO_ADNP=yCONFIG_GPIO_GW_PLD=m
# CONFIG_GPIO_MAX7300 is not setCONFIG_GPIO_MAX732X=yCONFIG_GPIO_MAX732X_IRQ=y
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not setCONFIG_GPIO_PCF857X=yCONFIG_GPIO_TPIC2810=y
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#CONFIG_GPIO_ADP5520=m
# CONFIG_GPIO_ARIZONA is not setCONFIG_GPIO_CS5535=y
# CONFIG_GPIO_DA9052 is not setCONFIG_GPIO_MADERA=y
# CONFIG_GPIO_PALMAS is not setCONFIG_GPIO_RC5T583=yCONFIG_GPIO_TPS65218=mCONFIG_GPIO_TPS65910=y
# CONFIG_GPIO_TPS65912 is not setCONFIG_GPIO_TQMX86=y
# CONFIG_GPIO_WM831X is not setCONFIG_GPIO_WM8350=m
# CONFIG_GPIO_WM8994 is not set
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not setCONFIG_GPIO_BT8XX=m
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCH is not setCONFIG_GPIO_PCI_IDIO_16=yCONFIG_GPIO_PCIE_IDIO_24=mCONFIG_GPIO_RDC321X=y
# CONFIG_GPIO_SODAVILLE is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not setCONFIG_GPIO_MAX3191X=yCONFIG_GPIO_MAX7301=m
# CONFIG_GPIO_MC33880 is not setCONFIG_GPIO_PISOSR=yCONFIG_GPIO_XRA1403=mCONFIG_GPIO_MOXTET=m
# end of SPI GPIO expanders
#
# Virtual GPIO drivers
#CONFIG_GPIO_AGGREGATOR=mCONFIG_GPIO_MOCKUP=y
# CONFIG_GPIO_VIRTIO is not set
# CONFIG_GPIO_SIM is not set
# end of Virtual GPIO drivers
CONFIG_W1=yCONFIG_W1_CON=y
#
# 1-wire Bus Masters
#CONFIG_W1_MASTER_MATROX=mCONFIG_W1_MASTER_DS2482=yCONFIG_W1_MASTER_DS1WM=mCONFIG_W1_MASTER_GPIO=m
# CONFIG_W1_MASTER_SGI is not set
# end of 1-wire Bus Masters
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=m
# CONFIG_W1_SLAVE_SMEM is not setCONFIG_W1_SLAVE_DS2405=yCONFIG_W1_SLAVE_DS2408=mCONFIG_W1_SLAVE_DS2408_READBACK=yCONFIG_W1_SLAVE_DS2413=m
# CONFIG_W1_SLAVE_DS2406 is not setCONFIG_W1_SLAVE_DS2423=mCONFIG_W1_SLAVE_DS2805=mCONFIG_W1_SLAVE_DS2430=yCONFIG_W1_SLAVE_DS2431=mCONFIG_W1_SLAVE_DS2433=yCONFIG_W1_SLAVE_DS2433_CRC=yCONFIG_W1_SLAVE_DS2438=yCONFIG_W1_SLAVE_DS250X=yCONFIG_W1_SLAVE_DS2780=yCONFIG_W1_SLAVE_DS2781=yCONFIG_W1_SLAVE_DS28E04=m
# CONFIG_W1_SLAVE_DS28E17 is not set
# end of 1-wire Slaves
# CONFIG_POWER_RESET is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_POWER_SUPPLY_HWMON is not setCONFIG_PDA_POWER=m
# CONFIG_IP5XXX_POWER is not set
# CONFIG_MAX8925_POWER is not setCONFIG_WM831X_BACKUP=y
# CONFIG_WM831X_POWER is not setCONFIG_WM8350_POWER=m
# CONFIG_TEST_POWER is not setCONFIG_CHARGER_ADP5061=mCONFIG_BATTERY_CW2015=yCONFIG_BATTERY_DS2760=mCONFIG_BATTERY_DS2780=mCONFIG_BATTERY_DS2781=m
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SAMSUNG_SDI is not setCONFIG_BATTERY_SBS=y
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not setCONFIG_BATTERY_DA9030=m
# CONFIG_BATTERY_DA9052 is not set
# CONFIG_BATTERY_DA9150 is not setCONFIG_BATTERY_MAX17040=m
# CONFIG_BATTERY_MAX17042 is not setCONFIG_BATTERY_MAX1721X=mCONFIG_CHARGER_PCF50633=mCONFIG_CHARGER_MAX8903=yCONFIG_CHARGER_LP8727=y
# CONFIG_CHARGER_GPIO is not setCONFIG_CHARGER_MANAGER=yCONFIG_CHARGER_LT3651=mCONFIG_CHARGER_LTC4162L=mCONFIG_CHARGER_MAX14577=m
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set
# CONFIG_CHARGER_MAX77693 is not set
# CONFIG_CHARGER_MAX77976 is not set
# CONFIG_CHARGER_BQ2415X is not setCONFIG_CHARGER_BQ24190=y
# CONFIG_CHARGER_BQ24257 is not setCONFIG_CHARGER_BQ24735=m
# CONFIG_CHARGER_BQ2515X is not setCONFIG_CHARGER_BQ25890=mCONFIG_CHARGER_BQ25980=mCONFIG_CHARGER_BQ256XX=m
# CONFIG_CHARGER_RK817 is not setCONFIG_CHARGER_SMB347=yCONFIG_CHARGER_TPS65217=m
# CONFIG_BATTERY_GAUGE_LTC2941 is not setCONFIG_BATTERY_GOLDFISH=yCONFIG_BATTERY_RT5033=mCONFIG_CHARGER_RT9455=mCONFIG_CHARGER_CROS_PCHG=mCONFIG_CHARGER_UCS1002=yCONFIG_CHARGER_BD99954=y
# CONFIG_BATTERY_UG3105 is not setCONFIG_HWMON=yCONFIG_HWMON_VID=y
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_ABITUGURU=m
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7314 is not setCONFIG_SENSORS_AD7414=mCONFIG_SENSORS_AD7418=y
# CONFIG_SENSORS_ADM1025 is not setCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=m
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM1177 is not setCONFIG_SENSORS_ADM9240=yCONFIG_SENSORS_ADT7X10=yCONFIG_SENSORS_ADT7310=mCONFIG_SENSORS_ADT7410=yCONFIG_SENSORS_ADT7411=yCONFIG_SENSORS_ADT7462=y
# CONFIG_SENSORS_ADT7470 is not setCONFIG_SENSORS_ADT7475=mCONFIG_SENSORS_AHT10=yCONFIG_SENSORS_AS370=mCONFIG_SENSORS_ASC7621=mCONFIG_SENSORS_AXI_FAN_CONTROL=yCONFIG_SENSORS_K8TEMP=m
# CONFIG_SENSORS_APPLESMC is not setCONFIG_SENSORS_ASB100=yCONFIG_SENSORS_ATXP1=y
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_CORSAIR_PSU is not setCONFIG_SENSORS_DRIVETEMP=mCONFIG_SENSORS_DS620=m
# CONFIG_SENSORS_DS1621 is not setCONFIG_SENSORS_DELL_SMM=m
# CONFIG_I8K is not setCONFIG_SENSORS_DA9052_ADC=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=yCONFIG_SENSORS_F71882FG=mCONFIG_SENSORS_F75375S=y
# CONFIG_SENSORS_GSC is not setCONFIG_SENSORS_MC13783_ADC=mCONFIG_SENSORS_FSCHMD=y
# CONFIG_SENSORS_GL518SM is not setCONFIG_SENSORS_GL520SM=m
# CONFIG_SENSORS_G760A is not setCONFIG_SENSORS_G762=yCONFIG_SENSORS_GPIO_FAN=mCONFIG_SENSORS_HIH6130=mCONFIG_SENSORS_IBMAEM=mCONFIG_SENSORS_IBMPEX=mCONFIG_SENSORS_I5500=mCONFIG_SENSORS_CORETEMP=mCONFIG_SENSORS_IT87=yCONFIG_SENSORS_JC42=mCONFIG_SENSORS_POWR1220=mCONFIG_SENSORS_LINEAGE=yCONFIG_SENSORS_LTC2945=mCONFIG_SENSORS_LTC2947=yCONFIG_SENSORS_LTC2947_I2C=yCONFIG_SENSORS_LTC2947_SPI=mCONFIG_SENSORS_LTC2990=mCONFIG_SENSORS_LTC2992=yCONFIG_SENSORS_LTC4151=yCONFIG_SENSORS_LTC4215=mCONFIG_SENSORS_LTC4222=yCONFIG_SENSORS_LTC4245=mCONFIG_SENSORS_LTC4260=yCONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not setCONFIG_SENSORS_MAX127=yCONFIG_SENSORS_MAX16065=mCONFIG_SENSORS_MAX1619=y
# CONFIG_SENSORS_MAX1668 is not setCONFIG_SENSORS_MAX197=yCONFIG_SENSORS_MAX31722=yCONFIG_SENSORS_MAX31730=y
# CONFIG_SENSORS_MAX31760 is not set
# CONFIG_SENSORS_MAX6620 is not set
# CONFIG_SENSORS_MAX6621 is not setCONFIG_SENSORS_MAX6639=y
# CONFIG_SENSORS_MAX6650 is not setCONFIG_SENSORS_MAX6697=yCONFIG_SENSORS_MAX31790=mCONFIG_SENSORS_MCP3021=yCONFIG_SENSORS_TC654=yCONFIG_SENSORS_TPS23861=y
# CONFIG_SENSORS_MENF21BMC_HWMON is not set
# CONFIG_SENSORS_MR75203 is not setCONFIG_SENSORS_ADCXX=mCONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not setCONFIG_SENSORS_LM73=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=m
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not setCONFIG_SENSORS_LM83=yCONFIG_SENSORS_LM85=yCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LM90=y
# CONFIG_SENSORS_LM92 is not setCONFIG_SENSORS_LM93=yCONFIG_SENSORS_LM95234=m
# CONFIG_SENSORS_LM95241 is not setCONFIG_SENSORS_LM95245=mCONFIG_SENSORS_PC87360=m
# CONFIG_SENSORS_PC87427 is not setCONFIG_SENSORS_NCT6683=m
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NCT6775_I2C is not setCONFIG_SENSORS_NCT7802=yCONFIG_SENSORS_NPCM7XX=m
# CONFIG_SENSORS_PCF8591 is not setCONFIG_PMBUS=y
# CONFIG_SENSORS_PMBUS is not setCONFIG_SENSORS_ADM1266=yCONFIG_SENSORS_ADM1275=mCONFIG_SENSORS_BEL_PFE=y
# CONFIG_SENSORS_BPA_RS600 is not set
# CONFIG_SENSORS_DELTA_AHE50DC_FAN is not setCONFIG_SENSORS_FSP_3Y=mCONFIG_SENSORS_IBM_CFFPS=yCONFIG_SENSORS_DPS920AB=m
# CONFIG_SENSORS_INSPUR_IPSPS is not setCONFIG_SENSORS_IR35221=y
# CONFIG_SENSORS_IR36021 is not setCONFIG_SENSORS_IR38064=y
# CONFIG_SENSORS_IR38064_REGULATOR is not setCONFIG_SENSORS_IRPS5401=yCONFIG_SENSORS_ISL68137=y
# CONFIG_SENSORS_LM25066 is not set
# CONFIG_SENSORS_LT7182S is not set
# CONFIG_SENSORS_LTC2978 is not setCONFIG_SENSORS_LTC3815=mCONFIG_SENSORS_MAX15301=y
# CONFIG_SENSORS_MAX16064 is not set
# CONFIG_SENSORS_MAX16601 is not setCONFIG_SENSORS_MAX20730=y
# CONFIG_SENSORS_MAX20751 is not setCONFIG_SENSORS_MAX31785=mCONFIG_SENSORS_MAX34440=mCONFIG_SENSORS_MAX8688=mCONFIG_SENSORS_MP2888=m
# CONFIG_SENSORS_MP2975 is not set
# CONFIG_SENSORS_MP5023 is not setCONFIG_SENSORS_PIM4328=m
# CONFIG_SENSORS_PLI1209BC is not set
# CONFIG_SENSORS_PM6764TR is not setCONFIG_SENSORS_PXE1610=mCONFIG_SENSORS_Q54SJ108A2=m
# CONFIG_SENSORS_STPDDC60 is not set
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not set
# CONFIG_SENSORS_TPS546D24 is not setCONFIG_SENSORS_UCD9000=m
# CONFIG_SENSORS_UCD9200 is not set
# CONFIG_SENSORS_XDPE152 is not setCONFIG_SENSORS_XDPE122=m
# CONFIG_SENSORS_XDPE122_REGULATOR is not setCONFIG_SENSORS_ZL6100=yCONFIG_SENSORS_PWM_FAN=y
# CONFIG_SENSORS_SBTSI is not setCONFIG_SENSORS_SBRMI=mCONFIG_SENSORS_SHT15=mCONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
CONFIG_SENSORS_SHT4x=m
# CONFIG_SENSORS_SHTC1 is not setCONFIG_SENSORS_SIS5595=yCONFIG_SENSORS_DME1737=mCONFIG_SENSORS_EMC1403=mCONFIG_SENSORS_EMC2103=y
# CONFIG_SENSORS_EMC2305 is not setCONFIG_SENSORS_EMC6W201=yCONFIG_SENSORS_SMSC47M1=yCONFIG_SENSORS_SMSC47M192=yCONFIG_SENSORS_SMSC47B397=y
# CONFIG_SENSORS_STTS751 is not setCONFIG_SENSORS_SMM665=mCONFIG_SENSORS_ADC128D818=y
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not setCONFIG_SENSORS_AMC6821=mCONFIG_SENSORS_INA209=yCONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA238 is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not setCONFIG_SENSORS_THMC50=yCONFIG_SENSORS_TMP102=mCONFIG_SENSORS_TMP103=mCONFIG_SENSORS_TMP108=yCONFIG_SENSORS_TMP401=y
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_TMP464 is not setCONFIG_SENSORS_TMP513=m
# CONFIG_SENSORS_VIA_CPUTEMP is not setCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=y
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83773G is not setCONFIG_SENSORS_W83781D=yCONFIG_SENSORS_W83791D=m
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not setCONFIG_SENSORS_W83L785TS=yCONFIG_SENSORS_W83L786NG=yCONFIG_SENSORS_W83627HF=yCONFIG_SENSORS_W83627EHF=yCONFIG_SENSORS_WM831X=m
# CONFIG_SENSORS_WM8350 is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_ASUS_WMI is not set
# CONFIG_SENSORS_ASUS_EC is not set CONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=yCONFIG_THERMAL_OF=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_GOV_FAIR_SHARE is not set CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_CPU_THERMAL is not set
# CONFIG_DEVFREQ_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_THERMAL_MMIO is not set
# CONFIG_DA9062_THERMAL is not set
#
# Intel thermal drivers
#
# CONFIG_INTEL_POWERCLAMP is not setCONFIG_X86_THERMAL_VECTOR=yCONFIG_X86_PKG_TEMP_THERMAL=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set
#
# ACPI INT340X thermal drivers
#
# end of ACPI INT340X thermal drivers
# CONFIG_INTEL_PCH_THERMAL is not set
# CONFIG_INTEL_TCC_COOLING is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_INTEL_HFI_THERMAL is not set
# end of Intel thermal drivers
# CONFIG_WATCHDOG is not setCONFIG_SSB_POSSIBLE=yCONFIG_SSB=mCONFIG_SSB_PCIHOST_POSSIBLE=y
# CONFIG_SSB_PCIHOST is not set
# CONFIG_SSB_DRIVER_GPIO is not setCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_PCI_POSSIBLE=y
# CONFIG_BCMA_HOST_PCI is not set
# CONFIG_BCMA_HOST_SOC is not setCONFIG_BCMA_DRIVER_PCI=y
# CONFIG_BCMA_DRIVER_GMAC_CMN is not set
# CONFIG_BCMA_DRIVER_GPIO is not set
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=yCONFIG_MFD_CS5535=y
# CONFIG_MFD_ACT8945A is not set
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not setCONFIG_PMIC_ADP5520=yCONFIG_MFD_AAT2870_CORE=yCONFIG_MFD_ATMEL_FLEXCOM=m
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not setCONFIG_MFD_CROS_EC_DEV=mCONFIG_MFD_MADERA=yCONFIG_MFD_MADERA_I2C=yCONFIG_MFD_MADERA_SPI=m
# CONFIG_MFD_CS47L15 is not setCONFIG_MFD_CS47L35=y
# CONFIG_MFD_CS47L85 is not set
# CONFIG_MFD_CS47L90 is not set
# CONFIG_MFD_CS47L92 is not setCONFIG_PMIC_DA903X=yCONFIG_PMIC_DA9052=y
# CONFIG_MFD_DA9052_SPI is not setCONFIG_MFD_DA9052_I2C=y
# CONFIG_MFD_DA9055 is not setCONFIG_MFD_DA9062=mCONFIG_MFD_DA9063=yCONFIG_MFD_DA9150=yCONFIG_MFD_GATEWORKS_GSC=mCONFIG_MFD_MC13XXX=mCONFIG_MFD_MC13XXX_SPI=m
# CONFIG_MFD_MC13XXX_I2C is not setCONFIG_MFD_MP2629=m
# CONFIG_MFD_HI6421_PMIC is not setCONFIG_MFD_HI6421_SPMI=mCONFIG_HTC_PASIC3=y
# CONFIG_HTC_I2CPLD is not setCONFIG_MFD_INTEL_QUARK_I2C_GPIO=y
# CONFIG_LPC_ICH is not set
# CONFIG_LPC_SCH is not set
# CONFIG_INTEL_SOC_PMIC_MRFLD is not setCONFIG_MFD_INTEL_LPSS=m
# CONFIG_MFD_INTEL_LPSS_ACPI is not setCONFIG_MFD_INTEL_LPSS_PCI=m
# CONFIG_MFD_INTEL_PMC_BXT is not setCONFIG_MFD_IQS62X=y
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not setCONFIG_MFD_88PM805=y
# CONFIG_MFD_88PM860X is not setCONFIG_MFD_MAX14577=m
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not set
# CONFIG_MFD_MAX77686 is not setCONFIG_MFD_MAX77693=m
# CONFIG_MFD_MAX77714 is not setCONFIG_MFD_MAX77843=yCONFIG_MFD_MAX8907=mCONFIG_MFD_MAX8925=yCONFIG_MFD_MAX8997=y
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6370 is not setCONFIG_MFD_MT6397=mCONFIG_MFD_MENF21BMC=m
# CONFIG_MFD_OCELOT is not set
# CONFIG_EZX_PCAP is not setCONFIG_MFD_CPCAP=yCONFIG_MFD_NTXEC=yCONFIG_MFD_RETU=mCONFIG_MFD_PCF50633=m
# CONFIG_PCF50633_ADC is not setCONFIG_PCF50633_GPIO=m
# CONFIG_MFD_SY7636A is not setCONFIG_MFD_RDC321X=yCONFIG_MFD_RT4831=mCONFIG_MFD_RT5033=m
# CONFIG_MFD_RT5120 is not setCONFIG_MFD_RC5T583=yCONFIG_MFD_RK808=yCONFIG_MFD_RN5T618=yCONFIG_MFD_SEC_CORE=yCONFIG_MFD_SI476X_CORE=yCONFIG_MFD_SM501=y
# CONFIG_MFD_SM501_GPIO is not setCONFIG_MFD_SKY81452=m
# CONFIG_MFD_STMPE is not setCONFIG_MFD_SYSCON=yCONFIG_MFD_TI_AM335X_TSCADC=y
# CONFIG_MFD_LP3943 is not setCONFIG_MFD_LP8788=y
# CONFIG_MFD_TI_LMU is not setCONFIG_MFD_PALMAS=y
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not setCONFIG_TPS6507X=y
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not setCONFIG_MFD_TPS65217=m
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not setCONFIG_MFD_TPS65218=m
# CONFIG_MFD_TPS6586X is not setCONFIG_MFD_TPS65910=yCONFIG_MFD_TPS65912=yCONFIG_MFD_TPS65912_I2C=mCONFIG_MFD_TPS65912_SPI=y
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not setCONFIG_MFD_WL1273_CORE=mCONFIG_MFD_LM3533=m
# CONFIG_MFD_TIMBERDALE is not set
# CONFIG_MFD_TC3589X is not setCONFIG_MFD_TQMX86=yCONFIG_MFD_VX855=m
# CONFIG_MFD_LOCHNAGAR is not setCONFIG_MFD_ARIZONA=yCONFIG_MFD_ARIZONA_I2C=mCONFIG_MFD_ARIZONA_SPI=y
# CONFIG_MFD_CS47L24 is not setCONFIG_MFD_WM5102=y
# CONFIG_MFD_WM5110 is not setCONFIG_MFD_WM8997=yCONFIG_MFD_WM8998=yCONFIG_MFD_WM8400=yCONFIG_MFD_WM831X=yCONFIG_MFD_WM831X_I2C=y
# CONFIG_MFD_WM831X_SPI is not setCONFIG_MFD_WM8350=yCONFIG_MFD_WM8350_I2C=yCONFIG_MFD_WM8994=mCONFIG_MFD_ROHM_BD718XX=m
# CONFIG_MFD_ROHM_BD71828 is not setCONFIG_MFD_ROHM_BD957XMUF=m
# CONFIG_MFD_STPMIC1 is not setCONFIG_MFD_STMFX=m
# CONFIG_MFD_ATC260X_I2C is not set
# CONFIG_MFD_QCOM_PM8008 is not set
# CONFIG_RAVE_SP_CORE is not set
# CONFIG_MFD_INTEL_M10_BMC is not set
# CONFIG_MFD_RSMU_I2C is not setCONFIG_MFD_RSMU_SPI=m
# end of Multifunction device drivers
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not setCONFIG_REGULATOR_FIXED_VOLTAGE=yCONFIG_REGULATOR_VIRTUAL_CONSUMER=y
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not setCONFIG_REGULATOR_88PG86X=yCONFIG_REGULATOR_ACT8865=yCONFIG_REGULATOR_AD5398=m
# CONFIG_REGULATOR_AAT2870 is not set
# CONFIG_REGULATOR_BD718XX is not set
# CONFIG_REGULATOR_BD957XMUF is not set
# CONFIG_REGULATOR_CPCAP is not set
# CONFIG_REGULATOR_CROS_EC is not set
# CONFIG_REGULATOR_DA9052 is not set
# CONFIG_REGULATOR_DA9062 is not setCONFIG_REGULATOR_DA9063=m
# CONFIG_REGULATOR_DA9121 is not setCONFIG_REGULATOR_DA9210=yCONFIG_REGULATOR_DA9211=mCONFIG_REGULATOR_FAN53555=mCONFIG_REGULATOR_FAN53880=yCONFIG_REGULATOR_GPIO=yCONFIG_REGULATOR_HI6421V600=mCONFIG_REGULATOR_ISL9305=yCONFIG_REGULATOR_ISL6271A=mCONFIG_REGULATOR_LP3971=y
# CONFIG_REGULATOR_LP3972 is not setCONFIG_REGULATOR_LP872X=yCONFIG_REGULATOR_LP8755=mCONFIG_REGULATOR_LP8788=m
# CONFIG_REGULATOR_LTC3589 is not setCONFIG_REGULATOR_LTC3676=yCONFIG_REGULATOR_MAX14577=mCONFIG_REGULATOR_MAX1586=y
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not setCONFIG_REGULATOR_MAX8893=yCONFIG_REGULATOR_MAX8907=m
# CONFIG_REGULATOR_MAX8925 is not setCONFIG_REGULATOR_MAX8952=y
# CONFIG_REGULATOR_MAX8973 is not set
# CONFIG_REGULATOR_MAX8997 is not set
# CONFIG_REGULATOR_MAX20086 is not setCONFIG_REGULATOR_MAX77693=yCONFIG_REGULATOR_MAX77826=mCONFIG_REGULATOR_MC13XXX_CORE=mCONFIG_REGULATOR_MC13783=m
# CONFIG_REGULATOR_MC13892 is not setCONFIG_REGULATOR_MCP16502=yCONFIG_REGULATOR_MP5416=yCONFIG_REGULATOR_MP8859=yCONFIG_REGULATOR_MP886X=y
# CONFIG_REGULATOR_MPQ7920 is not set
# CONFIG_REGULATOR_MT6311 is not setCONFIG_REGULATOR_MT6315=m
# CONFIG_REGULATOR_MT6323 is not set
# CONFIG_REGULATOR_MT6331 is not set
# CONFIG_REGULATOR_MT6332 is not set
# CONFIG_REGULATOR_MT6358 is not set
# CONFIG_REGULATOR_MT6359 is not set
# CONFIG_REGULATOR_MT6397 is not setCONFIG_REGULATOR_PALMAS=mCONFIG_REGULATOR_PCA9450=yCONFIG_REGULATOR_PCF50633=m
# CONFIG_REGULATOR_PF8X00 is not setCONFIG_REGULATOR_PFUZE100=y
# CONFIG_REGULATOR_PV88060 is not setCONFIG_REGULATOR_PV88080=mCONFIG_REGULATOR_PV88090=mCONFIG_REGULATOR_PWM=mCONFIG_REGULATOR_QCOM_SPMI=mCONFIG_REGULATOR_QCOM_USB_VBUS=mCONFIG_REGULATOR_RASPBERRYPI_TOUCHSCREEN_ATTINY=y
# CONFIG_REGULATOR_RC5T583 is not set
# CONFIG_REGULATOR_RK808 is not setCONFIG_REGULATOR_RN5T618=y
# CONFIG_REGULATOR_RT4801 is not set
# CONFIG_REGULATOR_RT4831 is not setCONFIG_REGULATOR_RT5033=m
# CONFIG_REGULATOR_RT5190A is not set
# CONFIG_REGULATOR_RT5759 is not setCONFIG_REGULATOR_RT6160=mCONFIG_REGULATOR_RT6245=yCONFIG_REGULATOR_RTQ2134=mCONFIG_REGULATOR_RTMV20=yCONFIG_REGULATOR_RTQ6752=yCONFIG_REGULATOR_S2MPA01=m
# CONFIG_REGULATOR_S2MPS11 is not setCONFIG_REGULATOR_S5M8767=yCONFIG_REGULATOR_SKY81452=m
# CONFIG_REGULATOR_SLG51000 is not setCONFIG_REGULATOR_SY8106A=mCONFIG_REGULATOR_SY8824X=y
# CONFIG_REGULATOR_SY8827N is not setCONFIG_REGULATOR_TPS51632=mCONFIG_REGULATOR_TPS62360=m
# CONFIG_REGULATOR_TPS6286X is not setCONFIG_REGULATOR_TPS65023=yCONFIG_REGULATOR_TPS6507X=mCONFIG_REGULATOR_TPS65132=y
# CONFIG_REGULATOR_TPS65217 is not setCONFIG_REGULATOR_TPS65218=mCONFIG_REGULATOR_TPS6524X=yCONFIG_REGULATOR_TPS65910=mCONFIG_REGULATOR_TPS65912=mCONFIG_REGULATOR_VCTRL=mCONFIG_REGULATOR_WM831X=mCONFIG_REGULATOR_WM8350=y
# CONFIG_REGULATOR_WM8400 is not setCONFIG_REGULATOR_WM8994=mCONFIG_REGULATOR_QCOM_LABIBB=m
# CONFIG_RC_CORE is not setCONFIG_CEC_CORE=yCONFIG_CEC_NOTIFIER=y
#
# CEC support
#CONFIG_MEDIA_CEC_SUPPORT=yCONFIG_CEC_CH7322=mCONFIG_CEC_CROS_EC=m
# CONFIG_CEC_SECO is not set
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set
# end of CEC support
CONFIG_MEDIA_SUPPORT=yCONFIG_MEDIA_SUPPORT_FILTER=yCONFIG_MEDIA_SUBDRV_AUTOSELECT=y
#
# Media device types
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=y
# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not setCONFIG_MEDIA_RADIO_SUPPORT=y
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_PLATFORM_SUPPORT is not set
# CONFIG_MEDIA_TEST_SUPPORT is not set
# end of Media device types
CONFIG_VIDEO_DEV=yCONFIG_MEDIA_CONTROLLER=y
#
# Video4Linux options
#CONFIG_VIDEO_V4L2_I2C=yCONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not setCONFIG_VIDEO_FIXED_MINOR_RANGES=yCONFIG_V4L2_FWNODE=yCONFIG_V4L2_ASYNC=y
# end of Video4Linux options
#
# Media controller options
#
# end of Media controller options
#
# Media drivers
#
#
# Drivers filtered as selected at 'Filter media drivers' #
#
# Media drivers
#
# CONFIG_MEDIA_PCI_SUPPORT is not setCONFIG_RADIO_ADAPTERS=yCONFIG_RADIO_MAXIRADIO=mCONFIG_RADIO_SAA7706H=m
# CONFIG_RADIO_SI4713 is not setCONFIG_RADIO_TEA575X=mCONFIG_RADIO_TEA5764=y
# CONFIG_RADIO_TEA5764_XTAL is not set
# CONFIG_RADIO_TEF6862 is not setCONFIG_RADIO_WL1273=mCONFIG_RADIO_SI470X=mCONFIG_I2C_SI470X=m
# CONFIG_V4L_RADIO_ISA_DRIVERS is not setCONFIG_VIDEOBUF2_CORE=yCONFIG_VIDEOBUF2_V4L2=yCONFIG_VIDEOBUF2_MEMOPS=yCONFIG_VIDEOBUF2_VMALLOC=y
# end of Media drivers
#
# Media ancillary drivers
#CONFIG_MEDIA_ATTACH=y
#
# Camera sensor devices
#
# CONFIG_VIDEO_AR0521 is not setCONFIG_VIDEO_HI556=yCONFIG_VIDEO_HI846=y
# CONFIG_VIDEO_HI847 is not setCONFIG_VIDEO_IMX208=y
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not setCONFIG_VIDEO_IMX258=yCONFIG_VIDEO_IMX274=m
# CONFIG_VIDEO_IMX290 is not setCONFIG_VIDEO_IMX319=yCONFIG_VIDEO_IMX334=mCONFIG_VIDEO_IMX335=yCONFIG_VIDEO_IMX355=mCONFIG_VIDEO_IMX412=yCONFIG_VIDEO_MAX9271_LIB=mCONFIG_VIDEO_MT9M001=y
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not setCONFIG_VIDEO_MT9T001=mCONFIG_VIDEO_MT9T112=m
# CONFIG_VIDEO_MT9V011 is not setCONFIG_VIDEO_MT9V032=m
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_OG01A1B is not setCONFIG_VIDEO_OV02A10=m
# CONFIG_VIDEO_OV08D10 is not set
# CONFIG_VIDEO_OV13858 is not setCONFIG_VIDEO_OV13B10=y
# CONFIG_VIDEO_OV2640 is not setCONFIG_VIDEO_OV2659=mCONFIG_VIDEO_OV2680=y
# CONFIG_VIDEO_OV2685 is not setCONFIG_VIDEO_OV2740=mCONFIG_VIDEO_OV5640=mCONFIG_VIDEO_OV5645=yCONFIG_VIDEO_OV5647=m
# CONFIG_VIDEO_OV5648 is not setCONFIG_VIDEO_OV5670=yCONFIG_VIDEO_OV5675=y
# CONFIG_VIDEO_OV5693 is not set
# CONFIG_VIDEO_OV5695 is not setCONFIG_VIDEO_OV6650=mCONFIG_VIDEO_OV7251=yCONFIG_VIDEO_OV7640=m
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV772X is not setCONFIG_VIDEO_OV7740=mCONFIG_VIDEO_OV8856=m
# CONFIG_VIDEO_OV8865 is not set
# CONFIG_VIDEO_OV9282 is not setCONFIG_VIDEO_OV9640=m
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV9734 is not setCONFIG_VIDEO_RDACM20=m
# CONFIG_VIDEO_RDACM21 is not set
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5C73M3 is not setCONFIG_VIDEO_S5K4ECGX=m
# CONFIG_VIDEO_S5K5BAF is not setCONFIG_VIDEO_S5K6A3=mCONFIG_VIDEO_S5K6AA=y
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_CCS is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_M5MOLS is not set
# end of Camera sensor devices
#
# Lens drivers
#CONFIG_VIDEO_AD5820=m
# CONFIG_VIDEO_AK7375 is not setCONFIG_VIDEO_DW9714=y
# CONFIG_VIDEO_DW9768 is not setCONFIG_VIDEO_DW9807_VCM=y
# end of Lens drivers
#
# Flash devices
#CONFIG_VIDEO_ADP1653=yCONFIG_VIDEO_LM3560=y
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices
#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_CS3308 is not setCONFIG_VIDEO_CS5345=m
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_MSP3400 is not setCONFIG_VIDEO_SONY_BTF_MPX=yCONFIG_VIDEO_TDA7432=m
# CONFIG_VIDEO_TDA9840 is not setCONFIG_VIDEO_TEA6415C=mCONFIG_VIDEO_TEA6420=mCONFIG_VIDEO_TLV320AIC23B=y
# CONFIG_VIDEO_TVAUDIO is not setCONFIG_VIDEO_UDA1342=yCONFIG_VIDEO_VP27SMPX=mCONFIG_VIDEO_WM8739=yCONFIG_VIDEO_WM8775=m
# end of Audio decoders, processors and mixers
#
# RDS decoders
#CONFIG_VIDEO_SAA6588=m
# end of RDS decoders
#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not setCONFIG_VIDEO_ADV7183=yCONFIG_VIDEO_ADV748X=yCONFIG_VIDEO_ADV7604=mCONFIG_VIDEO_ADV7604_CEC=yCONFIG_VIDEO_ADV7842=m
# CONFIG_VIDEO_ADV7842_CEC is not set
# CONFIG_VIDEO_BT819 is not setCONFIG_VIDEO_BT856=yCONFIG_VIDEO_BT866=m
# CONFIG_VIDEO_ISL7998X is not setCONFIG_VIDEO_KS0127=yCONFIG_VIDEO_MAX9286=yCONFIG_VIDEO_ML86V7667=y
# CONFIG_VIDEO_SAA7110 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not setCONFIG_VIDEO_TVP7002=m
# CONFIG_VIDEO_TW2804 is not setCONFIG_VIDEO_TW9903=mCONFIG_VIDEO_TW9906=y
# CONFIG_VIDEO_TW9910 is not setCONFIG_VIDEO_VPX3220=m
#
# Video and audio decoders
#CONFIG_VIDEO_SAA717X=y
# CONFIG_VIDEO_CX25840 is not set
# end of Video decoders
#
# Video encoders
#CONFIG_VIDEO_AD9389B=yCONFIG_VIDEO_ADV7170=m
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not setCONFIG_VIDEO_ADV7393=m
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not setCONFIG_VIDEO_THS8200=y
# end of Video encoders
#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not setCONFIG_VIDEO_UPD64083=m
# end of Video improvement chips
#
# Audio/Video compression chips
#CONFIG_VIDEO_SAA6752HS=m
# end of Audio/Video compression chips
#
# SDR tuner chips
#
# end of SDR tuner chips
#
# Miscellaneous helper chips
#CONFIG_VIDEO_I2C=yCONFIG_VIDEO_M52790=yCONFIG_VIDEO_ST_MIPID02=mCONFIG_VIDEO_THS7303=m
# end of Miscellaneous helper chips
#
# Media SPI Adapters
#
# CONFIG_VIDEO_GS1662 is not set
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=y
#
# Customize TV tuners
#
# CONFIG_MEDIA_TUNER_E4000 is not setCONFIG_MEDIA_TUNER_FC0011=y
# CONFIG_MEDIA_TUNER_FC0012 is not setCONFIG_MEDIA_TUNER_FC0013=yCONFIG_MEDIA_TUNER_FC2580=m
# CONFIG_MEDIA_TUNER_IT913X is not set
# CONFIG_MEDIA_TUNER_M88RS6000T is not setCONFIG_MEDIA_TUNER_MAX2165=yCONFIG_MEDIA_TUNER_MC44S803=y
# CONFIG_MEDIA_TUNER_MSI001 is not setCONFIG_MEDIA_TUNER_MT2060=m
# CONFIG_MEDIA_TUNER_MT2063 is not setCONFIG_MEDIA_TUNER_MT20XX=yCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MXL301RF=y
# CONFIG_MEDIA_TUNER_MXL5005S is not set
# CONFIG_MEDIA_TUNER_MXL5007T is not setCONFIG_MEDIA_TUNER_QM1D1B0004=m
# CONFIG_MEDIA_TUNER_QM1D1C0042 is not set
# CONFIG_MEDIA_TUNER_QT1010 is not setCONFIG_MEDIA_TUNER_R820T=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_SIMPLE=yCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_TDA18218=m
# CONFIG_MEDIA_TUNER_TDA18250 is not setCONFIG_MEDIA_TUNER_TDA18271=yCONFIG_MEDIA_TUNER_TDA827X=yCONFIG_MEDIA_TUNER_TDA8290=yCONFIG_MEDIA_TUNER_TDA9887=yCONFIG_MEDIA_TUNER_TEA5761=yCONFIG_MEDIA_TUNER_TEA5767=y
# CONFIG_MEDIA_TUNER_TUA9001 is not setCONFIG_MEDIA_TUNER_XC2028=yCONFIG_MEDIA_TUNER_XC4000=yCONFIG_MEDIA_TUNER_XC5000=y
# end of Customize TV tuners # end of Media ancillary drivers
#
# Graphics support
#CONFIG_APERTURE_HELPERS=yCONFIG_AGP=yCONFIG_AGP_ALI=y
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_INTEL is not set CONFIG_AGP_NVIDIA=mCONFIG_AGP_SIS=mCONFIG_AGP_SWORKS=mCONFIG_AGP_VIA=mCONFIG_AGP_EFFICEON=mCONFIG_INTEL_GTT=y
# CONFIG_VGA_SWITCHEROO is not set CONFIG_DRM=yCONFIG_DRM_MIPI_DBI=y CONFIG_DRM_MIPI_DSI=y
# CONFIG_DRM_DEBUG_MM is not set CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set # CONFIG_DRM_DEBUG_MODESET_LOCK is not set CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set CONFIG_DRM_DP_AUX_BUS=y CONFIG_DRM_DISPLAY_HELPER=y CONFIG_DRM_DISPLAY_DP_HELPER=y CONFIG_DRM_DISPLAY_HDCP_HELPER=y CONFIG_DRM_DISPLAY_HDMI_HELPER=y CONFIG_DRM_DP_AUX_CHARDEV=y CONFIG_DRM_DP_CEC=yCONFIG_DRM_TTM=yCONFIG_DRM_BUDDY=y CONFIG_DRM_VRAM_HELPER=y CONFIG_DRM_TTM_HELPER=y CONFIG_DRM_GEM_DMA_HELPER=y CONFIG_DRM_GEM_SHMEM_HELPER=y CONFIG_DRM_SCHED=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=yCONFIG_DRM_I2C_SIL164=yCONFIG_DRM_I2C_NXP_TDA998X=y
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#CONFIG_DRM_KOMEDA=m
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
# CONFIG_DRM_NOUVEAU is not setCONFIG_DRM_I915=yCONFIG_DRM_I915_FORCE_PROBE=""
# CONFIG_DRM_I915_CAPTURE_ERROR is not set
# CONFIG_DRM_I915_USERPTR is not set
#
# drm/i915 Debugging # # CONFIG_DRM_I915_WERROR is not set # CONFIG_DRM_I915_DEBUG is not set CONFIG_DRM_I915_DEBUG_MMIO=y CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS=y CONFIG_DRM_I915_SW_FENCE_CHECK_DAG=y # 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=y CONFIG_DRM_I915_DEBUG_RUNTIME_PM=y # end of drm/i915 Debugging
#
# drm/i915 Profile Guided Optimisation # CONFIG_DRM_I915_REQUEST_TIMEOUT=20000 CONFIG_DRM_I915_FENCE_TIMEOUT=10000 CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250 CONFIG_DRM_I915_HEARTBEAT_INTERVAL=2500 CONFIG_DRM_I915_PREEMPT_TIMEOUT=640 CONFIG_DRM_I915_MAX_REQUEST_BUSYWAIT=8000 CONFIG_DRM_I915_STOP_TIMEOUT=100 CONFIG_DRM_I915_TIMESLICE_DURATION=1 # end of drm/i915 Profile Guided Optimisation
CONFIG_DRM_VGEM=mCONFIG_DRM_VKMS=yCONFIG_DRM_VMWGFX=mCONFIG_DRM_VMWGFX_FBCON=y
# CONFIG_DRM_VMWGFX_MKSSTATS is not setCONFIG_DRM_GMA500=mCONFIG_DRM_AST=yCONFIG_DRM_MGAG200=mCONFIG_DRM_RCAR_DW_HDMI=m
# CONFIG_DRM_RCAR_USE_LVDS is not set
# CONFIG_DRM_RCAR_MIPI_DSI is not setCONFIG_DRM_QXL=mCONFIG_DRM_PANEL=y
#
# Display Panels
#CONFIG_DRM_PANEL_ABT_Y030XX067A=m CONFIG_DRM_PANEL_ARM_VERSATILE=y
# CONFIG_DRM_PANEL_ASUS_Z00T_TM5P5_NT35596 is not set # CONFIG_DRM_PANEL_BOE_BF060Y8M_AJ0 is not set CONFIG_DRM_PANEL_BOE_HIMAX8279D=m CONFIG_DRM_PANEL_BOE_TV101WUM_NL6=y CONFIG_DRM_PANEL_DSI_CM=y CONFIG_DRM_PANEL_LVDS=m CONFIG_DRM_PANEL_SIMPLE=y
# CONFIG_DRM_PANEL_EDP is not set
# CONFIG_DRM_PANEL_EBBG_FT8719 is not set CONFIG_DRM_PANEL_ELIDA_KD35T133=m
# CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D=m
# CONFIG_DRM_PANEL_ILITEK_IL9322 is not set CONFIG_DRM_PANEL_ILITEK_ILI9341=y CONFIG_DRM_PANEL_ILITEK_ILI9881C=m CONFIG_DRM_PANEL_INNOLUX_EJ030NA=m CONFIG_DRM_PANEL_INNOLUX_P079ZCA=y CONFIG_DRM_PANEL_JDI_LT070ME05000=y
# CONFIG_DRM_PANEL_JDI_R63452 is not set CONFIG_DRM_PANEL_KHADAS_TS050=y CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04=y CONFIG_DRM_PANEL_LEADTEK_LTK050H3146W=m CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829=y CONFIG_DRM_PANEL_SAMSUNG_LD9040=m CONFIG_DRM_PANEL_LG_LB035Q02=y CONFIG_DRM_PANEL_LG_LG4573=y CONFIG_DRM_PANEL_NEC_NL8048HL11=m
# CONFIG_DRM_PANEL_NEWVISION_NV3052C is not set CONFIG_DRM_PANEL_NOVATEK_NT35510=m
# CONFIG_DRM_PANEL_NOVATEK_NT35560 is not set # CONFIG_DRM_PANEL_NOVATEK_NT35950 is not set CONFIG_DRM_PANEL_NOVATEK_NT36672A=y
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set CONFIG_DRM_PANEL_MANTIX_MLAF057WE51=m
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set CONFIG_DRM_PANEL_ORISETECH_OTM8009A=y CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS=m CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00=y CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN=y CONFIG_DRM_PANEL_RAYDIUM_RM67191=y
# CONFIG_DRM_PANEL_RAYDIUM_RM68200 is not set # CONFIG_DRM_PANEL_RONBO_RB070D30 is not set CONFIG_DRM_PANEL_SAMSUNG_ATNA33XC20=y CONFIG_DRM_PANEL_SAMSUNG_DB7430=m CONFIG_DRM_PANEL_SAMSUNG_S6D16D0=y
# CONFIG_DRM_PANEL_SAMSUNG_S6D27A1 is not set # CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2 is not set CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03=y CONFIG_DRM_PANEL_SAMSUNG_S6E63M0=y
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0_SPI is not set CONFIG_DRM_PANEL_SAMSUNG_S6E63M0_DSI=m CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01=y CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0=m CONFIG_DRM_PANEL_SAMSUNG_SOFEF00=y CONFIG_DRM_PANEL_SEIKO_43WVF1G=y CONFIG_DRM_PANEL_SHARP_LQ101R1SX01=m
# CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set CONFIG_DRM_PANEL_SHARP_LS043T1LE01=m CONFIG_DRM_PANEL_SHARP_LS060T1SX01=y
# CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set # CONFIG_DRM_PANEL_SITRONIX_ST7703 is not set CONFIG_DRM_PANEL_SITRONIX_ST7789V=m CONFIG_DRM_PANEL_SONY_ACX565AKM=y
# CONFIG_DRM_PANEL_SONY_TULIP_TRULY_NT35521 is not set CONFIG_DRM_PANEL_TDO_TL070WSH30=y
# CONFIG_DRM_PANEL_TPO_TD028TTEC1 is not set CONFIG_DRM_PANEL_TPO_TD043MTEA1=y CONFIG_DRM_PANEL_TPO_TPG110=y CONFIG_DRM_PANEL_TRULY_NT35597_WQXGA=y CONFIG_DRM_PANEL_VISIONOX_RM69299=y CONFIG_DRM_PANEL_WIDECHIPS_WS2401=m
# CONFIG_DRM_PANEL_XINPENG_XPP055C272 is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_CDNS_DSI is not set CONFIG_DRM_CHIPONE_ICN6211=m CONFIG_DRM_CHRONTEL_CH7033=y CONFIG_DRM_CROS_EC_ANX7688=m CONFIG_DRM_DISPLAY_CONNECTOR=y
# CONFIG_DRM_ITE_IT6505 is not set
# CONFIG_DRM_LONTIUM_LT8912B is not set
# CONFIG_DRM_LONTIUM_LT9211 is not set CONFIG_DRM_LONTIUM_LT9611=m CONFIG_DRM_LONTIUM_LT9611UXC=m CONFIG_DRM_ITE_IT66121=m CONFIG_DRM_LVDS_CODEC=y
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set CONFIG_DRM_NWL_MIPI_DSI=y CONFIG_DRM_NXP_PTN3460=m CONFIG_DRM_PARADE_PS8622=m CONFIG_DRM_PARADE_PS8640=y CONFIG_DRM_SIL_SII8620=yCONFIG_DRM_SII902X=mCONFIG_DRM_SII9234=y
# CONFIG_DRM_SIMPLE_BRIDGE is not set
# CONFIG_DRM_THINE_THC63LVD1024 is not set
# CONFIG_DRM_TOSHIBA_TC358762 is not set CONFIG_DRM_TOSHIBA_TC358764=m CONFIG_DRM_TOSHIBA_TC358767=m
# CONFIG_DRM_TOSHIBA_TC358768 is not set
# CONFIG_DRM_TOSHIBA_TC358775 is not set
# CONFIG_DRM_TI_DLPC3433 is not set
# CONFIG_DRM_TI_TFP410 is not set CONFIG_DRM_TI_SN65DSI83=m CONFIG_DRM_TI_SN65DSI86=y
# CONFIG_DRM_TI_TPD12S015 is not set
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# CONFIG_DRM_ANALOGIX_ANX7625 is not set CONFIG_DRM_I2C_ADV7511=m CONFIG_DRM_I2C_ADV7511_CEC=y CONFIG_DRM_CDNS_MHDP8546=m CONFIG_DRM_DW_HDMI=m
# CONFIG_DRM_DW_HDMI_CEC is not set
# end of Display Interface Bridges
CONFIG_DRM_ETNAVIV=y
# CONFIG_DRM_ETNAVIV_THERMAL is not set
# CONFIG_DRM_LOGICVC is not set
# CONFIG_DRM_MXSFB is not set
# CONFIG_DRM_IMX_LCDIF is not setCONFIG_DRM_ARCPGU=yCONFIG_DRM_BOCHS=mCONFIG_DRM_CIRRUS_QEMU=m
# CONFIG_DRM_PANEL_MIPI_DBI is not set
# CONFIG_DRM_SIMPLEDRM is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9163 is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not setCONFIG_TINYDRM_ILI9486=yCONFIG_TINYDRM_MI0283QT=m
# CONFIG_TINYDRM_REPAPER is not setCONFIG_TINYDRM_ST7586=mCONFIG_TINYDRM_ST7735R=yCONFIG_DRM_VBOXVIDEO=y
# CONFIG_DRM_SSD130X is not setCONFIG_DRM_LEGACY=yCONFIG_DRM_TDFX=yCONFIG_DRM_R128=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not setCONFIG_DRM_SAVAGE=mCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=yCONFIG_DRM_NOMODESET=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=yCONFIG_FIRMWARE_EDID=yCONFIG_FB_DDC=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=yCONFIG_FB_SYS_COPYAREA=yCONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=yCONFIG_FB_DEFERRED_IO=yCONFIG_FB_SVGALIB=yCONFIG_FB_BACKLIGHT=yCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not setCONFIG_FB_CYBER2000=yCONFIG_FB_CYBER2000_DDC=y
# CONFIG_FB_ARC is not setCONFIG_FB_ASILIANT=y
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not setCONFIG_FB_VESA=y
# CONFIG_FB_N411 is not setCONFIG_FB_HGA=yCONFIG_FB_OPENCORES=y
# CONFIG_FB_S1D13XXX is not setCONFIG_FB_NVIDIA=m
# CONFIG_FB_NVIDIA_I2C is not set
# CONFIG_FB_NVIDIA_DEBUG is not setCONFIG_FB_NVIDIA_BACKLIGHT=y
# CONFIG_FB_RIVA is not setCONFIG_FB_I740=m
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not setCONFIG_FB_ATY128=mCONFIG_FB_ATY128_BACKLIGHT=yCONFIG_FB_ATY=yCONFIG_FB_ATY_CT=y
# CONFIG_FB_ATY_GENERIC_LCD is not set
# CONFIG_FB_ATY_GX is not setCONFIG_FB_ATY_BACKLIGHT=yCONFIG_FB_S3=yCONFIG_FB_S3_DDC=yCONFIG_FB_SAVAGE=mCONFIG_FB_SAVAGE_I2C=yCONFIG_FB_SAVAGE_ACCEL=yCONFIG_FB_SIS=m
# CONFIG_FB_SIS_300 is not setCONFIG_FB_SIS_315=y
# CONFIG_FB_VIA is not setCONFIG_FB_NEOMAGIC=y
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not setCONFIG_FB_VOODOO1=yCONFIG_FB_VT8623=yCONFIG_FB_TRIDENT=y
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not setCONFIG_FB_CARMINE=mCONFIG_FB_CARMINE_DRAM_EVAL=y
# CONFIG_CARMINE_DRAM_CUSTOM is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_SM501 is not setCONFIG_FB_IBM_GXT4500=mCONFIG_FB_GOLDFISH=y
# CONFIG_FB_VIRTUAL is not setCONFIG_FB_METRONOME=y
# CONFIG_FB_MB862XX is not setCONFIG_FB_SIMPLE=y
# CONFIG_FB_SSD1307 is not setCONFIG_FB_SM712=y
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=y
# CONFIG_LCD_L4F00242T03 is not setCONFIG_LCD_LMS283GF05=yCONFIG_LCD_LTV350QV=yCONFIG_LCD_ILI922X=yCONFIG_LCD_ILI9320=yCONFIG_LCD_TDO24M=m
# CONFIG_LCD_VGG2432A4 is not setCONFIG_LCD_PLATFORM=mCONFIG_LCD_AMS369FG06=mCONFIG_LCD_LMS501KF03=yCONFIG_LCD_HX8357=mCONFIG_LCD_OTM3225A=yCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_LM3533 is not setCONFIG_BACKLIGHT_PWM=y
# CONFIG_BACKLIGHT_DA903X is not setCONFIG_BACKLIGHT_DA9052=yCONFIG_BACKLIGHT_MAX8925=m
# CONFIG_BACKLIGHT_APPLE is not setCONFIG_BACKLIGHT_QCOM_WLED=mCONFIG_BACKLIGHT_RT4831=mCONFIG_BACKLIGHT_SAHARA=y
# CONFIG_BACKLIGHT_WM831X is not set
# CONFIG_BACKLIGHT_ADP5520 is not setCONFIG_BACKLIGHT_ADP8860=y
# CONFIG_BACKLIGHT_ADP8870 is not setCONFIG_BACKLIGHT_PCF50633=mCONFIG_BACKLIGHT_AAT2870=yCONFIG_BACKLIGHT_LM3630A=mCONFIG_BACKLIGHT_LM3639=y
# CONFIG_BACKLIGHT_LP855X is not setCONFIG_BACKLIGHT_LP8788=y
# CONFIG_BACKLIGHT_SKY81452 is not setCONFIG_BACKLIGHT_TPS65217=mCONFIG_BACKLIGHT_GPIO=mCONFIG_BACKLIGHT_LV5207LP=mCONFIG_BACKLIGHT_BD6107=y
# CONFIG_BACKLIGHT_ARCXCNN is not setCONFIG_BACKLIGHT_LED=y
# end of Backlight & LCD device support
CONFIG_VGASTATE=yCONFIG_VIDEOMODE_HELPERS=yCONFIG_HDMI=yCONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not set
# end of Graphics support
CONFIG_SOUND=y
# CONFIG_SND is not set
#
# HID support
#CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not setCONFIG_HID_GENERIC=y
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_VRC2 is not set
# CONFIG_HID_XIAOMI is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_ITE is not set
# CONFIG_HID_JABRA is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LED is not set
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_REDRAGON is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NINTENDO is not set
# CONFIG_HID_NTI is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PLAYSTATION is not set
# CONFIG_HID_PXRC is not set
# CONFIG_HID_RAZER is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SEMITEK is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_TOPRE is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
# CONFIG_HID_ALPS is not set
# end of Special HID drivers
#
# I2C HID support
#
# CONFIG_I2C_HID_ACPI is not set
# CONFIG_I2C_HID_OF is not set
# CONFIG_I2C_HID_OF_ELAN is not set
# CONFIG_I2C_HID_OF_GOODIX is not set
# end of I2C HID support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=y
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not setCONFIG_USB_ARCH_HAS_HCD=y
# CONFIG_USB is not setCONFIG_USB_PCI=y
#
# USB port drivers
#
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_TAHVO_USB is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not set
# CONFIG_TYPEC is not set
# CONFIG_USB_ROLE_SWITCH is not set
# CONFIG_MMC is not setCONFIG_SCSI_UFSHCD=m
# CONFIG_SCSI_UFS_BSG is not set
# CONFIG_SCSI_UFS_CRYPTO is not set
# CONFIG_SCSI_UFS_HPB is not set
# CONFIG_SCSI_UFS_FAULT_INJECTION is not set
# CONFIG_SCSI_UFS_HWMON is not setCONFIG_SCSI_UFSHCD_PCI=mCONFIG_SCSI_UFS_DWC_TC_PCI=mCONFIG_SCSI_UFSHCD_PLATFORM=mCONFIG_SCSI_UFS_CDNS_PLATFORM=mCONFIG_SCSI_UFS_DWC_TC_PLATFORM=mCONFIG_MEMSTICK=mCONFIG_MEMSTICK_DEBUG=y
#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not setCONFIG_MSPRO_BLOCK=mCONFIG_MS_BLOCK=m
#
# MemoryStick Host Controller Drivers
#CONFIG_MEMSTICK_TIFM_MS=m
# CONFIG_MEMSTICK_JMICRON_38X is not setCONFIG_MEMSTICK_R592=m
# CONFIG_MEMSTICK_REALTEK_PCI is not setCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not setCONFIG_LEDS_CLASS_MULTICOLOR=yCONFIG_LEDS_BRIGHTNESS_HW_CHANGED=y
#
# LED drivers
#
# CONFIG_LEDS_AN30259A is not setCONFIG_LEDS_APU=yCONFIG_LEDS_AW2013=yCONFIG_LEDS_BCM6328=m
# CONFIG_LEDS_BCM6358 is not setCONFIG_LEDS_CPCAP=y
# CONFIG_LEDS_CR0014114 is not setCONFIG_LEDS_EL15203000=mCONFIG_LEDS_LM3530=yCONFIG_LEDS_LM3532=mCONFIG_LEDS_LM3533=m
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_LM3692X is not set
# CONFIG_LEDS_MT6323 is not setCONFIG_LEDS_NET48XX=mCONFIG_LEDS_WRAP=m
# CONFIG_LEDS_PCA9532 is not setCONFIG_LEDS_GPIO=yCONFIG_LEDS_LP3944=yCONFIG_LEDS_LP3952=mCONFIG_LEDS_LP50XX=yCONFIG_LEDS_LP55XX_COMMON=mCONFIG_LEDS_LP5521=mCONFIG_LEDS_LP5523=mCONFIG_LEDS_LP5562=m
# CONFIG_LEDS_LP8501 is not setCONFIG_LEDS_LP8788=yCONFIG_LEDS_LP8860=yCONFIG_LEDS_PCA955X=mCONFIG_LEDS_PCA955X_GPIO=yCONFIG_LEDS_PCA963X=yCONFIG_LEDS_WM831X_STATUS=yCONFIG_LEDS_WM8350=mCONFIG_LEDS_DA903X=mCONFIG_LEDS_DA9052=y
# CONFIG_LEDS_DAC124S085 is not setCONFIG_LEDS_PWM=yCONFIG_LEDS_REGULATOR=y
# CONFIG_LEDS_BD2802 is not setCONFIG_LEDS_INTEL_SS4200=yCONFIG_LEDS_LT3593=yCONFIG_LEDS_ADP5520=m
# CONFIG_LEDS_MC13783 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_MAX8997 is not set
CONFIG_LEDS_LM355x=y
# CONFIG_LEDS_OT200 is not setCONFIG_LEDS_MENF21BMC=m
# CONFIG_LEDS_IS31FL319X is not set
# CONFIG_LEDS_IS31FL32XX is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=m
# CONFIG_LEDS_SYSCON is not setCONFIG_LEDS_MLXCPLD=yCONFIG_LEDS_MLXREG=m
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_SPI_BYTE is not setCONFIG_LEDS_TI_LMU_COMMON=yCONFIG_LEDS_LM3697=yCONFIG_LEDS_LGM=m
#
# Flash and Torch LED drivers
#
#
# RGB LED drivers
#
# CONFIG_LEDS_PWM_MULTICOLOR is not set
# CONFIG_LEDS_QCOM_LPG is not set
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not setCONFIG_LEDS_TRIGGER_ONESHOT=yCONFIG_LEDS_TRIGGER_DISK=yCONFIG_LEDS_TRIGGER_HEARTBEAT=mCONFIG_LEDS_TRIGGER_BACKLIGHT=m
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
#
# iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m # CONFIG_LEDS_TRIGGER_CAMERA is not set # CONFIG_LEDS_TRIGGER_PANIC is not set CONFIG_LEDS_TRIGGER_NETDEV=y CONFIG_LEDS_TRIGGER_PATTERN=m CONFIG_LEDS_TRIGGER_AUDIO=y # CONFIG_LEDS_TRIGGER_TTY is not set
#
# Simple LED drivers
#CONFIG_ACCESSIBILITY=y
#
# Speakup console speech
#
# end of Speakup console speech
CONFIG_INFINIBAND=mCONFIG_INFINIBAND_USER_MAD=m
# CONFIG_INFINIBAND_USER_ACCESS is not setCONFIG_INFINIBAND_ADDR_TRANS=yCONFIG_INFINIBAND_ADDR_TRANS_CONFIGFS=yCONFIG_INFINIBAND_IRDMA=mCONFIG_MLX4_INFINIBAND=m
# CONFIG_INFINIBAND_MTHCA is not setCONFIG_INFINIBAND_OCRDMA=mCONFIG_INFINIBAND_VMWARE_PVRDMA=m
# CONFIG_INFINIBAND_IPOIB is not set
# CONFIG_INFINIBAND_SRP is not set
# CONFIG_INFINIBAND_ISER is not setCONFIG_INFINIBAND_RTRS=mCONFIG_INFINIBAND_RTRS_CLIENT=mCONFIG_INFINIBAND_RTRS_SERVER=mCONFIG_EDAC_ATOMIC_SCRUB=yCONFIG_EDAC_SUPPORT=yCONFIG_EDAC=y
# CONFIG_EDAC_LEGACY_SYSFS is not set
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_AMD76X is not setCONFIG_EDAC_E7XXX=yCONFIG_EDAC_E752X=mCONFIG_EDAC_I82875P=yCONFIG_EDAC_I82975X=yCONFIG_EDAC_I3000=m
# CONFIG_EDAC_I3200 is not setCONFIG_EDAC_IE31200=mCONFIG_EDAC_X38=m
# CONFIG_EDAC_I5400 is not setCONFIG_EDAC_I82860=y
# CONFIG_EDAC_R82600 is not setCONFIG_EDAC_I5000=mCONFIG_EDAC_I5100=yCONFIG_EDAC_I7300=mCONFIG_RTC_LIB=yCONFIG_RTC_MC146818_LIB=yCONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not setCONFIG_RTC_SYSTOHC=yCONFIG_RTC_SYSTOHC_DEVICE="rtc0"CONFIG_RTC_DEBUG=y
# CONFIG_RTC_NVMEM is not set
#
# RTC interfaces
#
# CONFIG_RTC_INTF_SYSFS is not set
# CONFIG_RTC_INTF_PROC is not setCONFIG_RTC_INTF_DEV=yCONFIG_RTC_INTF_DEV_UIE_EMUL=y
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#CONFIG_RTC_DRV_ABB5ZES3=mCONFIG_RTC_DRV_ABEOZ9=yCONFIG_RTC_DRV_ABX80X=mCONFIG_RTC_DRV_DS1307=y
# CONFIG_RTC_DRV_DS1307_CENTURY is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not setCONFIG_RTC_DRV_HYM8563=yCONFIG_RTC_DRV_LP8788=y
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_MAX8907 is not setCONFIG_RTC_DRV_MAX8925=mCONFIG_RTC_DRV_MAX8997=y
# CONFIG_RTC_DRV_NCT3018Y is not setCONFIG_RTC_DRV_RK808=y
# CONFIG_RTC_DRV_RS5C372 is not setCONFIG_RTC_DRV_ISL1208=y
# CONFIG_RTC_DRV_ISL12022 is not setCONFIG_RTC_DRV_ISL12026=y
# CONFIG_RTC_DRV_X1205 is not setCONFIG_RTC_DRV_PCF8523=m
# CONFIG_RTC_DRV_PCF85063 is not setCONFIG_RTC_DRV_PCF85363=m
# CONFIG_RTC_DRV_PCF8563 is not setCONFIG_RTC_DRV_PCF8583=mCONFIG_RTC_DRV_M41T80=y
# CONFIG_RTC_DRV_M41T80_WDT is not set
# CONFIG_RTC_DRV_BQ32K is not setCONFIG_RTC_DRV_PALMAS=mCONFIG_RTC_DRV_TPS65910=yCONFIG_RTC_DRV_RC5T583=m
# CONFIG_RTC_DRV_RC5T619 is not set
# 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 setCONFIG_RTC_DRV_RV3032=m
# CONFIG_RTC_DRV_RV8803 is not setCONFIG_RTC_DRV_S5M=mCONFIG_RTC_DRV_SD3078=y
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not setCONFIG_RTC_DRV_M41T94=mCONFIG_RTC_DRV_DS1302=mCONFIG_RTC_DRV_DS1305=y
# CONFIG_RTC_DRV_DS1343 is not setCONFIG_RTC_DRV_DS1347=m
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not setCONFIG_RTC_DRV_RX4581=mCONFIG_RTC_DRV_RS5C348=y
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not setCONFIG_RTC_DRV_MCP795=yCONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#CONFIG_RTC_DRV_DS3232=yCONFIG_RTC_DRV_DS3232_HWMON=yCONFIG_RTC_DRV_PCF2127=mCONFIG_RTC_DRV_RV3029C2=y
# CONFIG_RTC_DRV_RV3029_HWMON is not setCONFIG_RTC_DRV_RX6110=m
#
# Platform RTC drivers
#CONFIG_RTC_DRV_CMOS=mCONFIG_RTC_DRV_DS1286=yCONFIG_RTC_DRV_DS1511=mCONFIG_RTC_DRV_DS1553=yCONFIG_RTC_DRV_DS1685_FAMILY=m
# CONFIG_RTC_DRV_DS1685 is not set
# CONFIG_RTC_DRV_DS1689 is not set
# CONFIG_RTC_DRV_DS17285 is not setCONFIG_RTC_DRV_DS17485=y
# CONFIG_RTC_DRV_DS17885 is not set
# CONFIG_RTC_DRV_DS1742 is not setCONFIG_RTC_DRV_DS2404=m
# CONFIG_RTC_DRV_DA9052 is not setCONFIG_RTC_DRV_DA9063=yCONFIG_RTC_DRV_STK17TA8=yCONFIG_RTC_DRV_M48T86=yCONFIG_RTC_DRV_M48T35=mCONFIG_RTC_DRV_M48T59=m
# CONFIG_RTC_DRV_MSM6242 is not setCONFIG_RTC_DRV_BQ4802=mCONFIG_RTC_DRV_RP5C01=m
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_WM831X is not set
# CONFIG_RTC_DRV_WM8350 is not setCONFIG_RTC_DRV_PCF50633=mCONFIG_RTC_DRV_ZYNQMP=yCONFIG_RTC_DRV_CROS_EC=mCONFIG_RTC_DRV_NTXEC=y
#
# on-CPU RTC drivers
#CONFIG_RTC_DRV_CADENCE=m
# CONFIG_RTC_DRV_FTRTC010 is not setCONFIG_RTC_DRV_MC13XXX=m
# CONFIG_RTC_DRV_MT6397 is not set
# CONFIG_RTC_DRV_R7301 is not set
# CONFIG_RTC_DRV_CPCAP is not set
#
# HID Sensor RTC drivers
#CONFIG_RTC_DRV_GOLDFISH=y
# CONFIG_DMADEVICES is not set
#
# DMABUF options
#CONFIG_SYNC_FILE=y
# CONFIG_SW_SYNC is not setCONFIG_UDMABUF=yCONFIG_DMABUF_MOVE_NOTIFY=yCONFIG_DMABUF_DEBUG=y
# CONFIG_DMABUF_SELFTESTS is not setCONFIG_DMABUF_HEAPS=y
# CONFIG_DMABUF_SYSFS_STATS is not setCONFIG_DMABUF_HEAPS_SYSTEM=yCONFIG_DMABUF_HEAPS_CMA=y
# end of DMABUF options
CONFIG_AUXDISPLAY=yCONFIG_CHARLCD=yCONFIG_HD44780_COMMON=mCONFIG_HD44780=mCONFIG_KS0108=mCONFIG_KS0108_PORT=0x378CONFIG_KS0108_DELAY=2CONFIG_CFAG12864B=mCONFIG_CFAG12864B_RATE=20
# CONFIG_IMG_ASCII_LCD is not set
# CONFIG_HT16K33 is not setCONFIG_LCD2S=yCONFIG_PARPORT_PANEL=mCONFIG_PANEL_PARPORT=0CONFIG_PANEL_PROFILE=5CONFIG_PANEL_CHANGE_MESSAGE=yCONFIG_PANEL_BOOT_MESSAGE=""
# CONFIG_CHARLCD_BL_OFF is not setCONFIG_CHARLCD_BL_ON=y
# CONFIG_CHARLCD_BL_FLASH is not setCONFIG_PANEL=mCONFIG_UIO=yCONFIG_UIO_CIF=y
# CONFIG_UIO_PDRV_GENIRQ is not set
# CONFIG_UIO_DMEM_GENIRQ is not setCONFIG_UIO_AEC=y
# CONFIG_UIO_SERCOS3 is not set
# CONFIG_UIO_PCI_GENERIC is not setCONFIG_UIO_NETX=y
# CONFIG_UIO_PRUSS is not setCONFIG_UIO_MF624=y
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not setCONFIG_VIRTIO_ANCHOR=yCONFIG_VIRTIO=y
# CONFIG_VIRTIO_MENU is not set
# CONFIG_VDPA is not setCONFIG_VHOST_IOTLB=yCONFIG_VHOST_RING=y
# CONFIG_VHOST_MENU is not set
#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
# end of Microsoft Hyper-V guest support
CONFIG_GREYBUS=m
# CONFIG_COMEDI is not set
# CONFIG_STAGING is not set
# CONFIG_GOLDFISH_PIPE is not setCONFIG_CHROME_PLATFORMS=y
# CONFIG_CHROMEOS_ACPI is not setCONFIG_CHROMEOS_LAPTOP=m
# CONFIG_CHROMEOS_PSTORE is not set
# CONFIG_CHROMEOS_TBMC is not setCONFIG_CROS_EC=mCONFIG_CROS_EC_I2C=mCONFIG_CROS_EC_RPMSG=mCONFIG_CROS_EC_SPI=m
# CONFIG_CROS_EC_LPC is not setCONFIG_CROS_EC_PROTO=y
# CONFIG_CROS_KBD_LED_BACKLIGHT is not set
# CONFIG_CROS_EC_CHARDEV is not setCONFIG_CROS_EC_LIGHTBAR=m
# CONFIG_CROS_EC_VBC is not setCONFIG_CROS_EC_DEBUGFS=mCONFIG_CROS_EC_SENSORHUB=mCONFIG_CROS_EC_SYSFS=m
# CONFIG_CROS_USBPD_NOTIFY is not set
# CONFIG_CHROMEOS_PRIVACY_SCREEN is not set
# CONFIG_MELLANOX_PLATFORM is not setCONFIG_SURFACE_PLATFORMS=y
# CONFIG_SURFACE3_WMI is not set
# CONFIG_SURFACE_3_POWER_OPREGION is not set
# CONFIG_SURFACE_GPE is not set
# CONFIG_SURFACE_HOTPLUG is not set
# CONFIG_SURFACE_PRO3_BUTTON is not set
# CONFIG_SURFACE_AGGREGATOR is not setCONFIG_X86_PLATFORM_DEVICES=yCONFIG_ACPI_WMI=yCONFIG_WMI_BMOF=y
# CONFIG_HUAWEI_WMI is not set
# CONFIG_MXM_WMI is not set
# CONFIG_PEAQ_WMI is not set
# CONFIG_NVIDIA_WMI_EC_BACKLIGHT is not set
# CONFIG_XIAOMI_WMI is not set
# CONFIG_GIGABYTE_WMI is not set
# CONFIG_YOGABOOK_WMI is not set
# CONFIG_ACERHDF is not set
# CONFIG_ACER_WIRELESS is not set
# CONFIG_ACER_WMI is not set
# CONFIG_AMD_PMF is not set
# CONFIG_AMD_PMC is not set
# CONFIG_ADV_SWBUTTON is not set
# CONFIG_APPLE_GMUX is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_ASUS_WIRELESS is not set
# CONFIG_ASUS_TF103C_DOCK is not set
# CONFIG_X86_PLATFORM_DRIVERS_DELL is not setCONFIG_AMILO_RFKILL=m
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_FUJITSU_TABLET is not set
# CONFIG_GPD_POCKET_FAN is not set
# CONFIG_HP_ACCEL is not set
# CONFIG_WIRELESS_HOTKEY is not set
# CONFIG_HP_WMI is not set
# CONFIG_TC1100_WMI is not setCONFIG_IBM_RTL=y
# CONFIG_IDEAPAD_LAPTOP is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_THINKPAD_LMI is not setCONFIG_INTEL_ATOMISP2_PDX86=yCONFIG_INTEL_ATOMISP2_LED=yCONFIG_INTEL_ATOMISP2_PM=m
# CONFIG_INTEL_SAR_INT1092 is not set
# CONFIG_INTEL_SKL_INT3472 is not set
# CONFIG_INTEL_PMC_CORE is not set
# CONFIG_INTEL_WMI_SBL_FW_UPDATE is not set
# CONFIG_INTEL_WMI_THUNDERBOLT is not set
# CONFIG_INTEL_HID_EVENT is not set
# CONFIG_INTEL_VBTN is not set
# CONFIG_INTEL_INT0002_VGPIO is not set
# CONFIG_INTEL_OAKTRAIL is not setCONFIG_INTEL_PUNIT_IPC=m
# CONFIG_INTEL_RST is not set
# CONFIG_INTEL_SMARTCONNECT is not set
# CONFIG_INTEL_VSEC is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_MSI_WMI is not set
# CONFIG_PCENGINES_APU2 is not setCONFIG_BARCO_P50_GPIO=mCONFIG_SAMSUNG_LAPTOP=y
# CONFIG_SAMSUNG_Q10 is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_TOSHIBA_HAPS is not set
# CONFIG_TOSHIBA_WMI is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_LG_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_SYSTEM76_ACPI is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_SERIAL_MULTI_INSTANTIATE is not setCONFIG_MLX_PLATFORM=y
# CONFIG_INTEL_IPS is not setCONFIG_INTEL_SCU_IPC=yCONFIG_INTEL_SCU=yCONFIG_INTEL_SCU_PCI=y
# CONFIG_INTEL_SCU_PLATFORM is not setCONFIG_INTEL_SCU_IPC_UTIL=y
# CONFIG_SIEMENS_SIMATIC_IPC is not set
# CONFIG_WINMATE_FM07_KEYS is not setCONFIG_P2SB=yCONFIG_HAVE_CLK=yCONFIG_HAVE_CLK_PREPARE=yCONFIG_COMMON_CLK=yCONFIG_COMMON_CLK_WM831X=y
# CONFIG_LMK04832 is not set
# CONFIG_COMMON_CLK_MAX9485 is not setCONFIG_COMMON_CLK_RK808=m
# CONFIG_COMMON_CLK_SI5341 is not setCONFIG_COMMON_CLK_SI5351=mCONFIG_COMMON_CLK_SI514=yCONFIG_COMMON_CLK_SI544=yCONFIG_COMMON_CLK_SI570=yCONFIG_COMMON_CLK_CDCE706=mCONFIG_COMMON_CLK_CDCE925=m
# CONFIG_COMMON_CLK_CS2000_CP is not setCONFIG_COMMON_CLK_S2MPS11=mCONFIG_COMMON_CLK_AXI_CLKGEN=yCONFIG_COMMON_CLK_PALMAS=yCONFIG_COMMON_CLK_PWM=y
# CONFIG_COMMON_CLK_RS9_PCIE is not setCONFIG_COMMON_CLK_VC5=y
# CONFIG_COMMON_CLK_VC7 is not setCONFIG_COMMON_CLK_BD718XX=m
# CONFIG_COMMON_CLK_FIXED_MMIO is not set
# CONFIG_CLK_LGM_CGU is not setCONFIG_XILINX_VCU=y
# CONFIG_COMMON_CLK_XLNX_CLKWZRD is not setCONFIG_HWSPINLOCK=y
#
# Clock Source drivers
#CONFIG_TIMER_OF=yCONFIG_TIMER_PROBE=yCONFIG_CLKSRC_I8253=yCONFIG_CLKEVT_I8253=yCONFIG_CLKBLD_I8253=yCONFIG_MICROCHIP_PIT64B=y
# end of Clock Source drivers
CONFIG_MAILBOX=yCONFIG_PLATFORM_MHU=y
# CONFIG_PCC is not set
# CONFIG_ALTERA_MBOX is not set
# CONFIG_MAILBOX_TEST is not setCONFIG_IOMMU_IOVA=yCONFIG_IOMMU_API=yCONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support
CONFIG_IOMMU_DEBUGFS=y
# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not setCONFIG_IOMMU_DEFAULT_DMA_LAZY=y
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not setCONFIG_OF_IOMMU=yCONFIG_IOMMU_DMA=y
# CONFIG_INTEL_IOMMU is not setCONFIG_VIRTIO_IOMMU=m
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers
#
# Rpmsg drivers
#CONFIG_RPMSG=yCONFIG_RPMSG_CHAR=y
# CONFIG_RPMSG_CTRL is not setCONFIG_RPMSG_NS=yCONFIG_RPMSG_QCOM_GLINK=yCONFIG_RPMSG_QCOM_GLINK_RPM=yCONFIG_RPMSG_VIRTIO=y
# end of Rpmsg drivers
CONFIG_SOUNDWIRE=y
#
# SoundWire Devices
#
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# end of NXP/Freescale QorIQ SoC drivers
#
# fujitsu SoC drivers # # end of fujitsu SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Enable LiteX SoC Builder specific drivers
#CONFIG_LITEX=yCONFIG_LITEX_SOC_CONTROLLER=m
# end of Enable LiteX SoC Builder specific drivers
#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers
CONFIG_SOC_TI=y
#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers # end of SOC (System On Chip) specific Drivers
CONFIG_PM_DEVFREQ=y
#
# DEVFREQ Governors
#CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=yCONFIG_DEVFREQ_GOV_PERFORMANCE=y
# CONFIG_DEVFREQ_GOV_POWERSAVE is not setCONFIG_DEVFREQ_GOV_USERSPACE=yCONFIG_DEVFREQ_GOV_PASSIVE=y
#
# DEVFREQ Drivers
#CONFIG_PM_DEVFREQ_EVENT=yCONFIG_EXTCON=y
#
# Extcon Device Drivers
#
# CONFIG_EXTCON_FSA9480 is not setCONFIG_EXTCON_GPIO=y
# CONFIG_EXTCON_INTEL_INT3496 is not set
# CONFIG_EXTCON_MAX14577 is not setCONFIG_EXTCON_MAX3355=m
# CONFIG_EXTCON_MAX77693 is not set
# CONFIG_EXTCON_MAX77843 is not set
# CONFIG_EXTCON_MAX8997 is not set
# CONFIG_EXTCON_PALMAS is not setCONFIG_EXTCON_PTN5150=yCONFIG_EXTCON_RT8973A=m
# CONFIG_EXTCON_SM5502 is not setCONFIG_EXTCON_USB_GPIO=yCONFIG_EXTCON_USBC_CROS_EC=mCONFIG_MEMORY=y
# CONFIG_IIO is not set
# CONFIG_NTB is not setCONFIG_PWM=yCONFIG_PWM_SYSFS=yCONFIG_PWM_DEBUG=yCONFIG_PWM_ATMEL_TCB=m
# CONFIG_PWM_CLK is not set
# CONFIG_PWM_CROS_EC is not set
# CONFIG_PWM_DWC is not set
# CONFIG_PWM_FSL_FTM is not setCONFIG_PWM_INTEL_LGM=yCONFIG_PWM_IQS620A=m
# CONFIG_PWM_LPSS_PCI is not set
# CONFIG_PWM_LPSS_PLATFORM is not setCONFIG_PWM_NTXEC=m
# CONFIG_PWM_PCA9685 is not set
# CONFIG_PWM_XILINX is not set
#
# IRQ chip support
#CONFIG_IRQCHIP=yCONFIG_AL_FIC=yCONFIG_MADERA_IRQ=y
# CONFIG_XILINX_INTC is not set
# end of IRQ chip support
CONFIG_IPACK_BUS=m
# CONFIG_BOARD_TPCI200 is not set
# CONFIG_SERIAL_IPOCTAL is not setCONFIG_RESET_CONTROLLER=y
# CONFIG_RESET_INTEL_GW is not setCONFIG_RESET_SIMPLE=y
# CONFIG_RESET_TI_SYSCON is not set
# CONFIG_RESET_TI_TPS380X is not set
#
# PHY Subsystem
#CONFIG_GENERIC_PHY=yCONFIG_GENERIC_PHY_MIPI_DPHY=y
# CONFIG_USB_LGM_PHY is not setCONFIG_PHY_CAN_TRANSCEIVER=m
#
# PHY drivers for Broadcom platforms
#CONFIG_BCM_KONA_USB2_PHY=y
# end of PHY drivers for Broadcom platforms
CONFIG_PHY_CADENCE_TORRENT=m
# CONFIG_PHY_CADENCE_DPHY is not set
# CONFIG_PHY_CADENCE_DPHY_RX is not setCONFIG_PHY_CADENCE_SIERRA=mCONFIG_PHY_CADENCE_SALVO=yCONFIG_PHY_PXA_28NM_HSIC=mCONFIG_PHY_PXA_28NM_USB2=m
# CONFIG_PHY_LAN966X_SERDES is not set
# CONFIG_PHY_MAPPHONE_MDM6600 is not set
# CONFIG_PHY_OCELOT_SERDES is not setCONFIG_PHY_INTEL_LGM_COMBO=yCONFIG_PHY_INTEL_LGM_EMMC=y
# end of PHY Subsystem
CONFIG_POWERCAP=yCONFIG_INTEL_RAPL_CORE=mCONFIG_INTEL_RAPL=m
# CONFIG_IDLE_INJECT is not setCONFIG_DTPM=yCONFIG_MCB=yCONFIG_MCB_PCI=y
# CONFIG_MCB_LPC is not set
#
# Performance monitor support
#
# end of Performance monitor support
CONFIG_RAS=y
# CONFIG_USB4 is not set
#
# Android
#
# CONFIG_ANDROID_BINDER_IPC is not set
# end of Android
CONFIG_DAX=y
# CONFIG_DEV_DAX is not setCONFIG_NVMEM=yCONFIG_NVMEM_SYSFS=yCONFIG_NVMEM_RMEM=mCONFIG_NVMEM_SPMI_SDAM=m
#
# HW tracing support
#CONFIG_STM=yCONFIG_STM_PROTO_BASIC=m
# CONFIG_STM_PROTO_SYS_T is not setCONFIG_STM_DUMMY=yCONFIG_STM_SOURCE_CONSOLE=yCONFIG_STM_SOURCE_HEARTBEAT=yCONFIG_STM_SOURCE_FTRACE=m
# CONFIG_INTEL_TH is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_FSI is not setCONFIG_MULTIPLEXER=y
#
# Multiplexer drivers
#CONFIG_MUX_ADG792A=yCONFIG_MUX_ADGS1408=m
# CONFIG_MUX_GPIO is not setCONFIG_MUX_MMIO=m
# end of Multiplexer drivers
CONFIG_PM_OPP=yCONFIG_SIOX=yCONFIG_SIOX_BUS_GPIO=y
# CONFIG_SLIMBUS is not setCONFIG_INTERCONNECT=yCONFIG_COUNTER=yCONFIG_104_QUAD_8=y
# CONFIG_INTERRUPT_CNT is not setCONFIG_FTM_QUADDEC=yCONFIG_MICROCHIP_TCB_CAPTURE=mCONFIG_INTEL_QEP=y
# CONFIG_MOST is not set
# CONFIG_PECI is not set
# CONFIG_HTE is not set
# end of Device Drivers
#
# File systems
#CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not setCONFIG_FS_IOMAP=yCONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not setCONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_POSIX_ACL is not setCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS=y
# CONFIG_EXT4_FS_POSIX_ACL is not setCONFIG_EXT4_FS_SECURITY=yCONFIG_EXT4_DEBUG=yCONFIG_JBD2=yCONFIG_JBD2_DEBUG=yCONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not setCONFIG_OCFS2_FS=y
# CONFIG_OCFS2_FS_O2CB is not setCONFIG_OCFS2_FS_STATS=y
# CONFIG_OCFS2_DEBUG_MASKLOG is not setCONFIG_OCFS2_DEBUG_FS=y
# CONFIG_BTRFS_FS is not setCONFIG_NILFS2_FS=yCONFIG_F2FS_FS=m
# CONFIG_F2FS_STAT_FS is not setCONFIG_F2FS_FS_XATTR=y
# CONFIG_F2FS_FS_POSIX_ACL is not set
# CONFIG_F2FS_FS_SECURITY is not setCONFIG_F2FS_CHECK_FS=y
# CONFIG_F2FS_FAULT_INJECTION is not setCONFIG_F2FS_FS_COMPRESSION=yCONFIG_F2FS_FS_LZO=y
# CONFIG_F2FS_FS_LZORLE is not set
# CONFIG_F2FS_FS_LZ4 is not set
# CONFIG_F2FS_FS_ZSTD is not setCONFIG_F2FS_IOSTAT=yCONFIG_FS_POSIX_ACL=yCONFIG_EXPORTFS=yCONFIG_EXPORTFS_BLOCK_OPS=yCONFIG_FILE_LOCKING=yCONFIG_FS_ENCRYPTION=yCONFIG_FS_ENCRYPTION_ALGS=yCONFIG_FS_ENCRYPTION_INLINE_CRYPT=y
# CONFIG_FS_VERITY is not setCONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=yCONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not setCONFIG_QUOTA=yCONFIG_QUOTA_NETLINK_INTERFACE=yCONFIG_PRINT_QUOTA_WARNING=yCONFIG_QUOTA_DEBUG=yCONFIG_QUOTA_TREE=yCONFIG_QFMT_V1=mCONFIG_QFMT_V2=yCONFIG_QUOTACTL=y
# CONFIG_AUTOFS4_FS is not setCONFIG_AUTOFS_FS=y
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not setCONFIG_UDF_FS=m
# end of CD-ROM/DVD Filesystems
#
# DOS/FAT/EXFAT/NT Filesystems
#CONFIG_FAT_FS=yCONFIG_MSDOS_FS=y
# CONFIG_VFAT_FS is not setCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_EXFAT_FS=mCONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS3_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems
#
# Pseudo filesystems
#CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not setCONFIG_PROC_SYSCTL=y
# CONFIG_PROC_PAGE_MONITOR is not set
# CONFIG_PROC_CHILDREN is not setCONFIG_PROC_PID_ARCH_STATUS=yCONFIG_KERNFS=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_TMPFS_XATTR=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_MEMFD_CREATE=yCONFIG_CONFIGFS_FS=y
# end of Pseudo filesystems
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ORANGEFS_FS is not set CONFIG_ADFS_FS=mCONFIG_ADFS_FS_RW=yCONFIG_AFFS_FS=y
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not setCONFIG_CRAMFS=m
# CONFIG_CRAMFS_BLOCKDEV is not set CONFIG_SQUASHFS=y CONFIG_SQUASHFS_FILE_CACHE=y
# CONFIG_SQUASHFS_FILE_DIRECT is not set
# CONFIG_SQUASHFS_DECOMP_SINGLE is not set # CONFIG_SQUASHFS_DECOMP_MULTI is not set CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y
# CONFIG_SQUASHFS_XATTR is not set CONFIG_SQUASHFS_ZLIB=y
# CONFIG_SQUASHFS_LZ4 is not set CONFIG_SQUASHFS_LZO=y
# CONFIG_SQUASHFS_XZ is not set CONFIG_SQUASHFS_ZSTD=y
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set CONFIG_SQUASHFS_EMBEDDED=y CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 CONFIG_VXFS_FS=mCONFIG_MINIX_FS=mCONFIG_OMFS_FS=yCONFIG_HPFS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set CONFIG_ROMFS_FS=m CONFIG_ROMFS_BACKED_BY_BLOCK=y CONFIG_ROMFS_ON_BLOCK=yCONFIG_PSTORE=y CONFIG_PSTORE_DEFAULT_KMSG_BYTES=10240 CONFIG_PSTORE_DEFLATE_COMPRESS=m CONFIG_PSTORE_LZO_COMPRESS=m CONFIG_PSTORE_LZ4_COMPRESS=m
# CONFIG_PSTORE_LZ4HC_COMPRESS is not set
# CONFIG_PSTORE_842_COMPRESS is not set
# CONFIG_PSTORE_ZSTD_COMPRESS is not set CONFIG_PSTORE_COMPRESS=y
# CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT is not set # CONFIG_PSTORE_LZO_COMPRESS_DEFAULT is not set CONFIG_PSTORE_LZ4_COMPRESS_DEFAULT=y CONFIG_PSTORE_COMPRESS_DEFAULT="lz4"
# CONFIG_PSTORE_CONSOLE is not set CONFIG_PSTORE_PMSG=y
# CONFIG_PSTORE_FTRACE is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_PSTORE_BLK is not set CONFIG_SYSV_FS=y
# CONFIG_UFS_FS is not set CONFIG_EROFS_FS=mCONFIG_EROFS_FS_DEBUG=y
# CONFIG_EROFS_FS_XATTR is not set
# CONFIG_EROFS_FS_ZIP is not set
# CONFIG_NETWORK_FILESYSTEMS is not set CONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=y
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=y CONFIG_NLS_CODEPAGE_860=y CONFIG_NLS_CODEPAGE_861=y CONFIG_NLS_CODEPAGE_862=m
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set CONFIG_NLS_CODEPAGE_866=m
# CONFIG_NLS_CODEPAGE_869 is not set CONFIG_NLS_CODEPAGE_936=m
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set CONFIG_NLS_CODEPAGE_949=y
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set CONFIG_NLS_ISO8859_3=m
# CONFIG_NLS_ISO8859_4 is not set CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set CONFIG_NLS_ISO8859_14=y CONFIG_NLS_ISO8859_15=yCONFIG_NLS_KOI8_R=yCONFIG_NLS_KOI8_U=mCONFIG_NLS_MAC_ROMAN=y CONFIG_NLS_MAC_CELTIC=y CONFIG_NLS_MAC_CENTEURO=m
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set CONFIG_NLS_MAC_GAELIC=y CONFIG_NLS_MAC_GREEK=m CONFIG_NLS_MAC_ICELAND=y CONFIG_NLS_MAC_INUIT=y
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set CONFIG_NLS_UTF8=y
# CONFIG_DLM is not setCONFIG_UNICODE=y
# CONFIG_UNICODE_NORMALIZATION_SELFTEST is not set
# end of File systems
#
# Security options
#CONFIG_KEYS=y
# CONFIG_KEYS_REQUEST_CACHE is not set CONFIG_PERSISTENT_KEYRINGS=y
# CONFIG_TRUSTED_KEYS is not set
# CONFIG_ENCRYPTED_KEYS is not set
# CONFIG_KEY_DH_OPERATIONS is not set CONFIG_SECURITY_DMESG_RESTRICT=yCONFIG_SECURITY=y
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_INFINIBAND is not set
# CONFIG_SECURITY_PATH is not set CONFIG_STATIC_USERMODEHELPER=y CONFIG_STATIC_USERMODEHELPER_PATH="/sbin/usermode-helper" # CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
# CONFIG_SECURITY_LANDLOCK is not setCONFIG_INTEGRITY=y
# CONFIG_INTEGRITY_SIGNATURE is not set
# CONFIG_IMA is not set
# CONFIG_EVM is not setCONFIG_DEFAULT_SECURITY_DAC=y CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,integrity,bpf"
#
# Kernel hardening options
#
#
# Memory initialization
#CONFIG_CC_HAS_AUTO_VAR_INIT_PATTERN=yCONFIG_CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER=yCONFIG_CC_HAS_AUTO_VAR_INIT_ZERO=y
# CONFIG_INIT_STACK_NONE is not setCONFIG_INIT_STACK_ALL_PATTERN=y
# CONFIG_INIT_STACK_ALL_ZERO is not setCONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
# end of Memory initialization
CONFIG_RANDSTRUCT_NONE=y
# end of Kernel hardening options # end of Security options
CONFIG_CRYPTO=y
#
# Crypto core or helper
#CONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_SKCIPHER=yCONFIG_CRYPTO_SKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG=yCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_RNG_DEFAULT=yCONFIG_CRYPTO_AKCIPHER2=yCONFIG_CRYPTO_AKCIPHER=yCONFIG_CRYPTO_KPP2=yCONFIG_CRYPTO_KPP=yCONFIG_CRYPTO_ACOMP2=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=yCONFIG_CRYPTO_USER=mCONFIG_CRYPTO_MANAGER_DISABLE_TESTS=yCONFIG_CRYPTO_GF128MUL=yCONFIG_CRYPTO_NULL=yCONFIG_CRYPTO_NULL2=yCONFIG_CRYPTO_PCRYPT=mCONFIG_CRYPTO_CRYPTD=yCONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not setCONFIG_CRYPTO_SIMD=y
# end of Crypto core or helper
#
# Public-key cryptography
#CONFIG_CRYPTO_RSA=yCONFIG_CRYPTO_DH=m
# CONFIG_CRYPTO_DH_RFC7919_GROUPS is not setCONFIG_CRYPTO_ECC=yCONFIG_CRYPTO_ECDH=yCONFIG_CRYPTO_ECDSA=mCONFIG_CRYPTO_ECRDSA=y
# CONFIG_CRYPTO_SM2 is not setCONFIG_CRYPTO_CURVE25519=y
# end of Public-key cryptography
#
# Block ciphers
#CONFIG_CRYPTO_AES=yCONFIG_CRYPTO_AES_TI=y
# CONFIG_CRYPTO_ARIA is not setCONFIG_CRYPTO_BLOWFISH=yCONFIG_CRYPTO_BLOWFISH_COMMON=yCONFIG_CRYPTO_CAMELLIA=y
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not setCONFIG_CRYPTO_SERPENT=y
# CONFIG_CRYPTO_SM4_GENERIC is not set
# CONFIG_CRYPTO_TWOFISH is not setCONFIG_CRYPTO_TWOFISH_COMMON=m
# end of Block ciphers
#
# Length-preserving ciphers and modes
#CONFIG_CRYPTO_ADIANTUM=mCONFIG_CRYPTO_CHACHA20=mCONFIG_CRYPTO_CBC=yCONFIG_CRYPTO_CFB=mCONFIG_CRYPTO_CTR=yCONFIG_CRYPTO_CTS=yCONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_HCTR2 is not set
# CONFIG_CRYPTO_KEYWRAP is not set
# CONFIG_CRYPTO_LRW is not setCONFIG_CRYPTO_OFB=yCONFIG_CRYPTO_PCBC=yCONFIG_CRYPTO_XTS=mCONFIG_CRYPTO_NHPOLY1305=m
# end of Length-preserving ciphers and modes
#
# AEAD (authenticated encryption with associated data) ciphers #
# CONFIG_CRYPTO_AEGIS128 is not set
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set CONFIG_CRYPTO_CCM=yCONFIG_CRYPTO_GCM=yCONFIG_CRYPTO_SEQIV=mCONFIG_CRYPTO_ECHAINIV=yCONFIG_CRYPTO_ESSIV=m
# end of AEAD (authenticated encryption with associated data) ciphers
#
# Hashes, digests, and MACs
#CONFIG_CRYPTO_BLAKE2B=mCONFIG_CRYPTO_CMAC=yCONFIG_CRYPTO_GHASH=yCONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_MD4 is not setCONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_RMD160 is not setCONFIG_CRYPTO_SHA1=yCONFIG_CRYPTO_SHA256=yCONFIG_CRYPTO_SHA512=yCONFIG_CRYPTO_SHA3=y
# CONFIG_CRYPTO_SM3_GENERIC is not setCONFIG_CRYPTO_STREEBOG=y
# CONFIG_CRYPTO_VMAC is not setCONFIG_CRYPTO_WP512=m
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_XXHASH is not set
# end of Hashes, digests, and MACs
#
# CRCs (cyclic redundancy checks)
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32=mCONFIG_CRYPTO_CRCT10DIF=yCONFIG_CRYPTO_CRC64_ROCKSOFT=y
# end of CRCs (cyclic redundancy checks)
#
# Compression
#CONFIG_CRYPTO_DEFLATE=mCONFIG_CRYPTO_LZO=mCONFIG_CRYPTO_842=mCONFIG_CRYPTO_LZ4=mCONFIG_CRYPTO_LZ4HC=yCONFIG_CRYPTO_ZSTD=m
# end of Compression
#
# Random number generation
#CONFIG_CRYPTO_ANSI_CPRNG=yCONFIG_CRYPTO_DRBG_MENU=yCONFIG_CRYPTO_DRBG_HMAC=yCONFIG_CRYPTO_DRBG_HASH=yCONFIG_CRYPTO_DRBG_CTR=yCONFIG_CRYPTO_DRBG=yCONFIG_CRYPTO_JITTERENTROPY=y
# end of Random number generation
#
# Userspace interface
#CONFIG_CRYPTO_USER_API=y CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=y CONFIG_CRYPTO_USER_API_RNG=y
# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set # CONFIG_CRYPTO_USER_API_AEAD is not set
# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE is not set # CONFIG_CRYPTO_STATS is not set
# end of Userspace interface
CONFIG_CRYPTO_HASH_INFO=y
#
# Accelerated Cryptographic Algorithms for CPU (x86) #
# CONFIG_CRYPTO_AES_NI_INTEL is not set CONFIG_CRYPTO_SERPENT_SSE2_586=y CONFIG_CRYPTO_TWOFISH_586=m
# CONFIG_CRYPTO_CRC32C_INTEL is not set CONFIG_CRYPTO_CRC32_PCLMUL=y
# end of Accelerated Cryptographic Algorithms for CPU (x86)
# CONFIG_CRYPTO_HW is not setCONFIG_ASYMMETRIC_KEY_TYPE=yCONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=yCONFIG_X509_CERTIFICATE_PARSER=y
# CONFIG_PKCS8_PRIVATE_KEY_PARSER is not setCONFIG_PKCS7_MESSAGE_PARSER=y
# CONFIG_FIPS_SIGNATURE_SELFTEST is not set
#
# Certificates for signature checking
#
# CONFIG_SYSTEM_TRUSTED_KEYRING is not set
# CONFIG_SYSTEM_BLACKLIST_KEYRING is not set
# end of Certificates for signature checking
CONFIG_BINARY_PRINTF=y
#
# Library routines
#CONFIG_LINEAR_RANGES=yCONFIG_PACKING=yCONFIG_BITREVERSE=yCONFIG_GENERIC_STRNCPY_FROM_USER=yCONFIG_GENERIC_STRNLEN_USER=yCONFIG_GENERIC_NET_UTILS=y
# CONFIG_CORDIC is not setCONFIG_PRIME_NUMBERS=yCONFIG_RATIONAL=yCONFIG_GENERIC_PCI_IOMAP=yCONFIG_GENERIC_IOMAP=yCONFIG_ARCH_HAS_FAST_MULTIPLIER=yCONFIG_ARCH_USE_SYM_ANNOTATIONS=y
#
# Crypto library routines
#CONFIG_CRYPTO_LIB_UTILS=yCONFIG_CRYPTO_LIB_AES=yCONFIG_CRYPTO_LIB_ARC4=yCONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=yCONFIG_CRYPTO_LIB_CHACHA_GENERIC=mCONFIG_CRYPTO_LIB_CHACHA=mCONFIG_CRYPTO_LIB_CURVE25519_GENERIC=y
# CONFIG_CRYPTO_LIB_CURVE25519 is not setCONFIG_CRYPTO_LIB_POLY1305_RSIZE=1CONFIG_CRYPTO_LIB_POLY1305_GENERIC=mCONFIG_CRYPTO_LIB_POLY1305=mCONFIG_CRYPTO_LIB_CHACHA20POLY1305=mCONFIG_CRYPTO_LIB_SHA1=yCONFIG_CRYPTO_LIB_SHA256=y
# end of Crypto library routines
CONFIG_CRC_CCITT=yCONFIG_CRC16=yCONFIG_CRC_T10DIF=yCONFIG_CRC64_ROCKSOFT=yCONFIG_CRC_ITU_T=yCONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
# CONFIG_CRC32_SLICEBY8 is not set
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not setCONFIG_CRC32_BIT=yCONFIG_CRC64=yCONFIG_CRC4=mCONFIG_CRC7=yCONFIG_LIBCRC32C=mCONFIG_CRC8=yCONFIG_XXHASH=y
# CONFIG_RANDOM32_SELFTEST is not setCONFIG_842_COMPRESS=mCONFIG_842_DECOMPRESS=mCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_LZO_COMPRESS=mCONFIG_LZO_DECOMPRESS=yCONFIG_LZ4_COMPRESS=mCONFIG_LZ4HC_COMPRESS=yCONFIG_LZ4_DECOMPRESS=yCONFIG_ZSTD_COMMON=yCONFIG_ZSTD_COMPRESS=mCONFIG_ZSTD_DECOMPRESS=y
# CONFIG_XZ_DEC is not setCONFIG_DECOMPRESS_GZIP=yCONFIG_DECOMPRESS_BZIP2=yCONFIG_DECOMPRESS_ZSTD=yCONFIG_GENERIC_ALLOCATOR=yCONFIG_INTERVAL_TREE=yCONFIG_XARRAY_MULTI=yCONFIG_ASSOCIATIVE_ARRAY=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT_MAP=yCONFIG_HAS_DMA=yCONFIG_DMA_OPS=yCONFIG_NEED_SG_DMA_LENGTH=yCONFIG_DMA_CMA=yCONFIG_DMA_PERNUMA_CMA=y
#
# Default contiguous memory area size:
#CONFIG_CMA_SIZE_PERCENTAGE=0
# CONFIG_CMA_SIZE_SEL_MBYTES is not setCONFIG_CMA_SIZE_SEL_PERCENTAGE=y
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not setCONFIG_CMA_ALIGNMENT=8
# CONFIG_DMA_API_DEBUG is not setCONFIG_DMA_MAP_BENCHMARK=yCONFIG_SGL_ALLOC=yCONFIG_CHECK_SIGNATURE=y
# CONFIG_FORCE_NR_CPUS is not setCONFIG_CPU_RMAP=yCONFIG_DQL=yCONFIG_GLOB=y
# CONFIG_GLOB_SELFTEST is not setCONFIG_NLATTR=yCONFIG_CLZ_TAB=yCONFIG_IRQ_POLL=yCONFIG_MPILIB=yCONFIG_DIMLIB=yCONFIG_LIBFDT=yCONFIG_OID_REGISTRY=yCONFIG_HAVE_GENERIC_VDSO=yCONFIG_GENERIC_GETTIMEOFDAY=yCONFIG_GENERIC_VDSO_32=yCONFIG_GENERIC_VDSO_TIME_NS=yCONFIG_SG_POOL=yCONFIG_ARCH_STACKWALK=yCONFIG_STACKDEPOT=yCONFIG_SBITMAP=y
# end of Library routines
CONFIG_PLDMFW=y
#
# Kernel hacking
#
#
# printk and dmesg options # CONFIG_PRINTK_TIME=y CONFIG_PRINTK_CALLER=y # CONFIG_STACKTRACE_BUILD_ID is not set CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7 CONFIG_CONSOLE_LOGLEVEL_QUIET=4 CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4 # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_DYNAMIC_DEBUG_CORE is not set # CONFIG_SYMBOLIC_ERRNAME is not set CONFIG_DEBUG_BUGVERBOSE=y # end of printk and dmesg options
CONFIG_DEBUG_KERNEL=yCONFIG_DEBUG_MISC=y
#
# Compile-time checks and compiler options
#CONFIG_DEBUG_INFO=yCONFIG_AS_HAS_NON_CONST_LEB128=y
# CONFIG_DEBUG_INFO_NONE is not setCONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
# CONFIG_DEBUG_INFO_DWARF4 is not set
# CONFIG_DEBUG_INFO_DWARF5 is not set
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not setCONFIG_DEBUG_INFO_BTF=yCONFIG_PAHOLE_HAS_SPLIT_BTF=yCONFIG_PAHOLE_HAS_BTF_TAG=yCONFIG_DEBUG_INFO_BTF_MODULES=y
# CONFIG_MODULE_ALLOW_BTF_MISMATCH is not set
# CONFIG_GDB_SCRIPTS is not setCONFIG_FRAME_WARN=8192CONFIG_STRIP_ASM_SYMS=yCONFIG_HEADERS_INSTALL=yCONFIG_SECTION_MISMATCH_WARN_ONLY=yCONFIG_FRAME_POINTER=yCONFIG_VMLINUX_MAP=yCONFIG_DEBUG_FORCE_WEAK_PER_CPU=y
# end of Compile-time checks and compiler options
#
# Generic Kernel Debugging Instruments
#CONFIG_MAGIC_SYSRQ=yCONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1CONFIG_MAGIC_SYSRQ_SERIAL=yCONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""CONFIG_DEBUG_FS=y
# CONFIG_DEBUG_FS_ALLOW_ALL is not setCONFIG_DEBUG_FS_DISALLOW_MOUNT=y
# CONFIG_DEBUG_FS_ALLOW_NONE is not setCONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not setCONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=yCONFIG_UBSAN=y
# CONFIG_UBSAN_TRAP is not setCONFIG_CC_HAS_UBSAN_BOUNDS=yCONFIG_CC_HAS_UBSAN_ARRAY_BOUNDS=yCONFIG_UBSAN_BOUNDS=yCONFIG_UBSAN_ARRAY_BOUNDS=yCONFIG_UBSAN_SHIFT=yCONFIG_UBSAN_UNREACHABLE=y
# CONFIG_UBSAN_BOOL is not set
# CONFIG_UBSAN_ENUM is not set
# CONFIG_UBSAN_ALIGNMENT is not setCONFIG_UBSAN_SANITIZE_ALL=y
# CONFIG_TEST_UBSAN is not setCONFIG_HAVE_KCSAN_COMPILER=y
# end of Generic Kernel Debugging Instruments
#
# Networking Debugging
#
# CONFIG_NET_DEV_REFCNT_TRACKER is not set
# CONFIG_NET_NS_REFCNT_TRACKER is not set
# CONFIG_DEBUG_NET is not set
# end of Networking Debugging
#
# Memory Debugging
#CONFIG_PAGE_EXTENSION=y
# CONFIG_DEBUG_PAGEALLOC is not setCONFIG_PAGE_OWNER=y
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_PAGE_REF is not set
# CONFIG_DEBUG_RODATA_TEST is not setCONFIG_ARCH_HAS_DEBUG_WX=y
# CONFIG_DEBUG_WX is not setCONFIG_GENERIC_PTDUMP=yCONFIG_PTDUMP_CORE=yCONFIG_PTDUMP_DEBUGFS=yCONFIG_DEBUG_OBJECTS=y
# CONFIG_DEBUG_OBJECTS_SELFTEST is not set
# CONFIG_DEBUG_OBJECTS_FREE is not set
# CONFIG_DEBUG_OBJECTS_TIMERS is not setCONFIG_DEBUG_OBJECTS_WORK=y
# CONFIG_DEBUG_OBJECTS_RCU_HEAD is not set
# CONFIG_DEBUG_OBJECTS_PERCPU_COUNTER is not setCONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1
# CONFIG_SHRINKER_DEBUG is not setCONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not setCONFIG_DEBUG_STACK_USAGE=y
# CONFIG_SCHED_STACK_END_CHECK is not setCONFIG_ARCH_HAS_DEBUG_VM_PGTABLE=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VM_PGTABLE is not setCONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not setCONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not setCONFIG_DEBUG_KMAP_LOCAL=yCONFIG_ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP=y
# CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is not set
# CONFIG_DEBUG_HIGHMEM is not setCONFIG_HAVE_DEBUG_STACKOVERFLOW=yCONFIG_DEBUG_STACKOVERFLOW=yCONFIG_CC_HAS_KASAN_GENERIC=yCONFIG_CC_HAS_KASAN_SW_TAGS=yCONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=yCONFIG_HAVE_ARCH_KFENCE=yCONFIG_HAVE_KMSAN_COMPILER=y
# end of Memory Debugging
# CONFIG_DEBUG_SHIRQ is not set
#
# Debug Oops, Lockups and Hangs
#CONFIG_PANIC_ON_OOPS=yCONFIG_PANIC_ON_OOPS_VALUE=1CONFIG_PANIC_TIMEOUT=0CONFIG_LOCKUP_DETECTOR=yCONFIG_SOFTLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
# CONFIG_HARDLOCKUP_DETECTOR is not setCONFIG_DETECT_HUNG_TASK=yCONFIG_DEFAULT_HUNG_TASK_TIMEOUT=480
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not setCONFIG_WQ_WATCHDOG=y
# CONFIG_TEST_LOCKUP is not set
# end of Debug Oops, Lockups and Hangs
#
# Scheduler Debugging
#CONFIG_SCHED_DEBUG=yCONFIG_SCHED_INFO=yCONFIG_SCHEDSTATS=y
# end of Scheduler Debugging
CONFIG_DEBUG_TIMEKEEPING=y
#
# Lock Debugging (spinlocks, mutexes, etc...)
#CONFIG_LOCK_DEBUGGING_SUPPORT=yCONFIG_PROVE_LOCKING=y
# CONFIG_PROVE_RAW_LOCK_NESTING is not set
# CONFIG_LOCK_STAT is not setCONFIG_DEBUG_RT_MUTEXES=yCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_MUTEXES=yCONFIG_DEBUG_WW_MUTEX_SLOWPATH=yCONFIG_DEBUG_RWSEMS=yCONFIG_DEBUG_LOCK_ALLOC=yCONFIG_LOCKDEP=yCONFIG_LOCKDEP_BITS=15CONFIG_LOCKDEP_CHAINS_BITS=16CONFIG_LOCKDEP_STACK_TRACE_BITS=19CONFIG_LOCKDEP_STACK_TRACE_HASH_BITS=14CONFIG_LOCKDEP_CIRCULAR_QUEUE_BITS=12
# CONFIG_DEBUG_LOCKDEP is not setCONFIG_DEBUG_ATOMIC_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not setCONFIG_LOCK_TORTURE_TEST=m
# CONFIG_WW_MUTEX_SELFTEST is not set
# CONFIG_SCF_TORTURE_TEST is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)
CONFIG_TRACE_IRQFLAGS=yCONFIG_TRACE_IRQFLAGS_NMI=y
# CONFIG_DEBUG_IRQFLAGS is not setCONFIG_STACKTRACE=y
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
#
# Debug kernel data structures
#CONFIG_DEBUG_LIST=y
# CONFIG_DEBUG_PLIST is not setCONFIG_DEBUG_SG=y
# CONFIG_DEBUG_NOTIFIERS is not setCONFIG_BUG_ON_DATA_CORRUPTION=y
# CONFIG_DEBUG_MAPLE_TREE is not set
# end of Debug kernel data structures
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#CONFIG_PROVE_RCU=y
# CONFIG_PROVE_RCU_LIST is not setCONFIG_TORTURE_TEST=mCONFIG_RCU_SCALE_TEST=mCONFIG_RCU_TORTURE_TEST=m
# CONFIG_RCU_REF_SCALE_TEST is not setCONFIG_RCU_CPU_STALL_TIMEOUT=21CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0CONFIG_RCU_TRACE=y
# CONFIG_RCU_EQS_DEBUG is not set
# end of RCU Debugging
CONFIG_DEBUG_WQ_FORCE_RR_CPU=yCONFIG_CPU_HOTPLUG_STATE_CONTROL=yCONFIG_LATENCYTOP=yCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_NOP_TRACER=yCONFIG_HAVE_RETHOOK=yCONFIG_RETHOOK=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=yCONFIG_HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS=yCONFIG_HAVE_DYNAMIC_FTRACE_NO_PATCHABLE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_SYSCALL_TRACEPOINTS=yCONFIG_HAVE_FENTRY=yCONFIG_HAVE_C_RECORDMCOUNT=yCONFIG_HAVE_BUILDTIME_MCOUNT_SORT=yCONFIG_BUILDTIME_MCOUNT_SORT=yCONFIG_TRACER_MAX_TRACE=yCONFIG_TRACE_CLOCK=yCONFIG_RING_BUFFER=yCONFIG_EVENT_TRACING=yCONFIG_CONTEXT_SWITCH_TRACER=yCONFIG_RING_BUFFER_ALLOW_SWAP=yCONFIG_PREEMPTIRQ_TRACEPOINTS=yCONFIG_TRACING=yCONFIG_GENERIC_TRACER=yCONFIG_TRACING_SUPPORT=yCONFIG_FTRACE=y
# CONFIG_BOOTTIME_TRACING is not setCONFIG_FUNCTION_TRACER=yCONFIG_FUNCTION_GRAPH_TRACER=yCONFIG_DYNAMIC_FTRACE=yCONFIG_DYNAMIC_FTRACE_WITH_REGS=yCONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS=y
# CONFIG_FPROBE is not set
# CONFIG_FUNCTION_PROFILER is not setCONFIG_STACK_TRACER=yCONFIG_IRQSOFF_TRACER=yCONFIG_SCHED_TRACER=yCONFIG_HWLAT_TRACER=yCONFIG_OSNOISE_TRACER=y
# CONFIG_TIMERLAT_TRACER is not setCONFIG_MMIOTRACE=yCONFIG_FTRACE_SYSCALLS=yCONFIG_TRACER_SNAPSHOT=yCONFIG_TRACER_SNAPSHOT_PER_CPU_SWAP=yCONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_BLK_DEV_IO_TRACE is not setCONFIG_KPROBE_EVENTS=yCONFIG_KPROBE_EVENTS_ON_NOTRACE=yCONFIG_UPROBE_EVENTS=yCONFIG_BPF_EVENTS=yCONFIG_DYNAMIC_EVENTS=yCONFIG_PROBE_EVENTS=yCONFIG_BPF_KPROBE_OVERRIDE=yCONFIG_FTRACE_MCOUNT_RECORD=yCONFIG_FTRACE_MCOUNT_USE_RECORDMCOUNT=yCONFIG_TRACING_MAP=yCONFIG_SYNTH_EVENTS=yCONFIG_HIST_TRIGGERS=yCONFIG_TRACE_EVENT_INJECT=yCONFIG_TRACEPOINT_BENCHMARK=yCONFIG_RING_BUFFER_BENCHMARK=m
# CONFIG_TRACE_EVAL_MAP_FILE is not setCONFIG_FTRACE_RECORD_RECURSION=yCONFIG_FTRACE_RECORD_RECURSION_SIZE=128
# CONFIG_RING_BUFFER_RECORD_RECURSION is not set
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_FTRACE_SORT_STARTUP_TEST is not set
# CONFIG_RING_BUFFER_STARTUP_TEST is not setCONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS=y
# CONFIG_MMIOTRACE_TEST is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
# CONFIG_SYNTH_EVENT_GEN_TEST is not set
# CONFIG_KPROBE_EVENT_GEN_TEST is not setCONFIG_HIST_TRIGGERS_DEBUG=y
# CONFIG_RV is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not setCONFIG_SAMPLES=y
# CONFIG_SAMPLE_AUXDISPLAY is not setCONFIG_SAMPLE_TRACE_EVENTS=m
# CONFIG_SAMPLE_TRACE_CUSTOM_EVENTS is not set
# CONFIG_SAMPLE_TRACE_PRINTK is not set
# CONFIG_SAMPLE_TRACE_ARRAY is not set
# CONFIG_SAMPLE_KOBJECT is not setCONFIG_SAMPLE_KPROBES=m
# CONFIG_SAMPLE_KRETPROBES is not set
# CONFIG_SAMPLE_HW_BREAKPOINT is not set
# CONFIG_SAMPLE_KFIFO is not setCONFIG_SAMPLE_RPMSG_CLIENT=mCONFIG_SAMPLE_CONFIGFS=mCONFIG_SAMPLE_CONNECTOR=mCONFIG_SAMPLE_FANOTIFY_ERROR=yCONFIG_SAMPLE_HIDRAW=y
# CONFIG_SAMPLE_LANDLOCK is not set
# CONFIG_SAMPLE_PIDFD is not setCONFIG_SAMPLE_TIMER=yCONFIG_SAMPLE_UHID=yCONFIG_SAMPLE_VFIO_MDEV_MDPY_FB=m
# CONFIG_SAMPLE_ANDROID_BINDERFS is not setCONFIG_SAMPLE_VFS=y
# CONFIG_SAMPLE_INTEL_MEI is not setCONFIG_SAMPLE_WATCHDOG=yCONFIG_SAMPLE_WATCH_QUEUE=yCONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
# CONFIG_STRICT_DEVMEM is not set
#
# x86 Debugging # CONFIG_EARLY_PRINTK_USB=y CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y CONFIG_EARLY_PRINTK_DBGP=y CONFIG_EARLY_PRINTK_USB_XDBC=y CONFIG_DEBUG_TLBFLUSH=y CONFIG_HAVE_MMIOTRACE_SUPPORT=y # CONFIG_X86_DECODER_SELFTEST is not set CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set # CONFIG_DEBUG_BOOT_PARAMS is not set # CONFIG_CPA_DEBUG is not set # CONFIG_DEBUG_ENTRY is not set # CONFIG_DEBUG_NMI_SELFTEST is not set # CONFIG_X86_DEBUG_FPU is not set CONFIG_PUNIT_ATOM_DEBUG=m CONFIG_UNWINDER_FRAME_POINTER=y # end of x86 Debugging
#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set CONFIG_NOTIFIER_ERROR_INJECTION=m CONFIG_PM_NOTIFIER_ERROR_INJECT=m CONFIG_OF_RECONFIG_NOTIFIER_ERROR_INJECT=m CONFIG_NETDEV_NOTIFIER_ERROR_INJECT=m CONFIG_FUNCTION_ERROR_INJECTION=y CONFIG_FAULT_INJECTION=y
# CONFIG_FAIL_PAGE_ALLOC is not set CONFIG_FAULT_INJECTION_USERCOPY=y
# CONFIG_FAIL_MAKE_REQUEST is not set CONFIG_FAIL_IO_TIMEOUT=yCONFIG_FAIL_FUTEX=y CONFIG_FAULT_INJECTION_DEBUG_FS=y CONFIG_FAIL_FUNCTION=y
# CONFIG_FAULT_INJECTION_STACKTRACE_FILTER is not set CONFIG_CC_HAS_SANCOV_TRACE_PC=y
# CONFIG_RUNTIME_TESTING_MENU is not set CONFIG_ARCH_USE_MEMTEST=yCONFIG_MEMTEST=y
# end of Kernel Testing and Coverage
#
# Rust hacking
#
# end of Rust hacking # end of Kernel hacking
RFC v2 13/14 bnxt: Introduce bnxt_xdp_buff wrapper for xdp_buff
In reply to Stanislav FomichevNo functional changes. Boilerplate to allow stuffing more data after xdp_buff.
--- drivers/net/ethernet/broadcom/bnxt/bnxt.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-)
drivers/net/ethernet/broadcom/bnxt/bnxt.c +11 -7
@@ -1789,6 +1789,10 @@ static void bnxt_deliver_skb(struct bnxt *bp, struct bnxt_napi *bnapi,napi_gro_receive (&bnapi->napi, skb); } +struct bnxt_xdp_buff { +struct xdp_buff xdp; +}; +/* returns the following: * 1 - 1 packet successfully received * 0 - successful TPA_START, packet not completed yet
@@ -1812,7 +1816,7 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr,bool xdp_active = false;dma_addr_t dma_addr;struct sk_buff *skb; -struct xdp_buff xdp; +struct bnxt_xdp_buff bxbuf;u32 flags, misc;void *data;int rc =0 ;
@@ -1922,9 +1926,9 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, dma_addr = rx_buf->mapping;if (bnxt_xdp_attached (bp, rxr)) { -bnxt_xdp_buff_init (bp, rxr, cons, &data_ptr, &len, &xdp); +bnxt_xdp_buff_init (bp, rxr, cons, &data_ptr, &len, &bxbuf.xdp);if (agg_bufs) { -u32 frag_len =bnxt_rx_agg_pages_xdp (bp, cpr, &xdp, +u32 frag_len =bnxt_rx_agg_pages_xdp (bp, cpr, &bxbuf.xdp, cp_cons, agg_bufs, false);if (!frag_len) {
@@ -1937,7 +1941,7 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, }if (xdp_active) { -if (bnxt_rx_xdp (bp, rxr, cons, xdp, data, &len, event)) { +if (bnxt_rx_xdp (bp, rxr, cons, bxbuf.xdp, data, &len, event)) { rc =1 ; goto next_rx; }
@@ -1952,7 +1956,7 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr,bnxt_reuse_rx_agg_bufs (cpr, cp_cons,0 , agg_bufs, false); else - bnxt_xdp_buff_frags_free(rxr, &xdp); + bnxt_xdp_buff_frags_free(rxr, &bxbuf.xdp); } cpr->sw_stats.rx.rx_oom_discards +=1 ; rc = -ENOMEM ;
@@ -1983,10 +1987,10 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, goto next_rx; } }else { - skb =bnxt_xdp_build_skb (bp, skb, agg_bufs, rxr->page_pool, &xdp, rxcmp1); + skb =bnxt_xdp_build_skb (bp, skb, agg_bufs, rxr->page_pool, &bxbuf.xdp, rxcmp1);if (!skb) {/* we should be able to free the old skb here */ -bnxt_xdp_buff_frags_free (rxr, &xdp); +bnxt_xdp_buff_frags_free (rxr, &bxbuf.xdp); cpr->sw_stats.rx.rx_oom_discards +=1 ; rc = -ENOMEM ; goto next_rx;
Signature · 1 line
2.38.1.431.g37b22c650d-goog
RFC v2 14/14 bnxt: Support rx timestamp metadata for xdp
In reply to Stanislav FomichevCOMPILE-TESTED ONLY!
--- drivers/net/ethernet/broadcom/bnxt/bnxt.c | 55 +++++++++++++++++++++++ 1 file changed, 55 insertions(+)
drivers/net/ethernet/broadcom/bnxt/bnxt.c +55 -0
@@ -37,6 +37,7 @@#include <linux/if_bridge.h> #include <linux/rtc.h> #include <linux/bpf.h> +#include <linux/bpf_patch.h> #include <net/gro.h> #include <net/ip.h> #include <net/tcp.h>
@@ -1791,8 +1792,53 @@ static void bnxt_deliver_skb(struct bnxt *bp, struct bnxt_napi *bnapi,struct bnxt_xdp_buff {struct xdp_buff xdp; +struct rx_cmp_ext *rxcmp1; +struct bnxt *bp; +u64 r0; }; +struct bnxt_xdp_buff *bnxt_xdp_rx_timestamp (struct bnxt_xdp_buff *ctx) +{ +struct bnxt_ptp_cfg *ptp; +u32 cmpl_ts; +u64 ns, ts; + +if (!ctx->rxcmp1) { + ctx->r0 =0 ; +return ctx; + } + + cmpl_ts =le32_to_cpu (ctx->rxcmp1->rx_cmp_timestamp); +if (bnxt_get_rx_ts_p5 (ctx->bp, &ts, cmpl_ts) <0 ) { + ctx->r0 =0 ; +return ctx; + } + + ptp = ctx->bp->ptp_cfg; + +spin_lock_bh (&ptp->ptp_lock); + ns =timecounter_cyc2time (&ptp->tc, ts); +spin_unlock_bh (&ptp->ptp_lock); + + ctx->r0 = (u64 )ns_to_ktime (ns); +return ctx; +} + +void bnxt_unroll_kfunc (const struct bpf_prog *prog,u32 func_id, +struct bpf_patch *patch) +{ +if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_EXPORT_TO_SKB )) { +return xdp_metadata_export_to_skb (prog, patch); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP_SUPPORTED )) { +/* return true; */ +bpf_patch_append (patch,BPF_MOV64_IMM (BPF_REG_0 ,1 )); + }else if (func_id ==xdp_metadata_kfunc_id (XDP_METADATA_KFUNC_RX_TIMESTAMP )) { +xdp_kfunc_call_preserving_r1 (patch, + offsetof(struct bnxt_xdp_buff , r0), + bnxt_xdp_rx_timestamp); + } +} +/* returns the following: * 1 - 1 packet successfully received * 0 - successful TPA_START, packet not completed yet
@@ -1941,6 +1987,14 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, }if (xdp_active) { +if (unlikely ((flags &RX_CMP_FLAGS_ITYPES_MASK ) == +RX_CMP_FLAGS_ITYPE_PTP_W_TS ) || bp->ptp_all_rx_tstamp) { +if (bp->flags &BNXT_FLAG_CHIP_P5 ) { + bxbuf.rxcmp1 = rxcmp1; + bxbuf.bp = bp; + } + } +if (bnxt_rx_xdp (bp, rxr, cons, bxbuf.xdp, data, &len, event)) { rc =1 ; goto next_rx;
@@ -13116,6 +13170,7 @@ static const struct net_device_ops bnxt_netdev_ops = { .ndo_bridge_getlink = bnxt_bridge_getlink, .ndo_bridge_setlink = bnxt_bridge_setlink, .ndo_get_devlink_port = bnxt_get_devlink_port, + .ndo_unroll_kfunc = bnxt_unroll_kfunc, };static void bnxt_remove_one (struct pci_dev *pdev)
Signature · 1 line
2.38.1.431.g37b22c650d-goog