Skip to contentSkip to conversation

mm: introduce sysctl file to flush per-cpu vmstat statistics

PATCH In review Marcelo Tosatti 8 participants 42 messages Nov 17, 2020 – Feb 1, 2021

Subsystems (5)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 mm: introduce sysctl file to flush per-cpu vmstat statistics

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

For those cases, it is ideal to avoid the workqueue function in the first place.

For the vmstat_update function, which syncs per-cpu statistics to global stats, one can modify the -rt app to explicitly flush before the realtime loop starts.

Suggested by Christoph Lameter at https://lkml.org/lkml/2017/5/12/364.

Documentation/admin-guide/sysctl/vm.rst +16 -0
index f455fa00c00f..ea4ad1f9f82f 100644
@@ -67,6 +67,7 @@ Currently, these files are in /proc/sys/vm:
 - percpu_pagelist_fraction
 - stat_interval
 - stat_refresh
+- quiet_vmstat
 - numa_stat
 - swappiness
 - unprivileged_userfaultfd
@@ -827,6 +828,21 @@ as 0) and "fails" with EINVAL if any are found, with a warning in dmesg.
 (At time of writing, a few stats are known sometimes to be found negative,
 with no ill effects: errors and warnings on these stats are suppressed.)
 
+quiet_vmstat
+============
+
+Any read or write flushes the current cpu's per-cpu vm statistics into
+their global totals, and flushes pending updates.
+
+This is useful for isolated realtime applications that, in the setup
+phase, use services that modify per-cpu vm statistics (mlock, for example).
+
+Performing an explicit flush before starting the time sensitive loop removes
+the need for it to happen at workqueue time (which would interrupt the
+application).
+
+Note that without pinning the task to a particular CPU, which CPU has its
+per-cpu vm statistics flushed is not well defined.
 
 numa_stat
 =========
include/linux/vmstat.h +2 -0
index 322dcbfcc933..da98cc28b3ca 100644
@@ -290,6 +290,8 @@ void refresh_zone_stat_thresholds(void);
 struct ctl_table;
 int vmstat_refresh(struct ctl_table *, int write, void *buffer, size_t *lenp,
 		loff_t *ppos);
+int proc_quiet_vmstat(struct ctl_table *table, int write, void *buffer,
+		      size_t *lenp, loff_t *ppos);
 
 void drain_zonestat(struct zone *zone, struct per_cpu_pageset *);
 
kernel/sysctl.c +7 -0
index afad085960b8..71b28311b950 100644
@@ -3016,6 +3016,13 @@ static struct ctl_table vm_table[] = {
 		.mode		= 0600,
 		.proc_handler	= vmstat_refresh,
 	},
+	{
+		.procname	= "quiet_vmstat",
+		.data		= NULL,
+		.maxlen		= 0,
+		.mode		= 0600,
+		.proc_handler	= proc_quiet_vmstat,
+	},
 #endif
 #ifdef CONFIG_MMU
 	{
mm/vmstat.c +18 -0
index 698bc0bc18d1..cec8e5c32f97 100644
@@ -1936,6 +1936,24 @@ void quiet_vmstat(void)
 	refresh_cpu_vm_stats(false);
 }
 
+int proc_quiet_vmstat(struct ctl_table *table, int write,
+		   void *buffer, size_t *lenp, loff_t *ppos)
+{
+	if (write)
+		*ppos += *lenp;
+	else
+		*lenp = 0;
+
+	preempt_disable();
+	if (need_update(smp_processor_id()) == true)
+		refresh_cpu_vm_stats(false);
+	preempt_enable();
+
+	flush_delayed_work(this_cpu_ptr(&vmstat_work));
+
+	return 0;
+}
+
 /*
  * Shepherd worker thread that checks the
  * differentials of processors that have their worker
#1 lore raw
Quoted 4 lines · Marcelo Tosatti

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

This seems a bit obscure to expect an application to do. Can we make this happen automatically when we bind an rt task to a group of CPUs?

#2 lore raw
Quoted 8 lines · Matthew Wilcox
Quoted 4 lines · Marcelo Tosatti

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

This seems a bit obscure to expect an application to do. Can we make this happen automatically when we bind an rt task to a group of CPUs?

Well the way we used it was just to let things be and run in the busy loop. There could be another flush of the vmstat data and then the vmstat worker will disable itself. So two more workqueue executions before the processor completely dies down. But then we also need a period like that to trigger the NOHZ logic to switch off the timer. Right?

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

#3 lore raw
Quoted 17 lines · Christopher Lameter
Quoted 8 lines · Matthew Wilcox
Quoted 4 lines · Marcelo Tosatti

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

This seems a bit obscure to expect an application to do. Can we make this happen automatically when we bind an rt task to a group of CPUs?

Well the way we used it was just to let things be and run in the busy loop. There could be another flush of the vmstat data and then the vmstat worker will disable itself. So two more workqueue executions before the processor completely dies down. But then we also need a period like that to trigger the NOHZ logic to switch off the timer. Right?

Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Why does it need to be something userspace does? It would seem reasonable that the kernel could figure out for itself that it's about to start this CPU operating in isolated mode and flush all the work first?

#4 lore raw
Quoted 7 lines · Matthew Wilcox
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Why does it need to be something userspace does? It would seem reasonable that the kernel could figure out for itself that it's about to start this CPU operating in isolated mode and flush all the work first?

The kernel holds objects for various purposes in caches just in case. And these objects are expired when they are considered cache cold. Similarly vmstat does not fold counters into the global ones just in case more things need to be locally counted in order to prevent contention on the global counters.

The kernel cannot know that user space will not be using system calls but wants a quiet operating environment without interruptions for cache expiration and other things. The kernel can do all sorts of preventitive work to avoid deferred actions and create a OS noise free environment for the application.

#5 lore raw
In reply to Christopher Lameter
Quoted 8 lines · Christopher Lameter
Quoted 6 lines · Matthew Wilcox
Quoted 4 lines · Marcelo Tosatti

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

Quoted 8 lines
Quoted 2 lines

This seems a bit obscure to expect an application to do. Can we make this happen automatically when we bind an rt task to a group of CPUs?

Well the way we used it was just to let things be and run in the busy loop. There could be another flush of the vmstat data and then the vmstat worker will disable itself. So two more workqueue executions before the processor completely dies down. But then we also need a period like that to trigger the NOHZ logic to switch off the timer. Right?

The application should not start its time sensitive loop until the workqueues have finished execution.

Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

Thanks.

#6 lore raw
Quoted 25 lines · Marcelo Tosatti
Quoted 8 lines · Christopher Lameter
Quoted 6 lines · Matthew Wilcox
Quoted 4 lines · Marcelo Tosatti

For isolated applications that busy loop (packet processing with DPDK, for example), workqueue functions either stall (if the -rt app priority is higher than kworker thread priority) or interrupt the -rt app (if the -rt app priority is lower than kworker thread priority.

Quoted 8 lines
Quoted 2 lines

This seems a bit obscure to expect an application to do. Can we make this happen automatically when we bind an rt task to a group of CPUs?

Well the way we used it was just to let things be and run in the busy loop. There could be another flush of the vmstat data and then the vmstat worker will disable itself. So two more workqueue executions before the processor completely dies down. But then we also need a period like that to trigger the NOHZ logic to switch off the timer. Right?

The application should not start its time sensitive loop until the workqueues have finished execution.

Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Quoted 7 lines

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

Thanks.

Hi Christoph,

Can you expand on the suggestion?

TIA

#7 lore raw
In reply to Marcelo Tosatti
Quoted 6 lines · Marcelo Tosatti
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will trigger kernel threads and whatever else is pending on that processor.

Quoted 2 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread runnable then you would compromise system performance through frequent counter folding and cache cleaning etc.

#8 lore raw
Quoted 11 lines · Christopher Lameter
Quoted 6 lines · Marcelo Tosatti
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will trigger kernel threads and whatever else is pending on that processor.

Please CC linux-api on future postings that introduce stuff like this.

Quoted 8 lines
Quoted 2 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread runnable then you would compromise system performance through frequent counter folding and cache cleaning etc.

If someone goes through the trouble of setting up NOHZ, these disruptions should be only temporary and happen during the setup, no?

#9 lore raw
Quoted 7 lines · Vlastimil Babka
Quoted 6 lines · Christopher Lameter
Quoted 4 lines · Marcelo Tosatti
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will trigger kernel threads and whatever else is pending on that processor.

Please CC linux-api on future postings that introduce stuff like this.

Thanks, will do.

Quoted 11 lines
Quoted 8 lines
Quoted 2 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread runnable then you would compromise system performance through frequent counter folding and cache cleaning etc.

If someone goes through the trouble of setting up NOHZ, these disruptions should be only temporary and happen during the setup, no?

There is no way for the userspace application to know when the disruptions are gone (vmstat work function executed).

But yes, they are temporary and happen during setup.

#10 lore raw
In reply to Christopher Lameter
Quoted 11 lines · Christopher Lameter
Quoted 6 lines · Marcelo Tosatti
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will trigger kernel threads and whatever else is pending on that processor.

OK, makes sense.

About sysctl, in particular:

NOTES top

Use of this system call was long discouraged: since Linux 2.6.24, uses of this system call result in warnings in the kernel log, and in Linux 5.5, the system call was finally removed. Use the /proc/sys interface instead.

Note that on older kernels where this system call still exists, it is available only if the kernel was configured with the CONFIG_SYSCTL_SYSCALL option. Furthermore, glibc does not provide a wrapper for this system call, necessitating the use of syscall(2).

So will stick to the /proc/ suggestion.

Quoted 8 lines
Quoted 2 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread runnable then you would compromise system performance through frequent counter folding and cache cleaning etc.

Makes sense.

#11 lore raw
In reply to Christopher Lameter
Quoted 12 lines · Christopher Lameter
Quoted 6 lines · Marcelo Tosatti
Quoted 3 lines

So what we would need would be something like a sysctl that puts the system into a quiet state by completing all workqueue items. Idle all subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will trigger kernel threads and whatever else is pending on that processor.

Quoted 8 lines
Quoted 2 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as there is a single thread running, so unclear why that would be needed.

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread runnable then you would compromise system performance through frequent counter folding and cache cleaning etc.

Christopher,

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

[1] perhaps a name that does not conflict with "task mode" patchset is a better idea.

#12 lore raw
Quoted 38 lines · Marcelo Tosatti

External Email

-------------------------------------------------------------------
---

Quoted 22 lines · Christopher Lameter
Quoted 9 lines · Marcelo Tosatti
Quoted 5 lines

So what we would need would be something like a sysctl that puts the
system into a quiet state by completing all workqueue items. Idle all
subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat
workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will
trigger kernel threads and whatever else is pending on that processor.

Quoted 4 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as
there is a single thread running, so unclear why that would be needed.

Quoted 8 lines

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread
runnable then you would compromise system performance through frequent
counter folding and cache cleaning etc.

Christopher,

Quoted 7 lines

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

This is what task isolation patch now does. Per-task attribute is used when dealing with a task (normally current task on its dedicated CPU), per-CPU attribute is used when other CPUs are involved (so they don't have to chase tasks that are running on other CPUs) or when performing low-level operations on entry and exit. Also since this per-CPU attribute is only updated from the local CPU, this significantly simplifies access to it.

The difficult part of this approach is how to properly handle a situation when for whatever reason isolation must be broken by an interrupt of whatever origin, and there is no way to avoid it.

And, of course, there is a matter of having to clean up all other sources of avoidable interrupts.

Since I first and foremost care about eliminating all disturbances for a running userspace task, my approach is to allow disabling everything including "unavoidable" synchronization IPIs, and make kernel entry procedure recognize that some delayed synchronization is necessary while avoiding race conditions. As far as I can tell, not everyone wants to go that far, and it may make sense to allow "almost isolated tasks" that still receive normal interrupts, including IPIs and page faults. While that would be useless for the purposes that task isolation patch was developed for, I recognize that some might prefer that to be one of the options set by the same prctl call. This still remains close enough to the design of task isolation -- same idea of something that affects CPU but being tied to a given task (and dying with it), same model of handling attributes, etc.

Maybe there can be a mask of what we do and don't want to avoid for the task. Say, some may want to only allow page faults or syscalls. Or re- enter isolation on breaking without notifying the userspace.

Then we may be able to combine those things, or make them separate features that can be enabled and disabled, but all tied to a single prctl. It will be possible to, say, check which features are implemented and then set a mode for the current task.

Quoted 32 lines

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

[1] perhaps a name that does not conflict with "task mode" patchset is a better idea.

#13 lore raw
Quoted 56 lines · Alex Belits
Quoted 38 lines · Marcelo Tosatti

External Email

-------------------------------------------------------------------
---

Quoted 22 lines · Christopher Lameter
Quoted 9 lines · Marcelo Tosatti
Quoted 5 lines

So what we would need would be something like a sysctl that puts the
system into a quiet state by completing all workqueue items. Idle all
subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat
workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will
trigger kernel threads and whatever else is pending on that processor.

Quoted 4 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as
there is a single thread running, so unclear why that would be needed.

Quoted 8 lines

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread
runnable then you would compromise system performance through frequent
counter folding and cache cleaning etc.

Christopher,

Quoted 7 lines

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

This is what task isolation patch now does. Per-task attribute is used when dealing with a task (normally current task on its dedicated CPU), per-CPU attribute is used when other CPUs are involved (so they don't have to chase tasks that are running on other CPUs) or when performing low-level operations on entry and exit. Also since this per-CPU attribute is only updated from the local CPU, this significantly simplifies access to it.

Quoted 3 lines

The difficult part of this approach is how to properly handle a situation when for whatever reason isolation must be broken by an interrupt of whatever origin, and there is no way to avoid it.

Right.

Quoted 2 lines

And, of course, there is a matter of having to clean up all other sources of avoidable interrupts.

Two questions:

What is the reason for not allowing _any_ interruption? Because it might be the case (and it is in the vRAN use cases our customers target), that some amount of interruption is tolerable.

For example, for one use case 20us (of interruptions) every 1ms of elapsed time is tolerable.

Quoted 2 lines

Since I first and foremost care about eliminating all disturbances for a running userspace task,

Why?

Quoted 5 lines

my approach is to allow disabling everything
including "unavoidable" synchronization IPIs, and make kernel entry procedure recognize that some delayed synchronization is necessary while avoiding race conditions. As far as I can tell, not everyone wants to go that far,

Suppose it depends on how long each interruption takes. Upon the suggestion from Thomas and Frederic, i've been thinking it should be possible, with the tracing framework, to record the length of all interruptions to a given CPU and, every second check how many have happened (and whether the sum of interruptions exceeds the acceptable threshold).

Its not as nice as the task isolation patch (in terms of spotting the culprit, since one won't get a backtrace on the originating CPU in case of an IPI for example), but it should be possible to verify that the latency threshold is not broken (which is what the application is interested in, isnt it?).

Quoted 11 lines

and it may make sense to allow "almost isolated
tasks" that still receive normal interrupts, including IPIs and page faults.

While that would be useless for the purposes that task isolation patch was developed for, I recognize that some might prefer that to be one of the options set by the same prctl call. This still remains close enough to the design of task isolation -- same idea of something that affects CPU but being tied to a given task (and dying with it), same model of handling attributes, etc.

Quoted 3 lines

Maybe there can be a mask of what we do and don't want to avoid for the task. Say, some may want to only allow page faults or syscalls. Or re- enter isolation on breaking without notifying the userspace.

OK, i will try to come up with an interface that allows additional attributes - please review and let me know if it works for task isolation patchset.

Can you talk a little about the signal handling part? What type of applications are expected to perform once isolation is broken?

Thanks!

Quoted 38 lines

Then we may be able to combine those things, or make them separate features that can be enabled and disabled, but all tied to a single prctl. It will be possible to, say, check which features are implemented and then set a mode for the current task.

Quoted 32 lines

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

[1] perhaps a name that does not conflict with "task mode" patchset is a better idea.

#14 lore raw
Quoted 114 lines · Marcelo Tosatti
Quoted 56 lines · Alex Belits
Quoted 38 lines · Marcelo Tosatti

External Email

-------------------------------------------------------------------
---

Quoted 22 lines · Christopher Lameter
Quoted 9 lines · Marcelo Tosatti
Quoted 5 lines

So what we would need would be something like a sysctl that puts the
system into a quiet state by completing all workqueue items. Idle all
subsystems that need it and put the cpu into NOHZ mode.

Are you suggesting that instead of a specific file to control vmstat
workqueue only, a more generic sysctl could be used?

Yes. Introduce a sysctl to quiet down the system. Clean caches that will
trigger kernel threads and whatever else is pending on that processor.

Quoted 4 lines

About NOHZ mode: the CPU should enter NOHZ automatically as soon as
there is a single thread running, so unclear why that would be needed.

Quoted 8 lines

There are typically pending actions that still trigger interruptions.

If you would immediately quiet down the system if there is only one thread
runnable then you would compromise system performance through frequent
counter folding and cache cleaning etc.

Christopher,

Quoted 7 lines

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

This is what task isolation patch now does. Per-task attribute is used when dealing with a task (normally current task on its dedicated CPU), per-CPU attribute is used when other CPUs are involved (so they don't have to chase tasks that are running on other CPUs) or when performing low-level operations on entry and exit. Also since this per-CPU attribute is only updated from the local CPU, this significantly simplifies access to it.

Quoted 3 lines

The difficult part of this approach is how to properly handle a situation when for whatever reason isolation must be broken by an interrupt of whatever origin, and there is no way to avoid it.

Right.

Quoted 2 lines

And, of course, there is a matter of having to clean up all other sources of avoidable interrupts.

Two questions:

What is the reason for not allowing _any_ interruption? Because it might be the case (and it is in the vRAN use cases our customers target), that some amount of interruption is tolerable.

For example, for one use case 20us (of interruptions) every 1ms of elapsed time is tolerable.

Quoted 2 lines

Since I first and foremost care about eliminating all disturbances for a running userspace task,

Why?

Quoted 5 lines

my approach is to allow disabling everything
including "unavoidable" synchronization IPIs, and make kernel entry procedure recognize that some delayed synchronization is necessary while avoiding race conditions. As far as I can tell, not everyone wants to go that far,

Suppose it depends on how long each interruption takes. Upon the suggestion from Thomas and Frederic, i've been thinking it should be possible, with the tracing framework, to record the length of all interruptions to a given CPU and, every second check how many have happened (and whether the sum of interruptions exceeds the acceptable threshold).

Its not as nice as the task isolation patch (in terms of spotting the culprit, since one won't get a backtrace on the originating CPU in case of an IPI for example), but it should be possible to verify that the latency threshold is not broken (which is what the application is interested in, isnt it?).

Quoted 11 lines

and it may make sense to allow "almost isolated
tasks" that still receive normal interrupts, including IPIs and page faults.

While that would be useless for the purposes that task isolation patch was developed for, I recognize that some might prefer that to be one of the options set by the same prctl call. This still remains close enough to the design of task isolation -- same idea of something that affects CPU but being tied to a given task (and dying with it), same model of handling attributes, etc.

Quoted 3 lines

Maybe there can be a mask of what we do and don't want to avoid for the task. Say, some may want to only allow page faults or syscalls. Or re- enter isolation on breaking without notifying the userspace.

Quoted 6 lines

OK, i will try to come up with an interface that allows additional attributes - please review and let me know if it works for task isolation patchset.

Can you talk a little about the signal handling part? What type of applications are expected to perform once isolation is broken?

Hi Alex,

Say, couldnt a notification from the trace-latency infrastructure, notifying the admin that latency was exceeded due to interruptions

x us (backtrace of x) + y us (backtrace of y) + z us (backtrace of z) >= maxlatency us

With an application which continue to handle traffic, be as functional as the signal? (then again, don't know exactly what you do in the signal handler...).

Could also count "enter kernel <-> exit kernel" window as in interruption such a scheme.

Quoted 40 lines

Thanks!

Quoted 38 lines

Then we may be able to combine those things, or make them separate features that can be enabled and disabled, but all tied to a single prctl. It will be possible to, say, check which features are implemented and then set a mode for the current task.

Quoted 32 lines

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

[1] perhaps a name that does not conflict with "task mode" patchset is a better idea.

#15 lore raw
Quoted 10 lines · Marcelo Tosatti
Quoted 1 line · Marcelo Tosatti

On Sat, Nov 28, 2020 at 03:49:38AM +0000, Alex Belits wrote:

Hi Alex,

Say, couldnt a notification from the trace-latency infrastructure, notifying the admin that latency was exceeded due to interruptions

x us (backtrace of x) + y us (backtrace of y) + z us (backtrace of z)

Quoted 1 line

= maxlatency us

I believe, for performance and readability reasons we may want to replace backtrace with "cause" record that lists specific recognized cause of entering kernel (page fault, interrupt) with event-specific arguments that don't show up in backtrace, such as syscall, address, interrupt number, IPI call, timer. And then, optionally, a backtrace.

It also should be taken into account that a backtrace is only useful if it is taken at the right point. We already know exactly what the backtrace is right after entering kernel, in task flags processing loop, or right before the exit. To determine anything important we have to do something (and possibly record a backtrace) in a specific handler, syscall, etc., but there we mostly care about the last function anyway.

Quoted 4 lines

With an application which continue to handle traffic, be as functional as the signal? (then again, don't know exactly what you do in the signal handler...).

If "the admin" is actually a manager process using an interface such as netlink, to collect this information from kernel. Isolated process wouldn't be able to use this interface until it knows that it exited isolation, because communication with kernel involves a syscall, so it will still need something -- notification through shared memory from the manager process, or possibly vdso, however touching vdso often may affect performance.

There is one more piece of information that I want to record, remote and cause. Remote cause is whatever was set by _another_ CPU before calling this one, possibly with its backtrace. In that case backtrace is useful because we already know that we are sending the IPI, however what we need is to know, from where and how that was called.

Quoted 3 lines

Could also count "enter kernel <-> exit kernel" window as in interruption such a scheme.

This is pretty much what the current patch does, conditionally on isolated state set in per-CPU flags, now that entry and exit hooks are in their places. If there will be tracing/logging done, timing can be collected there, and causes determined in a specific handler for them. We can add more flags for turning this mechanism on without full task isolation.

Signature · 1 line
Alex
#16 lore raw
In reply to Marcelo Tosatti
Quoted 8 lines · Marcelo Tosatti

Two questions:

What is the reason for not allowing _any_ interruption? Because it might be the case (and it is in the vRAN use cases our customers target), that some amount of interruption is tolerable.

For example, for one use case 20us (of interruptions) every 1ms of elapsed time is tolerable.

I agree that for many applications that would be sufficient, and if so, we can avoid the rest of the mechanism, However I know three types of applications where full isolation is absolutely necessary.

1. Physical process control. A program continuously polls data from sensors, processes it, determines the state of controlled device or process, and issues commands or tunes parameters, controlling it. An unpredictable delay caused by an interrupt or other performance-affecting event can break the timing of this mechanism.

Even taking into account that usually safety requirements demand that some low-latency reaction should be performed without CPU involvement, some of the control logic may demand involvement of a CPU usually within a closed control loop. For example, tracking the state of an RF connection and adjusting the signal, analysis of measurements and control of a mechanical system, including elasticity and vibration in industrial and transportation applications, all require a large amount of calculations, and benefit from reduced amount of buffering and delays. In case of RF this allows to maintain more reliable connections. Mechanical systems can have greater precision and lower stress on the components because such system can easily implement dampening and compensation of deformation and deterioration.

Usually when such processing is necessary, the "fast" part of it is performed on a microcontroller, separate CPU core built into an ASIC or even a "soft CPU" implemented on an FPGA, while "slow" calculations are performed by a large CPU or SoC. This, however, places severe limitations on the software design and requires engineers to waste "expensive" resources such as including PCIe links into microcontrollers, building ASICs, implementing soft CPU cores on FPGA, etc. while the use of CPU cores of modern CPUs and SoC is limited. Sometimes a large processing mechanism is built out of DSP blocks of FPGA and its built-in static RAM, while more capable SIMD of a CPU remains under-used.

2. Audio processing. A program implements a set of filters and mixers, processing multiple audio streams in a live performance. Processing should be synchronized not only between individual microphones, speakers and processors, but, when used as a part of sound reinforcement system, also with propagation of sound through the environment that bypasses the audio system but is subject to the acoustics of the building. The amount of data is large, however calculations are always the same, so it is possible to tune all delays to match the projected or measured timing. Program runs at the sample rate of the signals, with processing algorithms already creating delays, so additional buffering would place total delay out of the available range.

This can be seen as a subset of controlling the mechanical system, except usually a control loop, if present, is much slower (such as adapting to changing acoustical properties), however processing of incoming data includes very large amounts of calculations that should be performed on a full-featured CPU. The total amount of data that should be available to a CPU core at a time, usually can fit into its cache, and if sufficient cache allocation or partitioning is available, all necessary calculations (digital filters, mixing, etc.) can be reliably performed with minimal latency. Interrupts break this model, causing unpredictable cache invalidation, so design has to take into account not just the time spent processing the interrupt but also delays for re-filling the caches with data that normally remains there.

3. Parallel handling of network packets. Modern network-oriented SoCs have hardware scheduling mechanisms that can distribute packets processing, including packet processing within the same flow, to multiple CPU cores, form processing pipelines, etc. Flow-related state, if present, can be kept within the scheduling mechanism, and not handled by CPU cores. When CPUs work in a predictable manner, this allows fast processing of network traffic regardless of the distribution of the amount of data between flows or other details, save for situations that warrant some kind of additional per-flow processing that can't be performed in a stateless manner (and that may be still offloaded to dedicated CPU cores for "slow path"). This is fundamentally different from the model in which each flow is kept on a single CPU for stateful processing and buffering.

When interrupt happens, a core is temporarily excluded from this orchestrated process, and the packets that it handles stay in buffer, possibly keeping the whole flows waiting for reordering before the output. Every time this happens, buffers end up holding more data than they would be without interruption, so the whole system can provide lower throughput before it has to drop packets. Handling network buffers and CPU access to them is usually extremely optimized in such system, CPU usually only accesses a subset of header data in network buffers, then makes whatever decisions that are not already done by a complex system of hardware header parsers, CAMs and queues that precede and follow this CPU-based processing.

In many cases all three types applications suffer from insufficiently flexible cache management, however recently many CPUs and SoCs are built specifically for the above mentioned purposes, and more complex cache management can be easily added to them. When implementing those it's much easier to allow optimization for running an application with predictable limits on access, that will fall back into un-optimized state when a predictable pattern is broken. This means, designers of both hardware and software can breathe much easier if OS can guarantee interrupt-free environment for timing-critical tasks. Outside of those tasks it would be completely harmless for cache to get out of the optimized state as long as consistency is maintained by hardware, so there is no reason to expect any incompatibility or violation of specifications that would require any special software support. However as a person working on the software side of a hardware company, I can't request such a feature when I know that whatever they will build, will have to crash down like a Jenga tower every second, leave alone milliseconds.

To support this kind of tasks, various companies used either full- featured RTOS or "bare metal environments" that are basically specialized extremely reduced OSes, designed to run up to one application per CPU core with some minimal initialization and resource allocation. While I agree that this is not the place to evaluate merit of those approaches in general, I can say that my recent experience with both developers and users, including but not limited to myself being in both roles, shows that many would rather prefer if Linux provided this environment when running some tasks after initialization in a normal mode. If the task can go back and forth between isolated and non-isolated mode, that would greatly simplify re-configuration, and any mechanism for communicating outside of isolated environment can be a bonus, however isolation itself is the important part.

This was not the case in early 2000s, when embedded systems were built on single-core SoCs and microcontrollers. Then either everything had to be integrated in a single task under "bare metal", or everything depended on interrupt processing provided by the OS. Now, when network and embedded-oriented chips are built with tens of cores, sometimes it's better if OS prepared everything and left the task, along with its core and devices that it handles, alone and undisturbed. And if this can be done entirely within Linux, consistently and integrated with other related features and design of its subsystems, I think, this is justified.

Quoted 6 lines
Quoted 4 lines

Since I first and foremost care about eliminating all disturbances for
a running userspace task,

Why?

Mostly because I work on (3) from the list above. However experience with other mentioned uses contributed to that, too. I think, some very useful work is already done in Linux for limiting interrupts and disturbances in general and for isolated CPUs in particular. One additional step that will allow to provide a disturbances-free environment and greatly expand possible applications of Linux kernel looks to me like a useful applications of more efforts.

Quoted 14 lines
Quoted 6 lines

my approach is to allow disabling everything
including "unavoidable" synchronization IPIs, and make kernel entry procedure recognize that some delayed synchronization is necessary while avoiding race conditions. As far as I can tell, not everyone wants to go that far,

Suppose it depends on how long each interruption takes. Upon the suggestion from Thomas and Frederic, i've been thinking it should be possible, with the tracing framework, to record the length of all interruptions to a given CPU and, every second check how many have happened (and whether the sum of interruptions exceeds the acceptable threshold).

Quoted 5 lines

Its not as nice as the task isolation patch (in terms of spotting the culprit, since one won't get a backtrace on the originating CPU in case of an IPI for example), but it should be possible to verify that the latency threshold is not broken (which is what the application is interested in, isnt it?).

With the current version of the isolation patch I have completely removed the diagnostics part of the code. I want to re-introduce a much cleaner implementation of "interrupt cause diagnostics" on top of it, mostly for the purpose of development -- at least I think, it will give me a better tool to chase the root causes of interrupts that task isolation can see.

Now that I have functions where all kernel entry and exit passes for isolated tasks, and some easily readable indication of an isolated CPU, it should be easy to collect both "We are going to send an IPI to a task in this special state because..." and "We are doing something specific in kernel, and it happens, our task was in this special state". It may be that just using tracing this can be done as well, however if we will expand conditions for cause recording beyond just fully isolated task, a separate recording mechanism would be able to collect useful information and statistics with less of its own impact on latency and performance. At least, I think, it makes sense to try separately from task isolation implementation itself, that no longer depends on knowing why kernel was entered.

As for measuring latency, as I have mentioned before, it's not just the impact of time being spent in kernel in interrupt processing that matters, it's also all the memory that is being accessed in the process of doing so, and whatever performance-affecting changes, such as TLB flushes or expected delayed work, that made the call necessary in the first place. And for non-isolated tasks there is also a possibility of preemption that can further complicate the picture with timing.

Quoted 23 lines
Quoted 17 lines

and it may make sense to allow "almost isolated tasks" that still receive normal interrupts, including IPIs and page
faults.

While that would be useless for the purposes that task isolation patch was developed for, I recognize that some might prefer
that to be one of the options set by the same prctl call. This still
remains close enough to the design of task isolation -- same idea of
something that affects CPU but being tied to a given task (and dying
with it), same model of handling attributes, etc.

Quoted 5 lines

Maybe there can be a mask of what we do and don't want to avoid for the
task. Say, some may want to only allow page faults or syscalls. Or re-
enter isolation on breaking without notifying the userspace.

Quoted 3 lines

OK, i will try to come up with an interface that allows additional attributes - please review and let me know if it works for task isolation patchset.

I think, in addition to enable/disable and configuring a signal we will need some flags that enable and disable features, such as full isolation and avoidance of specific events and causes, logging (if supported), etc.

Quoted 3 lines

Can you talk a little about the signal handling part? What type of applications are expected to perform once isolation is broken?

First and foremost, a task may be killed because a signal was sent to it by another task, terminal, socket or pipe. Then it's completely normal signal processing, possibly a userspace cleanup, reloading, etc., except isolation breaking happens on kernel entry.

Second, application may encounter an early exit from isolation immediately after entering because some kernel event that was supposed to cause IPIs to all non-isolated tasks, happened while it was entering. Then all it has to do is re-enter.

Third, and this is what I do in libtmc, isolation breaking is handled by notifying a separate isolation manager thread or process, so it can check the state of tasks and timers, and decide if and when it should attempt re-enter, ask the task to leave and re-enter the CPU, etc. I will be happier if those actions became unnecessary, however for now it's the easiest way to check if anything and what in particular may prevent the task from entering isolation. Maybe it will make sense to make libtmc use ptrace() on a task from isolation manager, so isolation manager will handle that signal when necessary, and then notify the task.

As an alternative I have added a simple readable isolation mask that can be checked by processes (ones that are not isolated) such as isolation manager, and if there will be a separate mechanism for reporting isolation breaking, it may be used instead of the signal (and then isolation manager will be able to communicate with the task using shared memory, signal or other means).

The original patch used a signal, and I can't predict what else users may want to do on isolation breaking, so I have kept that interface unchanged.

Signature · 1 line
Alex
#17 lore raw
In reply to Marcelo Tosatti
Quoted 2 lines · Marcelo Tosatti

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

Right I think that was a good approach.

Quoted 4 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Sounds good but what would this do? Give a warning like the isolation patchset?

Quoted 3 lines

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

Yes good.

Quoted 16 lines

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

Quoted 7 lines

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

Maybe do both like in the isolation patchset?

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

#18 lore raw
Quoted 7 lines · Christoph Lameter
Quoted 2 lines · Marcelo Tosatti

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

Right I think that was a good approach.

Quoted 7 lines
Quoted 4 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Sounds good but what would this do? Give a warning like the isolation patchset?

Could be. Or disallow certain operations such as CPU hotplug, ring buffer resize, etc.

Quoted 28 lines
Quoted 3 lines

This per-CPU attribute can be used to, for example, return -EBUSY from ring_buffer_resize() (or any other IPI generating activity which can return an error to userspace).

Yes good.

Quoted 22 lines

So rather than:

prctl(PR_QUIESCE_CPU) (current interface, similar to
initial message on the thread but with prctl rather than sysfs)

To be called before real time loop, one would have:

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Quoted 7 lines
Quoted 1 line

Any objections against such an interface ?

Maybe do both like in the isolation patchset?

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

Yes, thanks.

#19 lore raw
In reply to Christoph Lameter
Quoted 6 lines · Christoph Lameter
Quoted 2 lines · Marcelo Tosatti

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

Right I think that was a good approach.

prctl() is the right thing to do.

Quoted 7 lines
Quoted 4 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Sounds good but what would this do? Give a warning like the isolation patchset?

This all needs a lot more thought about the overall picture. We already have too many knobs and ad hoc hooks which fiddle with isolation.

The current CPU isolation is a best effort approach and I agree that for more strict isolation modes we need to be able to enforce that and hunt down offenders and think about them one by one.

Quoted 1 line
Quoted 1 line

To be called before real time loop, one would have:

Can we please agree in the first place, that "real time" is absolutely the wrong term here?

It's about running undisturbed CPU bound computations whatever nature they are. It does not matter whether that loop does busy polling ala DPDK, whether it runs a huge math computation on a data set or whatever people come up with.

Quoted 10 lines
Quoted 10 lines

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

Plus returning an error if the task has no permissions to request this. This should not be an unprivileged prctl ever.

Quoted 6 lines
Quoted 4 lines

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

Maybe do both like in the isolation patchset?

We really want to define the scopes first. And here you go:

Quoted 3 lines

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

So you say some code can tolerate a few interrupts, then comes Alex and says 'no disturbance' at all.

The point is that all of this shares the mechanisms to quiesce certain parts of the kernel so this wants to build common infrastructure and the prctl(ISOLATION, MODE) mode argument defines the scope of isolation which the task asks for and the infrastructure decides whether it can be granted and if so orchestrates the operation and provides a common infrastructure for instrumentation, violation monitoring etc.

We really need to stop to look at particular workloads and defining adhoc solutions tailored to their particular itch if we don't want to end up with an uncoordinated and unmaintainable zoo of interfaces, hooks and knobs.

Just looking at the problem at hand as an example. NOHZ already issues quiet_vmstat(), but it does not cancel already scheduled work. Now Marcelo wants a new mechanism which is supposed to cancel the work and then Alex want's to prevent it from being rescheduled. If that's not properly coordinated this goes down the drain very fast.

So can we please come up with a central place to handle this prctl() with a future proof argument list so the various isolation needs can be expressed as required?

That allows Marcelo to start tackling the vmstat side and Alex can utilize that and build the other parts into it piece by piece.

Thanks,

tglx

#20 lore raw
Quoted 1 line · Thomas Gleixner

prctl() is the right thing to do.

Ok great consensus on that one.

Quoted 8 lines
Quoted 7 lines
Quoted 4 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Sounds good but what would this do? Give a warning like the isolation patchset?

Quoted 6 lines

This all needs a lot more thought about the overall picture. We already have too many knobs and ad hoc hooks which fiddle with isolation.

The current CPU isolation is a best effort approach and I agree that for more strict isolation modes we need to be able to enforce that and hunt down offenders and think about them one by one.

There are two apprahces actually to make the OS quiet. One is the best effort approach which is more like the current NOHZ one with additional actions to flush things. The other is the strict approach were one wants a guarantee that the OS does not do anything at all.

Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

To be called before real time loop, one would have:

Can we please agree in the first place, that "real time" is absolutely the wrong term here?

Sorry I once swore that I would not use real time since that term is so damaged by multiple meanings and marketing endeavor.

"to be called before a loop without any disturbance by the operating system"

Quoted 4 lines

It's about running undisturbed CPU bound computations whatever nature they are. It does not matter whether that loop does busy polling ala DPDK, whether it runs a huge math computation on a data set or whatever people come up with.

Right.

Quoted 6 lines
Quoted 3 lines

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

So you say some code can tolerate a few interrupts, then comes Alex and says 'no disturbance' at all.

Yes that is the current NOHZ approach. You switch it on and after the OS detects are polling loop it will quiet things down. Instead of detecting it we are actively telling the OS to quiet down now.

Quoted 4 lines

We really need to stop to look at particular workloads and defining adhoc solutions tailored to their particular itch if we don't want to end up with an uncoordinated and unmaintainable zoo of interfaces, hooks and knobs.

True....Multiple subsystem needs to be hooked into this to quiet things down.

Quoted 2 lines

That allows Marcelo to start tackling the vmstat side and Alex can utilize that and build the other parts into it piece by piece.

Yup. I agree.

#21 lore raw
Quoted 5 lines · Christoph Lameter
Quoted 1 line · Thomas Gleixner

prctl() is the right thing to do.

Ok great consensus on that one.

That's the easy part :)

Quoted 8 lines
Quoted 3 lines

The current CPU isolation is a best effort approach and I agree that for more strict isolation modes we need to be able to enforce that and hunt down offenders and think about them one by one.

There are two apprahces actually to make the OS quiet. One is the best effort approach which is more like the current NOHZ one with additional actions to flush things. The other is the strict approach were one wants a guarantee that the OS does not do anything at all.

And here the consensus stops again :)

The point is that between the relaxed best effort / heuristics based scenario and the 'user space task asks for absolute silence' scenario is a huge difference:

Is this really a black and white decision?

Definitely not. That would be again an imposed policy decision which is wrong to begin with. We burnt ourself with that over and over so can we please and if it's just for this particular problem learn from history?

The kernel provides mechanisms but does not impose policies unless there is no other choice.

And as we know that there are quite some shades of grey, there is lots of choice and we need to come up with solutions for delegating the policy decision to the user/admin and not just provide a off/on knob.

This 'isolate either perhaps or everything' appraoch is just wrong. The partisan thinking is obviously popular in the US, but it has no business in making technically sensible desicions.

Quoted 6 lines
Quoted 2 lines

So you say some code can tolerate a few interrupts, then comes Alex and says 'no disturbance' at all.

Yes that is the current NOHZ approach. You switch it on and after the OS detects are polling loop it will quiet things down. Instead of detecting it we are actively telling the OS to quiet down now.

Kinda. We want to provide mechanisms to quiet certain aspects of the OS and to enable enforcement of that, but again, that's not on/off it has to be configurable / selectable.

Again: I fundamentaly disagree with the proposed task isolation patches approach as they leave no choice at all.

There is a reasonable middle ground where an application is willing to pay the price (delay) until the reqested quiescing has taken place in order to run undisturbed (hint: cache ...) and also is willing to take the addtional overhead of an occacional syscall in the slow path without tripping some OS imposed isolation safe guard.

Aside of that such a granular approach does not necessarily require the application to be aware of it. If the admin knows the computational pattern of the application, e.g.

 1     read_data_set() <- involving syscalls/OS obviously
 2     compute_set()   <- let me alone
 3     save_data_set() <- involving syscalls/OS obviously

repeat the above...

then it's at his discretion to decide to inflict a particular isolation set on the task which is obviously ineffective while doing #1 and #3 but might provide the so desired 0.9% boost for compute_set() which dominates the judgement.

That's what we need to think about and once we figured out how to do that it gives Marcelo the mechanism to solve his 'run virt undisturbed by vmstat or whatever' problem and it allows Alex to build his stuff on it.

Summary: The problem to be solved cannot be restricted to

    self_defined_important_task(OWN_WORLD);

Policy is not a binary on/off problem. It's manifold across all levels of the stack and only a kernel problem when it comes down to the last line of defence.

Up to the point where the kernel puts the line of last defence, policy is defined by the user/admin via mechanims provided by the kernel.

Emphasis on "mechanims provided by the kernel", aka. user API.

Just in case, I hope that I don't have to explain what level of scrunity and thought this requires.

Thanks,

tglx

#22 lore raw
Quoted 9 lines · Thomas Gleixner
Quoted 8 lines
Quoted 3 lines

The current CPU isolation is a best effort approach and I agree that for more strict isolation modes we need to be able to enforce that and hunt down offenders and think about them one by one.

There are two apprahces actually to make the OS quiet. One is the best effort approach which is more like the current NOHZ one with additional actions to flush things. The other is the strict approach were one wants a guarantee that the OS does not do anything at all.

Quoted 5 lines

And here the consensus stops again :)

The point is that between the relaxed best effort / heuristics based scenario and the 'user space task asks for absolute silence' scenario is a huge difference:

The two approaches are:

1. Enforce silence and abort if the application tries anything that jeopardizes that silence (f.e. a syscall that cannot directly complete, a major page fault etc).

This mode needs to work like an on/off switch so that the application can exit the mode and do regular system calls. Only specially designed software will be able to use this mode since it is so restrictive and care needs to be taken to enable/disable this mode.

2. Silence now (dump all caches, correlate counters, all pending work finishes). This is a one shot approach. Anything later that causes counter increments, cache population etc etc may occur but will then cause additional latency required to re-enable the caches, statistics threads and so on and so on.

The silence now function will be used when the app waits for an event that may occur shortly and the reaction time to that event needs to be as low latency as possible. F.e. The app may be in a complex polling loop that should not be interrupted. Once an event is detected syscalls etc could potentially occur (depending on the event). When the app goes back to the polling loop it will do another "silence now" call.

Quoted 1 line

Is this really a black and white decision?

These are two different modes of usage.

Quoted 3 lines

And as we know that there are quite some shades of grey, there is lots of choice and we need to come up with solutions for delegating the policy decision to the user/admin and not just provide a off/on knob.

One of these choices is not an on-off knob.

Quoted 2 lines

Again: I fundamentaly disagree with the proposed task isolation patches approach as they leave no choice at all.

There are no degres of gray here. I dont understand why you have these concerns.

Quoted 3 lines

pattern of the application, e.g.

1 read_data_set() <- involving syscalls/OS obviously

??? You cannot use syscalls for high speed or low latency I/O!!!

Quoted 2 lines

2 compute_set() <- let me alone
3 save_data_set() <- involving syscalls/OS obviously

Again saving data may not be possible through the kernel since syscalls may have too much overhead and latency.

Quoted 1 line

repeat the above...

There is a fundamental misunderstanding here. This is not primarily about compute but about I/O. In particular I/O that does not involve the kernel. RDMA or things like DPDK, SPDK or other low hardware level things.

Typically a user space poll loop checks numerous memory locations related to this I/O or shared memory areas where other cpus interact with the thread that wants to be OS noise free.

Quoted 7 lines

Summary: The problem to be solved cannot be restricted to

    self_defined_important_task(OWN_WORLD);

Policy is not a binary on/off problem. It's manifold across all levels of the stack and only a kernel problem when it comes down to the last line of defence.

This a clearly defined set of functions and I am not sure how policy fits into that.

#23 lore raw
Quoted 9 lines · Christoph Lameter

On Thu, 3 Dec 2020, Thomas Gleixner wrote:
Again saving data may not be possible through the kernel since syscalls may have too much overhead and latency.

Quoted 1 line

repeat the above...

There is a fundamental misunderstanding here. This is not primarily about compute but about I/O. In particular I/O that does not involve the kernel. RDMA or things like DPDK, SPDK or other low hardware level things.

The fundamental misunderstanding is that people just look at and care about their own turf.

The above is valid in compute intensive workloads where the compute dominates the whole scenario. Not being disturbed there is a gain because of not losing cache locality due to interrupts, IPIs or whatever.

Quoted 6 lines
Quoted 3 lines

Policy is not a binary on/off problem. It's manifold across all levels of the stack and only a kernel problem when it comes down to the last line of defence.

This a clearly defined set of functions and I am not sure how policy fits into that.

It's about silencing different and largely independent parts of the OS on a particular CPU. Just defining upfront that there is only the choice of all or nothing _is_ policy.

There is a very wide range of use case scenarios out there and just because the ones which you care about needs X does not mean that X is the right thing for everybody else. You still can have X and let other people define their own set of things they want to be protected against.

Aside of that having it selectively is a plus for debugability, testing etc.

All or nothing is always the worst choice if a more fine grained approach is possible with no big effort. Granted there are things where you only can say: all or nothing, but that's definitely not the case here.

Thanks,

tglx

#24 lore raw
Quoted 7 lines · Thomas Gleixner
Quoted 2 lines · Christoph Lameter

This a clearly defined set of functions and I am not sure how policy fits into that.

It's about silencing different and largely independent parts of the OS on a particular CPU. Just defining upfront that there is only the choice of all or nothing _is_ policy.

Plus about the way to silence them because that's a matter of costs. Depending on the usage scenario you want to carefully weigh the costs against the benefits.

If you go into I/O polling forever you don't care how long it takes to fully quiesce the CPU. It simply does not matter at all.

In a real-world usecase we had the situation of compute bursts and an unfortunate hw enforced requirement to go into the kernel between them for synchronization between the compute threads and hardware (A quick hardware assisted save/load).

Unmodified NOHZ full accumulated to more than 6% loss compared to a fully undisturbed run. Most of it was caused by cache effects and not by the actually used CPU time.

A full enforced quiescing upfront gained ~2-3%, but a lazy approach of accepting that some stuff might happen once and does not happen again gained almost 5%. In that particular scenario 5% _is_ a huge win.

There is a world outside of the high frequency gambling bubble and there is neither a technical nor a justification to declare that everything has to be a nail just because the kernel provides is a hammer.

Thanks,

tglx

#25 lore raw
In reply to Thomas Gleixner
Quoted 15 lines · Thomas Gleixner
Quoted 6 lines · Christoph Lameter
Quoted 2 lines · Marcelo Tosatti

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

Right I think that was a good approach.

prctl() is the right thing to do.

Quoted 5 lines
Quoted 4 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Quoted 5 lines
Quoted 2 lines

Sounds good but what would this do? Give a warning like the isolation patchset?

This all needs a lot more thought about the overall picture. We already have too many knobs and ad hoc hooks which fiddle with isolation.

Well this would mainly add "task->is_isolated" and therefore (when given task is scheduled on CPU), "cpu->is_running_isolated_task". One can then use that information from the individual places in the kernel to make decisions.

Quoted 3 lines

The current CPU isolation is a best effort approach and I agree that for more strict isolation modes we need to be able to enforce that and hunt down offenders and think about them one by one.

What we see in practice, for vRAN scenarios is the following: There are per-application and even "per-installation" latency requirements (lets say, considering a packet travelling a number of forwarding hosts). Depending on:

* The end to end desired packet latency.

* The number of links, and latency of each link.

One can give each forwarding node an "allowed interruption sum per fixed period".

Or, for 4G/5G vRAN application requirement (due to HARQ response times, see http://dl.ifip.org/db/conf/icin/icin2016/1570230300.pdf), so far that is 100us per 1ms, or 50us per 1ms (on the safe side of the 100us) going down to 20us per 1ms.

If the kernel can keep:

1) How long each interruption took, that happened in a given period.
2) If the sum of those interruptions crosses a given threshold.

It would be useful to get traces of those interruptions (tracing this manually, on the field, _after_ reports of excessive latency on the application is quite difficult to do).

A scheme which parses trace entries in userspace would only trigger after processing the trace entries (and finding out about the over-threshold interruption).

So it would be:

1) Asynchronous.
2) Application would not be informed.

But it seems that a "0us tolerance with synchronous notifications" (task mode patchset) is also a valid use-case.

Quoted 9 lines
Quoted 1 line
Quoted 1 line

To be called before real time loop, one would have:

Can we please agree in the first place, that "real time" is absolutely the wrong term here?

It's about running undisturbed CPU bound computations whatever nature they are. It does not matter whether that loop does busy polling ala DPDK, whether it runs a huge math computation on a data set or whatever people come up with.

Agree. Should say "interruption length".

Quoted 22 lines
Quoted 11 lines
Quoted 11 lines

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

Plus returning an error if the task has no permissions to request this. This should not be an unprivileged prctl ever.

Quoted 6 lines
Quoted 4 lines

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

Maybe do both like in the isolation patchset?

Quoted 8 lines

We really want to define the scopes first. And here you go:

Quoted 3 lines

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

So you say some code can tolerate a few interrupts, then comes Alex and says 'no disturbance' at all.

Some setups can, some don't.

Quoted 11 lines

The point is that all of this shares the mechanisms to quiesce certain parts of the kernel so this wants to build common infrastructure and the prctl(ISOLATION, MODE) mode argument defines the scope of isolation which the task asks for and the infrastructure decides whether it can be granted and if so orchestrates the operation and provides a common infrastructure for instrumentation, violation monitoring etc.

We really need to stop to look at particular workloads and defining adhoc solutions tailored to their particular itch if we don't want to end up with an uncoordinated and unmaintainable zoo of interfaces, hooks and knobs.

Agree.

Quoted 10 lines

Just looking at the problem at hand as an example. NOHZ already issues quiet_vmstat(), but it does not cancel already scheduled work. Now Marcelo wants a new mechanism which is supposed to cancel the work and then Alex want's to prevent it from being rescheduled. If that's not properly coordinated this goes down the drain very fast.

So can we please come up with a central place to handle this prctl() with a future proof argument list so the various isolation needs can be expressed as required?

Quoted 6 lines

That allows Marcelo to start tackling the vmstat side and Alex can utilize that and build the other parts into it piece by piece.

Thanks,

tglx

Thanks Thomas.

I think need to discuss/think on the reporting via tracing infrastructure too... Maybe Arnaldo has some ideas.

Alex how is this (in general) ?
Should be able to enable the signalling with it, if i am not mistaken.

Will post a version with the vmstat sync shortly.

include/uapi/linux/prctl.h +5 -0
Index: linux-2.6-vmstat2/include/uapi/linux/prctl.h
===================================================================
@@ -247,4 +247,9 @@ struct prctl_mm_map {
 #define PR_SET_IO_FLUSHER		57
 #define PR_GET_IO_FLUSHER		58
 
+/* Task isolation control */
+#define PR_TASK_ISOLATION_FEATURES	59
+#define PR_TASK_ISOLATION_GET		60
+#define PR_TASK_ISOLATION_SET		61
+
 #endif /* _LINUX_PRCTL_H */
