Re: [RFC] kernel random segmentation fault?
On Wednesday 2015-05-06 05:46, long.wanglong wrote:
>
>int main(int argc, char** argv)
>{
>rlim.rlim_cur=20 MB;
>rlim.rlim_max=20 MB;
>ret = setrlimit(RLIMIT_AS, );
>[...]
>char tmp[20 MB];
>for (i = 0; i < 20 MB; i++)
>tmp[i]=1;
if tmp already takes 20 MB, where will the remainder of the program find
space if you only allow for 20 MB? This is bound to fail under normal
considerations.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC] kernel random segmentation fault?
On 2015/5/6 16:20, Hillf Danton wrote:
>>
>> Hi all:
>>
>> I meet a kernel problem about the random segmentation fault(x86_64). In my
>> testcase, the size of local variables exceeds 20MB.
>> when run the testcase, it will cause segmentation fault(because the default
>> stack size limit is 8192KB).
>> when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
>> testcase will pass.
>>
>> But when I run the testcase 100 times, it will cause random segmentation
>> fault.
>>
>> Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 "mm: propagate
>> error from stack expansion even for guard page"
>> cause this problems, when I revert it, the testcase will not cause random
>> segmentation fault problem.
>>
>> Can anyone give some ideas about this problem?
>>
>> Best Regards
>> Wang Long
>>
>> Test Environment #
>>
>> # uname -a
>> Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
>> x86_64 x86_64 GNU/Linux
>>
>>
>> The Testcase
>>
>> #include
>> #include
>> #include
>>
>> #define KB *1024
>> #define MB *(1024*1024)
>> #define GB *(1024*1024*1024)
>>
>> int main(int argc, char** argv)
>> {
>> int ret;
>> struct rlimit rlim;
>>
>> rlim.rlim_cur=20 MB;
>> rlim.rlim_max=20 MB;
>
> Can you please get rlimit before setting it?
> And try again without reverting fee7e49d45?
>
Hi,Hillf Danton
After add getrlimit function before setting it. the testcase will not cause
random segmentation fault problem.
Could you please explain why? Are there any special considerations when we
use setrlimit and getrlimit functions?
Best Regards
Wang Long
>> ret = setrlimit(RLIMIT_AS, );
>> if ( 0 > ret)
>> {
>> perror("setrlimit failed");
>> exit(1);
>> }
>>
>> printf("setrlimit success\n");
>>
>> char tmp[20 MB];
>> int i = 0;
>>
>> for (i = 0; i < 20 MB; i++)
>> {
>> tmp[i]=1;
>> }
>>
>> printf("test success\n");
>> exit(1);
>> }
>>
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC] kernel random segmentation fault?
>
> Hi all:
>
> I meet a kernel problem about the random segmentation fault(x86_64). In my
> testcase, the size of local variables exceeds 20MB.
> when run the testcase, it will cause segmentation fault(because the default
> stack size limit is 8192KB).
> when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
> testcase will pass.
>
> But when I run the testcase 100 times, it will cause random segmentation
> fault.
>
> Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 "mm: propagate
> error from stack expansion even for guard page"
> cause this problems, when I revert it, the testcase will not cause random
> segmentation fault problem.
>
> Can anyone give some ideas about this problem?
>
> Best Regards
> Wang Long
>
> Test Environment #
>
> # uname -a
> Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
> x86_64 x86_64 GNU/Linux
>
>
> The Testcase
>
> #include
> #include
> #include
>
> #define KB *1024
> #define MB *(1024*1024)
> #define GB *(1024*1024*1024)
>
> int main(int argc, char** argv)
> {
> int ret;
> struct rlimit rlim;
>
> rlim.rlim_cur=20 MB;
> rlim.rlim_max=20 MB;
Can you please get rlimit before setting it?
And try again without reverting fee7e49d45?
> ret = setrlimit(RLIMIT_AS, );
> if ( 0 > ret)
> {
> perror("setrlimit failed");
> exit(1);
> }
>
> printf("setrlimit success\n");
>
> char tmp[20 MB];
> int i = 0;
>
> for (i = 0; i < 20 MB; i++)
> {
> tmp[i]=1;
> }
>
> printf("test success\n");
> exit(1);
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC] kernel random segmentation fault?
On 2015/5/6 16:20, Hillf Danton wrote:
Hi all:
I meet a kernel problem about the random segmentation fault(x86_64). In my
testcase, the size of local variables exceeds 20MB.
when run the testcase, it will cause segmentation fault(because the default
stack size limit is 8192KB).
when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
testcase will pass.
But when I run the testcase 100 times, it will cause random segmentation
fault.
Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 mm: propagate
error from stack expansion even for guard page
cause this problems, when I revert it, the testcase will not cause random
segmentation fault problem.
Can anyone give some ideas about this problem?
Best Regards
Wang Long
Test Environment #
# uname -a
Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
x86_64 x86_64 GNU/Linux
The Testcase
#include stdio.h
#include stdlib.h
#include sys/resource.h
#define KB *1024
#define MB *(1024*1024)
#define GB *(1024*1024*1024)
int main(int argc, char** argv)
{
int ret;
struct rlimit rlim;
rlim.rlim_cur=20 MB;
rlim.rlim_max=20 MB;
Can you please get rlimit before setting it?
And try again without reverting fee7e49d45?
Hi,Hillf Danton
After add getrlimit function before setting it. the testcase will not cause
random segmentation fault problem.
Could you please explain why? Are there any special considerations when we
use setrlimit and getrlimit functions?
Best Regards
Wang Long
ret = setrlimit(RLIMIT_AS, rlim);
if ( 0 ret)
{
perror(setrlimit failed);
exit(1);
}
printf(setrlimit success\n);
char tmp[20 MB];
int i = 0;
for (i = 0; i 20 MB; i++)
{
tmp[i]=1;
}
printf(test success\n);
exit(1);
}
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC] kernel random segmentation fault?
Hi all:
I meet a kernel problem about the random segmentation fault(x86_64). In my
testcase, the size of local variables exceeds 20MB.
when run the testcase, it will cause segmentation fault(because the default
stack size limit is 8192KB).
when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
testcase will pass.
But when I run the testcase 100 times, it will cause random segmentation
fault.
Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 mm: propagate
error from stack expansion even for guard page
cause this problems, when I revert it, the testcase will not cause random
segmentation fault problem.
Can anyone give some ideas about this problem?
Best Regards
Wang Long
Test Environment #
# uname -a
Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
x86_64 x86_64 GNU/Linux
The Testcase
#include stdio.h
#include stdlib.h
#include sys/resource.h
#define KB *1024
#define MB *(1024*1024)
#define GB *(1024*1024*1024)
int main(int argc, char** argv)
{
int ret;
struct rlimit rlim;
rlim.rlim_cur=20 MB;
rlim.rlim_max=20 MB;
Can you please get rlimit before setting it?
And try again without reverting fee7e49d45?
ret = setrlimit(RLIMIT_AS, rlim);
if ( 0 ret)
{
perror(setrlimit failed);
exit(1);
}
printf(setrlimit success\n);
char tmp[20 MB];
int i = 0;
for (i = 0; i 20 MB; i++)
{
tmp[i]=1;
}
printf(test success\n);
exit(1);
}
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC] kernel random segmentation fault?
On Wednesday 2015-05-06 05:46, long.wanglong wrote:
int main(int argc, char** argv)
{
rlim.rlim_cur=20 MB;
rlim.rlim_max=20 MB;
ret = setrlimit(RLIMIT_AS, rlim);
[...]
char tmp[20 MB];
for (i = 0; i 20 MB; i++)
tmp[i]=1;
if tmp already takes 20 MB, where will the remainder of the program find
space if you only allow for 20 MB? This is bound to fail under normal
considerations.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[RFC] kernel random segmentation fault?
Hi all:
I meet a kernel problem about the random segmentation fault(x86_64). In my
testcase, the size of local variables exceeds 20MB.
when run the testcase, it will cause segmentation fault(because the default
stack size limit is 8192KB).
when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
testcase will pass.
But when I run the testcase 100 times, it will cause random segmentation fault.
Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 "mm: propagate error
from stack expansion even for guard page"
cause this problems, when I revert it, the testcase will not cause random
segmentation fault problem.
Can anyone give some ideas about this problem?
Best Regards
Wang Long
Test Environment #
# uname -a
Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
x86_64 x86_64 GNU/Linux
The Testcase
#include
#include
#include
#define KB *1024
#define MB *(1024*1024)
#define GB *(1024*1024*1024)
int main(int argc, char** argv)
{
int ret;
struct rlimit rlim;
rlim.rlim_cur=20 MB;
rlim.rlim_max=20 MB;
ret = setrlimit(RLIMIT_AS, );
if ( 0 > ret)
{
perror("setrlimit failed");
exit(1);
}
printf("setrlimit success\n");
char tmp[20 MB];
int i = 0;
for (i = 0; i < 20 MB; i++)
{
tmp[i]=1;
}
printf("test success\n");
exit(1);
}
# My config
--
1.8.3.4
.
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.1.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx
-fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10
-fcall-saved-r11"
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
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_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_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_LEGACY_ALLOC_HWIRQ=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_DOMAIN=y
CONFIG_GENERIC_MSI_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=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
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
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
#
# RCU Subsystem
#
CONFIG_PREEMPT_RCU=y
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_RCU_USER_QS is not set
CONFIG_RCU_FANOUT=64
[RFC] kernel random segmentation fault?
Hi all:
I meet a kernel problem about the random segmentation fault(x86_64). In my
testcase, the size of local variables exceeds 20MB.
when run the testcase, it will cause segmentation fault(because the default
stack size limit is 8192KB).
when I increase the stack size limit to 1024000KB(ulimit -s 1024000), the
testcase will pass.
But when I run the testcase 100 times, it will cause random segmentation fault.
Maybe the commit fee7e49d45149fba60156f5b59014f764d3e3728 mm: propagate error
from stack expansion even for guard page
cause this problems, when I revert it, the testcase will not cause random
segmentation fault problem.
Can anyone give some ideas about this problem?
Best Regards
Wang Long
Test Environment #
# uname -a
Linux ivybridge 4.1.0-rc2+ #3 SMP PREEMPT Wed May 6 10:46:57 CST 2015 x86_64
x86_64 x86_64 GNU/Linux
The Testcase
#include stdio.h
#include stdlib.h
#include sys/resource.h
#define KB *1024
#define MB *(1024*1024)
#define GB *(1024*1024*1024)
int main(int argc, char** argv)
{
int ret;
struct rlimit rlim;
rlim.rlim_cur=20 MB;
rlim.rlim_max=20 MB;
ret = setrlimit(RLIMIT_AS, rlim);
if ( 0 ret)
{
perror(setrlimit failed);
exit(1);
}
printf(setrlimit success\n);
char tmp[20 MB];
int i = 0;
for (i = 0; i 20 MB; i++)
{
tmp[i]=1;
}
printf(test success\n);
exit(1);
}
# My config
--
1.8.3.4
.
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.1.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs/x86_64_defconfig
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx
-fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10
-fcall-saved-r11
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=
# CONFIG_LOCALVERSION_AUTO is not set
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_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_DEFAULT_HOSTNAME=(none)
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_LEGACY_ALLOC_HWIRQ=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_DOMAIN=y
CONFIG_GENERIC_MSI_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=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
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
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
#
# RCU Subsystem
#
CONFIG_PREEMPT_RCU=y
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_RCU_USER_QS is not set
CONFIG_RCU_FANOUT=64
