| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
The zero values makes the kernel use the RCU_CPU_STALL_TIMEOUT value,
which is already set to a big enough value.
Context: see the recent LKML discussion at
https://lore.kernel.org/all/6723aa4d.050a0220.35b515.0161.GAE@google.com/T/
|
| | |
|
| |
|
|
|
|
|
| |
Update the configs to the latest Linux versions: v6.2-rc5 and
next-20230124.
Enable CONFIG_NMI_CHECK_CPU and rcupdate.rcu_cpu_stall_cputime.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update linux upstream configs to the latest mainline/linux-next tags.
- RANDOM_TRUST_CPU was removed (defaults to y)
- RANDOM_TRUST_BOOTLOADER was removed (defaults to y)
- X86_SGX now requires X86_X2APIC
- DRM_VMWGFX_FBCON was removed
- ANDROID was removed
- NFT_OBJREF was removed
- CAN_SLCAN now requires new CAN_NETLINK
- CRYPTO_BLAKE2S was split into CRYPTO_BLAKE2S_X86 and CRYPTO_BLAKE2S_ARM
- DEBUG_VM_VMACACHE was removed
- CONTEXT_TRACKING_FORCE was removed
- DRM_DP_AUX_CHARDEV now requires DRM_I915 (or some other DRM driver)
- CRYPTO_SM4 was split into x86_64 amd arm64 configs
- ARM_CRYPTO was removed
- BINFMT_SHARED_FLAT was removed
Also update all configs that were marked as linux-next.
|
|
|
Also, factor emulation-dependent consts into a separate file.
|