kernel/sys.c +44 -0

56 lines not on this page · raw message

Documentation/userspace-api/task_isolation.rst new file +59 -0

59 lines not on this page · raw message

include/uapi/linux/isolation.h new file +21 -0
Index: linux-2.6-vmstat2/include/uapi/linux/isolation.h
===================================================================
@@ -0,0 +1,21 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+
+/* For PR_TASK_ISOLATION_FEATURES */
+struct isolation_features {
+	__u32	flags;
+	__u32	pad[3];
+};
+
+/* For PR_TASK_ISOLATION_GET / PR_TASK_ISOLATION_SET */
+struct isolation_control {
+	__u32	flags;
+	__u32	pad[15];
+};
+
+/*
+ * Quiesce pending background activity, such as
+ * flushing per-CPU VM statistics.
+ */
+
+#define TASK_ISOLATION_QUIESCE_CPU 0x1
+
kernel/isolation.c new file +30 -0
Index: linux-2.6-vmstat2/kernel/isolation.c
===================================================================
@@ -0,0 +1,30 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ *  Implementation of task isolation.
+ *
+ * Authors:
+ *   Chris Metcalf <[email protected]>
+ *   Alex Belits <[email protected]>
+ *   Yuri Norov <[email protected]>
+ *   Marcelo Tosatti <[email protected]>
+ */
+
+#include <linux/sched.h>
+#include <linux/isolation.h>
+
+int prctl_task_isolation_features(struct isolation_features *ifeat)
+{
+	ifeat->flags = TASK_ISOLATION_QUIESCE_CPU;
+
+	return 0;
+}
+
+int prctl_task_isolation_set(struct isolation_control *control)
+{
+	return 0;
+}
+
+int prctl_task_isolation_get(struct isolation_control *control)
+{
+	return 0;
+}
#26 lore raw
Quoted 23 lines · Marcelo Tosatti
Documentation/userspace-api/task_isolation.rst new file +23 -0
+Usage
+=====
+``PR_TASK_ISOLATION_FEATURES``:
+        Returns the supported features. Features are defined
+        at include/uapi/linux/isolation.h.
+
+        Usage::
+
+                prctl(PR_TASK_ISOLATION_FEATURES, ifeat, 0, 0, 0);
+
+        The 'ifeat' argument is a pointer to a struct isolation_features:
+
+                struct isolation_features {
+                        __u32   flags;
+                        __u32   pad[3];
+                };
+
+        Where flags contains bit sets for the features the kernel supports.
+
+        FIXME: describe error codes
+
+``PR_TASK_ISOLATION_SET``:
+        Enables task isolation mode. The type of task isolation is specified

Documentation/userspace-api/task_isolation.rst line 47

Quoted 10 lines
Documentation/userspace-api/task_isolation.rst new file +10 -0
+        via
+
+        struct isolation_control {
+                __u32   flags;
+                __u32   pad[15];
+        };
+
+``PR_TASK_ISOLATION_GET``:
+        Retrieves the currently configured task isolation mode and
+        parameters.

So, I guess we can think of two kinds of calls here:

* Modes, or isolation states: signal on disallowed kernel entry, arrange for not taking some IPIs toward delayed processing, etc...

For such "mode" it makes sense to have set() and get(), because the mode can be turned on and off.

* Oneshot requests: quiescing (eg: vmstat), flush some pending events.

For that it makes no sense to have a get().

I would rather decouple the above with, for modes:

PR_TASK_ISOLATION_SET
PR_TASK_ISOLATION_GET

And for oneshot requests:

PR_TASK_ISOLATION_REQUEST

Thanks.

#27 lore raw
Quoted 50 lines · Frederic Weisbecker
Quoted 23 lines · Marcelo Tosatti
Documentation/userspace-api/task_isolation.rst new file +23 -0
+Usage
+=====
+``PR_TASK_ISOLATION_FEATURES``:
+        Returns the supported features. Features are defined
+        at include/uapi/linux/isolation.h.
+
+        Usage::
+
+                prctl(PR_TASK_ISOLATION_FEATURES, ifeat, 0, 0, 0);
+
+        The 'ifeat' argument is a pointer to a struct isolation_features:
+
+                struct isolation_features {
+                        __u32   flags;
+                        __u32   pad[3];
+                };
+
+        Where flags contains bit sets for the features the kernel supports.
+
+        FIXME: describe error codes
+
+``PR_TASK_ISOLATION_SET``:
+        Enables task isolation mode. The type of task isolation is specified

Documentation/userspace-api/task_isolation.rst line 47

Quoted 10 lines
Documentation/userspace-api/task_isolation.rst new file +10 -0
+        via
+
+        struct isolation_control {
+                __u32   flags;
+                __u32   pad[15];
+        };
+
+``PR_TASK_ISOLATION_GET``:
+        Retrieves the currently configured task isolation mode and
+        parameters.

So, I guess we can think of two kinds of calls here:

* Modes, or isolation states: signal on disallowed kernel entry, arrange for not taking some IPIs toward delayed processing, etc...

For such "mode" it makes sense to have set() and get(), because the mode can be turned on and off.

* Oneshot requests: quiescing (eg: vmstat), flush some pending events.

For that it makes no sense to have a get().

I would rather decouple the above with, for modes:

Quoted 8 lines

PR_TASK_ISOLATION_SET
PR_TASK_ISOLATION_GET

And for oneshot requests:

PR_TASK_ISOLATION_REQUEST

Thanks.

Yes, this was annoying.

Will extend the interface to split SET/GET per command as well (so its easier to know from which feature the error comes from), and use REQUEST to finally enter isolated mode.

Thanks for the suggestion!

#28 lore raw
In reply to Thomas Gleixner
Quoted 20 lines · Thomas Gleixner
Quoted 6 lines · Christoph Lameter
Quoted 2 lines · Marcelo Tosatti

Decided to switch to prctl interface, and then it starts to become similar to "task mode isolation" patchset API.

Right I think that was a good approach.

prctl() is the right thing to do.

Quoted 9 lines
Quoted 5 lines

In addition to quiescing pending activities on the CPU, it would also be useful to assign a per-task attribute (which is then assigned
to a per-CPU attribute), indicating whether that CPU is running an isolated task or not.

Sounds good but what would this do? Give a warning like the isolation
patchset?

Isolation patch right now produces log warnings because there is no application interface for it yet. I am trying to make something suitable for applications, so they can react to it, collect statistics and produce human-readable logs. It is still not entirely clear, what should be included and in which cases (other than isolation breaking) monitored events should be recorded, so for now and for the purposes of task isolation alone I have kept ugly-looking messages.

Two things that I want to add are:

1. "Cause" that describes what kind of event happened (generic IPI, specific call, exception, page fault, timer, interrupt, syscall entry) with some relevant data. Or default "we have entered kernel and now exiting, however we have no idea what exactly was called in between" cause, to catch everything that is not tracked yet. The "relevant data" part is what can make this feature useful (handlers of specific events always know what they are), however it should be chosen carefully.

2. Optional "remote cause" that describes why did someone sent an IPI to this CPU (to be picked when IPI is being processed). This may include something like description like a normal cause, or a backtrace. If we know that we are about to kick a task out of isolation, we can just as well include an explanation why.

Quoted 10 lines

This all needs a lot more thought about the overall picture. We already
have too many knobs and ad hoc hooks which fiddle with isolation.

The current CPU isolation is a best effort approach and I agree that for
more strict isolation modes we need to be able to enforce that and hunt
down offenders and think about them one by one.

Quoted 5 lines
Quoted 1 line
Quoted 1 line

To be called before real time loop, one would have:

Can we please agree in the first place, that "real time" is absolutely
the wrong term here?

We can call it "isolated mode" or "isolated user mode", so it would be clear that it is the opposite to anything related to interrupts and preemption.

Quoted 11 lines

It's about running undisturbed CPU bound computations whatever nature they are. It does not matter whether that loop does busy polling ala DPDK, whether it runs a huge math computation on a data set or whatever people come up with.

Quoted 6 lines
Quoted 6 lines

prctl(PR_SET_TASK_ISOLATION, ISOLATION_ENABLE) [1] real time loop prctl(PR_SET_TASK_ISOLATION, ISOLATION_DISABLE)

(with the attribute also being cleared on task exit).

Quoted 7 lines
Quoted 4 lines
Quoted 4 lines

The general description would be:

"Set task isolated mode for a given task, returning an error if the task is not pinned to a single CPU.

Plus returning an error if the task has no permissions to request this. This should not be an unprivileged prctl ever.

If we want a consistent interface, it can also return corresponding error if the task has permissions but can't because, say, there are multiple tasks all bound to the same CPU.

Quoted 9 lines
Quoted 6 lines
Quoted 4 lines

In this mode, the kernel will avoid interruptions to isolated CPUs when possible."

Any objections against such an interface ?

Maybe do both like in the isolation patchset?

We really want to define the scopes first. And here you go:

Quoted 7 lines
Quoted 3 lines

Often code can tolerate a few interruptions (in some code branches regular syscalls may be needed) but one wants the thread to be as quiet as possible.

So you say some code can tolerate a few interrupts, then comes Alex and
says 'no disturbance' at all.

I agree. I would prefer a shared interface to closely related functionality even if parts of implementation vary, or may not even be present / enabled at the same time.

Quoted 25 lines

The point is that all of this shares the mechanisms to quiesce certain
parts of the kernel so this wants to build common infrastructure and the
prctl(ISOLATION, MODE) mode argument defines the scope of isolation which the task asks for and the infrastructure decides whether it can be
granted and if so orchestrates the operation and provides a common infrastructure for instrumentation, violation monitoring etc.

We really need to stop to look at particular workloads and defining adhoc solutions tailored to their particular itch if we don't want to end up with an uncoordinated and unmaintainable zoo of interfaces, hooks
and knobs.

Just looking at the problem at hand as an example. NOHZ already issues
quiet_vmstat(), but it does not cancel already scheduled work. Now Marcelo wants a new mechanism which is supposed to cancel the work and
then Alex want's to prevent it from being rescheduled. If that's not properly coordinated this goes down the drain very fast.

Quoted 7 lines

So can we please come up with a central place to handle this prctl() with a future proof argument list so the various isolation needs can be
expressed as required?

That allows Marcelo to start tackling the vmstat side and Alex can utilize that and build the other parts into it piece by piece.

Right. I think, we should choose, which parameters should be handled as flags and which as mutually exclusive modes, if any. For example, enabling diagnostics / recording causes can be a flag, so if we really want, we can collect interrupt logging while our task is running even without isolation (but then there would be a large amount of noise there). Maybe someone would want to do that on tasks that it ptrace()'s?

Recording may have filtering, for example, "remote cause" may be disabled, or some class of events, such as page faults, ignored or minimally recorded only with cause type.

Since the original interface uses signals, maybe we can keep signal number as a common feature for notification of isolation breaking or exceeding some parameters if such a thing applies.

We may want to set a separate flag to enable automatic re-entering isolation when broken and notification by signal. For some isolated tasks either of those features can be useful or not. "Best effort" modes where interrupts are expected, would by default remain active until turned off, and with no signals.

Since there is a great variety of those, and more may be added, we probably should have a "query" call that will return a mask of what is supported on the system or available to the given task.

Signature · 1 line
Alex
#29 lore raw

RFC 1/1 tentative prctl task isolation interface

Hi,

So as discussed, this is one possible prctl interface for task isolation.

Is this something that is desired? If not, what is the proper way for the interface to be?

(addition of a new capability CAP_TASK_ISOLATION, for permissions is still missing, should be done in the next versions).

Thanks.

add prctl interface for task isolation

Add a new extensible interface for task isolation, and allow userspace to quiesce the CPU.

This means putting the system into a quiet state by completing all workqueue items, idle all subsystems that need it and put the cpu into NOHZ mode.

include/uapi/linux/prctl.h +6 -0
Index: linux-2.6-vmstat2/include/uapi/linux/prctl.h
===================================================================
@@ -247,4 +247,10 @@ struct prctl_mm_map {
 #define PR_SET_IO_FLUSHER		57
 #define PR_GET_IO_FLUSHER		58
 
+/* Task isolation control */
+#define PR_TASK_ISOLATION_FEATURES	59
+#define PR_TASK_ISOLATION_GET		60
+#define PR_TASK_ISOLATION_SET		61
+#define PR_TASK_ISOLATION_REQUEST	62
+
 #endif /* _LINUX_PRCTL_H */
kernel/sys.c +20 -0
Index: linux-2.6-vmstat2/kernel/sys.c
===================================================================
@@ -58,6 +58,7 @@
 #include <linux/sched/coredump.h>
 #include <linux/sched/task.h>
 #include <linux/sched/cputime.h>
+#include <linux/isolation.h>
 #include <linux/rcupdate.h>
 #include <linux/uidgid.h>
 #include <linux/cred.h>
@@ -2530,6 +2531,25 @@ SYSCALL_DEFINE5(prctl, int, option, unsi
 
 		error = (current->flags & PR_IO_FLUSHER) == PR_IO_FLUSHER;
 		break;
+	case PR_TASK_ISOLATION_FEATURES: {
+		struct isolation_features ifeat;
+
+		memset(&ifeat, 0, sizeof(ifeat));
+
+		prctl_task_isolation_features(&ifeat);
+		if (copy_to_user((char __user *)arg2, &ifeat, sizeof(ifeat)))
+			return -EFAULT;
+		break;
+	}
+	case PR_TASK_ISOLATION_SET:
+		error = prctl_task_isolation_set(arg2, arg3, arg4, arg5);
+		break;
+	case PR_TASK_ISOLATION_GET:
+		error = prctl_task_isolation_get(arg2, arg3, arg4, arg5);
+		break;
+	case PR_TASK_ISOLATION_REQUEST:
+		error = prctl_task_isolation_request(arg2, arg3, arg4, arg5);
+		break;
 	default:
 		error = -EINVAL;
 		break;
Documentation/userspace-api/task_isolation.rst new file +99 -0

99 lines not on this page · raw message

include/uapi/linux/isolation.h new file +16 -0
Index: linux-2.6-vmstat2/include/uapi/linux/isolation.h
===================================================================
@@ -0,0 +1,16 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+
+#ifndef _UAPI_LINUX_ISOL_H
+#define _UAPI_LINUX_ISOL_H
+
+/* For PR_TASK_ISOLATION_FEATURES */
+struct isolation_features {
+	__u32	flags;
+	__u32	pad[3];
+};
+
+/* Isolation features */
+#define	ISOL_F_QUIESCE		0x1
+
+#endif /* _UAPI_LINUX_ISOL_H */
+
kernel/isolation.c new file +41 -0

41 lines not on this page · raw message

samples/task_isolation/task_isolation.c new file +50 -0

50 lines not on this page · raw message

include/linux/isolation.h new file +18 -0
Index: linux-2.6-vmstat2/include/linux/isolation.h
===================================================================
@@ -0,0 +1,18 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+
+#ifndef __LINUX_ISOL_H
+#define __LINUX_ISOL_H
+
+#include <uapi/linux/isolation.h>
+
+void prctl_task_isolation_features(struct isolation_features *ifeat);
+
+int prctl_task_isolation_get(unsigned long arg2, unsigned long arg3,
+			     unsigned long arg4, unsigned long arg5);
+
+int prctl_task_isolation_set(unsigned long arg2, unsigned long arg3,
+			     unsigned long arg4, unsigned long arg5);
+
+int prctl_task_isolation_request(unsigned long arg2, unsigned long arg3,
+				 unsigned long arg4, unsigned long arg5);
+#endif /* __LINUX_ISOL_H */
kernel/Makefile +1 -1
Index: linux-2.6-vmstat2/kernel/Makefile
===================================================================
@@ -10,7 +10,7 @@ obj-y     = fork.o exec_domain.o panic.o
 	    extable.o params.o \
 	    kthread.o sys_ni.o nsproxy.o \
 	    notifier.o ksysfs.o cred.o reboot.o \
-	    async.o range.o smpboot.o ucount.o regset.o
+	    async.o range.o smpboot.o ucount.o regset.o isolation.o
 
 obj-$(CONFIG_USERMODE_DRIVER) += usermode_driver.o
 obj-$(CONFIG_MODULES) += kmod.o
include/linux/vmstat.h +1 -0
Index: linux-2.6-vmstat2/include/linux/vmstat.h
===================================================================
@@ -290,6 +290,7 @@ void refresh_zone_stat_thresholds(void);
 struct ctl_table;
 int vmstat_refresh(struct ctl_table *, int write, void *buffer, size_t *lenp,
 		loff_t *ppos);
+int user_quiet_vmstat(int cpu);
 
 void drain_zonestat(struct zone *zone, struct per_cpu_pageset *);
 
mm/vmstat.c +10 -0
Index: linux-2.6-vmstat2/mm/vmstat.c
===================================================================
@@ -1936,6 +1936,16 @@ void quiet_vmstat(void)
 	refresh_cpu_vm_stats(false);
 }
 
+int user_quiet_vmstat(int cpu)
+{
+	if (need_update(cpu) == true)
+		refresh_cpu_vm_stats(false);
+
+	flush_delayed_work(per_cpu_ptr(&vmstat_work, cpu));
+
+	return 0;
+}
+
 /*
  * Shepherd worker thread that checks the
  * differentials of processors that have their worker
#30 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 5 lines · Marcelo Tosatti

So as discussed, this is one possible prctl interface for task isolation.

Is this something that is desired? If not, what is the proper way for the interface to be?

Sure that sounds liek a good beginning but I guess we need some specificity on the features

Quoted 2 lines

+Task isolation CPU interface
+============================

How does one do a oneshot flush of OS activities?

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop. In the loop itself some activities may require syscalls so they will potentialy cause the OS services such as timers to start again. When such an activities is complete another quiet down call can be issued.

Could be implemented by setting a flag that does an action and then resets itself? Or the flag could be reset if a syscall that requires timers etc is used?

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

#31 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 8 lines · Christoph Lameter
Quoted 5 lines · Marcelo Tosatti

So as discussed, this is one possible prctl interface for task isolation.

Is this something that is desired? If not, what is the proper way for the interface to be?

Quoted 7 lines

Sure that sounds liek a good beginning but I guess we need some specificity on the features

Quoted 2 lines

+Task isolation CPU interface
+============================

How does one do a oneshot flush of OS activities?

        ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
        if (ret == -1) {
                perror("prctl PR_TASK_ISOLATION_REQUEST");
                exit(0);
        }
Quoted 4 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Syscalls disallowed:
===================

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

        if ((ifeat & ISOL_F_BLOCK_SYSCALLS) == ISOL_F_BLOCK_SYSCALLS) {
		struct task_isolation_block_syscalls tibs = { list of
							 syscalls to block,
							 additional
							 parameters }

		struct task_isolation_notif tis = { parameters to control
						signal handling upon
						isolation breaking event }
		
                ret = prctl(PR_TASK_ISOLATION_SET, ISOL_F_SETUP_NOTIF, &tis);
		if (ret != 0) { ... }
		featuremask |= ISOL_F_SETUP_NOTIF;

                ret = prctl(PR_TASK_ISOLATION_SET, ISOL_F_BLOCK_SYSCALLS, &tibs);
		if (ret != 0) { ... }
		featuremask |= ISOL_F_BLOCK_SIGNALS;

                featuremask |= ISOL_F_QUIESCE;
        }

This would require knowledge of the behaviour of individual system calls, that is whether or not these syscalls cause the CPU to be a target of interruptions (1) (while the QUIESCE / HARD / WARN division you propose allows for coarse-grained control).

Perhaps coarse control while also allowing finer grained control (if desired) is a useful choice?

1: for example adding free pages to per-cpu free lists.

Syscalls allowed:
=================

Quoted 2 lines

In the loop itself some activities may require syscalls so they will potentialy cause the OS services such as timers to start again.

Or a different mode where the syscall return itself can finish any pending activities.

Quoted 2 lines

When such
an activities is complete another quiet down call can be issued.

Although this seems more efficient (if multiple syscalls are to be used).

Quoted 3 lines

Could be implemented by setting a flag that does an action and then resets itself? Or the flag could be reset if a syscall that requires timers etc is used?

You mean to let userspace know if a certain syscall triggered a pending action which must be finished (before "quiet mode" is entered again) ? Sounds like a good idea.

Quoted 7 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Unclear whether such blockage should be performed on:

-> Individual action basis (eg: BLOCK_CPU_HOTPLUG, BLOCK_PERCPU_TRACEBUFFER_SIZE, ...) (which could allow individual unblocking through a sysfs interface, for example).

Or

-> Be tied to a flag with a less implementation specific meaning such as F_ISOL_BAREMETAL_HARD.

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

That flexibility seems to be useful (so perhaps
F_ISOL_BAREMETAL_HARD but optionally permitting
certain interruptions).

Quoted 3 lines

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

Alex seems to be interested in different notification methods as well.

Thanks for the input.

#32 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

        ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
        if (ret == -1) {
                perror("prctl PR_TASK_ISOLATION_REQUEST");
                exit(0);
        }
Quoted 1 line
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

And I already said that I want the system to quiet down and allow system calls. Some indication that deferred actions have occurred may be useful by f.e. resetting the flag.

Quoted 3 lines

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

Well come up with a use case for that .... I know mine. What you propose could be useful for debugging for me but I would prefer the quiet down approach where I determine when I use some syscalls or not and will deal with the consequences.

Quoted 10 lines
Quoted 8 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

To disinguish it from "Realtime". We want the processor for ourselves without anything else running on it.

Quoted 5 lines

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

Quoted 6 lines

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

Does reading these really cause deferred actions by the OS? AFAICT you could map these into memory as well as read them without OS activities.

"Interruptions that can be tolerated".... Well that is the wild west of "realtime" where you can define how much of a time slice is "real" and how much can be use by other processes. I do not think that any of that should come into this API.

#33 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 12 lines · Christoph Lameter

----------------------------------------------------------------------

Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

         ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
         if (ret == -1) {
                 perror("prctl PR_TASK_ISOLATION_REQUEST");
                 exit(0);
         }
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

Some of those syscalls go through vdso, and don't enter the kernel -- nothing specific is necessary to allow them, and it would be pointless and difficult to prevent them.

For syscalls that enter the kernel, it's often difficult to predict, if they will or won't cause deferred processing, so I am afraid, it won't be possible to provide a "safe" class of syscalls for this purpose and not end up with something minimal like reading /sys and /proc. Right now isolation only "allows" syscalls that exit isolation.

It may be possible to set up a filter by the system (allowing few safe things like reading /proc) and let the user expand it by adding combinations of syscall / file descriptor. If some device is known to process operations safely, user can open it and mark file descriptor as allowed, say, for reading.

Quoted 3 lines

And I already said that I want the system to quiet down and allow system calls. Some indication that deferred actions have occurred may be useful by f.e. resetting the flag.

I think, it should be possible to process a syscall, and if any deferred action occurred, exit isolation on return to userspace. Then there is a question, how userspace should be notified about isolation being lost. Normally this happens with a signal, but that is useful if we want syscall to fail with EINTR, not to succeed. Make sure that signal arrives after successful syscall return but before deferred action to happen? Sounds convoluted. Maybe reflecting isolation status in vdso and having the user check it there will be a good solution.

When I worked on my implementation I have encountered both a problem of interaction with the rest of system from isolated task (at least simple things as logging) and a problem of handling enter/exit from isolation on a system when it's possible for a task to be interrupted early after entering isolation due to various events that were still in progress on other CPUs.

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

It would be great if the complexity and amount of functionality of that manager/helper task can be reduced, however I believe that having such a task is a legitimate way of implementing things that otherwise would require additional functionality in kernel.

Quoted 9 lines
Quoted 4 lines

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

Well come up with a use case for that .... I know mine. What you propose could be useful for debugging for me but I would prefer the quiet down approach where I determine when I use some syscalls or not and will deal with the consequences.

For my purposes breaking isolation on syscalls and notifications about isolation breaking is a very useful approach -- this is why I kept it exactly as it was in the original implementation by Chris Metcalf.

In applications that I intend to use isolation for, the primary concern is consistent time for running code in userspace, so syscalls should be only issued when the task is specifically not in isolated mode. If the program issues a syscall by mistake (and that may happen when some libraries are used, or thread synchronization primitives are kept from non-isolated version of the program, even though isolated tasks are not supposed to use those), it means not only that deferred work may cause delay in the future, but also that there is an additional time to be spent in kernel. This should be immediately visible to the developer, and the best way to do it is by breaking isolation on syscall immediately.

Quoted 15 lines
Quoted 11 lines
Quoted 9 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

To disinguish it from "Realtime". We want the processor for ourselves without anything else running on it.

Quoted 8 lines
Quoted 5 lines

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex: with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

I guess, if we want to add more controls, we can allow the user to choose either of those four options, or of a subset of them. In my opinion, if (4) will be available, and the only additional cost will be time for synchronization spent in breaking isolation procedure, there is not much need in the other three. Without (4) I don't think, the goal of providing consistent, interruption-free environment is achieved at all, so not implementing it would be very bad.

Quoted 9 lines
Quoted 6 lines

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

Does reading these really cause deferred actions by the OS? AFAICT you could map these into memory as well as read them without OS activities.

Access to those is hardware/architecture-specific, and in many cases, indeed, there is no need to issue a syscall at all.

However for many applications the model with a helper task performing interactions with OS on a different core and exchanging data over shared memory may be sufficient, and it will also provide clear separation between operations that do require consistent timing and those that don't.

Quoted 6 lines

"Interruptions that can be tolerated".... Well that is the wild west of "realtime" where you can define how much of a time slice is "real" and how much can be use by other processes. I do not think that any of that should come into this API.

To be honest, I have no idea, what can and can not be tolerated by applications other than what I am familiar with. Applications that I know, require no interruptions at all, so I want to implement that. I assume, someone already uses existing CPU isolation for the purpose of providing "nearly interrupt-less" environment.

I can imaging something like a task of controlling a large slow-updating LED display by bit-banging a strictly timed long serial message representing a frame or frame update. If interrupted, it may, depending on the protocol, corrupt the state of a single LED or fail to update until the end of the screen, but the next start of message will reset the state, and everything will work until the next interrupt. Maybe there are more realistic or useful examples.

Signature · 1 line
Alex
#34 lore raw

Re: [RFC] tentative prctl task isolation interface

Hi Alex,

Quoted 27 lines · Alex Belits
Quoted 12 lines · Christoph Lameter

----------------------------------------------------------------------

Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

         ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
         if (ret == -1) {
                 perror("prctl PR_TASK_ISOLATION_REQUEST");
                 exit(0);
         }
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

Some of those syscalls go through vdso, and don't enter the kernel -- nothing specific is necessary to allow them, and it would be pointless and difficult to prevent them.

Quoted 5 lines

For syscalls that enter the kernel, it's often difficult to predict, if they will or won't cause deferred processing, so I am afraid, it won't be possible to provide a "safe" class of syscalls for this purpose and not end up with something minimal like reading /sys and /proc. Right now isolation only "allows" syscalls that exit isolation.

Christoph wrote:

"> Features that I think may be needed:

Quoted 10 lines

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

"

It seems the only difference between HARD and WARN (lets call it SOFT) would be whether a notification is sent to userspace.

The definition

"F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future."

fails in the static_key_enable case: Alex's idea is to queue the i-cache flush if the remote task/cpu is in isolated mode (and perform the flush when entering the kernel).

So even if userspace uses syscalls that do not require delayed processing, there are events which are out of control of the application and might require it.

So lets assume the application performs a number of syscalls on a given time critical codepath.

Either the system is configured so that
the number/frequency of static_key_enable's is limited, or the cost of i-cache flushes must be accounted on that critical codepath.

Anyway, trying to improve Christoph's definition:

F_ISOL_QUIESCE -> flush any pending operations that might cause
the CPU to be interrupted (ex: free's per-CPU queues, sync MM statistics counters, etc).

F_ISOL_ISOLATE -> inform the kernel that userspace is
entering isolated mode (see description below on "ISOLATION MODES").

F_ISOL_UNISOLATE -> inform the kernel that userspace is
leaving isolated mode.

F_ISOL_NOTIFY -> notification mode of isolation breakage
modes.

Isolation modes:
---------------

There are two main types of isolation modes:

- SOFT mode: does not prevent activities which might generate interruptions (such as CPU hotplug).

- HARD mode: prevents all blockable activities that might generate interruptions. Administrators can override this via /sys.

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

(new modes can be added, for example signals).

A new feature can be added to disallow syscalls (by default syscalls are enabled, with reporting of pending activities that might cause an interruption in a VDSO).

How about that?

Quoted 9 lines

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

Quoted 5 lines

It may be possible to set up a filter by the system (allowing few safe things like reading /proc) and let the user expand it by adding combinations of syscall / file descriptor. If some device is known to process operations safely, user can open it and mark file descriptor as allowed, say, for reading.

Makes sense.

Quoted 3 lines
Quoted 3 lines

And I already said that I want the system to quiet down and allow system calls. Some indication that deferred actions have occurred may be useful by f.e. resetting the flag.

Do you think reporting activities that add overhead (the i-cache flush in mind) to syscalls separately in the VDSO?

Quoted 2 lines

I think, it should be possible to process a syscall, and if any deferred action occurred, exit isolation on return to userspace.

On the interface we are creating:

	ret = syscall()...
	if (vdso.pending_activity) {
		prctl(PR_TASK_ISOLATION_REQUEST, F_ISOL_UNISOLATE, 0, 0);
		...
	}

Why would it be necessary to exit isolation on return to userspace again?

Quoted 7 lines

Then there is a
question, how userspace should be notified about isolation being lost. Normally this happens with a signal, but that is useful if we want syscall to fail with EINTR, not to succeed. Make sure that signal arrives after successful syscall return but before deferred action to happen? Sounds convoluted. Maybe reflecting isolation status in vdso and having the user check it there will be a good solution.

Why can't userspace enable/disable isolation mode (and the kernel only reports it) ?

I fail to see why the order of the events "isolated mode disablement" and "return to userspace" is critical.

Quoted 6 lines

When I worked on my implementation I have encountered both a problem of interaction with the rest of system from isolated task (at least simple things as logging) and a problem of handling enter/exit from isolation on a system when it's possible for a task to be interrupted early after entering isolation due to various events that were still in progress on other CPUs.

Quoted 7 lines

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

Interesting. Are you considering opensourcing such library? Seems like a generic problem.

Quoted 19 lines

It would be great if the complexity and amount of functionality of that manager/helper task can be reduced, however I believe that having such a task is a legitimate way of implementing things that otherwise would require additional functionality in kernel.

Quoted 9 lines
Quoted 4 lines

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

Well come up with a use case for that .... I know mine. What you propose could be useful for debugging for me but I would prefer the quiet down approach where I determine when I use some syscalls or not and will deal with the consequences.

For my purposes breaking isolation on syscalls and notifications about isolation breaking is a very useful approach -- this is why I kept it exactly as it was in the original implementation by Chris Metcalf.

Quoted 10 lines

In applications that I intend to use isolation for, the primary concern is consistent time for running code in userspace, so syscalls should be only issued when the task is specifically not in isolated mode. If the program issues a syscall by mistake (and that may happen when some libraries are used, or thread synchronization primitives are kept from non-isolated version of the program, even though isolated tasks are not supposed to use those), it means not only that deferred work may cause delay in the future, but also that there is an additional time to be spent in kernel. This should be immediately visible to the developer, and the best way to do it is by breaking isolation on syscall immediately.

I guess you can do that by hooking a BPF program to cpu->is_isolated == true (for development) and syscall entry.

Quoted 45 lines
Quoted 14 lines
Quoted 10 lines
Quoted 8 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

To disinguish it from "Realtime". We want the processor for ourselves without anything else running on it.

Quoted 8 lines
Quoted 5 lines

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex:
with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

Quoted 3 lines

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

Agree. (3) will be necessary as intermediate step. The proposed improvement to Christoph's reply, in this thread, separates notification and syscall blockage.

Quoted 7 lines

I guess, if we want to add more controls, we can allow the user to choose either of those four options, or of a subset of them. In my opinion, if (4) will be available, and the only additional cost will be time for synchronization spent in breaking isolation procedure, there is not much need in the other three. Without (4) I don't think, the goal of providing consistent, interruption-free environment is achieved at all, so not implementing it would be very bad.

Agree.

Quoted 10 lines
Quoted 9 lines
Quoted 6 lines

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

Does reading these really cause deferred actions by the OS? AFAICT you could map these into memory as well as read them without OS activities.

Quoted 7 lines

Access to those is hardware/architecture-specific, and in many cases, indeed, there is no need to issue a syscall at all.

However for many applications the model with a helper task performing interactions with OS on a different core and exchanging data over shared memory may be sufficient, and it will also provide clear separation between operations that do require consistent timing and those that don't.

I see.

Quoted 12 lines
Quoted 5 lines

"Interruptions that can be tolerated".... Well that is the wild west of "realtime" where you can define how much of a time slice is "real" and how much can be use by other processes. I do not think that any of that should come into this API.

To be honest, I have no idea, what can and can not be tolerated by applications other than what I am familiar with. Applications that I know, require no interruptions at all, so I want to implement that. I assume, someone already uses existing CPU isolation for the purpose of providing "nearly interrupt-less" environment.

Quoted 7 lines

I can imaging something like a task of controlling a large slow-updating LED display by bit-banging a strictly timed long serial message representing a frame or frame update. If interrupted, it may, depending on the protocol, corrupt the state of a single LED or fail to update until the end of the screen, but the next start of message will reset the state, and everything will work until the next interrupt. Maybe there are more realistic or useful examples.

Agree that "no interruptions" as a goal makes most sense.

Can "whitelist" certain interruptions if necessary (to handle the MSR read case), if user desires.

#35 lore raw

Re: [RFC] tentative prctl task isolation interface

Adding Nitesh to CC.

Quoted 331 lines · Marcelo Tosatti

Hi Alex,

Quoted 27 lines · Alex Belits
Quoted 12 lines · Christoph Lameter

----------------------------------------------------------------------

Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

         ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
         if (ret == -1) {
                 perror("prctl PR_TASK_ISOLATION_REQUEST");
                 exit(0);
         }
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

Some of those syscalls go through vdso, and don't enter the kernel -- nothing specific is necessary to allow them, and it would be pointless and difficult to prevent them.

Quoted 5 lines

For syscalls that enter the kernel, it's often difficult to predict, if they will or won't cause deferred processing, so I am afraid, it won't be possible to provide a "safe" class of syscalls for this purpose and not end up with something minimal like reading /sys and /proc. Right now isolation only "allows" syscalls that exit isolation.

Christoph wrote:

"> Features that I think may be needed:

Quoted 10 lines

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

"

It seems the only difference between HARD and WARN (lets call it SOFT) would be whether a notification is sent to userspace.

The definition

"F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future."

fails in the static_key_enable case: Alex's idea is to queue the i-cache flush if the remote task/cpu is in isolated mode (and perform the flush when entering the kernel).

So even if userspace uses syscalls that do not require delayed processing, there are events which are out of control of the application and might require it.

So lets assume the application performs a number of syscalls on a given time critical codepath.

Either the system is configured so that
the number/frequency of static_key_enable's is limited, or the cost of i-cache flushes must be accounted on that critical codepath.

Anyway, trying to improve Christoph's definition:

F_ISOL_QUIESCE -> flush any pending operations that might cause
the CPU to be interrupted (ex: free's per-CPU queues, sync MM statistics counters, etc).

F_ISOL_ISOLATE -> inform the kernel that userspace is
entering isolated mode (see description below on "ISOLATION MODES").

F_ISOL_UNISOLATE -> inform the kernel that userspace is
leaving isolated mode.

F_ISOL_NOTIFY -> notification mode of isolation breakage
modes.

Isolation modes:
---------------

There are two main types of isolation modes:

- SOFT mode: does not prevent activities which might generate interruptions (such as CPU hotplug).

- HARD mode: prevents all blockable activities that might generate interruptions. Administrators can override this via /sys.

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

(new modes can be added, for example signals).

A new feature can be added to disallow syscalls (by default syscalls are enabled, with reporting of pending activities that might cause an interruption in a VDSO).

How about that?

Quoted 9 lines

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

Quoted 5 lines

It may be possible to set up a filter by the system (allowing few safe things like reading /proc) and let the user expand it by adding combinations of syscall / file descriptor. If some device is known to process operations safely, user can open it and mark file descriptor as allowed, say, for reading.

Makes sense.

Quoted 3 lines
Quoted 3 lines

And I already said that I want the system to quiet down and allow system calls. Some indication that deferred actions have occurred may be useful by f.e. resetting the flag.

Do you think reporting activities that add overhead (the i-cache flush in mind) to syscalls separately in the VDSO?

Quoted 2 lines

I think, it should be possible to process a syscall, and if any deferred action occurred, exit isolation on return to userspace.

On the interface we are creating:

	ret = syscall()...
	if (vdso.pending_activity) {
		prctl(PR_TASK_ISOLATION_REQUEST, F_ISOL_UNISOLATE, 0, 0);
		...
	}

Why would it be necessary to exit isolation on return to userspace again?

Quoted 7 lines

Then there is a
question, how userspace should be notified about isolation being lost. Normally this happens with a signal, but that is useful if we want syscall to fail with EINTR, not to succeed. Make sure that signal arrives after successful syscall return but before deferred action to happen? Sounds convoluted. Maybe reflecting isolation status in vdso and having the user check it there will be a good solution.

Why can't userspace enable/disable isolation mode (and the kernel only reports it) ?

I fail to see why the order of the events "isolated mode disablement" and "return to userspace" is critical.

Quoted 6 lines

When I worked on my implementation I have encountered both a problem of interaction with the rest of system from isolated task (at least simple things as logging) and a problem of handling enter/exit from isolation on a system when it's possible for a task to be interrupted early after entering isolation due to various events that were still in progress on other CPUs.

Quoted 7 lines

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

Interesting. Are you considering opensourcing such library? Seems like a generic problem.

Quoted 19 lines

It would be great if the complexity and amount of functionality of that manager/helper task can be reduced, however I believe that having such a task is a legitimate way of implementing things that otherwise would require additional functionality in kernel.

Quoted 9 lines
Quoted 4 lines

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

Well come up with a use case for that .... I know mine. What you propose could be useful for debugging for me but I would prefer the quiet down approach where I determine when I use some syscalls or not and will deal with the consequences.

For my purposes breaking isolation on syscalls and notifications about isolation breaking is a very useful approach -- this is why I kept it exactly as it was in the original implementation by Chris Metcalf.

Quoted 10 lines

In applications that I intend to use isolation for, the primary concern is consistent time for running code in userspace, so syscalls should be only issued when the task is specifically not in isolated mode. If the program issues a syscall by mistake (and that may happen when some libraries are used, or thread synchronization primitives are kept from non-isolated version of the program, even though isolated tasks are not supposed to use those), it means not only that deferred work may cause delay in the future, but also that there is an additional time to be spent in kernel. This should be immediately visible to the developer, and the best way to do it is by breaking isolation on syscall immediately.

I guess you can do that by hooking a BPF program to cpu->is_isolated == true (for development) and syscall entry.

Quoted 45 lines
Quoted 14 lines
Quoted 10 lines
Quoted 8 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

To disinguish it from "Realtime". We want the processor for ourselves without anything else running on it.

Quoted 8 lines
Quoted 5 lines

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex:
with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

Quoted 3 lines

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

Agree. (3) will be necessary as intermediate step. The proposed improvement to Christoph's reply, in this thread, separates notification and syscall blockage.

Quoted 7 lines

I guess, if we want to add more controls, we can allow the user to choose either of those four options, or of a subset of them. In my opinion, if (4) will be available, and the only additional cost will be time for synchronization spent in breaking isolation procedure, there is not much need in the other three. Without (4) I don't think, the goal of providing consistent, interruption-free environment is achieved at all, so not implementing it would be very bad.

Agree.

Quoted 10 lines
Quoted 9 lines
Quoted 6 lines

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

Does reading these really cause deferred actions by the OS? AFAICT you could map these into memory as well as read them without OS activities.

Quoted 7 lines

Access to those is hardware/architecture-specific, and in many cases, indeed, there is no need to issue a syscall at all.

However for many applications the model with a helper task performing interactions with OS on a different core and exchanging data over shared memory may be sufficient, and it will also provide clear separation between operations that do require consistent timing and those that don't.

I see.

Quoted 12 lines
Quoted 5 lines

"Interruptions that can be tolerated".... Well that is the wild west of "realtime" where you can define how much of a time slice is "real" and how much can be use by other processes. I do not think that any of that should come into this API.

To be honest, I have no idea, what can and can not be tolerated by applications other than what I am familiar with. Applications that I know, require no interruptions at all, so I want to implement that. I assume, someone already uses existing CPU isolation for the purpose of providing "nearly interrupt-less" environment.

Quoted 7 lines

I can imaging something like a task of controlling a large slow-updating LED display by bit-banging a strictly timed long serial message representing a frame or frame update. If interrupted, it may, depending on the protocol, corrupt the state of a single LED or fail to update until the end of the screen, but the next start of message will reset the state, and everything will work until the next interrupt. Maybe there are more realistic or useful examples.

Agree that "no interruptions" as a goal makes most sense.

Can "whitelist" certain interruptions if necessary (to handle the MSR read case), if user desires.

#36 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 122 lines · Marcelo Tosatti

Adding Nitesh to CC.

Quoted 118 lines · Marcelo Tosatti

Hi Alex,

Quoted 27 lines · Alex Belits
Quoted 12 lines · Christoph Lameter

----------------------------------------------------------------------

Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

         ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
         if (ret == -1) {
                 perror("prctl PR_TASK_ISOLATION_REQUEST");
                 exit(0);
         }
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

Some of those syscalls go through vdso, and don't enter the kernel -- nothing specific is necessary to allow them, and it would be pointless and difficult to prevent them.

Quoted 5 lines

For syscalls that enter the kernel, it's often difficult to predict, if they will or won't cause deferred processing, so I am afraid, it won't be possible to provide a "safe" class of syscalls for this purpose and not end up with something minimal like reading /sys and /proc. Right now isolation only "allows" syscalls that exit isolation.

Christoph wrote:

"> Features that I think may be needed:

Quoted 10 lines

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

F_ISOL_BAREMETAL_WARN -> Similar. Create a warning in the syslog when OS
services require delayed processing etc but continue while resetting the flag.

"

It seems the only difference between HARD and WARN (lets call it SOFT) would be whether a notification is sent to userspace.

The definition

"F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future."

fails in the static_key_enable case: Alex's idea is to queue the i-cache flush if the remote task/cpu is in isolated mode (and perform the flush when entering the kernel).

So even if userspace uses syscalls that do not require delayed processing, there are events which are out of control of the application and might require it.

So lets assume the application performs a number of syscalls on a given time critical codepath.

Either the system is configured so that
the number/frequency of static_key_enable's is limited, or the cost of i-cache flushes must be accounted on that critical codepath.

Anyway, trying to improve Christoph's definition:

F_ISOL_QUIESCE -> flush any pending operations that might cause
the CPU to be interrupted (ex: free's per-CPU queues, sync MM statistics counters, etc).

F_ISOL_ISOLATE -> inform the kernel that userspace is
entering isolated mode (see description below on "ISOLATION MODES").

F_ISOL_UNISOLATE -> inform the kernel that userspace is
leaving isolated mode.

F_ISOL_NOTIFY -> notification mode of isolation breakage
modes.

Isolation modes:
---------------

There are two main types of isolation modes:

- SOFT mode: does not prevent activities which might generate interruptions (such as CPU hotplug).

- HARD mode: prevents all blockable activities that might generate interruptions. Administrators can override this via /sys.

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

(new modes can be added, for example signals).

A new feature can be added to disallow syscalls (by default syscalls are enabled, with reporting of pending activities that might cause an interruption in a VDSO).

After discussion with Juri and Daniel, it became clearer that supporting unmodified applications would be quite useful:

- enter isolation mode
- run unmodified application
- leave isolation mode

This could work via an additional mode which goes through the quiesce operation at every syscall return. Since this includes freeing per-CPU pagevecs (therefore allocating per-CPU pagevecs at the next syscall), it might considerably slowdown system startup (and cause MM related spinlocks contention).

Better ideas are appreciated.

#37 lore raw

Re: [RFC] tentative prctl task isolation interface

In reply to Marcelo Tosatti
Quoted 11 lines · Marcelo Tosatti

Anyway, trying to improve Christoph's definition:

F_ISOL_QUIESCE -> flush any pending operations that might cause
the CPU to be interrupted (ex: free's per-CPU queues, sync MM statistics counters, etc).

F_ISOL_ISOLATE -> inform the kernel that userspace is
entering isolated mode (see description below on "ISOLATION MODES").

Quoted 5 lines

F_ISOL_UNISOLATE -> inform the kernel that userspace is
leaving isolated mode.

F_ISOL_NOTIFY -> notification mode of isolation breakage
modes.

Looks good to me.

Quoted 10 lines

Isolation modes:
---------------

There are two main types of isolation modes:

- SOFT mode: does not prevent activities which might generate interruptions (such as CPU hotplug).

- HARD mode: prevents all blockable activities that might generate interruptions. Administrators can override this via /sys.

Yup.

Quoted 10 lines

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

- Abort with core dump

This is useful for debugging and for hard core bare metalers that never want any interrupts.

One particular issue are page faults. One would have to prefault the binary executable functions in order to avoid "interruptions" through page faults. Are these proper interrutions of the code? Certainly major faults are but minor faults may be ok? Dunno.

In practice what I have often seen in such apps is that there is a "warm" up mode where all critical functions are executed, all important variables are touched and dummy I/Os are performed in order to populate the caches and prefault all the data.I guess one would run these without isolation first and then switch on some sort of isolation mode after warm up. So far I think most people relied on the timer interrupt etc etc to be turned off after a few secs of just running throught a polling loop without any OS activities.

Quoted 10 lines
Quoted 7 lines

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

Interesting. Are you considering opensourcing such library? Seems like a generic problem.

Well everyone swears on having the right implementation. The people I know would not do any thing with a socket in such situations. They would only use shared memory and direct access to I/O devices via SPDK and DPDK or the RDMA subsystem.

Quoted 19 lines
Quoted 19 lines
Quoted 2 lines

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex:
with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

Quoted 5 lines
Quoted 5 lines

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

Or move the actions to a different victim processor like done with rcu and vmstat etc etc.

Quoted 8 lines
Quoted 4 lines

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

Agree. (3) will be necessary as intermediate step. The proposed improvement to Christoph's reply, in this thread, separates notification and syscall blockage.

I guess the notification mode will take care of the way we handle these interruptions.

#38 lore raw

Re: [RFC] tentative prctl task isolation interface

Quoted 9 lines · Christoph Lameter
Quoted 9 lines

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

Syslog is intended for humans, and isn't useful for userspace software processing. Since there are at least some cases then isolation breaking is unavoidable on startup (benign race of isolation entering with isolation-breaking event, register-mapping page fault), I would rather allow completely automated processing of those events. Signal interface does that now, however I think, it would help to associate software-handled events with either software-identifiable "cause type" (ex: "scheduling timer" or "page fault") or more verbose human-readable "cause description" (ex: IPI received, and here is the sender CPU's stack dump that led to this IPI being sent).

The former ("cause") may be important for software (for example, it may want to have special processing of page faults for device registers), while the latter ("description") is more useful when it can be associated with particular event in userspace without manual log timing comparison and guesswork.

Quoted 3 lines

- Abort with core dump

I would use an existing signal interface for that, with user-defined signal. The user can choose to handle the signal, ignore it, let it kill the task with or without a core dump.

Oh, and if user wants, he can use ptrace() to delegate this signal to some other process.

Quoted 9 lines

This is useful for debugging and for hard core bare metalers that never want any interrupts.

One particular issue are page faults. One would have to prefault the binary executable functions in order to avoid "interruptions" through page faults. Are these proper interrutions of the code? Certainly major faults are but minor faults may be ok? Dunno.

Quoted 8 lines

In practice what I have often seen in such apps is that there is a "warm" up mode where all critical functions are executed, all important variables are touched and dummy I/Os are performed in order to populate the caches and prefault all the data.I guess one would run these without isolation first and then switch on some sort of isolation mode after warm up. So far I think most people relied on the timer interrupt etc etc to be turned off after a few secs of just running throught a polling loop without any OS activities.

This is usually done not as much for page preloading but for cache. There is mlock() and mlockall() that load and lock pages explicitly. One exception is device registers -- they may remain unmapped until accessed.

I can often see a pattern when application enters isolation, calls low-level library such as ODP, gets a page fault, leaves and re-enters isolation, and then everything is running perfectly because everything is mapped. However in those cases mlockall() is done before entering isolation, so regular memory mapping is already there.

Quoted 11 lines
Quoted 11 lines
Quoted 8 lines

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

Interesting. Are you considering opensourcing such library? Seems like a generic problem.

It's already open source, https://github.com/abelits/libtmc

It still needs some work. At the moment it does more than I would prefer because it tries to detect possible problems, such as running timers, and at the same time does not provide some obviously useful things like asynchronous interface to arbitrary file I/O.

I also want to allow the use of some generic interface to triggering interrupts from isolated task to the manager (through, say, a sacrifice of a single GPIO), so if this option is available, the manager won't have to do all that polling.

Quoted 6 lines

Well everyone swears on having the right implementation. The people I know would not do any thing with a socket in such situations. They would only use shared memory and direct access to I/O devices via SPDK and DPDK or the RDMA subsystem.

Same applies to me. My library uses sockets to communicate when the task is not isolated, and it will be necessary if we want to have a dedicated manager process instead of a manager thread in every process. I would prefer initiating a connection with a manager through a socket, and only after that succeeds, assume that I can use any particular part of shared memory (because it means that manager allocated it for me, and no one else will race with me trying to touch it).

Quoted 27 lines
Quoted 20 lines
Quoted 20 lines
Quoted 3 lines

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex:
with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

Quoted 5 lines
Quoted 5 lines

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

Quoted 2 lines

Or move the actions to a different victim processor like done with rcu and vmstat etc etc.

If possible. For most of those things everything can be moved to other CPUs when entering for isolation, or not allowed on CPUs intended for isolation in the first place (how it's mostly done now). The troublesome sources of interruption are things that are legitimately supposed to be done on all CPUs at once to synchronize some important kind of state, and now we want to delay them on some CPUs until the end of isolation.

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

Quoted 7 lines
Quoted 3 lines

Agree. (3) will be necessary as intermediate step. The proposed improvement to Christoph's reply, in this thread, separates notification and syscall blockage.

I guess the notification mode will take care of the way we handle these interruptions.

I think, development should go in parallel -- to have a "delayed synchronization on entry" mechanism that allows "no-interruption mode" (4) to work given that all interruptions are dealt with (that won't work perfectly at first because there are still "unprocessed" sources of interruptions) and a notification mechanism that will allow us to find and properly process them as (3), so we can exclude them and allow (4). Since (4) still requires somewhat intrusive architecture-specific changes, there may be some time when (4) will be only available on some CPUs, but (3) will work on everything.

Signature · 1 line
Alex
#39 lore raw

Re: [RFC] tentative prctl task isolation interface

In reply to Christoph Lameter
Quoted 50 lines · Christoph Lameter
Quoted 11 lines · Marcelo Tosatti

Anyway, trying to improve Christoph's definition:

F_ISOL_QUIESCE -> flush any pending operations that might cause
the CPU to be interrupted (ex: free's per-CPU queues, sync MM statistics counters, etc).

F_ISOL_ISOLATE -> inform the kernel that userspace is
entering isolated mode (see description below on "ISOLATION MODES").

Quoted 5 lines

F_ISOL_UNISOLATE -> inform the kernel that userspace is
leaving isolated mode.

F_ISOL_NOTIFY -> notification mode of isolation breakage
modes.

Looks good to me.

Quoted 10 lines

Isolation modes:
---------------

There are two main types of isolation modes:

- SOFT mode: does not prevent activities which might generate interruptions (such as CPU hotplug).

- HARD mode: prevents all blockable activities that might generate interruptions. Administrators can override this via /sys.

Yup.

Quoted 10 lines

Notifications:
-------------

Notification mode of isolation breakage can be configured as follows:

- None (default): No notification is performed by the kernel on isolation breakage.

- Syslog: Isolation breakage is reported to syslog.

- Abort with core dump

Quoted 7 lines

This is useful for debugging and for hard core bare metalers that never want any interrupts.

One particular issue are page faults. One would have to prefault the binary executable functions in order to avoid "interruptions" through page faults. Are these proper interrutions of the code? Certainly major faults are but minor faults may be ok? Dunno.

mlockall man page:

Real-time processes that are using mlockall() to prevent delays on page faults should reserve enough locked stack pages before entering the time-critical section, so that no page fault can be caused by function calls. This can be achieved by calling a function that allocates a sufficiently large automatic variable (an array) and writes to the memory occupied by this array in order to touch these stack pages. This way, enough pages will be mapped for the stack and can be locked into RAM. The dummy writes ensure that not even copy-on-write page faults can occur in the critical section.

Quoted 8 lines

In practice what I have often seen in such apps is that there is a "warm" up mode where all critical functions are executed, all important variables are touched and dummy I/Os are performed in order to populate the caches and prefault all the data.I guess one would run these without isolation first and then switch on some sort of isolation mode after warm up. So far I think most people relied on the timer interrupt etc etc to be turned off after a few secs of just running throught a polling loop without any OS activities.

Yep.

Quoted 57 lines
Quoted 10 lines
Quoted 7 lines

I ended up implementing a manager/helper task that talks to tasks over a socket (when they are not isolated) and over ring buffers in shared memory (when they are isolated). While the current implementation is rather limited, the intention is to delegate to it everything that isolated task either can't do at all (like, writing logs) or that it would be cumbersome to implement (like monitoring the state of task, determining presence of deferred work after the task returned to userspace), etc.

Interesting. Are you considering opensourcing such library? Seems like a generic problem.

Well everyone swears on having the right implementation. The people I know would not do any thing with a socket in such situations. They would only use shared memory and direct access to I/O devices via SPDK and DPDK or the RDMA subsystem.

Quoted 19 lines
Quoted 19 lines
Quoted 2 lines

Blocking? The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

There are many supposedly innocent things, nowhere at the scale of CPU hotplug, that happen in a system and result in synchronization implemented as an IPI to every online CPU. We should consider them to be an ordinary occurrence, so there is a choice:

1. Ignore them completely and allow them in isolated mode. This will delay userspace with no indication and no isolation breaking.

2. Allow them, and notify userspace afterwards (through vdso or through userspace helper/manager over shared memory). This may be useful in those rare situations when the consequences of delay can be mitigated afterwards.

3. Make them break isolation, with userspace being notified normally (ex:
with a signal in the current implementation). I guess, can be used if somehow most of the causes will be eliminated.

Quoted 5 lines
Quoted 5 lines

4. Prevent them from reaching the target CPU and make sure that whatever synchronization they are intended to cause, will happen when intended target CPU will enter to kernel later. Since we may have to synchronize things like code modification, some of this synchronization has to happen very early on kernel entry.

Or move the actions to a different victim processor like done with rcu and vmstat etc etc.

Quoted 8 lines
Quoted 4 lines

I am most interested in (4), so this is what was implemented in my version of the patch (and currently I am trying to achieve completeness and, if possible, elegance of the implementation).

Agree. (3) will be necessary as intermediate step. The proposed improvement to Christoph's reply, in this thread, separates notification and syscall blockage.

I guess the notification mode will take care of the way we handle these interruptions.

#40 lore raw

Re: [RFC] tentative prctl task isolation interface

In reply to Christoph Lameter
Quoted 11 lines · Christoph Lameter
Quoted 9 lines · Marcelo Tosatti
Quoted 1 line

How does one do a oneshot flush of OS activities?

        ret = prctl(PR_TASK_ISOLATION_REQUEST, ISOL_F_QUIESCE, 0, 0, 0);
        if (ret == -1) {
                perror("prctl PR_TASK_ISOLATION_REQUEST");
                exit(0);
        }
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

I.e. I have a polling loop over numerous shared and I/o devices in user space and I want to make sure that the system is quite before I enter the loop.

You could configure things in two ways: with syscalls allowed or not.

Well syscalls that do not cause deferred processing like getting the time or determining the current cpu should be ok to use.

Yes.

Quoted 2 lines

And I already said that I want the system to quiet down and allow system calls.

Also see that as being useful.

Quoted 2 lines

Some indication that deferred actions have occurred may be useful by f.e. resetting the flag.

OK: will implement on next patchset.

Quoted 5 lines
Quoted 3 lines

1) Add a new isolation feature ISOL_F_BLOCK_SYSCALLS (to block certain syscalls) along with ISOL_F_SETUP_NOTIF (to notify upon isolation breaking):

Well come up with a use case for that .... I know mine.

Trying to come up with an interface that accomodates all known use cases. Maybe passing the allowed list of syscalls is overkill, but Alex seems interested in the notification to break isolation.

Quoted 4 lines

What you propose
could be useful for debugging for me but I would prefer the quiet down approach where I determine when I use some syscalls or not and will deal with the consequences.

Trying to cover the usecases that Alex mentioned on this thread...

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

Features that I think may be needed:

F_ISOL_QUIESCE -> quiet down now but allow all OS activities. OS
activites reset flag

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

F_ISOL_BAREMETAL_HARD -> No OS interruptions. Fault on syscalls that
require such actions in the future.

Question: why BAREMETAL ?

To disinguish it from "Realtime". We want the processor for ourselves without anything else running on it.

OK.

Quoted 7 lines
Quoted 5 lines

Two comments:

1) HARD mode could also block activities from different CPUs that can interrupt this isolated CPU (for example CPU hotplug, or increasing per-CPU trace buffer size).

Blocking?

Block CPU hotplug for example:

# echo 0 > /sys/devices/system/cpu/cpu3/online
returns -EBUSY with message saying:

"Can't offline cpu3: reason: cpu9 is isolated by application APP".

Quoted 10 lines

The app should fail if any deferred actions are triggered as a result of syscalls. It would give a warning with _WARN

Quoted 6 lines

2) For a type of application it is the case that certain interruptions can be tolerated, as long as they do not cross certain thresholds. For example, one loses the flexibility to read/write MSRs on the isolated CPUs (including performance counters, RDT/MBM type MSRs, frequency/power statistics) by
forcing a "no interruptions" mode.

Quoted 2 lines

Does reading these really cause deferred actions by the OS? AFAICT you could map these into memory as well as read them without OS activities.

AFAIK you can't for MSRs.

Quoted 4 lines

"Interruptions that can be tolerated".... Well that is the wild west of "realtime" where you can define how much of a time slice is "real" and how much can be use by other processes. I do not think that any of that should come into this API.

Understood.

#41 lore raw

[mm] e655d17ffa: BUG:using_smp_processor_id()in_preemptible

In reply to Marcelo Tosatti
FYI, we noticed the following commit (built with gcc-9):

Greeting,

FYI, we noticed the following commit (built with gcc-9):

commit: e655d17ffada57d11a82336a43fd91dd9c2ecbd2 ("[PATCH] mm: introduce sysctl file to flush per-cpu vmstat statistics")
url: https://github.com/0day-ci/linux/commits/Marcelo-Tosatti/mm-introduce-sysctl-file-to-flush-per-cpu-vmstat-statistics/20201118-002950
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git 9c87c9f41245baa3fc4716cf39141439cf405b01

in testcase: kernel-selftests
version: kernel-selftests-x86_64-b5a583fb-1_20201015 with following parameters:

	group: group-02
	ucode: 0xe2

test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt

on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G memory

caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):

If you fix the issue, kindly add following tag

kern  :err   : [  318.711546] BUG: using smp_processor_id() in preemptible [00000000] code: read/27945
kern  :warn  : [  318.719301] caller is proc_quiet_vmstat+0x44/0x80
kern  :warn  : [  318.724037] CPU: 1 PID: 27945 Comm: read Not tainted 5.10.0-rc4-00068-ge655d17ffada #1
kern  :warn  : [  318.731971] Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT, BIOS 1.8.1 12/05/2017
kern  :warn  : [  318.739377] Call Trace:
kern  :warn  : [  318.741824]  dump_stack+0x8d/0xb5
kern  :warn  : [  318.745140]  check_preemption_disabled+0xc3/0xe0
kern  :warn  : [  318.749761]  proc_quiet_vmstat+0x44/0x80
kern  :warn  : [  318.753684]  __cgroup_bpf_run_filter_sysctl+0xa4/0x580
kern  :warn  : [  318.758834]  proc_sys_call_handler+0x20f/0x260
kern  :warn  : [  318.763282]  new_sync_read+0x11b/0x1a0
kern  :warn  : [  318.767039]  vfs_read+0x16d/0x1e0
kern  :warn  : [  318.770381]  ksys_read+0x68/0xe0
kern  :warn  : [  318.773612]  do_syscall_64+0x33/0x40
kern  :warn  : [  318.777188]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern  :warn  : [  318.782241] RIP: 0033:0x7fe113db4461
kern  :warn  : [  318.785816] Code: fe ff ff 50 48 8d 3d fe d0 09 00 e8 e9 03 02 00 66 0f 1f 84 00 00 00 00 00 48 8d 05 99 62 0d 00 8b 00 85 c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 c3 66 0f 1f 44 00 00 41 54 49 89 d4 55 48
kern  :warn  : [  318.804587] RSP: 002b:00007ffdfe04a328 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
kern  :warn  : [  318.812158] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007fe113db4461
kern  :warn  : [  318.819293] RDX: 0000000000001000 RSI: 00007ffdfe04a330 RDI: 0000000000000008
kern  :warn  : [  318.826430] RBP: 0000559d31881039 R08: 0000000000000003 R09: 0000000000000078
kern  :warn  : [  318.833565] R10: 0000000000000000 R11: 0000000000000246 R12: 0000559d31881038
kern  :warn  : [  318.840704] R13: 0000000000000002 R14: 0000559d3188107a R15: 0000559d32a6f9db
kern  :err   : [  318.847944] BUG: using smp_processor_id() in preemptible [00000000] code: read/27945
kern  :warn  : [  318.855728] caller is proc_quiet_vmstat+0x44/0x80
kern  :warn  : [  318.860612] CPU: 1 PID: 27945 Comm: read Not tainted 5.10.0-rc4-00068-ge655d17ffada #1
kern  :warn  : [  318.868542] Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT, BIOS 1.8.1 12/05/2017
kern  :warn  : [  318.875938] Call Trace:
kern  :warn  : [  318.878387]  dump_stack+0x8d/0xb5
kern  :warn  : [  318.881706]  check_preemption_disabled+0xc3/0xe0
kern  :warn  : [  318.886341]  proc_quiet_vmstat+0x44/0x80
kern  :warn  : [  318.890278]  proc_sys_call_handler+0x13e/0x260
kern  :warn  : [  318.894728]  new_sync_read+0x11b/0x1a0
kern  :warn  : [  318.898486]  vfs_read+0x16d/0x1e0
kern  :warn  : [  318.901804]  ksys_read+0x68/0xe0
kern  :warn  : [  318.905035]  do_syscall_64+0x33/0x40
kern  :warn  : [  318.908612]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern  :warn  : [  318.913662] RIP: 0033:0x7fe113db4461
kern  :warn  : [  318.917237] Code: fe ff ff 50 48 8d 3d fe d0 09 00 e8 e9 03 02 00 66 0f 1f 84 00 00 00 00 00 48 8d 05 99 62 0d 00 8b 00 85 c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 c3 66 0f 1f 44 00 00 41 54 49 89 d4 55 48
kern  :warn  : [  318.936009] RSP: 002b:00007ffdfe04a328 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
kern  :warn  : [  318.943578] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007fe113db4461
kern  :warn  : [  318.950715] RDX: 0000000000001000 RSI: 00007ffdfe04a330 RDI: 0000000000000008
kern  :warn  : [  318.957849] RBP: 0000559d31881039 R08: 0000000000000003 R09: 0000000000000078
kern  :warn  : [  318.964982] R10: 0000000000000000 R11: 0000000000000246 R12: 0000559d31881038
kern  :warn  : [  318.972116] R13: 0000000000000002 R14: 0000559d3188107a R15: 0000559d32a6f9db
kern  :info  : [  319.061697] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) show-all-locks(d) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) dump-ftrace-buffer(z) 
user  :notice: [  321.570463] ok 12 selftests: proc: read

user :notice: [ 321.577830] # selftests: proc: self

user :notice: [ 321.599985] ok 13 selftests: proc: self

user :notice: [ 321.606065] # selftests: proc: setns-dcache

user :notice: [ 321.627516] ok 14 selftests: proc: setns-dcache

user :notice: [ 321.634335] # selftests: proc: setns-sysvipc

user :notice: [ 321.655104] ok 15 selftests: proc: setns-sysvipc

user :notice: [ 321.662039] # selftests: proc: thread-self

user :notice: [ 321.682210] ok 16 selftests: proc: thread-self

user :notice: [ 321.689137] # selftests: proc: proc-multiple-procfs

user :notice: [ 321.710024] ok 17 selftests: proc: proc-multiple-procfs

user :notice: [ 321.717763] # selftests: proc: proc-fsconfig-hidepid

user :notice: [ 321.737068] ok 18 selftests: proc: proc-fsconfig-hidepid

user :notice: [ 321.745566] make: warning: Clock skew detected. Your build may be incomplete.

user :notice: [ 321.757738] make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-7.6-kselftests-e655d17ffada57d11a82336a43fd91dd9c2ecbd2/tools/testing/selftests/proc'

kern  :info  : [  321.792514] ramoops: using module parameters
kern  :info  : [  321.798332] pstore: Using crash dump compression: deflate
kern  :info  : [  321.804336] printk: console [ramoops-1] enabled
kern  :info  : [  321.809491] pstore: Registered ramoops as persistent store backend
kern  :info  : [  321.815684] ramoops: using 0xf4240@0x8000000, ecc: 0
user  :notice: [  321.827756] 2019-02-14 10:16:47 make run_tests -C pstore

user :notice: [ 321.857425] make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-7.6-kselftests-e655d17ffada57d11a82336a43fd91dd9c2ecbd2/tools/testing/selftests/pstore'

user :notice: [ 321.875269] make: Warning: File '../lib.mk' has modification time 55836578 s in the future

user :notice: [ 321.885765] TAP version 13

user :notice: [ 321.890482] 1..2

user :notice: [ 321.894762] # selftests: pstore: pstore_tests

user :notice: [ 321.903480] # === Pstore unit tests (pstore_tests) ===

user :notice: [ 321.911204] # UUID=a6a480bd-f511-418e-83f0-0c625840f032

user :notice: [ 321.919011] # Checking pstore backend is registered ... ok

user :notice: [ 321.926522] # backend=ramoops

user :notice: [ 325.968623] # cmdline=ip=::::lkp-skl-d05::dhcp root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/lkp-skl-d05/kernel-selftests-group-02-ucode=0xe2-debian-10.4-x86_64-20200603.cgz-e655d17ffada57d11a82336a43fd91dd9c2ecbd2-20201122-19793-14arzjn-2.yaml ARCH=x86_64 kconfig=x86_64-rhel-7.6-kselftests branch=linux-review/Marcelo-Tosatti/mm-introduce-sysctl-file-to-flush-per-cpu-vmstat-statistics/20201118-002950 commit=e655d17ffada57d11a82336a43fd91dd9c2ecbd2 BOOT_IMAGE=/pkg/linux/x86_64-rhel-7.6-kselftests/gcc-9/e655d17ffada57d11a82336a43fd91dd9c2ecbd2/vmlinuz-5.10.0-rc4-00068-ge655d17ffada erst_disable max_uptime=3600 RESULT_ROOT=/result/kernel-selftests/group-02-ucode=0xe2/lkp-skl-d05/debian-10.4-x86_64-20200603.cgz/x86_64-rhel-7.6-kselftests/gcc-9/e655d17ffada57d11a82336a43fd91dd9c2ecbd2/3 LKP_SERVER=internal-lkp-server nokaslr selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeou

user :notice: [ 328.399180] # Checking pstore console is registered ... ok

user :notice: [ 328.406998] # Checking /dev/pmsg0 exists ... ok

user :notice: [ 328.414030] # Writing unique string to /dev/pmsg0 ... ok

user :notice: [ 328.421763] ok 1 selftests: pstore: pstore_tests

user :notice: [ 328.428885] # selftests: pstore: pstore_post_reboot_tests

user :notice: [ 328.818409] # === Pstore unit tests (pstore_post_reboot_tests) ===

user :notice: [ 328.827075] # UUID=5d84a735-2106-4f87-b7dd-61334ca4ce96

user :notice: [ 328.834896] # Checking pstore backend is registered ... ok

user :notice: [ 328.842335] # backend=ramoops

user :notice: [ 341.500511] # cmdline=ip=::::lkp-skl-d05::dhcp root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/lkp-skl-d05/kernel-selftests-group-02-ucode=0xe2-debian-10.4-x86_64-20200603.cgz-e655d17ffada57d11a82336a43fd91dd9c2ecbd2-20201122-19793-14arzjn-2.yaml ARCH=x86_64 kconfig=x86_64-rhel-7.6-kselftests branch=linux-review/Marcelo-Tosatti/mm-introduce-sysctl-file-to-flush-per-cpu-vmstat-statistics/20201118-002950 commit=e655d17ffada57d11a82336a43fd91dd9c2ecbd2 BOOT_IMAGE=/pkg/linux/x86_64-rhel-7.6-kselftests/gcc-9/e655d17ffada57d11a82336a43fd91dd9c2ecbd2/vmlinuz-5.10.0-rc4-00068-ge655d17ffada erst_disable max_uptime=3600 RESULT_ROOT=/result/kernel-selftests/group-02-ucode=0xe2/lkp-skl-d05/debian-10.4-x86_64-20200603.cgz/x86_64-rhel-7.6-kselftests/gcc-9/e655d17ffada57d11a82336a43fd91dd9c2ecbd2/3 LKP_SERVER=internal-lkp-server nokaslr selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeou

user :notice: [ 345.010149] # pstore_crash_test has not been executed yet. we skip further tests.

To reproduce:

git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml

Thanks,
Oliver Sang

#
# Automatically generated file; DO NOT EDIT. # Linux/x86_64 5.10.0-rc4 Kernel Configuration #
CONFIG_CC_VERSION_TEXT="gcc-9 (Debian 9.3.0-15) 9.3.0" CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=90300 CONFIG_LD_VERSION=235000000 CONFIG_CLANG_VERSION=0
CONFIG_CC_CAN_LINK=y CONFIG_CC_CAN_LINK_STATIC=y CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_HAVE_KERNEL_ZSTD=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
# CONFIG_KERNEL_ZSTD is not set
CONFIG_DEFAULT_INIT=""
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_WATCH_QUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_GENERIC_IRQ_MIGRATION=y
CONFIG_GENERIC_IRQ_INJECTION=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_SIM=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
CONFIG_IRQ_MSI_IOMMU=y
CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y
CONFIG_GENERIC_IRQ_RESERVATION_MODE=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set

# end of IRQ subsystem

CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_INIT=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=y
CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not set
CONFIG_NO_HZ_FULL=y
CONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

# end of Timers subsystem

# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y

#
# CPU/Task time and stats accounting
#
CONFIG_VIRT_CPU_ACCOUNTING=y
CONFIG_VIRT_CPU_ACCOUNTING_GEN=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_HAVE_SCHED_AVG_IRQ=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set

# end of CPU/Task time and stats accounting

CONFIG_CPU_ISOLATION=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
CONFIG_PREEMPT_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU_GENERIC=y
CONFIG_TASKS_RCU=y
CONFIG_TASKS_RUDE_RCU=y
CONFIG_TASKS_TRACE_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_RCU_NOCB_CPU=y

# end of RCU Subsystem

CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y

#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set

# end of Scheduler features

CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y
CONFIG_CC_HAS_INT128=y
CONFIG_ARCH_SUPPORTS_INT128=y
CONFIG_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_KMEM=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_PIDS=y
# CONFIG_CGROUP_RDMA is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_SOCK_CGROUP_DATA=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_TIME_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_CHECKPOINT_RESTORE=y
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not set
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BPF=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SGETMASK_SYSCALL=y
CONFIG_SYSFS_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_IO_URING=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_HAVE_ARCH_USERFAULTFD_WP=y
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_ABSOLUTE_PERCPU=y
CONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_BPF_LSM is not set
CONFIG_BPF_SYSCALL=y
CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y
CONFIG_BPF_JIT_ALWAYS_ON=y
CONFIG_BPF_JIT_DEFAULT_ON=y
# CONFIG_BPF_PRELOAD is not set
CONFIG_USERFAULTFD=y
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not set
CONFIG_EMBEDDED=y
CONFIG_HAVE_PERF_EVENTS=y
# CONFIG_PC104 is not set

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set

# end of Kernel Performance Events And Counters

CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_MEMCG_SYSFS_ON is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
CONFIG_SLUB_CPU_PARTIAL=y
CONFIG_SYSTEM_DATA_VERIFICATION=y
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y

# end of General setup

CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=28
CONFIG_ARCH_MMAP_RND_BITS_MAX=32
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_FILTER_PGPROT=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DYNAMIC_PHYSICAL_MASK=y
CONFIG_PGTABLE_LEVELS=5
CONFIG_CC_HAS_SANE_STACKPROTECTOR=y

#
# Processor type and features
#
CONFIG_ZONE_DMA=y
CONFIG_SMP=y
CONFIG_X86_FEATURE_NAMES=y
CONFIG_X86_X2APIC=y
CONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not set
CONFIG_RETPOLINE=y
CONFIG_X86_CPU_RESCTRL=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not set
CONFIG_X86_UV=y
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_MID is not set
CONFIG_X86_INTEL_LPSS=y
CONFIG_X86_AMD_PLATFORM_DEVICE=y
CONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set
CONFIG_HYPERVISOR_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_XXL=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_X86_HV_CALLBACK_VECTOR=y
CONFIG_XEN=y
CONFIG_XEN_PV=y
CONFIG_XEN_PV_SMP=y
# CONFIG_XEN_DOM0 is not set
CONFIG_XEN_PVHVM=y
CONFIG_XEN_PVHVM_SMP=y
CONFIG_XEN_512GB=y
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_PVH is not set
CONFIG_KVM_GUEST=y
CONFIG_ARCH_CPUIDLE_HALTPOLL=y
# CONFIG_PVH is not set
CONFIG_PARAVIRT_TIME_ACCOUNTING=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_ACRN_GUEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_IA32_FEAT_CTL=y
CONFIG_X86_VMX_FEATURE_NAMES=y
# CONFIG_PROCESSOR_SELECT is not set
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_HYGON=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_ZHAOXIN=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_MAXSMP=y
CONFIG_NR_CPUS_RANGE_BEGIN=8192
CONFIG_NR_CPUS_RANGE_END=8192
CONFIG_NR_CPUS_DEFAULT=8192
CONFIG_NR_CPUS=8192
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_SCHED_MC_PRIO=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCELOG_LEGACY is not set
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_X86_MCE_INJECT=m
CONFIG_X86_THERMAL_VECTOR=y

#
# Performance monitoring
#
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_PERF_EVENTS_INTEL_RAPL=y
CONFIG_PERF_EVENTS_INTEL_CSTATE=y
# CONFIG_PERF_EVENTS_AMD_POWER is not set

# end of Performance monitoring

CONFIG_X86_16BIT=y
CONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_IOPL_IOPERM=y
CONFIG_I8K=m
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_5LEVEL=y
CONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set CONFIG_AMD_MEM_ENCRYPT=y
# CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set CONFIG_NUMA=y
CONFIG_AMD_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NUMA_EMU=y
CONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=y
CONFIG_X86_SMAP=y
CONFIG_X86_UMIP=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_X86_INTEL_TSX_MODE_OFF=y
# CONFIG_X86_INTEL_TSX_MODE_ON is not set
# CONFIG_X86_INTEL_TSX_MODE_AUTO is not set CONFIG_EFI=y
CONFIG_EFI_STUB=y
CONFIG_EFI_MIXED=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y
# CONFIG_KEXEC_SIG is not set CONFIG_CRASH_DUMP=y
CONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=y
CONFIG_RANDOMIZE_BASE=y
CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_XONLY is not set
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=y
CONFIG_LIVEPATCH=y

# end of Processor type and features

CONFIG_ARCH_HAS_ADD_PAGES=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y
CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y
CONFIG_ARCH_ENABLE_THP_MIGRATION=y

#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not set
CONFIG_HIBERNATE_CALLBACKS=y
CONFIG_HIBERNATION=y
CONFIG_HIBERNATION_SNAPSHOT_DEV=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_PM_ADVANCED_DEBUG=y
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_PM_SLEEP_DEBUG=y
# CONFIG_DPM_WATCHDOG is not set
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not set
CONFIG_ARCH_SUPPORTS_ACPI=y
CONFIG_ACPI=y
CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y
CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y
CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not set
CONFIG_ACPI_SPCR_TABLE=y
CONFIG_ACPI_LPIT=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y
CONFIG_ACPI_EC_DEBUGFS=m
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_TAD is not set
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_CPU_FREQ_PSS=y
CONFIG_ACPI_PROCESSOR_CSTATE=y
CONFIG_ACPI_PROCESSOR_IDLE=y
CONFIG_ACPI_CPPC_LIB=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_IPMI=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
CONFIG_ACPI_THERMAL=y
CONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=y
CONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_HOTPLUG_MEMORY=y
CONFIG_ACPI_HOTPLUG_IOAPIC=y
CONFIG_ACPI_SBS=m
CONFIG_ACPI_HED=y
CONFIG_ACPI_CUSTOM_METHOD=m
CONFIG_ACPI_BGRT=y
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set
CONFIG_ACPI_NFIT=m
# CONFIG_NFIT_SECURITY_DEBUG is not set
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_HMAT is not set
CONFIG_HAVE_ACPI_APEI=y
CONFIG_HAVE_ACPI_APEI_NMI=y
CONFIG_ACPI_APEI=y
CONFIG_ACPI_APEI_GHES=y
CONFIG_ACPI_APEI_PCIEAER=y
CONFIG_ACPI_APEI_MEMORY_FAILURE=y
CONFIG_ACPI_APEI_EINJ=m
# CONFIG_ACPI_APEI_ERST_DEBUG is not set
# CONFIG_ACPI_DPTF is not set
CONFIG_ACPI_WATCHDOG=y
CONFIG_ACPI_EXTLOG=m
CONFIG_ACPI_ADXL=y
# CONFIG_ACPI_CONFIGFS is not set
# CONFIG_PMIC_OPREGION is not set
CONFIG_X86_PM_TIMER=y
CONFIG_SFI=y

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y 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_X86_INTEL_PSTATE=y
CONFIG_X86_PCC_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ_CPB=y
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_AMD_FREQ_SENSITIVITY=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
CONFIG_X86_P4_CLOCKMOD=m

#

# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=m
# end of CPU Frequency scaling

#
# CPU Idle
#
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
# CONFIG_CPU_IDLE_GOV_HALTPOLL is not set
CONFIG_HALTPOLL_CPUIDLE=y

# end of CPU Idle

CONFIG_INTEL_IDLE=y

# end of Power management and ACPI options

#
# Bus options (PCI etc.)
#
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_MMCONF_FAM10H=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_ISA_BUS is not set
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
# CONFIG_X86_SYSFB is not set

# end of Bus options (PCI etc.)

#
# Binary Emulations
#
CONFIG_IA32_EMULATION=y
# CONFIG_X86_X32 is not set
CONFIG_COMPAT_32=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y

# end of Binary Emulations

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_EDD_OFF is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_DMIID=y
CONFIG_DMI_SYSFS=y
CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
CONFIG_FW_CFG_SYSFS=y
# CONFIG_FW_CFG_SYSFS_CMDLINE is not set
# CONFIG_GOOGLE_FIRMWARE is not set

#
# EFI (Extensible Firmware Interface) Support
#
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_VARS_PSTORE=y
CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y
CONFIG_EFI_RUNTIME_MAP=y
# CONFIG_EFI_FAKE_MEMMAP is not set
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFI_TEST is not set
CONFIG_APPLE_PROPERTIES=y
# CONFIG_RESET_ATTACK_MITIGATION is not set
# CONFIG_EFI_RCI2_TABLE is not set
# CONFIG_EFI_DISABLE_PCI_DMA is not set

# end of EFI (Extensible Firmware Interface) Support

CONFIG_UEFI_CPER=y
CONFIG_UEFI_CPER_X86=y
CONFIG_EFI_DEV_PATH_PARSER=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_CUSTOM_SSDT_OVERLAYS=y

#
# Tegra firmware driver
#

# end of Tegra firmware driver
# end of Firmware Drivers

CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_IRQFD=y
CONFIG_HAVE_KVM_IRQ_ROUTING=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_HAVE_KVM_MSI=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_KVM_VFIO=y
CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y
CONFIG_KVM_COMPAT=y
CONFIG_HAVE_KVM_IRQ_BYPASS=y
CONFIG_HAVE_KVM_NO_POLL=y
CONFIG_KVM_XFER_TO_GUEST_WORK=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
# CONFIG_KVM_WERROR is not set
CONFIG_KVM_INTEL=y
# CONFIG_KVM_AMD is not set
CONFIG_KVM_MMU_AUDIT=y
CONFIG_AS_AVX512=y
CONFIG_AS_SHA1_NI=y
CONFIG_AS_SHA256_NI=y
CONFIG_AS_TPAUSE=y

#
# General architecture-dependent options
#
CONFIG_CRASH_CORE=y
CONFIG_KEXEC_CORE=y
CONFIG_HOTPLUG_SMT=y
CONFIG_GENERIC_ENTRY=y
CONFIG_OPROFILE=m
CONFIG_OPROFILE_EVENT_MULTIPLEX=y
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_STATIC_CALL_SELFTEST is not set
CONFIG_OPTPROBES=y
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_UPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_KRETPROBES=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_HAVE_FUNCTION_ERROR_INJECTION=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_ARCH_HAS_SET_DIRECT_MAP=y
CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y
CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=y
CONFIG_HAVE_ASM_MODVERSIONS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_FUNCTION_ARG_ACCESS_API=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=y
CONFIG_MMU_GATHER_TABLE_FREE=y
CONFIG_MMU_GATHER_RCU_TABLE_FREE=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_ARCH_STACKLEAK=y
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOVE_PMD=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=y
CONFIG_HAVE_ARCH_HUGE_VMAP=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_HAVE_ARCH_SOFT_DIRTY=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_RELA=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS=28
CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=y
CONFIG_ARCH_MMAP_RND_COMPAT_BITS=8
CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=y
CONFIG_HAVE_STACK_VALIDATION=y
CONFIG_HAVE_RELIABLE_STACKTRACE=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_COMPAT_OLD_SIGACTION=y
CONFIG_COMPAT_32BIT_TIME=y
CONFIG_HAVE_ARCH_VMAP_STACK=y
CONFIG_VMAP_STACK=y
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_STRICT_MODULE_RWX=y
CONFIG_HAVE_ARCH_PREL32_RELOCATIONS=y
CONFIG_ARCH_USE_MEMREMAP_PROT=y
# CONFIG_LOCK_EVENT_COUNTS is not set
CONFIG_ARCH_HAS_MEM_ENCRYPT=y
CONFIG_HAVE_STATIC_CALL=y
CONFIG_HAVE_STATIC_CALL_INLINE=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_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=y
CONFIG_BASE_SMALL=0
CONFIG_MODULE_SIG_FORMAT=y
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256"
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set # CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_BLK_SCSI_REQUEST=y CONFIG_BLK_CGROUP_RWSTAT=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_INTEGRITY_T10=m
# CONFIG_BLK_DEV_ZONED is not set CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set CONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set

# end of Partition Types

CONFIG_BLOCK_COMPAT=y
CONFIG_BLK_MQ_PCI=y
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_BLK_PM=y

#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set

# end of IO Schedulers

CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
CONFIG_ASN1=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y
CONFIG_QUEUED_SPINLOCKS=y
CONFIG_ARCH_USE_QUEUED_RWLOCKS=y
CONFIG_QUEUED_RWLOCKS=y
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
CONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=y
CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y
CONFIG_FREEZER=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
CONFIG_BINFMT_MISC=m
CONFIG_COREDUMP=y

# end of Executable file formats

#
# Memory Management options
#
CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_FAST_GUP=y CONFIG_NUMA_KEEP_MEMINFO=y CONFIG_MEMORY_ISOLATION=y CONFIG_HAVE_BOOTMEM_INFO_NODE=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set CONFIG_MEMORY_HOTREMOVE=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MEMORY_BALLOON=y CONFIG_BALLOON_COMPACTION=y CONFIG_COMPACTION=y
CONFIG_PAGE_REPORTING=y
CONFIG_MIGRATION=y
CONFIG_CONTIG_ALLOC=y CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y CONFIG_HWPOISON_INJECT=m CONFIG_TRANSPARENT_HUGEPAGE=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set CONFIG_ARCH_WANTS_THP_SWAP=y CONFIG_THP_SWAP=y
CONFIG_CLEANCACHE=y
CONFIG_FRONTSWAP=y
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set CONFIG_CMA_AREAS=7
CONFIG_MEM_SOFT_DIRTY=y
CONFIG_ZSWAP=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_ZSWAP_DEFAULT_ON is not set CONFIG_ZPOOL=y
CONFIG_ZBUD=y
# CONFIG_Z3FOLD is not set
CONFIG_ZSMALLOC=y
# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set # CONFIG_ZSMALLOC_STAT is not set CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_DEFERRED_STRUCT_PAGE_INIT=y CONFIG_IDLE_PAGE_TRACKING=y CONFIG_ARCH_HAS_PTE_DEVMAP=y CONFIG_ZONE_DEVICE=y CONFIG_DEV_PAGEMAP_OPS=y
CONFIG_HMM_MIRROR=y
CONFIG_DEVICE_PRIVATE=y
CONFIG_VMAP_PFN=y
CONFIG_FRAME_VECTOR=y CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y CONFIG_ARCH_HAS_PKEYS=y
# CONFIG_PERCPU_STATS is not set CONFIG_GUP_BENCHMARK=y
# CONFIG_READ_ONLY_THP_FOR_FS is not set CONFIG_ARCH_HAS_PTE_SPECIAL=y CONFIG_MAPPING_DIRTY_HELPERS=y

# end of Memory Management options

CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
CONFIG_NET_INGRESS=y
CONFIG_NET_EGRESS=y
CONFIG_NET_REDIRECT=y
CONFIG_SKB_EXTENSIONS=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_DIAG=m
CONFIG_UNIX=y
CONFIG_UNIX_SCM=y
CONFIG_UNIX_DIAG=m
CONFIG_TLS=m
# CONFIG_TLS_DEVICE is not set
# CONFIG_TLS_TOE is not set
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_USER_COMPAT is not set
# CONFIG_XFRM_INTERFACE is not set
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_XFRM_AH=m
CONFIG_XFRM_ESP=m
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_XDP_SOCKETS=y
# CONFIG_XDP_SOCKETS_DIAG is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_CLASSID=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE_DEMUX=y
CONFIG_NET_IP_TUNNEL=y
CONFIG_NET_IPGRE=y
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE_COMMON=y
CONFIG_IP_MROUTE=y
CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
CONFIG_NET_IPVTI=m
CONFIG_NET_UDP_TUNNEL=y
CONFIG_NET_FOU=y
CONFIG_NET_FOU_IP_TUNNELS=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
# CONFIG_INET_ESP_OFFLOAD is not set
# CONFIG_INET_ESPINTCP is not set
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_INET_UDP_DIAG=m
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
# CONFIG_TCP_CONG_NV is not set
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_TCP_CONG_DCTCP=m
# CONFIG_TCP_CONG_CDG is not set
# CONFIG_TCP_CONG_BBR is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
# CONFIG_INET6_ESP_OFFLOAD is not set
# CONFIG_INET6_ESPINTCP is not set
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
# CONFIG_IPV6_ILA is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=y
CONFIG_IPV6_VTI=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_SIT_6RD=y
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=y
CONFIG_IPV6_GRE=y
CONFIG_IPV6_FOU=y
CONFIG_IPV6_FOU_TUNNEL=y
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_IPV6_SEG6_LWTUNNEL=y
# CONFIG_IPV6_SEG6_HMAC is not set
CONFIG_IPV6_SEG6_BPF=y
# CONFIG_IPV6_RPL_LWTUNNEL is not set
CONFIG_NETLABEL=y
CONFIG_MPTCP=y
CONFIG_INET_MPTCP_DIAG=m
CONFIG_MPTCP_IPV6=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NET_PTP_CLASSIFY=y
CONFIG_NETWORK_PHY_TIMESTAMPING=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=m

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_FAMILY_BRIDGE=y
CONFIG_NETFILTER_FAMILY_ARP=y
CONFIG_NETFILTER_NETLINK_ACCT=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NETFILTER_NETLINK_OSF=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_LOG_COMMON=m
# CONFIG_NF_LOG_NETDEV is not set
CONFIG_NETFILTER_CONNCOUNT=m
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_ZONES=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=y
CONFIG_NF_CONNTRACK_LABELS=y
CONFIG_NF_CT_PROTO_DCCP=y
CONFIG_NF_CT_PROTO_GRE=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CT_PROTO_UDPLITE=y
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_BROADCAST=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_SNMP=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NF_CT_NETLINK_TIMEOUT=m
# CONFIG_NETFILTER_NETLINK_GLUE_CT is not set
CONFIG_NF_NAT=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_SIP=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_REDIRECT=y
CONFIG_NF_NAT_MASQUERADE=y
CONFIG_NETFILTER_SYNPROXY=m
CONFIG_NF_TABLES=m
CONFIG_NF_TABLES_INET=y
CONFIG_NF_TABLES_NETDEV=y
# CONFIG_NFT_NUMGEN is not set
CONFIG_NFT_CT=m
CONFIG_NFT_FLOW_OFFLOAD=m
CONFIG_NFT_COUNTER=m
# CONFIG_NFT_CONNLIMIT is not set
CONFIG_NFT_LOG=m
CONFIG_NFT_LIMIT=m
CONFIG_NFT_MASQ=m
CONFIG_NFT_REDIR=m
CONFIG_NFT_NAT=m
# CONFIG_NFT_TUNNEL is not set
CONFIG_NFT_OBJREF=m
CONFIG_NFT_QUEUE=m
# CONFIG_NFT_QUOTA is not set
CONFIG_NFT_REJECT=m
CONFIG_NFT_REJECT_INET=m
CONFIG_NFT_COMPAT=m
CONFIG_NFT_HASH=m
# CONFIG_NFT_XFRM is not set
# CONFIG_NFT_SOCKET is not set
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NFT_SYNPROXY is not set
# CONFIG_NF_DUP_NETDEV is not set
# CONFIG_NFT_DUP_NETDEV is not set
# CONFIG_NFT_FWD_NETDEV is not set
CONFIG_NF_FLOW_TABLE_INET=m
CONFIG_NF_FLOW_TABLE=m
CONFIG_NETFILTER_XTABLES=y

#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
CONFIG_NETFILTER_XT_CONNMARK=m
CONFIG_NETFILTER_XT_SET=m

#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_AUDIT=m
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_CT=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_HMARK=m
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_LOG=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_NAT=m
CONFIG_NETFILTER_XT_TARGET_NETMAP=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_REDIRECT=m
CONFIG_NETFILTER_XT_TARGET_MASQUERADE=m
CONFIG_NETFILTER_XT_TARGET_TEE=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m

#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
CONFIG_NETFILTER_XT_MATCH_BPF=m
CONFIG_NETFILTER_XT_MATCH_CGROUP=m
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLABEL=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_CPU=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ECN=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not set
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_IPVS=m
CONFIG_NETFILTER_XT_MATCH_L2TP=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_NFACCT=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m

# end of Core Netfilter Configuration

CONFIG_IP_SET=m
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=m
CONFIG_IP_SET_BITMAP_IPMAC=m
CONFIG_IP_SET_BITMAP_PORT=m
CONFIG_IP_SET_HASH_IP=m
CONFIG_IP_SET_HASH_IPMARK=m
CONFIG_IP_SET_HASH_IPPORT=m
CONFIG_IP_SET_HASH_IPPORTIP=m
CONFIG_IP_SET_HASH_IPPORTNET=m
CONFIG_IP_SET_HASH_IPMAC=m
CONFIG_IP_SET_HASH_MAC=m
CONFIG_IP_SET_HASH_NETPORTNET=m
CONFIG_IP_SET_HASH_NET=m
CONFIG_IP_SET_HASH_NETNET=m
CONFIG_IP_SET_HASH_NETPORT=m
CONFIG_IP_SET_HASH_NETIFACE=m
CONFIG_IP_SET_LIST_SET=m
CONFIG_IP_VS=m
CONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
CONFIG_IP_VS_PROTO_SCTP=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
# CONFIG_IP_VS_FO is not set
# CONFIG_IP_VS_OVF is not set
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
# CONFIG_IP_VS_MH is not set
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS SH scheduler
#
CONFIG_IP_VS_SH_TAB_BITS=8

#
# IPVS MH scheduler
#
CONFIG_IP_VS_MH_TAB_INDEX=12

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IP_VS_NFCT=y
CONFIG_IP_VS_PE_SIP=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_SOCKET_IPV4=m
CONFIG_NF_TPROXY_IPV4=m
CONFIG_NF_TABLES_IPV4=y
CONFIG_NFT_REJECT_IPV4=m
# CONFIG_NFT_DUP_IPV4 is not set
# CONFIG_NFT_FIB_IPV4 is not set
# CONFIG_NF_TABLES_ARP is not set
CONFIG_NF_FLOW_TABLE_IPV4=m
CONFIG_NF_DUP_IPV4=m
# CONFIG_NF_LOG_ARP is not set
CONFIG_NF_LOG_IPV4=m
CONFIG_NF_REJECT_IPV4=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_RPFILTER=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_SYNPROXY=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

# end of IP: Netfilter Configuration

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_SOCKET_IPV6=m
CONFIG_NF_TPROXY_IPV6=m
CONFIG_NF_TABLES_IPV6=y
CONFIG_NFT_REJECT_IPV6=m
# CONFIG_NFT_DUP_IPV6 is not set
# CONFIG_NFT_FIB_IPV6 is not set
CONFIG_NF_FLOW_TABLE_IPV6=m
CONFIG_NF_DUP_IPV6=m
CONFIG_NF_REJECT_IPV6=m
CONFIG_NF_LOG_IPV6=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RPFILTER=m
CONFIG_IP6_NF_MATCH_RT=m
# CONFIG_IP6_NF_MATCH_SRH is not set
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_TARGET_SYNPROXY=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
CONFIG_IP6_NF_NAT=m
CONFIG_IP6_NF_TARGET_MASQUERADE=m
CONFIG_IP6_NF_TARGET_NPT=m

# end of IPv6: Netfilter Configuration

CONFIG_NF_DEFRAG_IPV6=m
# CONFIG_NF_TABLES_BRIDGE is not set
# CONFIG_NF_CONNTRACK_BRIDGE is not set
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_BPFILTER is not set
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m

#
# DCCP CCIDs Configuration
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_TFRC_LIB=y

# end of DCCP CCIDs Configuration

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set

# end of DCCP Kernel Hacking

CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=m
CONFIG_L2TP_DEBUGFS=m
CONFIG_L2TP_V3=y
CONFIG_L2TP_IP=m
CONFIG_L2TP_ETH=m
CONFIG_STP=y
CONFIG_GARP=y
CONFIG_MRP=y
CONFIG_BRIDGE=y CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y
# CONFIG_BRIDGE_MRP is not set CONFIG_HAVE_NET_DSA=y
# CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=y
CONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
CONFIG_6LOWPAN=m
# CONFIG_6LOWPAN_DEBUGFS is not set CONFIG_6LOWPAN_NHC=m CONFIG_6LOWPAN_NHC_DEST=m CONFIG_6LOWPAN_NHC_FRAGMENT=m CONFIG_6LOWPAN_NHC_HOP=m CONFIG_6LOWPAN_NHC_IPV6=m CONFIG_6LOWPAN_NHC_MOBILITY=m CONFIG_6LOWPAN_NHC_ROUTING=m CONFIG_6LOWPAN_NHC_UDP=m
# CONFIG_6LOWPAN_GHC_EXT_HDR_HOP is not set # CONFIG_6LOWPAN_GHC_UDP is not set
# CONFIG_6LOWPAN_GHC_ICMPV6 is not set
# CONFIG_6LOWPAN_GHC_EXT_HDR_DEST is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE is not set CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=m
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFB=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
# CONFIG_NET_SCH_CBS is not set
CONFIG_NET_SCH_ETF=m
# CONFIG_NET_SCH_TAPRIO is not set
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=y
CONFIG_NET_SCH_DRR=m
CONFIG_NET_SCH_MQPRIO=m
# CONFIG_NET_SCH_SKBPRIO is not set
CONFIG_NET_SCH_CHOKE=m
CONFIG_NET_SCH_QFQ=m
CONFIG_NET_SCH_CODEL=m
CONFIG_NET_SCH_FQ_CODEL=m
# CONFIG_NET_SCH_CAKE is not set
CONFIG_NET_SCH_FQ=m
# CONFIG_NET_SCH_HHF is not set
# CONFIG_NET_SCH_PIE is not set
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_SCH_PLUG=m
CONFIG_NET_SCH_ETS=m
# CONFIG_NET_SCH_DEFAULT is not set

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_CLS_CGROUP=y
CONFIG_NET_CLS_BPF=m
CONFIG_NET_CLS_FLOWER=m
CONFIG_NET_CLS_MATCHALL=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_EMATCH_CANID=m
CONFIG_NET_EMATCH_IPSET=m
CONFIG_NET_EMATCH_IPT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_SAMPLE=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_ACT_SKBEDIT=m
CONFIG_NET_ACT_CSUM=m
CONFIG_NET_ACT_MPLS=m
CONFIG_NET_ACT_VLAN=m
CONFIG_NET_ACT_BPF=m
CONFIG_NET_ACT_CONNMARK=m
CONFIG_NET_ACT_CTINFO=m
CONFIG_NET_ACT_SKBMOD=m
CONFIG_NET_ACT_IFE=m
CONFIG_NET_ACT_TUNNEL_KEY=m
CONFIG_NET_ACT_CT=m
# CONFIG_NET_ACT_GATE is not set
CONFIG_NET_IFE_SKBMARK=m
CONFIG_NET_IFE_SKBPRIO=m
CONFIG_NET_IFE_SKBTCINDEX=m
# CONFIG_NET_TC_SKB_EXT is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
CONFIG_DNS_RESOLVER=m
# CONFIG_BATMAN_ADV is not set
CONFIG_OPENVSWITCH=m
CONFIG_OPENVSWITCH_GRE=m
CONFIG_OPENVSWITCH_VXLAN=m
CONFIG_OPENVSWITCH_GENEVE=m
CONFIG_VSOCKETS=m
CONFIG_VSOCKETS_DIAG=m
CONFIG_VSOCKETS_LOOPBACK=m
CONFIG_VMWARE_VMCI_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
CONFIG_HYPERV_VSOCKETS=m
CONFIG_NETLINK_DIAG=m
CONFIG_MPLS=y
CONFIG_NET_MPLS_GSO=m
CONFIG_MPLS_ROUTING=m
CONFIG_MPLS_IPTUNNEL=m
CONFIG_NET_NSH=m
# CONFIG_HSR is not set
CONFIG_NET_SWITCHDEV=y
CONFIG_NET_L3_MASTER_DEV=y
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
CONFIG_CGROUP_NET_CLASSID=y
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
CONFIG_BPF_JIT=y
CONFIG_BPF_STREAM_PARSER=y
CONFIG_NET_FLOW_LIMIT=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_NET_DROP_MONITOR=y

# end of Network testing
# end of Networking options

# CONFIG_HAMRADIO is not set
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m
# CONFIG_CAN_J1939 is not set
# CONFIG_CAN_ISOTP is not set

#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
# CONFIG_CAN_VXCAN is not set
CONFIG_CAN_SLCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_KVASER_PCIEFD is not set
CONFIG_CAN_C_CAN=m
CONFIG_CAN_C_CAN_PLATFORM=m
CONFIG_CAN_C_CAN_PCI=m
CONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not set
CONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not set
CONFIG_CAN_SJA1000=m
CONFIG_CAN_EMS_PCI=m
# CONFIG_CAN_F81601 is not set
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=y
CONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_SJA1000_ISA is not set
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_SOFTING=m

#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# CONFIG_CAN_MCP251XFD is not set

# end of CAN SPI interfaces

#
# CAN USB interfaces
#
CONFIG_CAN_8DEV_USB=m
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
# CONFIG_CAN_GS_USB is not set
CONFIG_CAN_KVASER_USB=m
# CONFIG_CAN_MCBA_USB is not set
CONFIG_CAN_PEAK_USB=m
# CONFIG_CAN_UCAN is not set

# end of CAN USB interfaces

# CONFIG_CAN_DEBUG_DEVICES is not set

# end of CAN Device Drivers

CONFIG_BT=m
CONFIG_BT_BREDR=y
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m
CONFIG_BT_HS=y
CONFIG_BT_LE=y
# CONFIG_BT_6LOWPAN is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_MSFTEXT is not set
CONFIG_BT_DEBUGFS=y
# CONFIG_BT_SELFTEST is not set

#
# Bluetooth device drivers
#
CONFIG_BT_INTEL=m
CONFIG_BT_BCM=m
CONFIG_BT_RTL=m
CONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTUSB_AUTOSUSPEND is not set
CONFIG_BT_HCIBTUSB_BCM=y
# CONFIG_BT_HCIBTUSB_MTK is not set
CONFIG_BT_HCIBTUSB_RTL=y
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_ATH3K=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_AG6XX is not set
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
CONFIG_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
CONFIG_BT_ATH3K=m
# CONFIG_BT_MTKSDIO is not set

# end of Bluetooth device drivers

# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
CONFIG_STREAM_PARSER=y
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
CONFIG_CFG80211_WEXT=y
CONFIG_LIB80211=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set
CONFIG_NET_9P=y
CONFIG_NET_9P_VIRTIO=m
# CONFIG_NET_9P_XEN is not set
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not set
CONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set
CONFIG_CEPH_LIB_USE_DNS_RESOLVER=y
# CONFIG_NFC is not set
CONFIG_PSAMPLE=m
CONFIG_NET_IFE=m
CONFIG_LWTUNNEL=y
CONFIG_LWTUNNEL_BPF=y
CONFIG_DST_CACHE=y
CONFIG_GRO_CELLS=y
CONFIG_NET_SOCK_MSG=y
CONFIG_NET_DEVLINK=y
CONFIG_PAGE_POOL=y
CONFIG_FAILOVER=m
CONFIG_ETHTOOL_NETLINK=y
CONFIG_HAVE_EBPF_JIT=y

#
# Device Drivers
#
CONFIG_HAVE_EISA=y
# CONFIG_EISA is not set
CONFIG_HAVE_PCI=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
CONFIG_PCIEAER_INJECT=m
CONFIG_PCIE_ECRC=y
CONFIG_PCIEASPM=y
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_PCIE_PME=y
# CONFIG_PCIE_DPC is not set
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_BW is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_MSI_IRQ_DOMAIN=y
CONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
CONFIG_PCI_STUB=y
# CONFIG_PCI_PF_STUB is not set
# CONFIG_XEN_PCIDEV_FRONTEND is not set
CONFIG_PCI_ATS=y
CONFIG_PCI_LOCKLESS_CONFIG=y
CONFIG_PCI_IOV=y
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not set
CONFIG_PCI_LABEL=y
CONFIG_PCI_HYPERV=m
# CONFIG_PCIE_BUS_TUNE_OFF is not set
CONFIG_PCIE_BUS_DEFAULT=y
# CONFIG_PCIE_BUS_SAFE is not set
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not set
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=y

#
# PCI controller drivers
#
CONFIG_VMD=y
CONFIG_PCI_HYPERV_INTERFACE=m

#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set

# end of DesignWare PCI Core Support

#
# Mobiveil PCIe Core Support
#

# end of Mobiveil PCIe Core Support

#
# Cadence PCIe controllers support
#

# end of Cadence PCIe controllers support
# end of PCI controller drivers

#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set

# end of PCI Endpoint

#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set

# end of PCI switch controller drivers

CONFIG_PCCARD=y
# CONFIG_PCMCIA is not set
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_RAPIDIO is not set

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Firmware loader
#
CONFIG_FW_LOADER=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set # CONFIG_FW_LOADER_COMPRESS is not set CONFIG_FW_CACHE=y

# end of Firmware loader

CONFIG_WANT_DEV_COREDUMP=y
CONFIG_ALLOW_DEV_COREDUMP=y
CONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
CONFIG_SYS_HYPERVISOR=y
CONFIG_GENERIC_CPU_AUTOPROBE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=m
CONFIG_REGMAP_SPI=m
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set

# end of Generic Driver Options

#
# Bus devices
#
# CONFIG_MHI_BUS is not set

# end of Bus devices

CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_GNSS is not set
CONFIG_MTD=m
# CONFIG_MTD_TESTS is not set

#
# Partition parsers
#
# CONFIG_MTD_AR7_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set

# end of Partition parsers

#
# User Modules And Translation Layers
#
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set

# end of RAM/ROM/Flash chip drivers

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set

# end of Mapping drivers for chip access

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not set
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set

# end of Self-contained MTD device drivers

#
# NAND
#
# CONFIG_MTD_ONENAND is not set
# CONFIG_MTD_RAW_NAND is not set
# CONFIG_MTD_SPI_NAND is not set

#
# ECC engine support
#

# end of ECC engine support
# end of NAND

#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set

# end of LPDDR & LPDDR2 PCM memory drivers

# CONFIG_MTD_SPI_NOR is not set
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_HYPERBUS is not set
# CONFIG_OF is not set
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_NULL_BLK=m
CONFIG_BLK_DEV_FD=m
CONFIG_CDROM=m
# CONFIG_PARIDE is not set
CONFIG_BLK_DEV_PCIESSD_MTIP32XX=m
CONFIG_ZRAM=m
# CONFIG_ZRAM_WRITEBACK is not set
# CONFIG_ZRAM_MEMORY_TRACKING is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=0
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SKD is not set
CONFIG_BLK_DEV_SX8=m
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_VIRTIO_BLK=m
CONFIG_BLK_DEV_RBD=m
# CONFIG_BLK_DEV_RSXX is not set

#
# NVME Support
#
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
# CONFIG_NVME_MULTIPATH is not set
# CONFIG_NVME_HWMON is not set
CONFIG_NVME_FABRICS=m
CONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not set
CONFIG_NVME_TARGET=m
# CONFIG_NVME_TARGET_PASSTHRU is not set
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_FC=m
CONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set

# end of NVME Support

#
# Misc devices
#
CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not set
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_SGI_XP=m
CONFIG_HP_ILO=m
CONFIG_SGI_GRU=m
# CONFIG_SGI_GRU_DEBUG is not set
CONFIG_APDS9802ALS=m
CONFIG_ISL29003=m
CONFIG_ISL29020=m
CONFIG_SENSORS_TSL2550=m
CONFIG_SENSORS_BH1770=m
CONFIG_SENSORS_APDS990X=m
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
CONFIG_VMWARE_BALLOON=m
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not set
CONFIG_PVPANIC=y
# CONFIG_C2PORT is not set

#
# EEPROM support
#
CONFIG_EEPROM_AT24=m
# CONFIG_EEPROM_AT25 is not set
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
CONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set

# end of EEPROM support

CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not set
CONFIG_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=m
CONFIG_ALTERA_STAPL=m
CONFIG_INTEL_MEI=m
CONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_VIRTIO is not set
# CONFIG_INTEL_MEI_HDCP is not set
CONFIG_VMWARE_VMCI=m
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# CONFIG_UACCE is not set

# end of Misc devices

CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_BLK_DEV_SR=m
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
CONFIG_SCSI_SRP_ATTRS=m

# end of SCSI Transports

CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_ISCSI_BOOT_SYSFS=m
CONFIG_SCSI_CXGB3_ISCSI=m
CONFIG_SCSI_CXGB4_ISCSI=m
CONFIG_SCSI_BNX2_ISCSI=m
CONFIG_SCSI_BNX2X_FCOE=m
CONFIG_BE2ISCSI=m
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
CONFIG_SCSI_HPSA=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_3W_SAS=m
# CONFIG_SCSI_ACARD is not set
CONFIG_SCSI_AACRAID=m
# CONFIG_SCSI_AIC7XXX is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not set
CONFIG_SCSI_MVSAS=m
# CONFIG_SCSI_MVSAS_DEBUG is not set
CONFIG_SCSI_MVSAS_TASKLET=y
CONFIG_SCSI_MVUMI=m
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
CONFIG_SCSI_ARCMSR=m
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT3SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
CONFIG_SCSI_MPT3SAS_MAX_SGE=128
CONFIG_SCSI_MPT2SAS=m
# CONFIG_SCSI_SMARTPQI is not set
CONFIG_SCSI_UFSHCD=m
CONFIG_SCSI_UFSHCD_PCI=m
# CONFIG_SCSI_UFS_DWC_TC_PCI is not set
# CONFIG_SCSI_UFSHCD_PLATFORM is not set
# CONFIG_SCSI_UFS_BSG is not set
CONFIG_SCSI_HPTIOP=m
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
CONFIG_VMWARE_PVSCSI=m
# CONFIG_XEN_SCSI_FRONTEND is not set
CONFIG_HYPERV_STORAGE=m
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
CONFIG_FCOE_FNIC=m
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_GDTH is not set
CONFIG_SCSI_ISCI=m
# CONFIG_SCSI_IPS is not set
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
CONFIG_SCSI_STEX=m
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA_FC=m
CONFIG_TCM_QLA2XXX=m
# CONFIG_TCM_QLA2XXX_DEBUG is not set
CONFIG_SCSI_QLA_ISCSI=m
# CONFIG_QEDI is not set
# CONFIG_QEDF is not set
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not set
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_PMCRAID=m
CONFIG_SCSI_PM8001=m
# CONFIG_SCSI_BFA_FC is not set
CONFIG_SCSI_VIRTIO=m
# CONFIG_SCSI_CHELSIO_FCOE is not set
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=y
CONFIG_SCSI_DH_HP_SW=y
CONFIG_SCSI_DH_EMC=y
CONFIG_SCSI_DH_ALUA=y

# end of SCSI device support

CONFIG_ATA=m
CONFIG_SATA_HOST=y
CONFIG_PATA_TIMINGS=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_FORCE=y
CONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not set
CONFIG_SATA_PMP=y

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=m
CONFIG_SATA_MOBILE_LPM_POLICY=0
CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not set
CONFIG_SATA_ACARD_AHCI=m
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_SX4=m
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=m
# CONFIG_SATA_DWC is not set
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_SVW=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m

#
# PATA SFF controllers with BMDMA
#
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_ATP867X=m
CONFIG_PATA_CMD64X=m
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT8213=m
CONFIG_PATA_IT821X=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
# CONFIG_PATA_NS87415 is not set
CONFIG_PATA_OLDPIIX=m
# CONFIG_PATA_OPTIDMA is not set
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not set
CONFIG_PATA_RDC=m
CONFIG_PATA_SCH=m
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_TOSHIBA=m
# CONFIG_PATA_TRIFLEX is not set
CONFIG_PATA_VIA=m
# CONFIG_PATA_WINBOND is not set

#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set

#
# Generic fallback / legacy drivers
#
CONFIG_PATA_ACPI=m
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MD_MULTIPATH is not set CONFIG_MD_FAULTY=m
# CONFIG_MD_CLUSTER is not set
# CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=m
CONFIG_DM_DEBUG=y
CONFIG_DM_BUFIO=m
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m
# CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=m
CONFIG_DM_CACHE_SMQ=m
# CONFIG_DM_WRITECACHE is not set
# CONFIG_DM_EBS is not set
CONFIG_DM_ERA=m
# CONFIG_DM_CLONE is not set CONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=m
CONFIG_DM_RAID=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m
# CONFIG_DM_MULTIPATH_HST is not set CONFIG_DM_DELAY=m
# CONFIG_DM_DUST is not set CONFIG_DM_UEVENT=y
CONFIG_DM_FLAKEY=m
CONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set # CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=m
CONFIG_DM_LOG_WRITES=m
# CONFIG_DM_INTEGRITY is not set CONFIG_TARGET_CORE=m
CONFIG_TCM_IBLOCK=m
CONFIG_TCM_FILEIO=m
CONFIG_TCM_PSCSI=m
CONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=m
CONFIG_TCM_FC=m
CONFIG_ISCSI_TARGET=m CONFIG_ISCSI_TARGET_CXGB4=m
# CONFIG_SBP_TARGET is not set CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
# CONFIG_FUSION_FC is not set CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=m CONFIG_FUSION_LOGGING=y

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
# CONFIG_FIREWIRE_NOSY is not set

# end of IEEE 1394 (FireWire) support

CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
CONFIG_MII=m
CONFIG_NET_CORE=y
CONFIG_BONDING=m
CONFIG_DUMMY=y
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
CONFIG_NET_FC=y
CONFIG_IFB=y
CONFIG_NET_TEAM=m
CONFIG_NET_TEAM_MODE_BROADCAST=m
CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
CONFIG_NET_TEAM_MODE_RANDOM=m
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
CONFIG_NET_TEAM_MODE_LOADBALANCE=m
CONFIG_MACVLAN=m
CONFIG_MACVTAP=m
# CONFIG_IPVLAN is not set
CONFIG_VXLAN=y
CONFIG_GENEVE=y
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
CONFIG_MACSEC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_NTB_NETDEV=m
CONFIG_TUN=m
CONFIG_TAP=m
# CONFIG_TUN_VNET_CROSS_LE is not set
CONFIG_VETH=y
CONFIG_VIRTIO_NET=m
CONFIG_NLMON=m
CONFIG_NET_VRF=y
CONFIG_VSOCKMON=m
# CONFIG_ARCNET is not set
# CONFIG_ATM_DRIVERS is not set

#
# Distributed Switch Architecture drivers
#

# end of Distributed Switch Architecture drivers

CONFIG_ETHERNET=y
CONFIG_MDIO=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
CONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not set
CONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_ALTERA_TSE is not set
CONFIG_NET_VENDOR_AMAZON=y
CONFIG_ENA_ETHERNET=m
CONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not set
CONFIG_AMD_XGBE=m
# CONFIG_AMD_XGBE_DCB is not set
CONFIG_AMD_XGBE_HAVE_ECC=y
CONFIG_NET_VENDOR_AQUANTIA=y
CONFIG_AQTION=m
CONFIG_NET_VENDOR_ARC=y
CONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
CONFIG_ALX=m
CONFIG_NET_VENDOR_AURORA=y
# CONFIG_AURORA_NB8800 is not set
CONFIG_NET_VENDOR_BROADCOM=y
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
# CONFIG_BCMGENET is not set
CONFIG_BNX2=m
CONFIG_CNIC=m
# CONFIG_TIGON3 is not set
CONFIG_BNX2X=m
CONFIG_BNX2X_SRIOV=y
# CONFIG_SYSTEMPORT is not set
CONFIG_BNXT=m
CONFIG_BNXT_SRIOV=y
CONFIG_BNXT_FLOWER_OFFLOAD=y
CONFIG_BNXT_DCB=y
CONFIG_BNXT_HWMON=y
CONFIG_NET_VENDOR_BROCADE=y
CONFIG_BNA=m
CONFIG_NET_VENDOR_CADENCE=y
CONFIG_MACB=m
CONFIG_MACB_USE_HWSTAMP=y
# CONFIG_MACB_PCI is not set
CONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not set
CONFIG_CAVIUM_PTP=y
CONFIG_LIQUIDIO=m
CONFIG_LIQUIDIO_VF=m
CONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
CONFIG_CHELSIO_T3=m
CONFIG_CHELSIO_T4=m
# CONFIG_CHELSIO_T4_DCB is not set
CONFIG_CHELSIO_T4VF=m
CONFIG_CHELSIO_LIB=m
CONFIG_CHELSIO_INLINE_CRYPTO=y
CONFIG_NET_VENDOR_CISCO=y
CONFIG_ENIC=m
CONFIG_NET_VENDOR_CORTINA=y
# CONFIG_CX_ECAT is not set
CONFIG_DNET=m
CONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not set
# CONFIG_NET_VENDOR_DLINK is not set
CONFIG_NET_VENDOR_EMULEX=y
CONFIG_BE2NET=m
CONFIG_BE2NET_HWMON=y
CONFIG_BE2NET_BE2=y
CONFIG_BE2NET_BE3=y
CONFIG_BE2NET_LANCER=y
CONFIG_BE2NET_SKYHAWK=y
CONFIG_NET_VENDOR_EZCHIP=y
CONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not set
CONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not set
# CONFIG_NET_VENDOR_I825XX is not set
CONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not set
CONFIG_E1000=y
CONFIG_E1000E=y
CONFIG_E1000E_HWTS=y
CONFIG_IGB=y
CONFIG_IGB_HWMON=y
CONFIG_IGBVF=m
# CONFIG_IXGB is not set
CONFIG_IXGBE=y
CONFIG_IXGBE_HWMON=y
CONFIG_IXGBE_DCB=y
CONFIG_IXGBEVF=m
CONFIG_I40E=y
CONFIG_I40E_DCB=y
CONFIG_IAVF=m
CONFIG_I40EVF=m
# CONFIG_ICE is not set
CONFIG_FM10K=m
# CONFIG_IGC is not set
CONFIG_JME=m
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_MVMDIO=m
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_PRESTERA is not set
CONFIG_NET_VENDOR_MELLANOX=y
CONFIG_MLX4_EN=m
CONFIG_MLX4_EN_DCB=y
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_MLX4_CORE_GEN2=y
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
CONFIG_NET_VENDOR_MICROSEMI=y
CONFIG_NET_VENDOR_MYRI=y
CONFIG_MYRI10GE=m
CONFIG_MYRI10GE_DCA=y
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
CONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
CONFIG_NET_VENDOR_NETRONOME=y
CONFIG_NFP=m
CONFIG_NFP_APP_FLOWER=y
CONFIG_NFP_APP_ABM_NIC=y
# CONFIG_NFP_DEBUG is not set
CONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not set
# CONFIG_NET_VENDOR_NVIDIA is not set
CONFIG_NET_VENDOR_OKI=y
CONFIG_ETHOC=m
CONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_IONIC is not set
CONFIG_NET_VENDOR_QLOGIC=y
CONFIG_QLA3XXX=m
CONFIG_QLCNIC=m
CONFIG_QLCNIC_SRIOV=y
CONFIG_QLCNIC_DCB=y
CONFIG_QLCNIC_HWMON=y
CONFIG_NETXEN_NIC=m
CONFIG_QED=m
CONFIG_QED_SRIOV=y
CONFIG_QEDE=m
CONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not set
# CONFIG_NET_VENDOR_RDC is not set
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_R8169=y
CONFIG_NET_VENDOR_RENESAS=y
CONFIG_NET_VENDOR_ROCKER=y
CONFIG_ROCKER=m
CONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
# CONFIG_NET_VENDOR_SEEQ is not set
CONFIG_NET_VENDOR_SOLARFLARE=y
CONFIG_SFC=m
CONFIG_SFC_MTD=y
CONFIG_SFC_MCDI_MON=y
CONFIG_SFC_SRIOV=y
CONFIG_SFC_MCDI_LOGGING=y
CONFIG_SFC_FALCON=m
CONFIG_SFC_FALCON_MTD=y
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
CONFIG_NET_VENDOR_SMSC=y
CONFIG_EPIC100=m
# CONFIG_SMSC911X is not set
CONFIG_SMSC9420=m
CONFIG_NET_VENDOR_SOCIONEXT=y
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
CONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
CONFIG_NET_VENDOR_TI=y
# CONFIG_TI_CPSW_PHY_SEL is not set
CONFIG_TLAN=m
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not set
CONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_AXI_EMAC is not set
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not set
CONFIG_PHYLINK=m
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not set
CONFIG_FIXED_PHY=y
# CONFIG_SFP is not set

#
# MII PHY device drivers
#
CONFIG_AMD_PHY=m
# CONFIG_ADIN_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not set
CONFIG_BROADCOM_PHY=m
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
CONFIG_BCM87XX_PHY=m
CONFIG_BCM_NET_PHYLIB=m
CONFIG_CICADA_PHY=m
# CONFIG_CORTINA_PHY is not set
CONFIG_DAVICOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_LXT_PHY=m
# CONFIG_INTEL_XWAY_PHY is not set
CONFIG_LSI_ET1011C_PHY=m
CONFIG_MARVELL_PHY=m
# CONFIG_MARVELL_10G_PHY is not set
CONFIG_MICREL_PHY=m
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
CONFIG_NATIONAL_PHY=m
# CONFIG_NXP_TJA11XX_PHY is not set
CONFIG_QSEMI_PHY=m
CONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
CONFIG_SMSC_PHY=m
CONFIG_STE10XP=m
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
CONFIG_VITESSE_PHY=m
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not set
CONFIG_MDIO_DEVICE=y
CONFIG_MDIO_BUS=y
CONFIG_MDIO_DEVRES=y
CONFIG_MDIO_BITBANG=m
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_GPIO is not set
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_THUNDER is not set

#
# MDIO Multiplexers
#

#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set

# end of PCS device drivers

# CONFIG_PLIP is not set
CONFIG_PPP=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOATM=m
CONFIG_PPPOE=m
CONFIG_PPTP=m
CONFIG_PPPOL2TP=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_SLIP=m
CONFIG_SLHC=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
CONFIG_USB_RTL8152=m
# CONFIG_USB_LAN78XX is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_HSO=m
# CONFIG_USB_IPHETH is not set
CONFIG_WLAN=y
# CONFIG_WIRELESS_WDS is not set
CONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not set
CONFIG_ATH_COMMON=m
CONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
CONFIG_ATH9K_HW=m
CONFIG_ATH9K_COMMON=m
CONFIG_ATH9K_BTCOEX_SUPPORT=y
# CONFIG_ATH9K is not set
CONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not set
# CONFIG_ATH11K is not set
CONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not set
CONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not set
CONFIG_WLAN_VENDOR_CISCO=y
# CONFIG_AIRO is not set
CONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
CONFIG_IWLEGACY=m
CONFIG_IWL4965=m
CONFIG_IWL3945=m

#

# iwl3945 / iwl4965 Debugging Options
#
CONFIG_IWLEGACY_DEBUG=y
CONFIG_IWLEGACY_DEBUGFS=y
# end of iwl3945 / iwl4965 Debugging Options

CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLDVM=m
CONFIG_IWLMVM=m
CONFIG_IWLWIFI_OPMODE_MODULAR=y
# CONFIG_IWLWIFI_BCAST_FILTERING is not set

#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLWIFI_DEBUGFS=y
# CONFIG_IWLWIFI_DEVICE_TRACING is not set

# end of Debugging Options

CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not set
CONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
# CONFIG_MWL8K is not set
CONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x0E is not set
# CONFIG_MT76x2E is not set
# CONFIG_MT76x2U is not set
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not set
# CONFIG_MT7663U is not set
# CONFIG_MT7663S is not set
# CONFIG_MT7915E is not set
CONFIG_WLAN_VENDOR_MICROCHIP=y
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not set
CONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not set
CONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_RTL_CARDS is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not set
CONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not set
CONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not set
CONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
CONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not set
CONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not set
CONFIG_MAC80211_HWSIM=m
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers #
CONFIG_WAN=y
# CONFIG_LANMEDIA is not set
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
# CONFIG_HDLC_RAW_ETH is not set CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m

#
# X.25/LAPB support is disabled
#
# CONFIG_PCI200SYN is not set
# CONFIG_WANXL is not set
# CONFIG_PC300TOO is not set
# CONFIG_FARSYNC is not set
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
# CONFIG_SBNI is not set
CONFIG_IEEE802154_DRIVERS=m
CONFIG_IEEE802154_FAKELB=m
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
# CONFIG_IEEE802154_ATUSB is not set
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
# CONFIG_IEEE802154_HWSIM is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_VMXNET3=m
CONFIG_FUJITSU_ES=m
CONFIG_HYPERV_NET=m
CONFIG_NETDEVSIM=m
CONFIG_NET_FAILOVER=m
CONFIG_ISDN=y
CONFIG_ISDN_CAPI=y
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_MISDN=m
CONFIG_MISDN_DSP=m
CONFIG_MISDN_L1OIP=m

#
# mISDN hardware drivers
#
CONFIG_MISDN_HFCPCI=m
CONFIG_MISDN_HFCMULTI=m
CONFIG_MISDN_HFCUSB=m
CONFIG_MISDN_AVMFRITZ=m
CONFIG_MISDN_SPEEDFAX=m
CONFIG_MISDN_INFINEON=m
CONFIG_MISDN_W6692=m
CONFIG_MISDN_NETJET=m
CONFIG_MISDN_HDLC=m
CONFIG_MISDN_IPAC=m
CONFIG_MISDN_ISAR=m
# CONFIG_NVM is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_LEDS=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=m
CONFIG_INPUT_SPARSEKMAP=m
# CONFIG_INPUT_MATRIXKMAP is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
# CONFIG_KEYBOARD_APPLESPI is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_BYD=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_ELANTECH_SMBUS=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_PS2_FOCALTECH=y
CONFIG_MOUSE_PS2_VMMOUSE=y
CONFIG_MOUSE_PS2_SMBUS=y
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
CONFIG_MOUSE_BCM5974=m
CONFIG_MOUSE_CYAPA=m
# CONFIG_MOUSE_ELAN_I2C is not set
CONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_GPIO is not set
CONFIG_MOUSE_SYNAPTICS_I2C=m
CONFIG_MOUSE_SYNAPTICS_USB=m
# CONFIG_INPUT_JOYSTICK is not set
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
# CONFIG_TABLET_USB_HANWANG is not set
CONFIG_TABLET_USB_KBTAB=m
# CONFIG_TABLET_USB_PEGASUS is not set
# CONFIG_TABLET_SERIAL_WACOM4 is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ADC is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8505 is not set
# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not set
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_WACOM_W8001=m
CONFIG_TOUCHSCREEN_WACOM_I2C=m
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_WM97XX is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not set
# CONFIG_TOUCHSCREEN_ZINITIX is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_MMA8450 is not set
CONFIG_INPUT_APANEL=m
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not set
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
# CONFIG_INPUT_KXTJ9 is not set
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_CM109=m
CONFIG_INPUT_UINPUT=m
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not set
CONFIG_INPUT_GPIO_ROTARY_ENCODER=m
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_IQS269A is not set
# CONFIG_INPUT_CMA3000 is not set
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
CONFIG_RMI4_CORE=m
# CONFIG_RMI4_I2C is not set
# CONFIG_RMI4_SPI is not set
CONFIG_RMI4_SMB=m
CONFIG_RMI4_F03=y
CONFIG_RMI4_F03_SERIO=m
CONFIG_RMI4_2D_SENSOR=y
CONFIG_RMI4_F11=y
CONFIG_RMI4_F12=y
CONFIG_RMI4_F30=y
# CONFIG_RMI4_F34 is not set
# CONFIG_RMI4_F3A is not set
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_SERIO_ALTERA_PS2=m
# CONFIG_SERIO_PS2MULT is not set
CONFIG_SERIO_ARC_PS2=m
CONFIG_HYPERV_KEYBOARD=m
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set

# end of Hardware I/O ports
# end of Input device support

#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_LDISC_AUTOLOAD=y

#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_16550A_VARIANTS is not set # CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DWLIB=y CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
# CONFIG_SERIAL_LANTIQ is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
CONFIG_SERIAL_ARC=m
CONFIG_SERIAL_ARC_NR_PORTS=1
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_SPRD is not set

# end of Serial drivers

CONFIG_SERIAL_MCTRL_GPIO=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not set
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
# CONFIG_ISI is not set
CONFIG_N_HDLC=m
CONFIG_N_GSM=m
CONFIG_NOZOMI=m
# CONFIG_NULL_TTY is not set
# CONFIG_TRACE_SINK is not set
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
CONFIG_HVC_XEN_FRONTEND=y
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_TTY_PRINTK is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_VIRTIO_CONSOLE=m
CONFIG_IPMI_HANDLER=m
CONFIG_IPMI_DMI_DECODE=y
CONFIG_IPMI_PLAT_DATA=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_SSIF=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
# CONFIG_HW_RANDOM_BA431 is not set
CONFIG_HW_RANDOM_VIA=m
CONFIG_HW_RANDOM_VIRTIO=m
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
CONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not set
CONFIG_NVRAM=y
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=8192
CONFIG_DEVPORT=y
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
# CONFIG_HPET_MMAP_DEFAULT is not set
CONFIG_HANGCHECK_TIMER=m
CONFIG_UV_MMTIMER=m
CONFIG_TCG_TPM=y
CONFIG_HW_RANDOM_TPM=y
CONFIG_TCG_TIS_CORE=y
CONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not set
CONFIG_TCG_TIS_I2C_ATMEL=m
CONFIG_TCG_TIS_I2C_INFINEON=m
CONFIG_TCG_TIS_I2C_NUVOTON=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
# CONFIG_TCG_XEN is not set
CONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not set
CONFIG_TCG_TIS_ST33ZP24=m
CONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not set
CONFIG_TELCLOCK=m
# CONFIG_XILLYBUS is not set

# end of Character devices

# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_ACPI_I2C_OPREGION=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_MUX=m

#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_REG is not set
# CONFIG_I2C_MUX_MLXCPLD is not set

# end of Multiplexer I2C Chip support

CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=m
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
# CONFIG_I2C_AMD_MP2 is not set
CONFIG_I2C_I801=m
CONFIG_I2C_ISCH=m
CONFIG_I2C_ISMT=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m

#
# ACPI drivers
#
CONFIG_I2C_SCMI=m

#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_SIMTEC=m
# CONFIG_I2C_XILINX is not set

#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_DIOLAN_U2C=m
CONFIG_I2C_PARPORT=m
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
CONFIG_I2C_TINY_USB=m
CONFIG_I2C_VIPERBOARD=m

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_MLXCPLD is not set

# end of I2C Hardware Bus support

CONFIG_I2C_STUB=m
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set

# end of I2C support

# CONFIG_I3C is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_LANTIQ_SSC is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set

#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
CONFIG_SPI_DYNAMIC=y
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set

#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
CONFIG_PPS_CLIENT_LDISC=m
CONFIG_PPS_CLIENT_PARPORT=m
CONFIG_PPS_CLIENT_GPIO=m

#
# PPS generators support
#

#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=y
CONFIG_DP83640_PHY=m
# CONFIG_PTP_1588_CLOCK_INES is not set
CONFIG_PTP_1588_CLOCK_KVM=m
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# CONFIG_PTP_1588_CLOCK_VMW is not set

# end of PTP clock support

CONFIG_PINCTRL=y
CONFIG_PINMUX=y
CONFIG_PINCONF=y
CONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
CONFIG_PINCTRL_AMD=m
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SX150X is not set
CONFIG_PINCTRL_BAYTRAIL=y
# CONFIG_PINCTRL_CHERRYVIEW is not set
# CONFIG_PINCTRL_LYNXPOINT is not set
CONFIG_PINCTRL_INTEL=y
# CONFIG_PINCTRL_BROXTON is not set
CONFIG_PINCTRL_CANNONLAKE=m
# CONFIG_PINCTRL_CEDARFORK is not set
CONFIG_PINCTRL_DENVERTON=m
# CONFIG_PINCTRL_EMMITSBURG is not set
CONFIG_PINCTRL_GEMINILAKE=m
# CONFIG_PINCTRL_ICELAKE is not set
# CONFIG_PINCTRL_JASPERLAKE is not set
CONFIG_PINCTRL_LEWISBURG=m
CONFIG_PINCTRL_SUNRISEPOINT=m
# CONFIG_PINCTRL_TIGERLAKE is not set

#
# Renesas pinctrl drivers
#

# end of Renesas pinctrl drivers

CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
CONFIG_GPIO_ACPI=y
CONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
CONFIG_GPIO_SYSFS=y
CONFIG_GPIO_CDEV=y
CONFIG_GPIO_CDEV_V1=y
CONFIG_GPIO_GENERIC=m

#
# Memory mapped GPIO drivers
#
CONFIG_GPIO_AMDPT=m
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
CONFIG_GPIO_ICH=m
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_VX855 is not set
# 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_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set

# end of Port-mapped I/O GPIO drivers

#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set

# end of I2C GPIO expanders

#
# MFD GPIO expanders
#

# end of MFD GPIO expanders

#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set

# end of PCI GPIO expanders

#
# SPI GPIO expanders
#
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set

# end of SPI GPIO expanders

#
# USB GPIO expanders
#
CONFIG_GPIO_VIPERBOARD=m

# end of USB GPIO expanders

# CONFIG_GPIO_AGGREGATOR is not set
CONFIG_GPIO_MOCKUP=m
# CONFIG_W1 is not set
CONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_RESTART is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
CONFIG_CHARGER_SMB347=m
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_BD99954 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not set
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM1177 is not set
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7X10=m
# CONFIG_SENSORS_ADT7310 is not set
CONFIG_SENSORS_ADT7410=m
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
# CONFIG_SENSORS_AS370 is not set
CONFIG_SENSORS_ASC7621=m
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
# CONFIG_SENSORS_AMD_ENERGY is not set
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ASPEED is not set
CONFIG_SENSORS_ATXP1=m
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_DRIVETEMP is not set
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DELL_SMM=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_FTSTEUTATES is not set
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
# CONFIG_SENSORS_I5500 is not set
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set
CONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not set
CONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not set
CONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not set
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
CONFIG_SENSORS_MAX197=m
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX6621 is not set
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_MAX6697=m
# CONFIG_SENSORS_MAX31790 is not set
CONFIG_SENSORS_MCP3021=m
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_ADCXX is not set
CONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not set
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LM95234=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not set
CONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
CONFIG_SENSORS_PCF8591=m
CONFIG_PMBUS=m
CONFIG_SENSORS_PMBUS=m
# CONFIG_SENSORS_ADM1266 is not set
CONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_BEL_PFE is not set
# CONFIG_SENSORS_IBM_CFFPS is not set
# CONFIG_SENSORS_INSPUR_IPSPS is not set
# CONFIG_SENSORS_IR35221 is not set
# CONFIG_SENSORS_IR38064 is not set
# CONFIG_SENSORS_IRPS5401 is not set
# CONFIG_SENSORS_ISL68137 is not set
CONFIG_SENSORS_LM25066=m
CONFIG_SENSORS_LTC2978=m
# CONFIG_SENSORS_LTC3815 is not set
CONFIG_SENSORS_MAX16064=m
# CONFIG_SENSORS_MAX16601 is not set
# CONFIG_SENSORS_MAX20730 is not set
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not set
CONFIG_SENSORS_MAX34440=m
CONFIG_SENSORS_MAX8688=m
# CONFIG_SENSORS_MP2975 is not set
# CONFIG_SENSORS_PXE1610 is not set
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not set
CONFIG_SENSORS_UCD9000=m
CONFIG_SENSORS_UCD9200=m
# CONFIG_SENSORS_XDPE122 is not set
CONFIG_SENSORS_ZL6100=m
CONFIG_SENSORS_SHT15=m
CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
# CONFIG_SENSORS_EMC2103 is not set
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not set
CONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_ADS7871 is not set
CONFIG_SENSORS_AMC6821=m
CONFIG_SENSORS_INA209=m
CONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not set
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
# CONFIG_SENSORS_TMP513 is not set
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
# CONFIG_SENSORS_W83773G is not set
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_XGENE is not set

#
# ACPI drivers
#
CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=m
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=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=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_DEVFREQ_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set

#
# Intel thermal drivers
#
CONFIG_INTEL_POWERCLAMP=m
CONFIG_X86_PKG_TEMP_THERMAL=m
CONFIG_INTEL_SOC_DTS_IOSF_CORE=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set

#
# ACPI INT340X thermal drivers
#
CONFIG_INT340X_THERMAL=m
CONFIG_ACPI_THERMAL_REL=m
# CONFIG_INT3406_THERMAL is not set
CONFIG_PROC_THERMAL_MMIO_RAPL=y

# end of ACPI INT340X thermal drivers

# CONFIG_INTEL_PCH_THERMAL is not set

# end of Intel thermal drivers

# CONFIG_GENERIC_ADC_THERMAL is not set
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
CONFIG_WATCHDOG_SYSFS=y

#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_WDAT_WDT=m
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
# CONFIG_EBC_C384_WDT is not set
CONFIG_F71808E_WDT=m
CONFIG_SP5100_TCO=m
CONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not set
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not set
CONFIG_I6300ESB_WDT=y
CONFIG_IE6XX_WDT=m
CONFIG_ITCO_WDT=y
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
CONFIG_IT87_WDT=m
CONFIG_HP_WATCHDOG=m
CONFIG_HPWDT_NMI_DECODING=y
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
CONFIG_NV_TCO=m
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not set
CONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not set
CONFIG_VIA_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
CONFIG_INTEL_MEI_WDT=m
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not set
CONFIG_XEN_WDT=m

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_SDIOHOST_POSSIBLE=y
CONFIG_SSB_SDIOHOST=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
CONFIG_SSB_DRIVER_GPIO=y
CONFIG_BCMA_POSSIBLE=y
CONFIG_BCMA=m
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
CONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not set
CONFIG_BCMA_DRIVER_PCI=y
CONFIG_BCMA_DRIVER_GMAC_CMN=y
CONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not set
CONFIG_LPC_ICH=m
CONFIG_LPC_SCH=m
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not set
CONFIG_MFD_INTEL_LPSS=y
CONFIG_MFD_INTEL_LPSS_ACPI=y
CONFIG_MFD_INTEL_LPSS_PCI=y
# CONFIG_MFD_INTEL_PMC_BXT is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
CONFIG_MFD_VIPERBOARD=m
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_UCB1400_CORE is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SL28CPLD is not set
CONFIG_MFD_SM501=m
CONFIG_MFD_SM501_GPIO=y
# CONFIG_MFD_SKY81452 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TQMX86 is not set
CONFIG_MFD_VX855=m
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_INTEL_M10_BMC is not set

# end of Multifunction device drivers

# CONFIG_REGULATOR is not set
CONFIG_RC_CORE=m
CONFIG_RC_MAP=m
CONFIG_LIRC=y
CONFIG_RC_DECODERS=y
CONFIG_IR_NEC_DECODER=m
CONFIG_IR_RC5_DECODER=m
CONFIG_IR_RC6_DECODER=m
CONFIG_IR_JVC_DECODER=m
CONFIG_IR_SONY_DECODER=m
CONFIG_IR_SANYO_DECODER=m
CONFIG_IR_SHARP_DECODER=m
CONFIG_IR_MCE_KBD_DECODER=m
# CONFIG_IR_XMP_DECODER is not set
CONFIG_IR_IMON_DECODER=m
# CONFIG_IR_RCMM_DECODER is not set
CONFIG_RC_DEVICES=y
CONFIG_RC_ATI_REMOTE=m
CONFIG_IR_ENE=m
CONFIG_IR_IMON=m
# CONFIG_IR_IMON_RAW is not set
CONFIG_IR_MCEUSB=m
CONFIG_IR_ITE_CIR=m
CONFIG_IR_FINTEK=m
CONFIG_IR_NUVOTON=m
CONFIG_IR_REDRAT3=m
CONFIG_IR_STREAMZAP=m
CONFIG_IR_WINBOND_CIR=m
# CONFIG_IR_IGORPLUGUSB is not set
CONFIG_IR_IGUANA=m
CONFIG_IR_TTUSBIR=m
CONFIG_RC_LOOPBACK=m
# CONFIG_IR_SERIAL is not set
# CONFIG_IR_SIR is not set
# CONFIG_RC_XBOX_DVD is not set
# CONFIG_IR_TOY is not set
# CONFIG_MEDIA_CEC_SUPPORT is not set
CONFIG_MEDIA_SUPPORT=m
# CONFIG_MEDIA_SUPPORT_FILTER is not set
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y

#
# Media device types
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_MEDIA_SDR_SUPPORT=y
CONFIG_MEDIA_PLATFORM_SUPPORT=y
CONFIG_MEDIA_TEST_SUPPORT=y

# end of Media device types

#
# Media core support
#
CONFIG_VIDEO_DEV=m
CONFIG_MEDIA_CONTROLLER=y
CONFIG_DVB_CORE=m

# end of Media core support

#
# Video4Linux options
#
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L2_I2C=y
# CONFIG_VIDEO_V4L2_SUBDEV_API is not set
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m

# end of Video4Linux options

#
# Media controller options
#
CONFIG_MEDIA_CONTROLLER_DVB=y

# end of Media controller options

#
# Digital TV options
#
# CONFIG_DVB_MMAP is not set
CONFIG_DVB_NET=y
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set

# end of Digital TV options

#
# Media drivers
#
CONFIG_TTPCI_EEPROM=m
CONFIG_MEDIA_USB_SUPPORT=y

#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_BENQ=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_CPIA1=m
# CONFIG_USB_GSPCA_DTCS033 is not set
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_JL2005BCD=m
# CONFIG_USB_GSPCA_KINECT is not set
CONFIG_USB_GSPCA_KONICA=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_NW80X=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_OV534_9=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7302=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SE401=m
CONFIG_USB_GSPCA_SN9C2028=m
CONFIG_USB_GSPCA_SN9C20X=m
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SPCA1528=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_SQ930X=m
CONFIG_USB_GSPCA_STK014=m
# CONFIG_USB_GSPCA_STK1135 is not set
CONFIG_USB_GSPCA_STV0680=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TOPRO=m
# CONFIG_USB_GSPCA_TOUPTEK is not set
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_VICAM=m
CONFIG_USB_GSPCA_XIRLINK_CIT=m
CONFIG_USB_GSPCA_ZC3XX=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_VIDEO_CPIA2 is not set
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
# CONFIG_VIDEO_USBTV is not set

#
# Analog TV USB devices
#
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
# CONFIG_VIDEO_STK1160_COMMON is not set
# CONFIG_VIDEO_GO7007 is not set

#
# Analog/digital TV USB devices
#
CONFIG_VIDEO_AU0828=m
CONFIG_VIDEO_AU0828_V4L2=y
# CONFIG_VIDEO_AU0828_RC is not set
CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_RC=y
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
CONFIG_VIDEO_TM6000=m
CONFIG_VIDEO_TM6000_ALSA=m
CONFIG_VIDEO_TM6000_DVB=m

#
# Digital TV USB devices
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_DIB3000MC=m
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
# CONFIG_DVB_USB_CXUSB_ANALOG is not set
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_USB_PCTV452E=m
CONFIG_DVB_USB_DW2102=m
CONFIG_DVB_USB_CINERGY_T2=m
CONFIG_DVB_USB_DTV5100=m
CONFIG_DVB_USB_AZ6027=m
CONFIG_DVB_USB_TECHNISAT_USB2=m
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_AF9015=m
CONFIG_DVB_USB_AF9035=m
CONFIG_DVB_USB_ANYSEE=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_AZ6007=m
CONFIG_DVB_USB_CE6230=m
CONFIG_DVB_USB_EC168=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_LME2510=m
CONFIG_DVB_USB_MXL111SF=m
CONFIG_DVB_USB_RTL28XXU=m
# CONFIG_DVB_USB_DVBSKY is not set
# CONFIG_DVB_USB_ZD1301 is not set
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_SMS_USB_DRV=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set
# CONFIG_DVB_AS102 is not set

#
# Webcam, TV (analog/digital) USB devices
#
CONFIG_VIDEO_EM28XX=m
# CONFIG_VIDEO_EM28XX_V4L2 is not set
CONFIG_VIDEO_EM28XX_ALSA=m
CONFIG_VIDEO_EM28XX_DVB=m
CONFIG_VIDEO_EM28XX_RC=m

#
# Software defined radio USB devices
#
# CONFIG_USB_AIRSPY is not set
# CONFIG_USB_HACKRF is not set
# CONFIG_USB_MSI2500 is not set
CONFIG_MEDIA_PCI_SUPPORT=y

#
# Media capture support
#
# CONFIG_VIDEO_MEYE is not set
# CONFIG_VIDEO_SOLO6X10 is not set
# CONFIG_VIDEO_TW5864 is not set
# CONFIG_VIDEO_TW68 is not set
# CONFIG_VIDEO_TW686X is not set

#
# Media capture/analog TV support
#
CONFIG_VIDEO_IVTV=m
# CONFIG_VIDEO_IVTV_DEPRECATED_IOCTLS is not set
# CONFIG_VIDEO_IVTV_ALSA is not set
CONFIG_VIDEO_FB_IVTV=m
# CONFIG_VIDEO_FB_IVTV_FORCE_PAT is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DT3155 is not set

#
# Media capture/analog/hybrid TV support
#
CONFIG_VIDEO_CX18=m
CONFIG_VIDEO_CX18_ALSA=m
CONFIG_VIDEO_CX23885=m
CONFIG_MEDIA_ALTERA_CI=m
# CONFIG_VIDEO_CX25821 is not set
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_ENABLE_VP3054=y
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX88_MPEG=m
CONFIG_VIDEO_BT848=m
CONFIG_DVB_BT8XX=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_RC=y
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_SAA7164=m

#
# Media digital TV PCI Adapters
#
CONFIG_DVB_AV7110_IR=y
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=m
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set
CONFIG_DVB_PLUTO2=m
CONFIG_DVB_DM1105=m
CONFIG_DVB_PT1=m
# CONFIG_DVB_PT3 is not set
CONFIG_MANTIS_CORE=m
CONFIG_DVB_MANTIS=m
CONFIG_DVB_HOPPER=m
CONFIG_DVB_NGENE=m
CONFIG_DVB_DDBRIDGE=m
# CONFIG_DVB_DDBRIDGE_MSIENABLE is not set
# CONFIG_DVB_SMIPCIE is not set
# CONFIG_DVB_NETUP_UNIDVB is not set
# CONFIG_VIDEO_IPU3_CIO2 is not set
# CONFIG_VIDEO_PCI_SKELETON is not set
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_TEA575X=m
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
CONFIG_MEDIA_COMMON_OPTIONS=y

#

# common driver options
#
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_CYPRESS_FIRMWARE=m
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_V4L2=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_VIDEOBUF2_DMA_SG=m
CONFIG_VIDEOBUF2_DVB=m
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_SMS_SIANO_MDTV=m
CONFIG_SMS_SIANO_RC=y
# CONFIG_SMS_SIANO_DEBUGFS is not set
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
# CONFIG_SDR_PLATFORM_DRIVERS is not set

#
# MMC/SDIO DVB adapters
#
CONFIG_SMS_SDIO_DRV=m
# CONFIG_V4L_TEST_DRIVERS is not set
# CONFIG_DVB_TEST_DRIVERS is not set

#
# FireWire (IEEE 1394) Adapters
#
CONFIG_DVB_FIREDTV=m
CONFIG_DVB_FIREDTV_INPUT=y

# end of Media drivers

#
# Media ancillary drivers
#
CONFIG_MEDIA_ATTACH=y

#
# IR I2C driver auto-selected by 'Autoselect ancillary drivers' #
CONFIG_VIDEO_IR_I2C=m

#
# Audio decoders, processors and mixers
#
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TDA1997X is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS3308=m
CONFIG_VIDEO_CS5345=m
CONFIG_VIDEO_CS53L32A=m
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not set
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
# CONFIG_VIDEO_SONY_BTF_MPX is not set

# end of Audio decoders, processors and mixers

#
# RDS decoders
#
CONFIG_VIDEO_SAA6588=m

# end of RDS decoders

#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not set
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV7604 is not set
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not set
# CONFIG_VIDEO_ML86V7667 is not set
# CONFIG_VIDEO_SAA7110 is not set
CONFIG_VIDEO_SAA711X=m
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set

#
# Video and audio decoders
#
CONFIG_VIDEO_SAA717X=m
CONFIG_VIDEO_CX25840=m

# end of Video decoders

#
# Video encoders
#
CONFIG_VIDEO_SAA7127=m
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_ADV7511 is not set
# CONFIG_VIDEO_AD9389B is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set

# end of Video encoders

#
# Video improvement chips
#
CONFIG_VIDEO_UPD64031A=m
CONFIG_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
#
# CONFIG_SDR_MAX2175 is not set

# end of SDR tuner chips

#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not set
CONFIG_VIDEO_M52790=m
# CONFIG_VIDEO_I2C is not set
# CONFIG_VIDEO_ST_MIPID02 is not set

# end of Miscellaneous helper chips

#
# Camera sensor devices
#
# CONFIG_VIDEO_HI556 is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV2740 is not set
# CONFIG_VIDEO_OV5647 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5670 is not set
# CONFIG_VIDEO_OV5675 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV7251 is not set
# CONFIG_VIDEO_OV772X is not set
# CONFIG_VIDEO_OV7640 is not set
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV8856 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV13858 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M001 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9T112 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_RDACM20 is not set
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_SMIAPP is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_S5C73M3 is not set

# end of Camera sensor devices

#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not set
# CONFIG_VIDEO_AK7375 is not set
# CONFIG_VIDEO_DW9714 is not set
# CONFIG_VIDEO_DW9768 is not set
# CONFIG_VIDEO_DW9807_VCM is not set

# end of Lens drivers

#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set

# end of Flash devices

#
# SPI helper chips
#
# CONFIG_VIDEO_GS1662 is not set

# end of SPI helper chips

#
# Media SPI Adapters
#
# CONFIG_CXD2880_SPI_DRV is not set

# end of Media SPI Adapters

CONFIG_MEDIA_TUNER=m

#
# Customize TV tuners
#
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA18250=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
# CONFIG_MEDIA_TUNER_MSI001 is not set
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_MT2060=m
CONFIG_MEDIA_TUNER_MT2063=m
CONFIG_MEDIA_TUNER_MT2266=m
CONFIG_MEDIA_TUNER_MT2131=m
CONFIG_MEDIA_TUNER_QT1010=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_XC4000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MXL5007T=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_MEDIA_TUNER_MAX2165=m
CONFIG_MEDIA_TUNER_TDA18218=m
CONFIG_MEDIA_TUNER_FC0011=m
CONFIG_MEDIA_TUNER_FC0012=m
CONFIG_MEDIA_TUNER_FC0013=m
CONFIG_MEDIA_TUNER_TDA18212=m
CONFIG_MEDIA_TUNER_E4000=m
CONFIG_MEDIA_TUNER_FC2580=m
CONFIG_MEDIA_TUNER_M88RS6000T=m
CONFIG_MEDIA_TUNER_TUA9001=m
CONFIG_MEDIA_TUNER_SI2157=m
CONFIG_MEDIA_TUNER_IT913X=m
CONFIG_MEDIA_TUNER_R820T=m
# CONFIG_MEDIA_TUNER_MXL301RF is not set
CONFIG_MEDIA_TUNER_QM1D1C0042=m
CONFIG_MEDIA_TUNER_QM1D1B0004=m

# end of Customize TV tuners

#
# Customise DVB Frontends
#

#
# Multistandard (satellite) frontends
#
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=m
CONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=m
CONFIG_DVB_STV6111=m
CONFIG_DVB_MXL5XX=m
CONFIG_DVB_M88DS3103=m

#
# Multistandard (cable + terrestrial) frontends
#
CONFIG_DVB_DRXK=m
CONFIG_DVB_TDA18271C2DD=m
CONFIG_DVB_SI2165=m
CONFIG_DVB_MN88472=m
CONFIG_DVB_MN88473=m

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_MT312=m
CONFIG_DVB_ZL10036=m
CONFIG_DVB_ZL10039=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TUNER_ITD1000=m
CONFIG_DVB_TUNER_CX24113=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_CX24117=m
CONFIG_DVB_CX24120=m
CONFIG_DVB_SI21XX=m
CONFIG_DVB_TS2020=m
CONFIG_DVB_DS3000=m
CONFIG_DVB_MB86A16=m
CONFIG_DVB_TDA10071=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
# CONFIG_DVB_S5H1432 is not set
CONFIG_DVB_DRXD=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m
# CONFIG_DVB_DIB9000 is not set
CONFIG_DVB_TDA10048=m
CONFIG_DVB_AF9013=m
CONFIG_DVB_EC100=m
CONFIG_DVB_STV0367=m
CONFIG_DVB_CXD2820R=m
CONFIG_DVB_CXD2841ER=m
CONFIG_DVB_RTL2830=m
CONFIG_DVB_RTL2832=m
CONFIG_DVB_RTL2832_SDR=m
CONFIG_DVB_SI2168=m
# CONFIG_DVB_ZD1301_DEMOD is not set
CONFIG_DVB_GP8PSK_FE=m
# CONFIG_DVB_CXD2880 is not set

#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_LGDT3305=m
CONFIG_DVB_LGDT3306A=m
CONFIG_DVB_LG2160=m
CONFIG_DVB_S5H1409=m
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m
CONFIG_DVB_S5H1411=m

#
# ISDB-T (terrestrial) frontends
#
CONFIG_DVB_S921=m
CONFIG_DVB_DIB8000=m
CONFIG_DVB_MB86A20S=m

#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #
CONFIG_DVB_TC90522=m
# CONFIG_DVB_MN88443X is not set

#
# Digital terrestrial only tuners/PLL
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TUNER_DIB0070=m
CONFIG_DVB_TUNER_DIB0090=m

#
# SEC control devices for DVB-S
#
CONFIG_DVB_DRX39XYJ=m
CONFIG_DVB_LNBH25=m
# CONFIG_DVB_LNBH29 is not set
CONFIG_DVB_LNBP21=m
CONFIG_DVB_LNBP22=m
CONFIG_DVB_ISL6405=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_ISL6423=m
CONFIG_DVB_A8293=m
# CONFIG_DVB_LGS8GL5 is not set
CONFIG_DVB_LGS8GXX=m
CONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=m
CONFIG_DVB_IX2505V=m
CONFIG_DVB_M88RS2000=m
CONFIG_DVB_AF9033=m
# CONFIG_DVB_HORUS3A is not set
# CONFIG_DVB_ASCOT2E is not set
# CONFIG_DVB_HELENE is not set

#
# Common Interface (EN50221) controller drivers
#
CONFIG_DVB_CXD2099=m
# CONFIG_DVB_SP2 is not set

# end of Customise DVB Frontends

#
# Tools to develop new frontends
#
CONFIG_DVB_DUMMY_FE=m

# end of Media ancillary drivers

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_SIS=y
CONFIG_AGP_VIA=y
CONFIG_INTEL_GTT=y
CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=64 CONFIG_VGA_SWITCHEROO=y
CONFIG_DRM=y
CONFIG_DRM_MIPI_DSI=y CONFIG_DRM_DP_AUX_CHARDEV=y
# CONFIG_DRM_DEBUG_MM is not set CONFIG_DRM_DEBUG_SELFTEST=m CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set CONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not set CONFIG_DRM_TTM=m CONFIG_DRM_TTM_DMA_PAGE_POOL=y CONFIG_DRM_VRAM_HELPER=m CONFIG_DRM_TTM_HELPER=m CONFIG_DRM_GEM_SHMEM_HELPER=y

#
# I2C encoder or helper chips
#
CONFIG_DRM_I2C_CH7006=m
CONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set

# end of I2C encoder or helper chips

#
# ARM devices
#

# end of ARM devices

# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
# CONFIG_DRM_NOUVEAU is not set
CONFIG_DRM_I915=m
CONFIG_DRM_I915_FORCE_PROBE=""
CONFIG_DRM_I915_CAPTURE_ERROR=y
CONFIG_DRM_I915_COMPRESS_ERROR=y
CONFIG_DRM_I915_USERPTR=y
CONFIG_DRM_I915_GVT=y
CONFIG_DRM_I915_GVT_KVMGT=m

#

# drm/i915 Debugging
#
# CONFIG_DRM_I915_WERROR is not set
# CONFIG_DRM_I915_DEBUG is not set
# CONFIG_DRM_I915_DEBUG_MMIO is not set
# CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set
# CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set
# CONFIG_DRM_I915_DEBUG_GUC is not set
# CONFIG_DRM_I915_SELFTEST is not set
# CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set
# CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set
# CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set
# end of drm/i915 Debugging

#

# drm/i915 Profile Guided Optimisation
#
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=y
# CONFIG_DRM_VKMS is not set
CONFIG_DRM_VMWGFX=m
CONFIG_DRM_VMWGFX_FBCON=y
CONFIG_DRM_GMA500=m
CONFIG_DRM_GMA600=y
CONFIG_DRM_GMA3600=y
CONFIG_DRM_UDL=m
CONFIG_DRM_AST=m
CONFIG_DRM_MGAG200=m
CONFIG_DRM_QXL=m
CONFIG_DRM_BOCHS=m
CONFIG_DRM_VIRTIO_GPU=m
CONFIG_DRM_PANEL=y

#
# Display Panels
#
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set

# end of Display Panels

CONFIG_DRM_BRIDGE=y
CONFIG_DRM_PANEL_BRIDGE=y

#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set

# end of Display Interface Bridges

# CONFIG_DRM_ETNAVIV is not set
CONFIG_DRM_CIRRUS_QEMU=m
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_XEN is not set
# CONFIG_DRM_VBOXVIDEO is not set
# CONFIG_DRM_LEGACY is not set
CONFIG_DRM_EXPORT_FOR_TESTS=y
CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
CONFIG_DRM_LIB_RANDOM=y

#
# Frame buffer Devices
#
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_MODE_HELPERS is not set
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SM501 is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
CONFIG_FB_HYPERV=m
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SM712 is not set

# end of Frame buffer Devices

#
# Backlight & LCD device support
#
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not set
CONFIG_LCD_PLATFORM=m
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_PWM is not set
CONFIG_BACKLIGHT_APPLE=m
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
CONFIG_BACKLIGHT_LP855X=m
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set

# end of Backlight & LCD device support

CONFIG_HDMI=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set

# end of Console display driver support

CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

# end of Graphics support

CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_PCM_ELD=y
CONFIG_SND_HWDEP=m
CONFIG_SND_SEQ_DEVICE=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_COMPRESS_OFFLOAD=m
CONFIG_SND_JACK=y
CONFIG_SND_JACK_INPUT_DEV=y
CONFIG_SND_OSSEMUL=y
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
CONFIG_SND_PCM_TIMER=y
CONFIG_SND_HRTIMER=m
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_MAX_CARDS=32
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_PROC_FS=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_SEQUENCER_OSS=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_SEQ_MIDI_EVENT=m
CONFIG_SND_SEQ_MIDI=m
CONFIG_SND_SEQ_MIDI_EMUL=m
CONFIG_SND_SEQ_VIRMIDI=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_OPL3_LIB_SEQ=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
CONFIG_SND_PCSP=m
CONFIG_SND_DUMMY=m
CONFIG_SND_ALOOP=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m
# CONFIG_SND_PORTMAN2X4 is not set
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=5
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
CONFIG_SND_ALI5451=m
CONFIG_SND_ASIHPI=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
# CONFIG_SND_CS4281 is not set
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CTXFI=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_INDIGOIOX=m
CONFIG_SND_INDIGODJX=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1_SEQ=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not set
CONFIG_SND_ES1968=m
CONFIG_SND_ES1968_INPUT=y
CONFIG_SND_ES1968_RADIO=y
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_LOLA=m
CONFIG_SND_LX6464ES=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MAESTRO3_INPUT=y
CONFIG_SND_MIXART=m
# CONFIG_SND_NM256 is not set
CONFIG_SND_PCXHR=m
# CONFIG_SND_RIPTIDE is not set
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
# CONFIG_SND_SONICVIBES is not set
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
# CONFIG_SND_YMFPCI is not set

#
# HD-Audio
#
CONFIG_SND_HDA=m CONFIG_SND_HDA_GENERIC_LEDS=y CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_BEEP_MODE=0 CONFIG_SND_HDA_PATCH_LOADER=y CONFIG_SND_HDA_CODEC_REALTEK=m CONFIG_SND_HDA_CODEC_ANALOG=m CONFIG_SND_HDA_CODEC_SIGMATEL=m CONFIG_SND_HDA_CODEC_VIA=m CONFIG_SND_HDA_CODEC_HDMI=m CONFIG_SND_HDA_CODEC_CIRRUS=m CONFIG_SND_HDA_CODEC_CONEXANT=m CONFIG_SND_HDA_CODEC_CA0110=m CONFIG_SND_HDA_CODEC_CA0132=m CONFIG_SND_HDA_CODEC_CA0132_DSP=y CONFIG_SND_HDA_CODEC_CMEDIA=m CONFIG_SND_HDA_CODEC_SI3054=m CONFIG_SND_HDA_GENERIC=m CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM is not set

# end of HD-Audio

CONFIG_SND_HDA_CORE=m
CONFIG_SND_HDA_DSP_LOADER=y
CONFIG_SND_HDA_COMPONENT=y
CONFIG_SND_HDA_I915=y
CONFIG_SND_HDA_EXT_CORE=m
CONFIG_SND_HDA_PREALLOC_SIZE=512
CONFIG_SND_INTEL_NHLT=y
CONFIG_SND_INTEL_DSP_CONFIG=m
# CONFIG_SND_SPI is not set
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=y
CONFIG_SND_USB_UA101=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=m
CONFIG_SND_USB_6FIRE=m
CONFIG_SND_USB_HIFACE=m
CONFIG_SND_BCD2000=m
CONFIG_SND_USB_LINE6=m
CONFIG_SND_USB_POD=m
CONFIG_SND_USB_PODHD=m
CONFIG_SND_USB_TONEPORT=m
CONFIG_SND_USB_VARIAX=m
CONFIG_SND_FIREWIRE=y
CONFIG_SND_FIREWIRE_LIB=m
# CONFIG_SND_DICE is not set
# CONFIG_SND_OXFW is not set
CONFIG_SND_ISIGHT=m
# CONFIG_SND_FIREWORKS is not set
# CONFIG_SND_BEBOB is not set
# CONFIG_SND_FIREWIRE_DIGI00X is not set
# CONFIG_SND_FIREWIRE_TASCAM is not set
# CONFIG_SND_FIREWIRE_MOTU is not set
# CONFIG_SND_FIREFACE is not set
CONFIG_SND_SOC=m
CONFIG_SND_SOC_COMPRESS=y
CONFIG_SND_SOC_TOPOLOGY=y
CONFIG_SND_SOC_ACPI=m
# CONFIG_SND_SOC_AMD_ACP is not set
# CONFIG_SND_SOC_AMD_ACP3x is not set
# CONFIG_SND_SOC_AMD_RENOIR is not set
# CONFIG_SND_ATMEL_SOC is not set
# CONFIG_SND_BCM63XX_I2S_WHISTLER is not set
# CONFIG_SND_DESIGNWARE_I2S is not set

#
# SoC Audio for Freescale CPUs
#

#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set

# end of SoC Audio for Freescale CPUs

# CONFIG_SND_I2S_HI6210_I2S is not set
# CONFIG_SND_SOC_IMG is not set CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SOC_INTEL_SST=m
# CONFIG_SND_SOC_INTEL_CATPT is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m
# CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m CONFIG_SND_SOC_INTEL_SKYLAKE=m CONFIG_SND_SOC_INTEL_SKL=m CONFIG_SND_SOC_INTEL_APL=m CONFIG_SND_SOC_INTEL_KBL=m CONFIG_SND_SOC_INTEL_GLK=m CONFIG_SND_SOC_INTEL_CNL=m CONFIG_SND_SOC_INTEL_CFL=m
# CONFIG_SND_SOC_INTEL_CML_H is not set
# CONFIG_SND_SOC_INTEL_CML_LP is not set CONFIG_SND_SOC_INTEL_SKYLAKE_FAMILY=m CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m
# CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC is not set CONFIG_SND_SOC_INTEL_SKYLAKE_COMMON=m CONFIG_SND_SOC_ACPI_INTEL_MATCH=m CONFIG_SND_SOC_INTEL_MACH=y
# CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES is not set CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m
# CONFIG_SND_SOC_INTEL_CHT_BSW_NAU8824_MACH is not set # CONFIG_SND_SOC_INTEL_BYT_CHT_CX2072X_MACH is not set CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=m CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_DA7219_MAX98357A_GENERIC=m CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_COMMON=m CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set # CONFIG_SND_SOC_MTK_BTCVSD is not set
# CONFIG_SND_SOC_SOF_TOPLEVEL is not set

#
# STMicroelectronics STM32 SOC audio support
#

# end of STMicroelectronics STM32 SOC audio support

# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set # CONFIG_SND_SOC_XILINX_SPDIF is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# CONFIG_ZX_TDM is not set CONFIG_SND_SOC_I2C_AND_SPI=m

#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_ADAU7118_HW is not set
# CONFIG_SND_SOC_ADAU7118_I2C is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS42L42 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4234 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS53L30 is not set
# CONFIG_SND_SOC_CX2072X is not set
CONFIG_SND_SOC_DA7213=m
CONFIG_SND_SOC_DA7219=m
CONFIG_SND_SOC_DMIC=m
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not set
CONFIG_SND_SOC_ES8316=m
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_GTM601 is not set
CONFIG_SND_SOC_HDAC_HDMI=m
# CONFIG_SND_SOC_INNO_RK3036 is not set
# CONFIG_SND_SOC_MAX98088 is not set
CONFIG_SND_SOC_MAX98090=m
CONFIG_SND_SOC_MAX98357A=m
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not set
CONFIG_SND_SOC_MAX98927=m
# CONFIG_SND_SOC_MAX98373_I2C is not set
CONFIG_SND_SOC_MAX98390=m
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RK3328 is not set
CONFIG_SND_SOC_RL6231=m
CONFIG_SND_SOC_RL6347A=m
CONFIG_SND_SOC_RT286=m
CONFIG_SND_SOC_RT298=m
CONFIG_SND_SOC_RT5514=m
CONFIG_SND_SOC_RT5514_SPI=m
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not set
CONFIG_SND_SOC_RT5640=m
CONFIG_SND_SOC_RT5645=m
CONFIG_SND_SOC_RT5651=m
CONFIG_SND_SOC_RT5663=m
CONFIG_SND_SOC_RT5670=m
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
CONFIG_SND_SOC_SSM4567=m
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS2562 is not set
# CONFIG_SND_SOC_TAS2764 is not set
# CONFIG_SND_SOC_TAS2770 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X is not set
# CONFIG_SND_SOC_TLV320ADCX140 is not set
CONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_UDA1334 is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8904 is not set
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_WM8985 is not set
# CONFIG_SND_SOC_ZL38060 is not set
# CONFIG_SND_SOC_ZX_AUD96P22 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6358 is not set
# CONFIG_SND_SOC_MT6660 is not set
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8822 is not set
CONFIG_SND_SOC_NAU8824=m
CONFIG_SND_SOC_NAU8825=m
# CONFIG_SND_SOC_TPA6130A2 is not set

# end of CODEC drivers

# CONFIG_SND_SIMPLE_CARD is not set
CONFIG_SND_X86=y
CONFIG_HDMI_LPE_AUDIO=m
CONFIG_SND_SYNTH_EMUX=m
# CONFIG_SND_XEN_FRONTEND is not set
CONFIG_AC97_BUS=m

#
# HID support
#
CONFIG_HID=y
CONFIG_HID_BATTERY_STRENGTH=y
CONFIG_HIDRAW=y
CONFIG_UHID=m
CONFIG_HID_GENERIC=y

#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
# CONFIG_HID_ACCUTOUCH is not set
CONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not set
CONFIG_HID_APPLE=y
CONFIG_HID_APPLEIR=m
# CONFIG_HID_ASUS is not set
CONFIG_HID_AUREAL=m
CONFIG_HID_BELKIN=y
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not set
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
CONFIG_HID_PRODIKEYS=m
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CREATIVE_SB0540 is not set
CONFIG_HID_CYPRESS=y
CONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not set
CONFIG_HID_ELECOM=m
# CONFIG_HID_ELO is not set
CONFIG_HID_EZKEY=y
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_GLORIOUS is not set
CONFIG_HID_HOLTEK=m
# CONFIG_HOLTEK_FF is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_GT683R is not set
CONFIG_HID_KEYTOUCH=m
CONFIG_HID_KYE=m
CONFIG_HID_UCLOGIC=m
CONFIG_HID_WALTOP=m
# CONFIG_HID_VIEWSONIC is not set
CONFIG_HID_GYRATION=m
CONFIG_HID_ICADE=m
CONFIG_HID_ITE=y
# CONFIG_HID_JABRA is not set
CONFIG_HID_TWINHAN=m
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LCPOWER=m
CONFIG_HID_LED=m
# CONFIG_HID_LENOVO is not set
CONFIG_HID_LOGITECH=y
CONFIG_HID_LOGITECH_DJ=m
CONFIG_HID_LOGITECH_HIDPP=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not set
CONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
CONFIG_HID_REDRAGON=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_MULTITOUCH=m
# CONFIG_HID_NTI is not set
CONFIG_HID_NTRIG=y
CONFIG_HID_ORTEK=m
CONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PENMOUNT is not set
CONFIG_HID_PETALYNX=m
CONFIG_HID_PICOLCD=m
CONFIG_HID_PICOLCD_FB=y
CONFIG_HID_PICOLCD_BACKLIGHT=y
CONFIG_HID_PICOLCD_LCD=y
CONFIG_HID_PICOLCD_LEDS=y
CONFIG_HID_PICOLCD_CIR=y
CONFIG_HID_PLANTRONICS=y
CONFIG_HID_PRIMAX=m
# CONFIG_HID_RETRODE is not set
CONFIG_HID_ROCCAT=m
CONFIG_HID_SAITEK=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
# CONFIG_SONY_FF is not set
CONFIG_HID_SPEEDLINK=m
# CONFIG_HID_STEAM is not set
CONFIG_HID_STEELSERIES=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_RMI=m
CONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_HYPERV_MOUSE=m
CONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not set
CONFIG_HID_TIVO=m
CONFIG_HID_TOPSEED=m
CONFIG_HID_THINGM=m
CONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
CONFIG_HID_WACOM=m
CONFIG_HID_WIIMOTE=m
# CONFIG_HID_XINMO is not set
CONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not set
CONFIG_HID_ZYDACRON=m
CONFIG_HID_SENSOR_HUB=m
CONFIG_HID_SENSOR_CUSTOM_SENSOR=m
CONFIG_HID_ALPS=m
# CONFIG_HID_MCP2221 is not set

# end of Special HID drivers

#
# USB HID support
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y

# end of USB HID support

#
# I2C HID support
#
CONFIG_I2C_HID=m

# end of I2C HID support

#
# Intel ISH HID support
#
CONFIG_INTEL_ISH_HID=y
# CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER is not set

# end of Intel ISH HID support
# end of HID support

CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
CONFIG_USB_PCI=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_FEW_INIT_RETRIES is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_OTG_DISABLE_EXTERNAL_HUB is not set
CONFIG_USB_LEDS_TRIGGER_USBPORT=m
CONFIG_USB_AUTOSUSPEND_DELAY=2
CONFIG_USB_MON=y

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not set
CONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PCI_RENESAS is not set
# CONFIG_USB_XHCI_PLATFORM is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_U132_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_SSB is not set
# CONFIG_USB_HCD_TEST_MODE is not set

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
CONFIG_USB_TMC=m

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #

#

# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
CONFIG_USB_UAS=m

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USBIP_CORE=m
# CONFIG_USBIP_VHCI_HCD is not set
# CONFIG_USBIP_HOST is not set
# CONFIG_USBIP_DEBUG is not set
# CONFIG_USB_CDNS3 is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set

#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not set
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP210X=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not set
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_METRO is not set
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7715_PARPORT=y
CONFIG_USB_SERIAL_MOS7840=m
# CONFIG_USB_SERIAL_MXUPORT is not set
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
CONFIG_USB_SERIAL_QCAUX=m
CONFIG_USB_SERIAL_QUALCOMM=m
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_SYMBOL=m
# CONFIG_USB_SERIAL_TI is not set
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_XSENS_MT=m
# CONFIG_USB_SERIAL_WISHBONE is not set
CONFIG_USB_SERIAL_SSU100=m
CONFIG_USB_SERIAL_QT2=m
# CONFIG_USB_SERIAL_UPD78F0730 is not set
CONFIG_USB_SERIAL_DEBUG=m

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_SEVSEG=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
# CONFIG_APPLE_MFI_FASTCHARGE is not set
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not set
CONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
CONFIG_USB_ISIGHTFW=m
# CONFIG_USB_YUREX is not set
CONFIG_USB_EZUSB_FX2=m
# CONFIG_USB_HUB_USB251XB is not set
CONFIG_USB_HSIC_USB3503=m
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m

#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set

# end of USB Physical Layer drivers

# CONFIG_USB_GADGET is not set
CONFIG_TYPEC=y
# CONFIG_TYPEC_TCPM is not set
CONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not set
CONFIG_UCSI_ACPI=y
# CONFIG_TYPEC_TPS6598X is not set
# CONFIG_TYPEC_STUSB160X is not set

#
# USB Type-C Multiplexer/DeMultiplexer Switch support #
# CONFIG_TYPEC_MUX_PI3USB30532 is not set

# end of USB Type-C Multiplexer/DeMultiplexer Switch support

#
# USB Type-C Alternate Mode drivers
#
# CONFIG_TYPEC_DP_ALTMODE is not set

# end of USB Type-C Alternate Mode drivers

# CONFIG_USB_ROLE_SWITCH is not set
CONFIG_MMC=m
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_IO_ACCESSORS=y
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=y
CONFIG_MMC_SDHCI_ACPI=m
CONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_WBSD is not set
CONFIG_MMC_TIFM_SD=m
# CONFIG_MMC_SPI is not set
CONFIG_MMC_CB710=m
CONFIG_MMC_VIA_SDMMC=m
CONFIG_MMC_VUB300=m
CONFIG_MMC_USHC=m
# CONFIG_MMC_USDHI6ROL0 is not set
CONFIG_MMC_CQHCI=m
# CONFIG_MMC_HSQ is not set
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not set
CONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set

#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
CONFIG_MSPRO_BLOCK=m
# CONFIG_MS_BLOCK is not set

#
# MemoryStick Host Controller Drivers
#
CONFIG_MEMSTICK_TIFM_MS=m
CONFIG_MEMSTICK_JMICRON_38X=m
CONFIG_MEMSTICK_R592=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set

#
# LED drivers
#
# CONFIG_LEDS_APU is not set
CONFIG_LEDS_LM3530=m
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
CONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP50XX is not set
CONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not set
CONFIG_LEDS_INTEL_SS4200=m
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set

#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #
CONFIG_LEDS_BLINKM=m
# CONFIG_LEDS_MLXCPLD is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set

7,115 lines not shown · raw message

Part of this message is not shown here. View the raw message.