Eric Lee / smarc-ti-linux-kernel

1

# Select 32 or 64 bit

1

# Select 32 or 64 bit

2

config 64BIT

2

config 64BIT

3

bool "64-bit kernel" if ARCH = "x86"

3

bool "64-bit kernel" if ARCH = "x86"

4

default ARCH != "i386"

4

default ARCH != "i386"

5

---help---

5

---help---

6

Say yes to build a 64-bit kernel - formerly known as x86_64

6

Say yes to build a 64-bit kernel - formerly known as x86_64

7

Say no to build a 32-bit kernel - formerly known as i386

7

Say no to build a 32-bit kernel - formerly known as i386

8

9

config X86_32

9

config X86_32

10

def_bool y

10

def_bool y

11

depends on !64BIT

11

depends on !64BIT

12

select CLKSRC_I8253

12

select CLKSRC_I8253

13

select HAVE_UID16

13

select HAVE_UID16

14

15

config X86_64

15

config X86_64

16

def_bool y

16

def_bool y

17

depends on 64BIT

17

depends on 64BIT

18

select X86_DEV_DMA_OPS

18

select X86_DEV_DMA_OPS

19

select ARCH_USE_CMPXCHG_LOCKREF

19

select ARCH_USE_CMPXCHG_LOCKREF

20

21

### Arch settings

21

### Arch settings

22

config X86

22

config X86

23

def_bool y

23

def_bool y

24

select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS

24

select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS

25

select HAVE_AOUT if X86_32

25

select HAVE_AOUT if X86_32

26

select HAVE_UNSTABLE_SCHED_CLOCK

26

select HAVE_UNSTABLE_SCHED_CLOCK

27

select ARCH_SUPPORTS_NUMA_BALANCING

27

select ARCH_SUPPORTS_NUMA_BALANCING

28

select ARCH_WANTS_PROT_NUMA_PROT_NONE

28

select ARCH_WANTS_PROT_NUMA_PROT_NONE

29

select HAVE_IDE

29

select HAVE_IDE

30

select HAVE_OPROFILE

30

select HAVE_OPROFILE

31

select HAVE_PCSPKR_PLATFORM

31

select HAVE_PCSPKR_PLATFORM

32

select HAVE_PERF_EVENTS

32

select HAVE_PERF_EVENTS

33

select HAVE_IOREMAP_PROT

33

select HAVE_IOREMAP_PROT

34

select HAVE_KPROBES

34

select HAVE_KPROBES

35

select HAVE_MEMBLOCK

35

select HAVE_MEMBLOCK

36

select HAVE_MEMBLOCK_NODE_MAP

36

select HAVE_MEMBLOCK_NODE_MAP

37

select ARCH_DISCARD_MEMBLOCK

37

select ARCH_DISCARD_MEMBLOCK

38

select ARCH_WANT_OPTIONAL_GPIOLIB

38

select ARCH_WANT_OPTIONAL_GPIOLIB

39

select ARCH_WANT_FRAME_POINTERS

39

select ARCH_WANT_FRAME_POINTERS

40

select HAVE_DMA_ATTRS

40

select HAVE_DMA_ATTRS

41

select HAVE_DMA_CONTIGUOUS if !SWIOTLB

41

select HAVE_DMA_CONTIGUOUS if !SWIOTLB

42

select HAVE_KRETPROBES

42

select HAVE_KRETPROBES

43

select HAVE_OPTPROBES

43

select HAVE_OPTPROBES

44

select HAVE_KPROBES_ON_FTRACE

44

select HAVE_KPROBES_ON_FTRACE

45

select HAVE_FTRACE_MCOUNT_RECORD

45

select HAVE_FTRACE_MCOUNT_RECORD

46

select HAVE_FENTRY if X86_64

46

select HAVE_FENTRY if X86_64

47

select HAVE_C_RECORDMCOUNT

47

select HAVE_C_RECORDMCOUNT

48

select HAVE_DYNAMIC_FTRACE

48

select HAVE_DYNAMIC_FTRACE

49

select HAVE_DYNAMIC_FTRACE_WITH_REGS

49

select HAVE_DYNAMIC_FTRACE_WITH_REGS

50

select HAVE_FUNCTION_TRACER

50

select HAVE_FUNCTION_TRACER

51

select HAVE_FUNCTION_GRAPH_TRACER

51

select HAVE_FUNCTION_GRAPH_TRACER

52

select HAVE_FUNCTION_GRAPH_FP_TEST

52

select HAVE_FUNCTION_GRAPH_FP_TEST

53

select HAVE_FUNCTION_TRACE_MCOUNT_TEST

53

select HAVE_FUNCTION_TRACE_MCOUNT_TEST

54

select HAVE_SYSCALL_TRACEPOINTS

54

select HAVE_SYSCALL_TRACEPOINTS

55

select SYSCTL_EXCEPTION_TRACE

55

select SYSCTL_EXCEPTION_TRACE

56

select HAVE_KVM

56

select HAVE_KVM

57

select HAVE_ARCH_KGDB

57

select HAVE_ARCH_KGDB

58

select HAVE_ARCH_TRACEHOOK

58

select HAVE_ARCH_TRACEHOOK

59

select HAVE_GENERIC_DMA_COHERENT if X86_32

59

select HAVE_GENERIC_DMA_COHERENT if X86_32

60

select HAVE_EFFICIENT_UNALIGNED_ACCESS

60

select HAVE_EFFICIENT_UNALIGNED_ACCESS

61

select USER_STACKTRACE_SUPPORT

61

select USER_STACKTRACE_SUPPORT

62

select HAVE_REGS_AND_STACK_ACCESS_API

62

select HAVE_REGS_AND_STACK_ACCESS_API

63

select HAVE_DMA_API_DEBUG

63

select HAVE_DMA_API_DEBUG

64

select HAVE_KERNEL_GZIP

64

select HAVE_KERNEL_GZIP

65

select HAVE_KERNEL_BZIP2

65

select HAVE_KERNEL_BZIP2

66

select HAVE_KERNEL_LZMA

66

select HAVE_KERNEL_LZMA

67

select HAVE_KERNEL_XZ

67

select HAVE_KERNEL_XZ

68

select HAVE_KERNEL_LZO

68

select HAVE_KERNEL_LZO

69

select HAVE_KERNEL_LZ4

69

select HAVE_KERNEL_LZ4

70

select HAVE_HW_BREAKPOINT

70

select HAVE_HW_BREAKPOINT

71

select HAVE_MIXED_BREAKPOINTS_REGS

71

select HAVE_MIXED_BREAKPOINTS_REGS

72

select PERF_EVENTS

72

select PERF_EVENTS

73

select HAVE_PERF_EVENTS_NMI

73

select HAVE_PERF_EVENTS_NMI

74

select HAVE_PERF_REGS

74

select HAVE_PERF_REGS

75

select HAVE_PERF_USER_STACK_DUMP

75

select HAVE_PERF_USER_STACK_DUMP

76

select HAVE_DEBUG_KMEMLEAK

76

select HAVE_DEBUG_KMEMLEAK

77

select ANON_INODES

77

select ANON_INODES

78

select HAVE_ALIGNED_STRUCT_PAGE if SLUB

78

select HAVE_ALIGNED_STRUCT_PAGE if SLUB

79

select HAVE_CMPXCHG_LOCAL

79

select HAVE_CMPXCHG_LOCAL

80

select HAVE_CMPXCHG_DOUBLE

80

select HAVE_CMPXCHG_DOUBLE

81

select HAVE_ARCH_KMEMCHECK

81

select HAVE_ARCH_KMEMCHECK

82

select HAVE_USER_RETURN_NOTIFIER

82

select HAVE_USER_RETURN_NOTIFIER

83

select ARCH_BINFMT_ELF_RANDOMIZE_PIE

83

select ARCH_BINFMT_ELF_RANDOMIZE_PIE

84

select HAVE_ARCH_JUMP_LABEL

84

select HAVE_ARCH_JUMP_LABEL

85

select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE

85

select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE

86

select SPARSE_IRQ

86

select SPARSE_IRQ

87

select GENERIC_FIND_FIRST_BIT

87

select GENERIC_FIND_FIRST_BIT

88

select GENERIC_IRQ_PROBE

88

select GENERIC_IRQ_PROBE

89

select GENERIC_PENDING_IRQ if SMP

89

select GENERIC_PENDING_IRQ if SMP

90

select GENERIC_IRQ_SHOW

90

select GENERIC_IRQ_SHOW

91

select GENERIC_CLOCKEVENTS_MIN_ADJUST

91

select GENERIC_CLOCKEVENTS_MIN_ADJUST

92

select IRQ_FORCED_THREADING

92

select IRQ_FORCED_THREADING

93

select USE_GENERIC_SMP_HELPERS if SMP

93

select USE_GENERIC_SMP_HELPERS if SMP

94

select HAVE_BPF_JIT if X86_64

94

select HAVE_BPF_JIT if X86_64

95

select HAVE_ARCH_TRANSPARENT_HUGEPAGE

95

select HAVE_ARCH_TRANSPARENT_HUGEPAGE

96

select CLKEVT_I8253

96

select CLKEVT_I8253

97

select ARCH_HAVE_NMI_SAFE_CMPXCHG

97

select ARCH_HAVE_NMI_SAFE_CMPXCHG

98

select GENERIC_IOMAP

98

select GENERIC_IOMAP

99

select DCACHE_WORD_ACCESS

99

select DCACHE_WORD_ACCESS

100

select GENERIC_SMP_IDLE_THREAD

100

select GENERIC_SMP_IDLE_THREAD

101

select ARCH_WANT_IPC_PARSE_VERSION if X86_32

101

select ARCH_WANT_IPC_PARSE_VERSION if X86_32

102

select HAVE_ARCH_SECCOMP_FILTER

102

select HAVE_ARCH_SECCOMP_FILTER

103

select BUILDTIME_EXTABLE_SORT

103

select BUILDTIME_EXTABLE_SORT

104

select GENERIC_CMOS_UPDATE

104

select GENERIC_CMOS_UPDATE

105

select HAVE_ARCH_SOFT_DIRTY

105

select HAVE_ARCH_SOFT_DIRTY

106

select CLOCKSOURCE_WATCHDOG

106

select CLOCKSOURCE_WATCHDOG

107

select GENERIC_CLOCKEVENTS

107

select GENERIC_CLOCKEVENTS

108

select ARCH_CLOCKSOURCE_DATA if X86_64

108

select ARCH_CLOCKSOURCE_DATA if X86_64

109

select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)

109

select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)

110

select GENERIC_TIME_VSYSCALL if X86_64

110

select GENERIC_TIME_VSYSCALL if X86_64

111

select KTIME_SCALAR if X86_32

111

select KTIME_SCALAR if X86_32

112

select GENERIC_STRNCPY_FROM_USER

112

select GENERIC_STRNCPY_FROM_USER

113

select GENERIC_STRNLEN_USER

113

select GENERIC_STRNLEN_USER

114

select HAVE_CONTEXT_TRACKING if X86_64

114

select HAVE_CONTEXT_TRACKING if X86_64

115

select HAVE_IRQ_TIME_ACCOUNTING

115

select HAVE_IRQ_TIME_ACCOUNTING

116

select VIRT_TO_BUS

116

select VIRT_TO_BUS

117

select MODULES_USE_ELF_REL if X86_32

117

select MODULES_USE_ELF_REL if X86_32

118

select MODULES_USE_ELF_RELA if X86_64

118

select MODULES_USE_ELF_RELA if X86_64

119

select CLONE_BACKWARDS if X86_32

119

select CLONE_BACKWARDS if X86_32

120

select ARCH_USE_BUILTIN_BSWAP

120

select ARCH_USE_BUILTIN_BSWAP

121

select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION

121

select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION

122

select OLD_SIGACTION if X86_32

122

select OLD_SIGACTION if X86_32

123

select COMPAT_OLD_SIGACTION if IA32_EMULATION

123

select COMPAT_OLD_SIGACTION if IA32_EMULATION

124

select RTC_LIB

124

select RTC_LIB

125

select HAVE_DEBUG_STACKOVERFLOW

125

select HAVE_DEBUG_STACKOVERFLOW

126

127

config INSTRUCTION_DECODER

127

config INSTRUCTION_DECODER

128

def_bool y

128

def_bool y

129

depends on KPROBES || PERF_EVENTS || UPROBES

129

depends on KPROBES || PERF_EVENTS || UPROBES

130

131

config OUTPUT_FORMAT

131

config OUTPUT_FORMAT

132

string

132

string

133

default "elf32-i386" if X86_32

133

default "elf32-i386" if X86_32

134

default "elf64-x86-64" if X86_64

134

default "elf64-x86-64" if X86_64

135

136

config ARCH_DEFCONFIG

136

config ARCH_DEFCONFIG

137

string

137

string

138

default "arch/x86/configs/i386_defconfig" if X86_32

138

default "arch/x86/configs/i386_defconfig" if X86_32

139

default "arch/x86/configs/x86_64_defconfig" if X86_64

139

default "arch/x86/configs/x86_64_defconfig" if X86_64

140

141

config LOCKDEP_SUPPORT

141

config LOCKDEP_SUPPORT

142

def_bool y

142

def_bool y

143

144

config STACKTRACE_SUPPORT

144

config STACKTRACE_SUPPORT

145

def_bool y

145

def_bool y

146

147

config HAVE_LATENCYTOP_SUPPORT

147

config HAVE_LATENCYTOP_SUPPORT

148

def_bool y

148

def_bool y

149

150

config MMU

150

config MMU

151

def_bool y

151

def_bool y

152

153

config SBUS

153

config SBUS

154

bool

154

bool

155

156

config NEED_DMA_MAP_STATE

156

config NEED_DMA_MAP_STATE

157

def_bool y

157

def_bool y

158

depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG

158

depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG

159

160

config NEED_SG_DMA_LENGTH

160

config NEED_SG_DMA_LENGTH

161

def_bool y

161

def_bool y

162

163

config GENERIC_ISA_DMA

163

config GENERIC_ISA_DMA

164

def_bool y

164

def_bool y

165

depends on ISA_DMA_API

165

depends on ISA_DMA_API

166

167

config GENERIC_BUG

167

config GENERIC_BUG

168

def_bool y

168

def_bool y

169

depends on BUG

169

depends on BUG

170

select GENERIC_BUG_RELATIVE_POINTERS if X86_64

170

select GENERIC_BUG_RELATIVE_POINTERS if X86_64

171

172

config GENERIC_BUG_RELATIVE_POINTERS

172

config GENERIC_BUG_RELATIVE_POINTERS

173

bool

173

bool

174

175

config GENERIC_HWEIGHT

175

config GENERIC_HWEIGHT

176

def_bool y

176

def_bool y

177

178

config ARCH_MAY_HAVE_PC_FDC

178

config ARCH_MAY_HAVE_PC_FDC

179

def_bool y

179

def_bool y

180

depends on ISA_DMA_API

180

depends on ISA_DMA_API

181

182

config RWSEM_XCHGADD_ALGORITHM

182

config RWSEM_XCHGADD_ALGORITHM

183

def_bool y

183

def_bool y

184

185

config GENERIC_CALIBRATE_DELAY

185

config GENERIC_CALIBRATE_DELAY

186

def_bool y

186

def_bool y

187

188

config ARCH_HAS_CPU_RELAX

188

config ARCH_HAS_CPU_RELAX

189

def_bool y

189

def_bool y

190

191

config ARCH_HAS_CACHE_LINE_SIZE

191

config ARCH_HAS_CACHE_LINE_SIZE

192

def_bool y

192

def_bool y

193

194

config ARCH_HAS_CPU_AUTOPROBE

194

config ARCH_HAS_CPU_AUTOPROBE

195

def_bool y

195

def_bool y

196

197

config HAVE_SETUP_PER_CPU_AREA

197

config HAVE_SETUP_PER_CPU_AREA

198

def_bool y

198

def_bool y

199

200

config NEED_PER_CPU_EMBED_FIRST_CHUNK

200

config NEED_PER_CPU_EMBED_FIRST_CHUNK

201

def_bool y

201

def_bool y

202

203

config NEED_PER_CPU_PAGE_FIRST_CHUNK

203

config NEED_PER_CPU_PAGE_FIRST_CHUNK

204

def_bool y

204

def_bool y

205

206

config ARCH_HIBERNATION_POSSIBLE

206

config ARCH_HIBERNATION_POSSIBLE

207

def_bool y

207

def_bool y

208

209

config ARCH_SUSPEND_POSSIBLE

209

config ARCH_SUSPEND_POSSIBLE

210

def_bool y

210

def_bool y

211

212

config ARCH_WANT_HUGE_PMD_SHARE

212

config ARCH_WANT_HUGE_PMD_SHARE

213

def_bool y

213

def_bool y

214

215

config ARCH_WANT_GENERAL_HUGETLB

215

config ARCH_WANT_GENERAL_HUGETLB

216

def_bool y

216

def_bool y

217

218

config ZONE_DMA32

218

config ZONE_DMA32

219

bool

219

bool

220

default X86_64

220

default X86_64

221

222

config AUDIT_ARCH

222

config AUDIT_ARCH

223

bool

223

bool

224

default X86_64

224

default X86_64

225

226

config ARCH_SUPPORTS_OPTIMIZED_INLINING

226

config ARCH_SUPPORTS_OPTIMIZED_INLINING

227

def_bool y

227

def_bool y

228

229

config ARCH_SUPPORTS_DEBUG_PAGEALLOC

229

config ARCH_SUPPORTS_DEBUG_PAGEALLOC

230

def_bool y

230

def_bool y

231

232

config HAVE_INTEL_TXT

232

config HAVE_INTEL_TXT

233

def_bool y

233

def_bool y

234

depends on INTEL_IOMMU && ACPI

234

depends on INTEL_IOMMU && ACPI

235

236

config X86_32_SMP

236

config X86_32_SMP

237

def_bool y

237

def_bool y

238

depends on X86_32 && SMP

238

depends on X86_32 && SMP

239

240

config X86_64_SMP

240

config X86_64_SMP

241

def_bool y

241

def_bool y

242

depends on X86_64 && SMP

242

depends on X86_64 && SMP

243

244

config X86_HT

244

config X86_HT

245

def_bool y

245

def_bool y

246

depends on SMP

246

depends on SMP

247

248

config X86_32_LAZY_GS

248

config X86_32_LAZY_GS

249

def_bool y

249

def_bool y

250

depends on X86_32 && !CC_STACKPROTECTOR

250

depends on X86_32 && !CC_STACKPROTECTOR

251

252

config ARCH_HWEIGHT_CFLAGS

252

config ARCH_HWEIGHT_CFLAGS

253

string

253

string

254

default "-fcall-saved-ecx -fcall-saved-edx" if X86_32

254

default "-fcall-saved-ecx -fcall-saved-edx" if X86_32

255

default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64

255

default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64

256

257

config ARCH_CPU_PROBE_RELEASE

257

config ARCH_CPU_PROBE_RELEASE

258

def_bool y

258

def_bool y

259

depends on HOTPLUG_CPU

259

depends on HOTPLUG_CPU

260

261

config ARCH_SUPPORTS_UPROBES

261

config ARCH_SUPPORTS_UPROBES

262

def_bool y

262

def_bool y

263

264

source "init/Kconfig"

264

source "init/Kconfig"

265

source "kernel/Kconfig.freezer"

265

source "kernel/Kconfig.freezer"

266

267

menu "Processor type and features"

267

menu "Processor type and features"

268

269

config ZONE_DMA

269

config ZONE_DMA

270

bool "DMA memory allocation support" if EXPERT

270

bool "DMA memory allocation support" if EXPERT

271

default y

271

default y

272

help

272

help

273

DMA memory allocation support allows devices with less than 32-bit

273

DMA memory allocation support allows devices with less than 32-bit

274

addressing to allocate within the first 16MB of address space.

274

addressing to allocate within the first 16MB of address space.

275

Disable if no such devices will be used.

275

Disable if no such devices will be used.

276

277

If unsure, say Y.

277

If unsure, say Y.

278

279

config SMP

279

config SMP

280

bool "Symmetric multi-processing support"

280

bool "Symmetric multi-processing support"

281

---help---

281

---help---

282

This enables support for systems with more than one CPU. If you have

282

This enables support for systems with more than one CPU. If you have

283

a system with only one CPU, like most personal computers, say N. If

283

a system with only one CPU, like most personal computers, say N. If

284

you have a system with more than one CPU, say Y.

284

you have a system with more than one CPU, say Y.

285

286

If you say N here, the kernel will run on single and multiprocessor

286

If you say N here, the kernel will run on single and multiprocessor

287

machines, but will use only one CPU of a multiprocessor machine. If

287

machines, but will use only one CPU of a multiprocessor machine. If

288

you say Y here, the kernel will run on many, but not all,

288

you say Y here, the kernel will run on many, but not all,

289

singleprocessor machines. On a singleprocessor machine, the kernel

289

singleprocessor machines. On a singleprocessor machine, the kernel

290

will run faster if you say N here.

290

will run faster if you say N here.

291

292

Note that if you say Y here and choose architecture "586" or

292

Note that if you say Y here and choose architecture "586" or

293

"Pentium" under "Processor family", the kernel will not work on 486

293

"Pentium" under "Processor family", the kernel will not work on 486

294

architectures. Similarly, multiprocessor kernels for the "PPro"

294

architectures. Similarly, multiprocessor kernels for the "PPro"

295

architecture may not work on all Pentium based boards.

295

architecture may not work on all Pentium based boards.

296

297

People using multiprocessor machines who say Y here should also say

297

People using multiprocessor machines who say Y here should also say

298

Y to "Enhanced Real Time Clock Support", below. The "Advanced Power

298

Y to "Enhanced Real Time Clock Support", below. The "Advanced Power

299

Management" code will be disabled if you say Y here.

299

Management" code will be disabled if you say Y here.

300

301

See also <file:Documentation/x86/i386/IO-APIC.txt>,

301

See also <file:Documentation/x86/i386/IO-APIC.txt>,

302

<file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at

302

<file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at

303

<http://www.tldp.org/docs.html#howto>.

303

<http://www.tldp.org/docs.html#howto>.

304

305

If you don't know what to do here, say N.

305

If you don't know what to do here, say N.

306

307

config X86_X2APIC

307

config X86_X2APIC

308

bool "Support x2apic"

308

bool "Support x2apic"

309

depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP

309

depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP

310

---help---

310

---help---

311

This enables x2apic support on CPUs that have this feature.

311

This enables x2apic support on CPUs that have this feature.

312

313

This allows 32-bit apic IDs (so it can support very large systems),

313

This allows 32-bit apic IDs (so it can support very large systems),

314

and accesses the local apic via MSRs not via mmio.

314

and accesses the local apic via MSRs not via mmio.

315

316

If you don't know what to do here, say N.

316

If you don't know what to do here, say N.

317

318

config X86_MPPARSE

318

config X86_MPPARSE

319

bool "Enable MPS table" if ACPI || SFI

319

bool "Enable MPS table" if ACPI || SFI

320

default y

320

default y

321

depends on X86_LOCAL_APIC

321

depends on X86_LOCAL_APIC

322

---help---

322

---help---

323

For old smp systems that do not have proper acpi support. Newer systems

323

For old smp systems that do not have proper acpi support. Newer systems

324

(esp with 64bit cpus) with acpi support, MADT and DSDT will override it

324

(esp with 64bit cpus) with acpi support, MADT and DSDT will override it

325

326

config X86_BIGSMP

326

config X86_BIGSMP

327

bool "Support for big SMP systems with more than 8 CPUs"

327

bool "Support for big SMP systems with more than 8 CPUs"

328

depends on X86_32 && SMP

328

depends on X86_32 && SMP

329

---help---

329

---help---

330

This option is needed for the systems that have more than 8 CPUs

330

This option is needed for the systems that have more than 8 CPUs

331

332

config GOLDFISH

332

config GOLDFISH

333

def_bool y

333

def_bool y

334

depends on X86_GOLDFISH

334

depends on X86_GOLDFISH

335

336

if X86_32

336

if X86_32

337

config X86_EXTENDED_PLATFORM

337

config X86_EXTENDED_PLATFORM

338

bool "Support for extended (non-PC) x86 platforms"

338

bool "Support for extended (non-PC) x86 platforms"

339

default y

339

default y

340

---help---

340

---help---

341

If you disable this option then the kernel will only support

341

If you disable this option then the kernel will only support

342

standard PC platforms. (which covers the vast majority of

342

standard PC platforms. (which covers the vast majority of

343

systems out there.)

343

systems out there.)

344

345

If you enable this option then you'll be able to select support

345

If you enable this option then you'll be able to select support

346

for the following (non-PC) 32 bit x86 platforms:

346

for the following (non-PC) 32 bit x86 platforms:

347

Goldfish (Android emulator)

347

Goldfish (Android emulator)

348

AMD Elan

348

AMD Elan

349

NUMAQ (IBM/Sequent)

349

NUMAQ (IBM/Sequent)

350

RDC R-321x SoC

350

RDC R-321x SoC

351

SGI 320/540 (Visual Workstation)

351

SGI 320/540 (Visual Workstation)

352

STA2X11-based (e.g. Northville)

352

STA2X11-based (e.g. Northville)

353

Summit/EXA (IBM x440)

353

Summit/EXA (IBM x440)

354

Unisys ES7000 IA32 series

354

Unisys ES7000 IA32 series

355

Moorestown MID devices

355

Moorestown MID devices

356

357

If you have one of these systems, or if you want to build a

357

If you have one of these systems, or if you want to build a

358

generic distribution kernel, say Y here - otherwise say N.

358

generic distribution kernel, say Y here - otherwise say N.

359

endif

359

endif

360

361

if X86_64

361

if X86_64

362

config X86_EXTENDED_PLATFORM

362

config X86_EXTENDED_PLATFORM

363

bool "Support for extended (non-PC) x86 platforms"

363

bool "Support for extended (non-PC) x86 platforms"

364

default y

364

default y

365

---help---

365

---help---

366

If you disable this option then the kernel will only support

366

If you disable this option then the kernel will only support

367

standard PC platforms. (which covers the vast majority of

367

standard PC platforms. (which covers the vast majority of

368

systems out there.)

368

systems out there.)

369

370

If you enable this option then you'll be able to select support

370

If you enable this option then you'll be able to select support

371

for the following (non-PC) 64 bit x86 platforms:

371

for the following (non-PC) 64 bit x86 platforms:

372

Numascale NumaChip

372

Numascale NumaChip

373

ScaleMP vSMP

373

ScaleMP vSMP

374

SGI Ultraviolet

374

SGI Ultraviolet

375

376

If you have one of these systems, or if you want to build a

376

If you have one of these systems, or if you want to build a

377

generic distribution kernel, say Y here - otherwise say N.

377

generic distribution kernel, say Y here - otherwise say N.

378

endif

378

endif

379

# This is an alphabetically sorted list of 64 bit extended platforms

379

# This is an alphabetically sorted list of 64 bit extended platforms

380

# Please maintain the alphabetic order if and when there are additions

380

# Please maintain the alphabetic order if and when there are additions

381

config X86_NUMACHIP

381

config X86_NUMACHIP

382

bool "Numascale NumaChip"

382

bool "Numascale NumaChip"

383

depends on X86_64

383

depends on X86_64

384

depends on X86_EXTENDED_PLATFORM

384

depends on X86_EXTENDED_PLATFORM

385

depends on NUMA

385

depends on NUMA

386

depends on SMP

386

depends on SMP

387

depends on X86_X2APIC

387

depends on X86_X2APIC

388

depends on PCI_MMCONFIG

388

depends on PCI_MMCONFIG

389

---help---

389

---help---

390

Adds support for Numascale NumaChip large-SMP systems. Needed to

390

Adds support for Numascale NumaChip large-SMP systems. Needed to

391

enable more than ~168 cores.

391

enable more than ~168 cores.

392

If you don't have one of these, you should say N here.

392

If you don't have one of these, you should say N here.

393

394

config X86_VSMP

394

config X86_VSMP

395

bool "ScaleMP vSMP"

395

bool "ScaleMP vSMP"

396

select HYPERVISOR_GUEST

396

select HYPERVISOR_GUEST

397

select PARAVIRT

397

select PARAVIRT

398

depends on X86_64 && PCI

398

depends on X86_64 && PCI

399

depends on X86_EXTENDED_PLATFORM

399

depends on X86_EXTENDED_PLATFORM

400

depends on SMP

400

depends on SMP

401

---help---

401

---help---

402

Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is

402

Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is

403

supposed to run on these EM64T-based machines. Only choose this option

403

supposed to run on these EM64T-based machines. Only choose this option

404

if you have one of these machines.

404

if you have one of these machines.

405

406

config X86_UV

406

config X86_UV

407

bool "SGI Ultraviolet"

407

bool "SGI Ultraviolet"

408

depends on X86_64

408

depends on X86_64

409

depends on X86_EXTENDED_PLATFORM

409

depends on X86_EXTENDED_PLATFORM

410

depends on NUMA

410

depends on NUMA

411

depends on X86_X2APIC

411

depends on X86_X2APIC

412

---help---

412

---help---

413

This option is needed in order to support SGI Ultraviolet systems.

413

This option is needed in order to support SGI Ultraviolet systems.

414

If you don't have one of these, you should say N here.

414

If you don't have one of these, you should say N here.

415

416

# Following is an alphabetically sorted list of 32 bit extended platforms

416

# Following is an alphabetically sorted list of 32 bit extended platforms

417

# Please maintain the alphabetic order if and when there are additions

417

# Please maintain the alphabetic order if and when there are additions

418

419

config X86_GOLDFISH

419

config X86_GOLDFISH

420

bool "Goldfish (Virtual Platform)"

420

bool "Goldfish (Virtual Platform)"

421

depends on X86_32

421

depends on X86_32

422

depends on X86_EXTENDED_PLATFORM

422

depends on X86_EXTENDED_PLATFORM

423

---help---

423

---help---

424

Enable support for the Goldfish virtual platform used primarily

424

Enable support for the Goldfish virtual platform used primarily

425

for Android development. Unless you are building for the Android

425

for Android development. Unless you are building for the Android

426

Goldfish emulator say N here.

426

Goldfish emulator say N here.

427

428

config X86_INTEL_CE

428

config X86_INTEL_CE

429

bool "CE4100 TV platform"

429

bool "CE4100 TV platform"

430

depends on PCI

430

depends on PCI

431

depends on PCI_GODIRECT

431

depends on PCI_GODIRECT

432

depends on X86_32

432

depends on X86_32

433

depends on X86_EXTENDED_PLATFORM

433

depends on X86_EXTENDED_PLATFORM

434

select X86_REBOOTFIXUPS

434

select X86_REBOOTFIXUPS

435

select OF

435

select OF

436

select OF_EARLY_FLATTREE

436

select OF_EARLY_FLATTREE

437

select IRQ_DOMAIN

437

select IRQ_DOMAIN

438

---help---

438

---help---

439

Select for the Intel CE media processor (CE4100) SOC.

439

Select for the Intel CE media processor (CE4100) SOC.

440

This option compiles in support for the CE4100 SOC for settop

440

This option compiles in support for the CE4100 SOC for settop

441

boxes and media devices.

441

boxes and media devices.

442

443

config X86_WANT_INTEL_MID

443

config X86_WANT_INTEL_MID

444

bool "Intel MID platform support"

444

bool "Intel MID platform support"

445

depends on X86_32

445

depends on X86_32

446

depends on X86_EXTENDED_PLATFORM

446

depends on X86_EXTENDED_PLATFORM

447

---help---

447

---help---

448

Select to build a kernel capable of supporting Intel MID platform

448

Select to build a kernel capable of supporting Intel MID platform

449

systems which do not have the PCI legacy interfaces (Moorestown,

449

systems which do not have the PCI legacy interfaces (Moorestown,

450

Medfield). If you are building for a PC class system say N here.

450

Medfield). If you are building for a PC class system say N here.

451

452

if X86_WANT_INTEL_MID

452

if X86_WANT_INTEL_MID

453

454

config X86_INTEL_MID

454

config X86_INTEL_MID

455

bool

455

bool

456

457

config X86_MDFLD

457

config X86_MDFLD

458

bool "Medfield MID platform"

458

bool "Medfield MID platform"

459

depends on PCI

459

depends on PCI

460

depends on PCI_GOANY

460

depends on PCI_GOANY

461

depends on X86_IO_APIC

461

depends on X86_IO_APIC

462

select X86_INTEL_MID

462

select X86_INTEL_MID

463

select SFI

463

select SFI

464

select DW_APB_TIMER

464

select DW_APB_TIMER

465

select APB_TIMER

465

select APB_TIMER

466

select I2C

466

select I2C

467

select SPI

467

select SPI

468

select INTEL_SCU_IPC

468

select INTEL_SCU_IPC

469

select X86_PLATFORM_DEVICES

469

select X86_PLATFORM_DEVICES

470

select MFD_INTEL_MSIC

470

select MFD_INTEL_MSIC

471

---help---

471

---help---

472

Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin

472

Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin

473

Internet Device(MID) platform.

473

Internet Device(MID) platform.

474

Unlike standard x86 PCs, Medfield does not have many legacy devices

474

Unlike standard x86 PCs, Medfield does not have many legacy devices

475

nor standard legacy replacement devices/features. e.g. Medfield does

475

nor standard legacy replacement devices/features. e.g. Medfield does

476

not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.

476

not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.

477

478

endif

478

endif

479

480

config X86_INTEL_LPSS

480

config X86_INTEL_LPSS

481

bool "Intel Low Power Subsystem Support"

481

bool "Intel Low Power Subsystem Support"

482

depends on ACPI

482

depends on ACPI

483

select COMMON_CLK

483

select COMMON_CLK

484

select PINCTRL

484

select PINCTRL

485

---help---

485

---help---

486

Select to build support for Intel Low Power Subsystem such as

486

Select to build support for Intel Low Power Subsystem such as

487

found on Intel Lynxpoint PCH. Selecting this option enables

487

found on Intel Lynxpoint PCH. Selecting this option enables

488

things like clock tree (common clock framework) and pincontrol

488

things like clock tree (common clock framework) and pincontrol

489

which are needed by the LPSS peripheral drivers.

489

which are needed by the LPSS peripheral drivers.

490

491

config X86_RDC321X

491

config X86_RDC321X

492

bool "RDC R-321x SoC"

492

bool "RDC R-321x SoC"

493

depends on X86_32

493

depends on X86_32

494

depends on X86_EXTENDED_PLATFORM

494

depends on X86_EXTENDED_PLATFORM

495

select M486

495

select M486

496

select X86_REBOOTFIXUPS

496

select X86_REBOOTFIXUPS

497

---help---

497

---help---

498

This option is needed for RDC R-321x system-on-chip, also known

498

This option is needed for RDC R-321x system-on-chip, also known

499

as R-8610-(G).

499

as R-8610-(G).

500

If you don't have one of these chips, you should say N here.

500

If you don't have one of these chips, you should say N here.

501

502

config X86_32_NON_STANDARD

502

config X86_32_NON_STANDARD

503

bool "Support non-standard 32-bit SMP architectures"

503

bool "Support non-standard 32-bit SMP architectures"

504

depends on X86_32 && SMP

504

depends on X86_32 && SMP

505

depends on X86_EXTENDED_PLATFORM

505

depends on X86_EXTENDED_PLATFORM

506

---help---

506

---help---

507

This option compiles in the NUMAQ, Summit, bigsmp, ES7000,

507

This option compiles in the NUMAQ, Summit, bigsmp, ES7000,

508

STA2X11, default subarchitectures. It is intended for a generic

508

STA2X11, default subarchitectures. It is intended for a generic

509

binary kernel. If you select them all, kernel will probe it

509

binary kernel. If you select them all, kernel will probe it

510

one by one and will fallback to default.

510

one by one and will fallback to default.

511

512

# Alphabetically sorted list of Non standard 32 bit platforms

512

# Alphabetically sorted list of Non standard 32 bit platforms

513

514

config X86_NUMAQ

514

config X86_NUMAQ

515

bool "NUMAQ (IBM/Sequent)"

515

bool "NUMAQ (IBM/Sequent)"

516

depends on X86_32_NON_STANDARD

516

depends on X86_32_NON_STANDARD

517

depends on PCI

517

depends on PCI

518

select NUMA

518

select NUMA

519

select X86_MPPARSE

519

select X86_MPPARSE

520

---help---

520

---help---

521

This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)

521

This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)

522

NUMA multiquad box. This changes the way that processors are

522

NUMA multiquad box. This changes the way that processors are

523

bootstrapped, and uses Clustered Logical APIC addressing mode instead

523

bootstrapped, and uses Clustered Logical APIC addressing mode instead

524

of Flat Logical. You will need a new lynxer.elf file to flash your

524

of Flat Logical. You will need a new lynxer.elf file to flash your

525

firmware with - send email to <Martin.Bligh@us.ibm.com>.

525

firmware with - send email to <Martin.Bligh@us.ibm.com>.

526

527

config X86_SUPPORTS_MEMORY_FAILURE

527

config X86_SUPPORTS_MEMORY_FAILURE

528

def_bool y

528

def_bool y

529

# MCE code calls memory_failure():

529

# MCE code calls memory_failure():

530

depends on X86_MCE

530

depends on X86_MCE

531

# On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:

531

# On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:

532

depends on !X86_NUMAQ

532

depends on !X86_NUMAQ

533

# On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:

533

# On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:

534

depends on X86_64 || !SPARSEMEM

534

depends on X86_64 || !SPARSEMEM

535

select ARCH_SUPPORTS_MEMORY_FAILURE

535

select ARCH_SUPPORTS_MEMORY_FAILURE

536

537

config X86_VISWS

537

config X86_VISWS

538

bool "SGI 320/540 (Visual Workstation)"

538

bool "SGI 320/540 (Visual Workstation)"

539

depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT

539

depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT

540

depends on X86_32_NON_STANDARD

540

depends on X86_32_NON_STANDARD

541

---help---

541

---help---

542

The SGI Visual Workstation series is an IA32-based workstation

542

The SGI Visual Workstation series is an IA32-based workstation

543

based on SGI systems chips with some legacy PC hardware attached.

543

based on SGI systems chips with some legacy PC hardware attached.

544

545

Say Y here to create a kernel to run on the SGI 320 or 540.

545

Say Y here to create a kernel to run on the SGI 320 or 540.

546

547

A kernel compiled for the Visual Workstation will run on general

547

A kernel compiled for the Visual Workstation will run on general

548

PCs as well. See <file:Documentation/sgi-visws.txt> for details.

548

PCs as well. See <file:Documentation/sgi-visws.txt> for details.

549

550

config STA2X11

550

config STA2X11

551

bool "STA2X11 Companion Chip Support"

551

bool "STA2X11 Companion Chip Support"

552

depends on X86_32_NON_STANDARD && PCI

552

depends on X86_32_NON_STANDARD && PCI

553

select X86_DEV_DMA_OPS

553

select X86_DEV_DMA_OPS

554

select X86_DMA_REMAP

554

select X86_DMA_REMAP

555

select SWIOTLB

555

select SWIOTLB

556

select MFD_STA2X11

556

select MFD_STA2X11

557

select ARCH_REQUIRE_GPIOLIB

557

select ARCH_REQUIRE_GPIOLIB

558

default n

558

default n

559

---help---

559

---help---

560

This adds support for boards based on the STA2X11 IO-Hub,

560

This adds support for boards based on the STA2X11 IO-Hub,

561

a.k.a. "ConneXt". The chip is used in place of the standard

561

a.k.a. "ConneXt". The chip is used in place of the standard

562

PC chipset, so all "standard" peripherals are missing. If this

562

PC chipset, so all "standard" peripherals are missing. If this

563

option is selected the kernel will still be able to boot on

563

option is selected the kernel will still be able to boot on

564

standard PC machines.

564

standard PC machines.

565

566

config X86_SUMMIT

566

config X86_SUMMIT

567

bool "Summit/EXA (IBM x440)"

567

bool "Summit/EXA (IBM x440)"

568

depends on X86_32_NON_STANDARD

568

depends on X86_32_NON_STANDARD

569

---help---

569

---help---

570

This option is needed for IBM systems that use the Summit/EXA chipset.

570

This option is needed for IBM systems that use the Summit/EXA chipset.

571

In particular, it is needed for the x440.

571

In particular, it is needed for the x440.

572

573

config X86_ES7000

573

config X86_ES7000

574

bool "Unisys ES7000 IA32 series"

574

bool "Unisys ES7000 IA32 series"

575

depends on X86_32_NON_STANDARD && X86_BIGSMP

575

depends on X86_32_NON_STANDARD && X86_BIGSMP

576

---help---

576

---help---

577

Support for Unisys ES7000 systems. Say 'Y' here if this kernel is

577

Support for Unisys ES7000 systems. Say 'Y' here if this kernel is

578

supposed to run on an IA32-based Unisys ES7000 system.

578

supposed to run on an IA32-based Unisys ES7000 system.

579

580

config X86_32_IRIS

580

config X86_32_IRIS

581

tristate "Eurobraille/Iris poweroff module"

581

tristate "Eurobraille/Iris poweroff module"

582

depends on X86_32

582

depends on X86_32

583

---help---

583

---help---

584

The Iris machines from EuroBraille do not have APM or ACPI support

584

The Iris machines from EuroBraille do not have APM or ACPI support

585

to shut themselves down properly. A special I/O sequence is

585

to shut themselves down properly. A special I/O sequence is

586

needed to do so, which is what this module does at

586

needed to do so, which is what this module does at

587

kernel shutdown.

587

kernel shutdown.

588

589

This is only for Iris machines from EuroBraille.

589

This is only for Iris machines from EuroBraille.

590

591

If unused, say N.

591

If unused, say N.

592

593

config SCHED_OMIT_FRAME_POINTER

593

config SCHED_OMIT_FRAME_POINTER

594

def_bool y

594

def_bool y

595

prompt "Single-depth WCHAN output"

595

prompt "Single-depth WCHAN output"

596

depends on X86

596

depends on X86

597

---help---

597

---help---

598

Calculate simpler /proc/<PID>/wchan values. If this option

598

Calculate simpler /proc/<PID>/wchan values. If this option

599

is disabled then wchan values will recurse back to the

599

is disabled then wchan values will recurse back to the

600

caller function. This provides more accurate wchan values,

600

caller function. This provides more accurate wchan values,

601

at the expense of slightly more scheduling overhead.

601

at the expense of slightly more scheduling overhead.

602

603

If in doubt, say "Y".

603

If in doubt, say "Y".

604

605

menuconfig HYPERVISOR_GUEST

605

menuconfig HYPERVISOR_GUEST

606

bool "Linux guest support"

606

bool "Linux guest support"

607

---help---

607

---help---

608

Say Y here to enable options for running Linux under various hyper-

608

Say Y here to enable options for running Linux under various hyper-

609

visors. This option enables basic hypervisor detection and platform

609

visors. This option enables basic hypervisor detection and platform

610

setup.

610

setup.

611

612

If you say N, all options in this submenu will be skipped and

612

If you say N, all options in this submenu will be skipped and

613

disabled, and Linux guest support won't be built in.

613

disabled, and Linux guest support won't be built in.

614

615

if HYPERVISOR_GUEST

615

if HYPERVISOR_GUEST

616

617

config PARAVIRT

617

config PARAVIRT

618

bool "Enable paravirtualization code"

618

bool "Enable paravirtualization code"

619

---help---

619

---help---

620

This changes the kernel so it can modify itself when it is run

620

This changes the kernel so it can modify itself when it is run

621

under a hypervisor, potentially improving performance significantly

621

under a hypervisor, potentially improving performance significantly

622

over full virtualization. However, when run without a hypervisor

622

over full virtualization. However, when run without a hypervisor

623

the kernel is theoretically slower and slightly larger.

623

the kernel is theoretically slower and slightly larger.

624

625

config PARAVIRT_DEBUG

625

config PARAVIRT_DEBUG

626

bool "paravirt-ops debugging"

626

bool "paravirt-ops debugging"

627

depends on PARAVIRT && DEBUG_KERNEL

627

depends on PARAVIRT && DEBUG_KERNEL

628

---help---

628

---help---

629

Enable to debug paravirt_ops internals. Specifically, BUG if

629

Enable to debug paravirt_ops internals. Specifically, BUG if

630

a paravirt_op is missing when it is called.

630

a paravirt_op is missing when it is called.

631

632

config PARAVIRT_SPINLOCKS

632

config PARAVIRT_SPINLOCKS

633

bool "Paravirtualization layer for spinlocks"

633

bool "Paravirtualization layer for spinlocks"

634

depends on PARAVIRT && SMP

634

depends on PARAVIRT && SMP

635

select UNINLINE_SPIN_UNLOCK

635

select UNINLINE_SPIN_UNLOCK

636

---help---

636

---help---

637

Paravirtualized spinlocks allow a pvops backend to replace the

637

Paravirtualized spinlocks allow a pvops backend to replace the

638

spinlock implementation with something virtualization-friendly

638

spinlock implementation with something virtualization-friendly

639

(for example, block the virtual CPU rather than spinning).

639

(for example, block the virtual CPU rather than spinning).

640

641

Unfortunately the downside is an up to 5% performance hit on

641

Unfortunately the downside is an up to 5% performance hit on

642

native kernels, with various workloads.

642

native kernels, with various workloads.

643

644

If you are unsure how to answer this question, answer N.

644

If you are unsure how to answer this question, answer N.

645

646

source "arch/x86/xen/Kconfig"

646

source "arch/x86/xen/Kconfig"

647

648

config KVM_GUEST

648

config KVM_GUEST

649

bool "KVM Guest support (including kvmclock)"

649

bool "KVM Guest support (including kvmclock)"

650

depends on PARAVIRT

650

depends on PARAVIRT

651

select PARAVIRT_CLOCK

651

select PARAVIRT_CLOCK

652

default y

652

default y

653

---help---

653

---help---

654

This option enables various optimizations for running under the KVM

654

This option enables various optimizations for running under the KVM

655

hypervisor. It includes a paravirtualized clock, so that instead

655

hypervisor. It includes a paravirtualized clock, so that instead

656

of relying on a PIT (or probably other) emulation by the

656

of relying on a PIT (or probably other) emulation by the

657

underlying device model, the host provides the guest with

657

underlying device model, the host provides the guest with

658

timing infrastructure such as time of day, and system time

658

timing infrastructure such as time of day, and system time

659

660

config KVM_DEBUG_FS

660

config KVM_DEBUG_FS

661

bool "Enable debug information for KVM Guests in debugfs"

661

bool "Enable debug information for KVM Guests in debugfs"

662

depends on KVM_GUEST && DEBUG_FS

662

depends on KVM_GUEST && DEBUG_FS

663

default n

663

default n

664

---help---

664

---help---

665

This option enables collection of various statistics for KVM guest.

665

This option enables collection of various statistics for KVM guest.

666

Statistics are displayed in debugfs filesystem. Enabling this option

666

Statistics are displayed in debugfs filesystem. Enabling this option

667

may incur significant overhead.

667

may incur significant overhead.

668

669

source "arch/x86/lguest/Kconfig"

669

source "arch/x86/lguest/Kconfig"

670

671

config PARAVIRT_TIME_ACCOUNTING

671

config PARAVIRT_TIME_ACCOUNTING

672

bool "Paravirtual steal time accounting"

672

bool "Paravirtual steal time accounting"

673

depends on PARAVIRT

673

depends on PARAVIRT

674

default n

674

default n

675

---help---

675

---help---

676

Select this option to enable fine granularity task steal time

676

Select this option to enable fine granularity task steal time

677

accounting. Time spent executing other tasks in parallel with

677

accounting. Time spent executing other tasks in parallel with

678

the current vCPU is discounted from the vCPU power. To account for

678

the current vCPU is discounted from the vCPU power. To account for

679

that, there can be a small performance impact.

679

that, there can be a small performance impact.

680

681

If in doubt, say N here.

681

If in doubt, say N here.

682

683

config PARAVIRT_CLOCK

683

config PARAVIRT_CLOCK

684

bool

684

bool

685

686

endif #HYPERVISOR_GUEST

686

endif #HYPERVISOR_GUEST

687

688

config NO_BOOTMEM

688

config NO_BOOTMEM

689

def_bool y

689

def_bool y

690

691

config MEMTEST

691

config MEMTEST

692

bool "Memtest"

692

bool "Memtest"

693

---help---

693

---help---

694

This option adds a kernel parameter 'memtest', which allows memtest

694

This option adds a kernel parameter 'memtest', which allows memtest

695

to be set.

695

to be set.

696

memtest=0, mean disabled; -- default

696

memtest=0, mean disabled; -- default

697

memtest=1, mean do 1 test pattern;

697

memtest=1, mean do 1 test pattern;

698

...

698

...

699

memtest=4, mean do 4 test patterns.

699

memtest=4, mean do 4 test patterns.

700

If you are unsure how to answer this question, answer N.

700

If you are unsure how to answer this question, answer N.

701

702

config X86_SUMMIT_NUMA

702

config X86_SUMMIT_NUMA

703

def_bool y

703

def_bool y

704

depends on X86_32 && NUMA && X86_32_NON_STANDARD

704

depends on X86_32 && NUMA && X86_32_NON_STANDARD

705

706

config X86_CYCLONE_TIMER

706

config X86_CYCLONE_TIMER

707

def_bool y

707

def_bool y

708

depends on X86_SUMMIT

708

depends on X86_SUMMIT

709

710

source "arch/x86/Kconfig.cpu"

710

source "arch/x86/Kconfig.cpu"

711

712

config HPET_TIMER

712

config HPET_TIMER

713

def_bool X86_64

713

def_bool X86_64

714

prompt "HPET Timer Support" if X86_32

714

prompt "HPET Timer Support" if X86_32

715

---help---

715

---help---

716

Use the IA-PC HPET (High Precision Event Timer) to manage

716

Use the IA-PC HPET (High Precision Event Timer) to manage

717

time in preference to the PIT and RTC, if a HPET is

717

time in preference to the PIT and RTC, if a HPET is

718

present.

718

present.

719

HPET is the next generation timer replacing legacy 8254s.

719

HPET is the next generation timer replacing legacy 8254s.

720

The HPET provides a stable time base on SMP

720

The HPET provides a stable time base on SMP

721

systems, unlike the TSC, but it is more expensive to access,

721

systems, unlike the TSC, but it is more expensive to access,

722

as it is off-chip. You can find the HPET spec at

722

as it is off-chip. You can find the HPET spec at

723

<http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.

723

<http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.

724

725

You can safely choose Y here. However, HPET will only be

725

You can safely choose Y here. However, HPET will only be

726

activated if the platform and the BIOS support this feature.

726

activated if the platform and the BIOS support this feature.

727

Otherwise the 8254 will be used for timing services.

727

Otherwise the 8254 will be used for timing services.

728

729

Choose N to continue using the legacy 8254 timer.

729

Choose N to continue using the legacy 8254 timer.

730

731

config HPET_EMULATE_RTC

731

config HPET_EMULATE_RTC

732

def_bool y

732

def_bool y

733

depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)

733

depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)

734

735

config APB_TIMER

735

config APB_TIMER

736

def_bool y if X86_INTEL_MID

736

def_bool y if X86_INTEL_MID

737

prompt "Intel MID APB Timer Support" if X86_INTEL_MID

737

prompt "Intel MID APB Timer Support" if X86_INTEL_MID

738

select DW_APB_TIMER

738

select DW_APB_TIMER

739

depends on X86_INTEL_MID && SFI

739

depends on X86_INTEL_MID && SFI

740

help

740

help

741

APB timer is the replacement for 8254, HPET on X86 MID platforms.

741

APB timer is the replacement for 8254, HPET on X86 MID platforms.

742

The APBT provides a stable time base on SMP

742

The APBT provides a stable time base on SMP

743

systems, unlike the TSC, but it is more expensive to access,

743

systems, unlike the TSC, but it is more expensive to access,

744

as it is off-chip. APB timers are always running regardless of CPU

744

as it is off-chip. APB timers are always running regardless of CPU

745

C states, they are used as per CPU clockevent device when possible.

745

C states, they are used as per CPU clockevent device when possible.

746

747

# Mark as expert because too many people got it wrong.

747

# Mark as expert because too many people got it wrong.

748

# The code disables itself when not needed.

748

# The code disables itself when not needed.

749

config DMI

749

config DMI

750

default y

750

default y

751

bool "Enable DMI scanning" if EXPERT

751

bool "Enable DMI scanning" if EXPERT

752

---help---

752

---help---

753

Enabled scanning of DMI to identify machine quirks. Say Y

753

Enabled scanning of DMI to identify machine quirks. Say Y

754

here unless you have verified that your setup is not

754

here unless you have verified that your setup is not

755

affected by entries in the DMI blacklist. Required by PNP

755

affected by entries in the DMI blacklist. Required by PNP

756

BIOS code.

756

BIOS code.

757

758

config GART_IOMMU

758

config GART_IOMMU

759

bool "GART IOMMU support" if EXPERT

759

bool "GART IOMMU support" if EXPERT

760

default y

760

default y

761

select SWIOTLB

761

select SWIOTLB

762

depends on X86_64 && PCI && AMD_NB

762

depends on X86_64 && PCI && AMD_NB

763

---help---

763

---help---

764

Support for full DMA access of devices with 32bit memory access only

764

Support for full DMA access of devices with 32bit memory access only

765

on systems with more than 3GB. This is usually needed for USB,

765

on systems with more than 3GB. This is usually needed for USB,

766

sound, many IDE/SATA chipsets and some other devices.

766

sound, many IDE/SATA chipsets and some other devices.

767

Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART

767

Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART

768

based hardware IOMMU and a software bounce buffer based IOMMU used

768

based hardware IOMMU and a software bounce buffer based IOMMU used

769

on Intel systems and as fallback.

769

on Intel systems and as fallback.

770

The code is only active when needed (enough memory and limited

770

The code is only active when needed (enough memory and limited

771

device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified

771

device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified

772

too.

772

too.

773

774

config CALGARY_IOMMU

774

config CALGARY_IOMMU

775

bool "IBM Calgary IOMMU support"

775

bool "IBM Calgary IOMMU support"

776

select SWIOTLB

776

select SWIOTLB

777

depends on X86_64 && PCI

777

depends on X86_64 && PCI

778

---help---

778

---help---

779

Support for hardware IOMMUs in IBM's xSeries x366 and x460

779

Support for hardware IOMMUs in IBM's xSeries x366 and x460

780

systems. Needed to run systems with more than 3GB of memory

780

systems. Needed to run systems with more than 3GB of memory

781

properly with 32-bit PCI devices that do not support DAC

781

properly with 32-bit PCI devices that do not support DAC

782

(Double Address Cycle). Calgary also supports bus level

782

(Double Address Cycle). Calgary also supports bus level

783

isolation, where all DMAs pass through the IOMMU. This

783

isolation, where all DMAs pass through the IOMMU. This

784

prevents them from going anywhere except their intended

784

prevents them from going anywhere except their intended

785

destination. This catches hard-to-find kernel bugs and

785

destination. This catches hard-to-find kernel bugs and

786

mis-behaving drivers and devices that do not use the DMA-API

786

mis-behaving drivers and devices that do not use the DMA-API

787

properly to set up their DMA buffers. The IOMMU can be

787

properly to set up their DMA buffers. The IOMMU can be

788

turned off at boot time with the iommu=off parameter.

788

turned off at boot time with the iommu=off parameter.

789

Normally the kernel will make the right choice by itself.

789

Normally the kernel will make the right choice by itself.

790

If unsure, say Y.

790

If unsure, say Y.

791

792

config CALGARY_IOMMU_ENABLED_BY_DEFAULT

792

config CALGARY_IOMMU_ENABLED_BY_DEFAULT

793

def_bool y

793

def_bool y

794

prompt "Should Calgary be enabled by default?"

794

prompt "Should Calgary be enabled by default?"

795

depends on CALGARY_IOMMU

795

depends on CALGARY_IOMMU

796

---help---

796

---help---

797

Should Calgary be enabled by default? if you choose 'y', Calgary

797

Should Calgary be enabled by default? if you choose 'y', Calgary

798

will be used (if it exists). If you choose 'n', Calgary will not be

798

will be used (if it exists). If you choose 'n', Calgary will not be

799

used even if it exists. If you choose 'n' and would like to use

799

used even if it exists. If you choose 'n' and would like to use

800

Calgary anyway, pass 'iommu=calgary' on the kernel command line.

800

Calgary anyway, pass 'iommu=calgary' on the kernel command line.

801

If unsure, say Y.

801

If unsure, say Y.

802

803

# need this always selected by IOMMU for the VIA workaround

803

# need this always selected by IOMMU for the VIA workaround

804

config SWIOTLB

804

config SWIOTLB

805

def_bool y if X86_64

805

def_bool y if X86_64

806

---help---

806

---help---

807

Support for software bounce buffers used on x86-64 systems

807

Support for software bounce buffers used on x86-64 systems

808

which don't have a hardware IOMMU. Using this PCI devices

808

which don't have a hardware IOMMU. Using this PCI devices

809

which can only access 32-bits of memory can be used on systems

809

which can only access 32-bits of memory can be used on systems

810

with more than 3 GB of memory.

810

with more than 3 GB of memory.

811

If unsure, say Y.

811

If unsure, say Y.

812

813

config IOMMU_HELPER

813

config IOMMU_HELPER

814

def_bool y

814

def_bool y

815

depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU

815

depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU

816

817

config MAXSMP

817

config MAXSMP

818

bool "Enable Maximum number of SMP Processors and NUMA Nodes"

818

bool "Enable Maximum number of SMP Processors and NUMA Nodes"

819

depends on X86_64 && SMP && DEBUG_KERNEL

819

depends on X86_64 && SMP && DEBUG_KERNEL

820

select CPUMASK_OFFSTACK

820

select CPUMASK_OFFSTACK

821

---help---

821

---help---

822

Enable maximum number of CPUS and NUMA Nodes for this architecture.

822

Enable maximum number of CPUS and NUMA Nodes for this architecture.

823

If unsure, say N.

823

If unsure, say N.

824

825

config NR_CPUS

825

config NR_CPUS

826

int "Maximum number of CPUs" if SMP && !MAXSMP

826

int "Maximum number of CPUs" if SMP && !MAXSMP

827

range 2 8 if SMP && X86_32 && !X86_BIGSMP

827

range 2 8 if SMP && X86_32 && !X86_BIGSMP

828

range 2 512 if SMP && !MAXSMP

828

range 2 512 if SMP && !MAXSMP

829

default "1" if !SMP

829

default "1" if !SMP

830

default "4096" if MAXSMP

830

default "4096" if MAXSMP

831

default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)

831

default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)

832

default "8" if SMP

832

default "8" if SMP

833

---help---

833

---help---

834

This allows you to specify the maximum number of CPUs which this

834

This allows you to specify the maximum number of CPUs which this

835

kernel will support. The maximum supported value is 512 and the

835

kernel will support. The maximum supported value is 512 and the

836

minimum value which makes sense is 2.

836

minimum value which makes sense is 2.

837

838

This is purely to save memory - each supported CPU adds

838

This is purely to save memory - each supported CPU adds

839

approximately eight kilobytes to the kernel image.

839

approximately eight kilobytes to the kernel image.

840

841

config SCHED_SMT

841

config SCHED_SMT

842

bool "SMT (Hyperthreading) scheduler support"

842

bool "SMT (Hyperthreading) scheduler support"

843

depends on X86_HT

843

depends on X86_HT

844

---help---

844

---help---

845

SMT scheduler support improves the CPU scheduler's decision making

845

SMT scheduler support improves the CPU scheduler's decision making

846

when dealing with Intel Pentium 4 chips with HyperThreading at a

846

when dealing with Intel Pentium 4 chips with HyperThreading at a

847

cost of slightly increased overhead in some places. If unsure say

847

cost of slightly increased overhead in some places. If unsure say

848

N here.

848

N here.

849

850

config SCHED_MC

850

config SCHED_MC

851

def_bool y

851

def_bool y

852

prompt "Multi-core scheduler support"

852

prompt "Multi-core scheduler support"

853

depends on X86_HT

853

depends on X86_HT

854

---help---

854

---help---

855

Multi-core scheduler support improves the CPU scheduler's decision

855

Multi-core scheduler support improves the CPU scheduler's decision

856

making when dealing with multi-core CPU chips at a cost of slightly

856

making when dealing with multi-core CPU chips at a cost of slightly

857

increased overhead in some places. If unsure say N here.

857

increased overhead in some places. If unsure say N here.

858

859

source "kernel/Kconfig.preempt"

859

source "kernel/Kconfig.preempt"

860

861

config X86_UP_APIC

861

config X86_UP_APIC

862

bool "Local APIC support on uniprocessors"

862

bool "Local APIC support on uniprocessors"

863

depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI

863

depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI

864

---help---

864

---help---

865

A local APIC (Advanced Programmable Interrupt Controller) is an

865

A local APIC (Advanced Programmable Interrupt Controller) is an

866

integrated interrupt controller in the CPU. If you have a single-CPU

866

integrated interrupt controller in the CPU. If you have a single-CPU

867

system which has a processor with a local APIC, you can say Y here to

867

system which has a processor with a local APIC, you can say Y here to

868

enable and use it. If you say Y here even though your machine doesn't

868

enable and use it. If you say Y here even though your machine doesn't

869

have a local APIC, then the kernel will still run with no slowdown at

869

have a local APIC, then the kernel will still run with no slowdown at

870

all. The local APIC supports CPU-generated self-interrupts (timer,

870

all. The local APIC supports CPU-generated self-interrupts (timer,

871

performance counters), and the NMI watchdog which detects hard

871

performance counters), and the NMI watchdog which detects hard

872

lockups.

872

lockups.

873

874

config X86_UP_IOAPIC

874

config X86_UP_IOAPIC

875

bool "IO-APIC support on uniprocessors"

875

bool "IO-APIC support on uniprocessors"

876

depends on X86_UP_APIC

876

depends on X86_UP_APIC

877

---help---

877

---help---

878

An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an

878

An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an

879

SMP-capable replacement for PC-style interrupt controllers. Most

879

SMP-capable replacement for PC-style interrupt controllers. Most

880

SMP systems and many recent uniprocessor systems have one.

880

SMP systems and many recent uniprocessor systems have one.

881

882

If you have a single-CPU system with an IO-APIC, you can say Y here

882

If you have a single-CPU system with an IO-APIC, you can say Y here

883

to use it. If you say Y here even though your machine doesn't have

883

to use it. If you say Y here even though your machine doesn't have

884

an IO-APIC, then the kernel will still run with no slowdown at all.

884

an IO-APIC, then the kernel will still run with no slowdown at all.

885

886

config X86_LOCAL_APIC

886

config X86_LOCAL_APIC

887

def_bool y

887

def_bool y

888

depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI

888

depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI

889

890

config X86_IO_APIC

890

config X86_IO_APIC

891

def_bool y

891

def_bool y

892

depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI

892

depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI

893

894

config X86_VISWS_APIC

894

config X86_VISWS_APIC

895

def_bool y

895

def_bool y

896

depends on X86_32 && X86_VISWS

896

depends on X86_32 && X86_VISWS

897

898

config X86_REROUTE_FOR_BROKEN_BOOT_IRQS

898

config X86_REROUTE_FOR_BROKEN_BOOT_IRQS

899

bool "Reroute for broken boot IRQs"

899

bool "Reroute for broken boot IRQs"

900

depends on X86_IO_APIC

900

depends on X86_IO_APIC

901

---help---

901

---help---

902

This option enables a workaround that fixes a source of

902

This option enables a workaround that fixes a source of

903

spurious interrupts. This is recommended when threaded

903

spurious interrupts. This is recommended when threaded

904

interrupt handling is used on systems where the generation of

904

interrupt handling is used on systems where the generation of

905

superfluous "boot interrupts" cannot be disabled.

905

superfluous "boot interrupts" cannot be disabled.

906

907

Some chipsets generate a legacy INTx "boot IRQ" when the IRQ

907

Some chipsets generate a legacy INTx "boot IRQ" when the IRQ

908

entry in the chipset's IO-APIC is masked (as, e.g. the RT

908

entry in the chipset's IO-APIC is masked (as, e.g. the RT

909

kernel does during interrupt handling). On chipsets where this

909

kernel does during interrupt handling). On chipsets where this

910

boot IRQ generation cannot be disabled, this workaround keeps

910

boot IRQ generation cannot be disabled, this workaround keeps

911

the original IRQ line masked so that only the equivalent "boot

911

the original IRQ line masked so that only the equivalent "boot

912

IRQ" is delivered to the CPUs. The workaround also tells the

912

IRQ" is delivered to the CPUs. The workaround also tells the

913

kernel to set up the IRQ handler on the boot IRQ line. In this

913

kernel to set up the IRQ handler on the boot IRQ line. In this

914

way only one interrupt is delivered to the kernel. Otherwise

914

way only one interrupt is delivered to the kernel. Otherwise

915

the spurious second interrupt may cause the kernel to bring

915

the spurious second interrupt may cause the kernel to bring

916

down (vital) interrupt lines.

916

down (vital) interrupt lines.

917

918

Only affects "broken" chipsets. Interrupt sharing may be

918

Only affects "broken" chipsets. Interrupt sharing may be

919

increased on these systems.

919

increased on these systems.

920

921

config X86_MCE

921

config X86_MCE

922

bool "Machine Check / overheating reporting"

922

bool "Machine Check / overheating reporting"

923

default y

923

default y

924

---help---

924

---help---

925

Machine Check support allows the processor to notify the

925

Machine Check support allows the processor to notify the

926

kernel if it detects a problem (e.g. overheating, data corruption).

926

kernel if it detects a problem (e.g. overheating, data corruption).

927

The action the kernel takes depends on the severity of the problem,

927

The action the kernel takes depends on the severity of the problem,

928

ranging from warning messages to halting the machine.

928

ranging from warning messages to halting the machine.

929

930

config X86_MCE_INTEL

930

config X86_MCE_INTEL

931

def_bool y

931

def_bool y

932

prompt "Intel MCE features"

932

prompt "Intel MCE features"

933

depends on X86_MCE && X86_LOCAL_APIC

933

depends on X86_MCE && X86_LOCAL_APIC

934

---help---

934

---help---

935

Additional support for intel specific MCE features such as

935

Additional support for intel specific MCE features such as

936

the thermal monitor.

936

the thermal monitor.

937

938

config X86_MCE_AMD

938

config X86_MCE_AMD

939

def_bool y

939

def_bool y

940

prompt "AMD MCE features"

940

prompt "AMD MCE features"

941

depends on X86_MCE && X86_LOCAL_APIC

941

depends on X86_MCE && X86_LOCAL_APIC

942

---help---

942

---help---

943

Additional support for AMD specific MCE features such as

943

Additional support for AMD specific MCE features such as

944

the DRAM Error Threshold.

944

the DRAM Error Threshold.

945

946

config X86_ANCIENT_MCE

946

config X86_ANCIENT_MCE

947

bool "Support for old Pentium 5 / WinChip machine checks"

947

bool "Support for old Pentium 5 / WinChip machine checks"

948

depends on X86_32 && X86_MCE

948

depends on X86_32 && X86_MCE

949

---help---

949

---help---

950

Include support for machine check handling on old Pentium 5 or WinChip

950

Include support for machine check handling on old Pentium 5 or WinChip

951

systems. These typically need to be enabled explicitely on the command

951

systems. These typically need to be enabled explicitely on the command

952

line.

952

line.

953

954

config X86_MCE_THRESHOLD

954

config X86_MCE_THRESHOLD

955

depends on X86_MCE_AMD || X86_MCE_INTEL

955

depends on X86_MCE_AMD || X86_MCE_INTEL

956

def_bool y

956

def_bool y

957

958

config X86_MCE_INJECT

958

config X86_MCE_INJECT

959

depends on X86_MCE

959

depends on X86_MCE

960

tristate "Machine check injector support"

960

tristate "Machine check injector support"

961

---help---

961

---help---

962

Provide support for injecting machine checks for testing purposes.

962

Provide support for injecting machine checks for testing purposes.

963

If you don't know what a machine check is and you don't do kernel

963

If you don't know what a machine check is and you don't do kernel

964

QA it is safe to say n.

964

QA it is safe to say n.

965

966

config X86_THERMAL_VECTOR

966

config X86_THERMAL_VECTOR

967

def_bool y

967

def_bool y

968

depends on X86_MCE_INTEL

968

depends on X86_MCE_INTEL

969

970

config VM86

970

config VM86

971

bool "Enable VM86 support" if EXPERT

971

bool "Enable VM86 support" if EXPERT

972

default y

972

default y

973

depends on X86_32

973

depends on X86_32

974

---help---

974

---help---

975

This option is required by programs like DOSEMU to run 16-bit legacy

975

This option is required by programs like DOSEMU to run 16-bit legacy

976

code on X86 processors. It also may be needed by software like

976

code on X86 processors. It also may be needed by software like

977

XFree86 to initialize some video cards via BIOS. Disabling this

977

XFree86 to initialize some video cards via BIOS. Disabling this

978

option saves about 6k.

978

option saves about 6k.

979

980

config TOSHIBA

980

config TOSHIBA

981

tristate "Toshiba Laptop support"

981

tristate "Toshiba Laptop support"

982

depends on X86_32

982

depends on X86_32

983

---help---

983

---help---

984

This adds a driver to safely access the System Management Mode of

984

This adds a driver to safely access the System Management Mode of

985

the CPU on Toshiba portables with a genuine Toshiba BIOS. It does

985

the CPU on Toshiba portables with a genuine Toshiba BIOS. It does

986

not work on models with a Phoenix BIOS. The System Management Mode

986

not work on models with a Phoenix BIOS. The System Management Mode

987

is used to set the BIOS and power saving options on Toshiba portables.

987

is used to set the BIOS and power saving options on Toshiba portables.

988

989

For information on utilities to make use of this driver see the

989

For information on utilities to make use of this driver see the

990

Toshiba Linux utilities web site at:

990

Toshiba Linux utilities web site at:

991

<http://www.buzzard.org.uk/toshiba/>.

991

<http://www.buzzard.org.uk/toshiba/>.

992

993

Say Y if you intend to run this kernel on a Toshiba portable.

993

Say Y if you intend to run this kernel on a Toshiba portable.

994

Say N otherwise.

994

Say N otherwise.

995

996

config I8K

996

config I8K

997

tristate "Dell laptop support"

997

tristate "Dell laptop support"

998

select HWMON

998

select HWMON

999

---help---

999

---help---

1000

This adds a driver to safely access the System Management Mode

1000

This adds a driver to safely access the System Management Mode

1001

of the CPU on the Dell Inspiron 8000. The System Management Mode

1001

of the CPU on the Dell Inspiron 8000. The System Management Mode

1002

is used to read cpu temperature and cooling fan status and to

1002

is used to read cpu temperature and cooling fan status and to

1003

control the fans on the I8K portables.

1003

control the fans on the I8K portables.

1004

1005

This driver has been tested only on the Inspiron 8000 but it may

1005

This driver has been tested only on the Inspiron 8000 but it may

1006

also work with other Dell laptops. You can force loading on other

1006

also work with other Dell laptops. You can force loading on other

1007

models by passing the parameter `force=1' to the module. Use at

1007

models by passing the parameter `force=1' to the module. Use at

1008

your own risk.

1008

your own risk.

1009

1010

For information on utilities to make use of this driver see the

1010

For information on utilities to make use of this driver see the

1011

I8K Linux utilities web site at:

1011

I8K Linux utilities web site at:

1012

<http://people.debian.org/~dz/i8k/>

1012

<http://people.debian.org/~dz/i8k/>

1013

1014

Say Y if you intend to run this kernel on a Dell Inspiron 8000.

1014

Say Y if you intend to run this kernel on a Dell Inspiron 8000.

1015

Say N otherwise.

1015

Say N otherwise.

1016

1017

config X86_REBOOTFIXUPS

1017

config X86_REBOOTFIXUPS

1018

bool "Enable X86 board specific fixups for reboot"

1018

bool "Enable X86 board specific fixups for reboot"

1019

depends on X86_32

1019

depends on X86_32

1020

---help---

1020

---help---

1021

This enables chipset and/or board specific fixups to be done

1021

This enables chipset and/or board specific fixups to be done

1022

in order to get reboot to work correctly. This is only needed on

1022

in order to get reboot to work correctly. This is only needed on

1023

some combinations of hardware and BIOS. The symptom, for which

1023

some combinations of hardware and BIOS. The symptom, for which

1024

this config is intended, is when reboot ends with a stalled/hung

1024

this config is intended, is when reboot ends with a stalled/hung

1025

system.

1025

system.

1026

1027

Currently, the only fixup is for the Geode machines using

1027

Currently, the only fixup is for the Geode machines using

1028

CS5530A and CS5536 chipsets and the RDC R-321x SoC.

1028

CS5530A and CS5536 chipsets and the RDC R-321x SoC.

1029

1030

Say Y if you want to enable the fixup. Currently, it's safe to

1030

Say Y if you want to enable the fixup. Currently, it's safe to

1031

enable this option even if you don't need it.

1031

enable this option even if you don't need it.

1032

Say N otherwise.

1032

Say N otherwise.

1033

1034

config MICROCODE

1034

config MICROCODE

1035

tristate "CPU microcode loading support"

1035

tristate "CPU microcode loading support"

1036

depends on CPU_SUP_AMD || CPU_SUP_INTEL

1036

select FW_LOADER

1037

select FW_LOADER

1037

---help---

1038

---help---

1038

1039

If you say Y here, you will be able to update the microcode on

1040

If you say Y here, you will be able to update the microcode on

1040

certain Intel and AMD processors. The Intel support is for the

1041

certain Intel and AMD processors. The Intel support is for the

1041

IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,

1042

IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,

1042

Xeon etc. The AMD support is for families 0x10 and later. You will

1043

Xeon etc. The AMD support is for families 0x10 and later. You will

1043

obviously need the actual microcode binary data itself which is not

1044

obviously need the actual microcode binary data itself which is not

1044

shipped with the Linux kernel.

1045

shipped with the Linux kernel.

1045

1046

This option selects the general module only, you need to select

1047

This option selects the general module only, you need to select

1047

at least one vendor specific module as well.

1048

at least one vendor specific module as well.

1048

1049

To compile this driver as a module, choose M here: the module

1050

To compile this driver as a module, choose M here: the module

1050

will be called microcode.

1051

will be called microcode.

1051

1052

config MICROCODE_INTEL

1053

config MICROCODE_INTEL

1053

bool "Intel microcode loading support"

1054

bool "Intel microcode loading support"

1054

depends on MICROCODE

1055

depends on MICROCODE

1055

default MICROCODE

1056

default MICROCODE

1056

select FW_LOADER

1057

select FW_LOADER

1057

---help---

1058

---help---

1058

This options enables microcode patch loading support for Intel

1059

This options enables microcode patch loading support for Intel

1059

processors.

1060

processors.

1060

1061

For latest news and information on obtaining all the required

1062

For latest news and information on obtaining all the required

1062

Intel ingredients for this driver, check:

1063

Intel ingredients for this driver, check:

1063

<http://www.urbanmyth.org/microcode/>.

1064

<http://www.urbanmyth.org/microcode/>.

1064

1065

config MICROCODE_AMD

1066

config MICROCODE_AMD

1066

bool "AMD microcode loading support"

1067

bool "AMD microcode loading support"

1067

depends on MICROCODE

1068

depends on MICROCODE

1068

select FW_LOADER

1069

select FW_LOADER

1069

---help---

1070

---help---

1070

If you select this option, microcode patch loading support for AMD

1071

If you select this option, microcode patch loading support for AMD

1071

processors will be enabled.

1072

processors will be enabled.

1072

1073

config MICROCODE_OLD_INTERFACE

1074

config MICROCODE_OLD_INTERFACE

1074

def_bool y

1075

def_bool y

1075

depends on MICROCODE

1076

depends on MICROCODE

1076

1077

config MICROCODE_INTEL_LIB

1078

config MICROCODE_INTEL_LIB

1078

def_bool y

1079

def_bool y

1079

depends on MICROCODE_INTEL

1080

depends on MICROCODE_INTEL

1080

1081

config MICROCODE_INTEL_EARLY

1082

config MICROCODE_INTEL_EARLY

1082

def_bool n

1083

def_bool n

1083

1084

config MICROCODE_AMD_EARLY

1085

config MICROCODE_AMD_EARLY

1085

def_bool n

1086

def_bool n

1086

1087

config MICROCODE_EARLY

1088

config MICROCODE_EARLY

1088

bool "Early load microcode"

1089

bool "Early load microcode"

1089

depends on MICROCODE=y && BLK_DEV_INITRD

1090

depends on MICROCODE=y && BLK_DEV_INITRD

1090

select MICROCODE_INTEL_EARLY if MICROCODE_INTEL

1091

select MICROCODE_INTEL_EARLY if MICROCODE_INTEL

1091

select MICROCODE_AMD_EARLY if MICROCODE_AMD

1092

select MICROCODE_AMD_EARLY if MICROCODE_AMD

1092

default y

1093

default y

1093

help

1094

help

1094

This option provides functionality to read additional microcode data

1095

This option provides functionality to read additional microcode data

1095

at the beginning of initrd image. The data tells kernel to load

1096

at the beginning of initrd image. The data tells kernel to load

1096

microcode to CPU's as early as possible. No functional change if no

1097

microcode to CPU's as early as possible. No functional change if no

1097

microcode data is glued to the initrd, therefore it's safe to say Y.

1098

microcode data is glued to the initrd, therefore it's safe to say Y.

1098

1099

config X86_MSR

1100

config X86_MSR

1100

tristate "/dev/cpu/*/msr - Model-specific register support"

1101

tristate "/dev/cpu/*/msr - Model-specific register support"

1101

---help---

1102

---help---

1102

This device gives privileged processes access to the x86

1103

This device gives privileged processes access to the x86

1103

Model-Specific Registers (MSRs). It is a character device with

1104

Model-Specific Registers (MSRs). It is a character device with

1104

major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.

1105

major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.

1105

MSR accesses are directed to a specific CPU on multi-processor

1106

MSR accesses are directed to a specific CPU on multi-processor

1106

systems.

1107

systems.

1107

1108

config X86_CPUID

1109

config X86_CPUID

1109

tristate "/dev/cpu/*/cpuid - CPU information support"

1110

tristate "/dev/cpu/*/cpuid - CPU information support"

1110

---help---

1111

---help---

1111

This device gives processes access to the x86 CPUID instruction to

1112

This device gives processes access to the x86 CPUID instruction to

1112

be executed on a specific processor. It is a character device

1113

be executed on a specific processor. It is a character device

1113

with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to

1114

with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to

1114

/dev/cpu/31/cpuid.

1115

/dev/cpu/31/cpuid.

1115

1116

choice

1117

choice

1117

prompt "High Memory Support"

1118

prompt "High Memory Support"

1118

default HIGHMEM64G if X86_NUMAQ

1119

default HIGHMEM64G if X86_NUMAQ

1119

default HIGHMEM4G

1120

default HIGHMEM4G

1120

depends on X86_32

1121

depends on X86_32

1121

1122

config NOHIGHMEM

1123

config NOHIGHMEM

1123

bool "off"

1124

bool "off"

1124

depends on !X86_NUMAQ

1125

depends on !X86_NUMAQ

1125

---help---

1126

---help---

1126

Linux can use up to 64 Gigabytes of physical memory on x86 systems.

1127

Linux can use up to 64 Gigabytes of physical memory on x86 systems.

1127

However, the address space of 32-bit x86 processors is only 4

1128

However, the address space of 32-bit x86 processors is only 4

1128

Gigabytes large. That means that, if you have a large amount of

1129

Gigabytes large. That means that, if you have a large amount of

1129

physical memory, not all of it can be "permanently mapped" by the

1130

physical memory, not all of it can be "permanently mapped" by the

1130

kernel. The physical memory that's not permanently mapped is called

1131

kernel. The physical memory that's not permanently mapped is called

1131

"high memory".

1132

"high memory".

1132

1133

If you are compiling a kernel which will never run on a machine with

1134

If you are compiling a kernel which will never run on a machine with

1134

more than 1 Gigabyte total physical RAM, answer "off" here (default

1135

more than 1 Gigabyte total physical RAM, answer "off" here (default

1135

choice and suitable for most users). This will result in a "3GB/1GB"

1136

choice and suitable for most users). This will result in a "3GB/1GB"

1136

split: 3GB are mapped so that each process sees a 3GB virtual memory

1137

split: 3GB are mapped so that each process sees a 3GB virtual memory

1137

space and the remaining part of the 4GB virtual memory space is used

1138

space and the remaining part of the 4GB virtual memory space is used

1138

by the kernel to permanently map as much physical memory as

1139

by the kernel to permanently map as much physical memory as

1139

possible.

1140

possible.

1140

1141

If the machine has between 1 and 4 Gigabytes physical RAM, then

1142

If the machine has between 1 and 4 Gigabytes physical RAM, then

1142

answer "4GB" here.

1143

answer "4GB" here.

1143

1144

If more than 4 Gigabytes is used then answer "64GB" here. This

1145

If more than 4 Gigabytes is used then answer "64GB" here. This

1145

selection turns Intel PAE (Physical Address Extension) mode on.

1146

selection turns Intel PAE (Physical Address Extension) mode on.

1146

PAE implements 3-level paging on IA32 processors. PAE is fully

1147

PAE implements 3-level paging on IA32 processors. PAE is fully

1147

supported by Linux, PAE mode is implemented on all recent Intel

1148

supported by Linux, PAE mode is implemented on all recent Intel

1148

processors (Pentium Pro and better). NOTE: If you say "64GB" here,

1149

processors (Pentium Pro and better). NOTE: If you say "64GB" here,

1149

then the kernel will not boot on CPUs that don't support PAE!

1150

then the kernel will not boot on CPUs that don't support PAE!

1150

1151

The actual amount of total physical memory will either be

1152

The actual amount of total physical memory will either be

1152

auto detected or can be forced by using a kernel command line option

1153

auto detected or can be forced by using a kernel command line option

1153

such as "mem=256M". (Try "man bootparam" or see the documentation of

1154

such as "mem=256M". (Try "man bootparam" or see the documentation of

1154

your boot loader (lilo or loadlin) about how to pass options to the

1155

your boot loader (lilo or loadlin) about how to pass options to the

1155

kernel at boot time.)

1156

kernel at boot time.)

1156

1157

If unsure, say "off".

1158

If unsure, say "off".

1158

1159

config HIGHMEM4G

1160

config HIGHMEM4G

1160

bool "4GB"

1161

bool "4GB"

1161

depends on !X86_NUMAQ

1162

depends on !X86_NUMAQ

1162

---help---

1163

---help---

1163

Select this if you have a 32-bit processor and between 1 and 4

1164

Select this if you have a 32-bit processor and between 1 and 4

1164

gigabytes of physical RAM.

1165

gigabytes of physical RAM.

1165

1166

config HIGHMEM64G

1167

config HIGHMEM64G

1167

bool "64GB"

1168

bool "64GB"

1168

depends on !M486

1169

depends on !M486

1169

select X86_PAE

1170

select X86_PAE

1170

---help---

1171

---help---

1171

Select this if you have a 32-bit processor and more than 4

1172

Select this if you have a 32-bit processor and more than 4

1172

gigabytes of physical RAM.

1173

gigabytes of physical RAM.

1173

1174

endchoice

1175

endchoice

1175

1176

choice

1177

choice

1177

prompt "Memory split" if EXPERT

1178

prompt "Memory split" if EXPERT

1178

default VMSPLIT_3G

1179

default VMSPLIT_3G

1179

depends on X86_32

1180

depends on X86_32

1180

---help---

1181

---help---

1181

Select the desired split between kernel and user memory.

1182

Select the desired split between kernel and user memory.

1182

1183

If the address range available to the kernel is less than the

1184

If the address range available to the kernel is less than the

1184

physical memory installed, the remaining memory will be available

1185

physical memory installed, the remaining memory will be available

1185

as "high memory". Accessing high memory is a little more costly

1186

as "high memory". Accessing high memory is a little more costly

1186

than low memory, as it needs to be mapped into the kernel first.

1187

than low memory, as it needs to be mapped into the kernel first.

1187

Note that increasing the kernel address space limits the range

1188

Note that increasing the kernel address space limits the range

1188

available to user programs, making the address space there

1189

available to user programs, making the address space there

1189

tighter. Selecting anything other than the default 3G/1G split

1190

tighter. Selecting anything other than the default 3G/1G split

1190

will also likely make your kernel incompatible with binary-only

1191

will also likely make your kernel incompatible with binary-only

1191

kernel modules.

1192

kernel modules.

1192

1193

If you are not absolutely sure what you are doing, leave this

1194

If you are not absolutely sure what you are doing, leave this

1194

option alone!

1195

option alone!

1195

1196

config VMSPLIT_3G

1197

config VMSPLIT_3G

1197

bool "3G/1G user/kernel split"

1198

bool "3G/1G user/kernel split"

1198

config VMSPLIT_3G_OPT

1199

config VMSPLIT_3G_OPT

1199

depends on !X86_PAE

1200

depends on !X86_PAE

1200

bool "3G/1G user/kernel split (for full 1G low memory)"

1201

bool "3G/1G user/kernel split (for full 1G low memory)"

1201

config VMSPLIT_2G

1202

config VMSPLIT_2G

1202

bool "2G/2G user/kernel split"

1203

bool "2G/2G user/kernel split"

1203

config VMSPLIT_2G_OPT

1204

config VMSPLIT_2G_OPT

1204

depends on !X86_PAE

1205

depends on !X86_PAE

1205

bool "2G/2G user/kernel split (for full 2G low memory)"

1206

bool "2G/2G user/kernel split (for full 2G low memory)"

1206

config VMSPLIT_1G

1207

config VMSPLIT_1G

1207

bool "1G/3G user/kernel split"

1208

bool "1G/3G user/kernel split"

1208

endchoice

1209

endchoice

1209

1210

config PAGE_OFFSET

1211

config PAGE_OFFSET

1211

hex

1212

hex

1212

default 0xB0000000 if VMSPLIT_3G_OPT

1213

default 0xB0000000 if VMSPLIT_3G_OPT

1213

default 0x80000000 if VMSPLIT_2G

1214

default 0x80000000 if VMSPLIT_2G

1214

default 0x78000000 if VMSPLIT_2G_OPT

1215

default 0x78000000 if VMSPLIT_2G_OPT

1215

default 0x40000000 if VMSPLIT_1G

1216

default 0x40000000 if VMSPLIT_1G

1216

default 0xC0000000

1217

default 0xC0000000

1217

depends on X86_32

1218

depends on X86_32

1218

1219

config HIGHMEM

1220

config HIGHMEM

1220

def_bool y

1221

def_bool y

1221

depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)

1222

depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)

1222

1223

config X86_PAE

1224

config X86_PAE

1224

bool "PAE (Physical Address Extension) Support"

1225

bool "PAE (Physical Address Extension) Support"

1225

depends on X86_32 && !HIGHMEM4G

1226

depends on X86_32 && !HIGHMEM4G

1226

---help---

1227

---help---

1227

PAE is required for NX support, and furthermore enables

1228

PAE is required for NX support, and furthermore enables

1228

larger swapspace support for non-overcommit purposes. It

1229

larger swapspace support for non-overcommit purposes. It

1229

has the cost of more pagetable lookup overhead, and also

1230

has the cost of more pagetable lookup overhead, and also

1230

consumes more pagetable space per process.

1231

consumes more pagetable space per process.

1231

1232

config ARCH_PHYS_ADDR_T_64BIT

1233

config ARCH_PHYS_ADDR_T_64BIT

1233

def_bool y

1234

def_bool y

1234

depends on X86_64 || X86_PAE

1235

depends on X86_64 || X86_PAE

1235

1236

config ARCH_DMA_ADDR_T_64BIT

1237

config ARCH_DMA_ADDR_T_64BIT

1237

def_bool y

1238

def_bool y

1238

depends on X86_64 || HIGHMEM64G

1239

depends on X86_64 || HIGHMEM64G

1239

1240

config DIRECT_GBPAGES

1241

config DIRECT_GBPAGES

1241

bool "Enable 1GB pages for kernel pagetables" if EXPERT

1242

bool "Enable 1GB pages for kernel pagetables" if EXPERT

1242

default y

1243

default y

1243

depends on X86_64

1244

depends on X86_64

1244

---help---

1245

---help---

1245

Allow the kernel linear mapping to use 1GB pages on CPUs that

1246

Allow the kernel linear mapping to use 1GB pages on CPUs that

1246

support it. This can improve the kernel's performance a tiny bit by

1247

support it. This can improve the kernel's performance a tiny bit by

1247

reducing TLB pressure. If in doubt, say "Y".

1248

reducing TLB pressure. If in doubt, say "Y".

1248

1249

# Common NUMA Features

1250

# Common NUMA Features

1250

config NUMA

1251

config NUMA

1251

bool "Numa Memory Allocation and Scheduler Support"

1252

bool "Numa Memory Allocation and Scheduler Support"

1252

depends on SMP

1253

depends on SMP

1253

depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI))

1254

depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI))

1254

default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)

1255

default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)

1255

---help---

1256

---help---

1256

Enable NUMA (Non Uniform Memory Access) support.

1257

Enable NUMA (Non Uniform Memory Access) support.

1257

1258

The kernel will try to allocate memory used by a CPU on the

1259

The kernel will try to allocate memory used by a CPU on the

1259

local memory controller of the CPU and add some more

1260

local memory controller of the CPU and add some more

1260

NUMA awareness to the kernel.

1261

NUMA awareness to the kernel.

1261

1262

For 64-bit this is recommended if the system is Intel Core i7

1263

For 64-bit this is recommended if the system is Intel Core i7

1263

(or later), AMD Opteron, or EM64T NUMA.

1264

(or later), AMD Opteron, or EM64T NUMA.

1264

1265

For 32-bit this is only needed on (rare) 32-bit-only platforms

1266

For 32-bit this is only needed on (rare) 32-bit-only platforms

1266

that support NUMA topologies, such as NUMAQ / Summit, or if you

1267

that support NUMA topologies, such as NUMAQ / Summit, or if you

1267

boot a 32-bit kernel on a 64-bit NUMA platform.

1268

boot a 32-bit kernel on a 64-bit NUMA platform.

1268

1269

Otherwise, you should say N.

1270

Otherwise, you should say N.

1270

1271

comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"

1272

comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"

1272

depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)

1273

depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)

1273

1274

config AMD_NUMA

1275

config AMD_NUMA

1275

def_bool y

1276

def_bool y

1276

prompt "Old style AMD Opteron NUMA detection"

1277

prompt "Old style AMD Opteron NUMA detection"

1277

depends on X86_64 && NUMA && PCI

1278

depends on X86_64 && NUMA && PCI

1278

---help---

1279

---help---

1279

Enable AMD NUMA node topology detection. You should say Y here if

1280

Enable AMD NUMA node topology detection. You should say Y here if

1280

you have a multi processor AMD system. This uses an old method to

1281

you have a multi processor AMD system. This uses an old method to

1281

read the NUMA configuration directly from the builtin Northbridge

1282

read the NUMA configuration directly from the builtin Northbridge

1282

of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,

1283

of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,

1283

which also takes priority if both are compiled in.

1284

which also takes priority if both are compiled in.

1284

1285

config X86_64_ACPI_NUMA

1286

config X86_64_ACPI_NUMA

1286

def_bool y

1287

def_bool y

1287

prompt "ACPI NUMA detection"

1288

prompt "ACPI NUMA detection"

1288

depends on X86_64 && NUMA && ACPI && PCI

1289

depends on X86_64 && NUMA && ACPI && PCI

1289

select ACPI_NUMA

1290

select ACPI_NUMA

1290

---help---

1291

---help---

1291

Enable ACPI SRAT based node topology detection.

1292

Enable ACPI SRAT based node topology detection.

1292

1293

# Some NUMA nodes have memory ranges that span

1294

# Some NUMA nodes have memory ranges that span

1294

# other nodes. Even though a pfn is valid and

1295

# other nodes. Even though a pfn is valid and

1295

# between a node's start and end pfns, it may not

1296

# between a node's start and end pfns, it may not

1296

# reside on that node. See memmap_init_zone()

1297

# reside on that node. See memmap_init_zone()

1297

# for details.

1298

# for details.

1298

config NODES_SPAN_OTHER_NODES

1299

config NODES_SPAN_OTHER_NODES

1299

def_bool y

1300

def_bool y

1300

depends on X86_64_ACPI_NUMA

1301

depends on X86_64_ACPI_NUMA

1301

1302

config NUMA_EMU

1303

config NUMA_EMU

1303

bool "NUMA emulation"

1304

bool "NUMA emulation"

1304

depends on NUMA

1305

depends on NUMA

1305

---help---

1306

---help---

1306

Enable NUMA emulation. A flat machine will be split

1307

Enable NUMA emulation. A flat machine will be split

1307

into virtual nodes when booted with "numa=fake=N", where N is the

1308

into virtual nodes when booted with "numa=fake=N", where N is the

1308

number of nodes. This is only useful for debugging.

1309

number of nodes. This is only useful for debugging.

1309

1310

config NODES_SHIFT

1311

config NODES_SHIFT

1311

int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP

1312

int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP

1312

range 1 10

1313

range 1 10

1313

default "10" if MAXSMP

1314

default "10" if MAXSMP

1314

default "6" if X86_64

1315

default "6" if X86_64

1315

default "4" if X86_NUMAQ

1316

default "4" if X86_NUMAQ

1316

default "3"

1317

default "3"

1317

depends on NEED_MULTIPLE_NODES

1318

depends on NEED_MULTIPLE_NODES

1318

---help---

1319

---help---

1319

Specify the maximum number of NUMA Nodes available on the target

1320

Specify the maximum number of NUMA Nodes available on the target

1320

system. Increases memory reserved to accommodate various tables.

1321

system. Increases memory reserved to accommodate various tables.

1321

1322

config ARCH_HAVE_MEMORY_PRESENT

1323

config ARCH_HAVE_MEMORY_PRESENT

1323

def_bool y

1324

def_bool y

1324

depends on X86_32 && DISCONTIGMEM

1325

depends on X86_32 && DISCONTIGMEM

1325

1326

config NEED_NODE_MEMMAP_SIZE

1327

config NEED_NODE_MEMMAP_SIZE

1327

def_bool y

1328

def_bool y

1328

depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)

1329

depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)

1329

1330

config ARCH_FLATMEM_ENABLE

1331

config ARCH_FLATMEM_ENABLE

1331

def_bool y

1332

def_bool y

1332

depends on X86_32 && !NUMA

1333

depends on X86_32 && !NUMA

1333

1334

config ARCH_DISCONTIGMEM_ENABLE

1335

config ARCH_DISCONTIGMEM_ENABLE

1335

def_bool y

1336

def_bool y

1336

depends on NUMA && X86_32

1337

depends on NUMA && X86_32

1337

1338

config ARCH_DISCONTIGMEM_DEFAULT

1339

config ARCH_DISCONTIGMEM_DEFAULT

1339

def_bool y

1340

def_bool y

1340

depends on NUMA && X86_32

1341

depends on NUMA && X86_32

1341

1342

config ARCH_SPARSEMEM_ENABLE

1343

config ARCH_SPARSEMEM_ENABLE

1343

def_bool y

1344

def_bool y

1344

depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD

1345

depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD

1345

select SPARSEMEM_STATIC if X86_32

1346

select SPARSEMEM_STATIC if X86_32

1346

select SPARSEMEM_VMEMMAP_ENABLE if X86_64

1347

select SPARSEMEM_VMEMMAP_ENABLE if X86_64

1347

1348

config ARCH_SPARSEMEM_DEFAULT

1349

config ARCH_SPARSEMEM_DEFAULT

1349

def_bool y

1350

def_bool y

1350

depends on X86_64

1351

depends on X86_64

1351

1352

config ARCH_SELECT_MEMORY_MODEL

1353

config ARCH_SELECT_MEMORY_MODEL

1353

def_bool y

1354

def_bool y

1354

depends on ARCH_SPARSEMEM_ENABLE

1355

depends on ARCH_SPARSEMEM_ENABLE

1355

1356

config ARCH_MEMORY_PROBE

1357

config ARCH_MEMORY_PROBE

1357

bool "Enable sysfs memory/probe interface"

1358

bool "Enable sysfs memory/probe interface"

1358

depends on X86_64 && MEMORY_HOTPLUG

1359

depends on X86_64 && MEMORY_HOTPLUG

1359

help

1360

help

1360

This option enables a sysfs memory/probe interface for testing.

1361

This option enables a sysfs memory/probe interface for testing.

1361

See Documentation/memory-hotplug.txt for more information.

1362

See Documentation/memory-hotplug.txt for more information.

1362

If you are unsure how to answer this question, answer N.

1363

If you are unsure how to answer this question, answer N.

1363

1364

config ARCH_PROC_KCORE_TEXT

1365

config ARCH_PROC_KCORE_TEXT

1365

def_bool y

1366

def_bool y

1366

depends on X86_64 && PROC_KCORE

1367

depends on X86_64 && PROC_KCORE

1367

1368

config ILLEGAL_POINTER_VALUE

1369

config ILLEGAL_POINTER_VALUE

1369

hex

1370

hex

1370

default 0 if X86_32

1371

default 0 if X86_32

1371

default 0xdead000000000000 if X86_64

1372

default 0xdead000000000000 if X86_64

1372

1373

source "mm/Kconfig"

1374

source "mm/Kconfig"

1374

1375

config HIGHPTE

1376

config HIGHPTE

1376

bool "Allocate 3rd-level pagetables from highmem"

1377

bool "Allocate 3rd-level pagetables from highmem"

1377

depends on HIGHMEM

1378

depends on HIGHMEM

1378

---help---

1379

---help---

1379

The VM uses one page table entry for each page of physical memory.

1380

The VM uses one page table entry for each page of physical memory.

1380

For systems with a lot of RAM, this can be wasteful of precious

1381

For systems with a lot of RAM, this can be wasteful of precious

1381

low memory. Setting this option will put user-space page table

1382

low memory. Setting this option will put user-space page table

1382

entries in high memory.

1383

entries in high memory.

1383

1384

config X86_CHECK_BIOS_CORRUPTION

1385

config X86_CHECK_BIOS_CORRUPTION

1385

bool "Check for low memory corruption"

1386

bool "Check for low memory corruption"

1386

---help---

1387

---help---

1387

Periodically check for memory corruption in low memory, which

1388

Periodically check for memory corruption in low memory, which

1388

is suspected to be caused by BIOS. Even when enabled in the

1389

is suspected to be caused by BIOS. Even when enabled in the

1389

configuration, it is disabled at runtime. Enable it by

1390

configuration, it is disabled at runtime. Enable it by

1390

setting "memory_corruption_check=1" on the kernel command

1391

setting "memory_corruption_check=1" on the kernel command

1391

line. By default it scans the low 64k of memory every 60

1392

line. By default it scans the low 64k of memory every 60

1392

seconds; see the memory_corruption_check_size and

1393

seconds; see the memory_corruption_check_size and

1393

memory_corruption_check_period parameters in

1394

memory_corruption_check_period parameters in

1394

Documentation/kernel-parameters.txt to adjust this.

1395

Documentation/kernel-parameters.txt to adjust this.

1395

1396

When enabled with the default parameters, this option has

1397

When enabled with the default parameters, this option has

1397

almost no overhead, as it reserves a relatively small amount

1398

almost no overhead, as it reserves a relatively small amount

1398

of memory and scans it infrequently. It both detects corruption

1399

of memory and scans it infrequently. It both detects corruption

1399

and prevents it from affecting the running system.

1400

and prevents it from affecting the running system.

1400

1401

It is, however, intended as a diagnostic tool; if repeatable

1402

It is, however, intended as a diagnostic tool; if repeatable

1402

BIOS-originated corruption always affects the same memory,

1403

BIOS-originated corruption always affects the same memory,

1403

you can use memmap= to prevent the kernel from using that

1404

you can use memmap= to prevent the kernel from using that

1404

memory.

1405

memory.

1405

1406

config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK

1407

config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK

1407

bool "Set the default setting of memory_corruption_check"

1408

bool "Set the default setting of memory_corruption_check"

1408

depends on X86_CHECK_BIOS_CORRUPTION

1409

depends on X86_CHECK_BIOS_CORRUPTION

1409

default y

1410

default y

1410

---help---

1411

---help---

1411

Set whether the default state of memory_corruption_check is

1412

Set whether the default state of memory_corruption_check is

1412

on or off.

1413

on or off.

1413

1414

config X86_RESERVE_LOW

1415

config X86_RESERVE_LOW

1415

int "Amount of low memory, in kilobytes, to reserve for the BIOS"

1416

int "Amount of low memory, in kilobytes, to reserve for the BIOS"

1416

default 64

1417

default 64

1417

range 4 640

1418

range 4 640

1418

---help---

1419

---help---

1419

Specify the amount of low memory to reserve for the BIOS.

1420

Specify the amount of low memory to reserve for the BIOS.

1420

1421

The first page contains BIOS data structures that the kernel

1422

The first page contains BIOS data structures that the kernel

1422

must not use, so that page must always be reserved.

1423

must not use, so that page must always be reserved.

1423

1424

By default we reserve the first 64K of physical RAM, as a

1425

By default we reserve the first 64K of physical RAM, as a

1425

number of BIOSes are known to corrupt that memory range

1426

number of BIOSes are known to corrupt that memory range

1426

during events such as suspend/resume or monitor cable

1427

during events such as suspend/resume or monitor cable

1427

insertion, so it must not be used by the kernel.

1428

insertion, so it must not be used by the kernel.

1428

1429

You can set this to 4 if you are absolutely sure that you

1430

You can set this to 4 if you are absolutely sure that you

1430

trust the BIOS to get all its memory reservations and usages

1431

trust the BIOS to get all its memory reservations and usages

1431

right. If you know your BIOS have problems beyond the

1432

right. If you know your BIOS have problems beyond the

1432

default 64K area, you can set this to 640 to avoid using the

1433

default 64K area, you can set this to 640 to avoid using the

1433

entire low memory range.

1434

entire low memory range.

1434

1435

If you have doubts about the BIOS (e.g. suspend/resume does

1436

If you have doubts about the BIOS (e.g. suspend/resume does

1436

not work or there's kernel crashes after certain hardware

1437

not work or there's kernel crashes after certain hardware

1437

hotplug events) then you might want to enable

1438

hotplug events) then you might want to enable

1438

X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check

1439

X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check

1439

typical corruption patterns.

1440

typical corruption patterns.

1440

1441

Leave this to the default value of 64 if you are unsure.

1442

Leave this to the default value of 64 if you are unsure.

1442

1443

config MATH_EMULATION

1444

config MATH_EMULATION

1444

bool

1445

bool

1445

prompt "Math emulation" if X86_32

1446

prompt "Math emulation" if X86_32

1446

---help---

1447

---help---

1447

Linux can emulate a math coprocessor (used for floating point

1448

Linux can emulate a math coprocessor (used for floating point

1448

operations) if you don't have one. 486DX and Pentium processors have

1449

operations) if you don't have one. 486DX and Pentium processors have

1449

a math coprocessor built in, 486SX and 386 do not, unless you added

1450

a math coprocessor built in, 486SX and 386 do not, unless you added

1450

a 487DX or 387, respectively. (The messages during boot time can

1451

a 487DX or 387, respectively. (The messages during boot time can

1451

give you some hints here ["man dmesg"].) Everyone needs either a

1452

give you some hints here ["man dmesg"].) Everyone needs either a

1452

coprocessor or this emulation.

1453

coprocessor or this emulation.

1453

1454

If you don't have a math coprocessor, you need to say Y here; if you

1455

If you don't have a math coprocessor, you need to say Y here; if you

1455

say Y here even though you have a coprocessor, the coprocessor will

1456

say Y here even though you have a coprocessor, the coprocessor will

1456

be used nevertheless. (This behavior can be changed with the kernel

1457

be used nevertheless. (This behavior can be changed with the kernel

1457

command line option "no387", which comes handy if your coprocessor

1458

command line option "no387", which comes handy if your coprocessor

1458

is broken. Try "man bootparam" or see the documentation of your boot

1459

is broken. Try "man bootparam" or see the documentation of your boot

1459

loader (lilo or loadlin) about how to pass options to the kernel at

1460

loader (lilo or loadlin) about how to pass options to the kernel at

1460

boot time.) This means that it is a good idea to say Y here if you

1461

boot time.) This means that it is a good idea to say Y here if you

1461

intend to use this kernel on different machines.

1462

intend to use this kernel on different machines.

1462

1463

More information about the internals of the Linux math coprocessor

1464

More information about the internals of the Linux math coprocessor

1464

emulation can be found in <file:arch/x86/math-emu/README>.

1465

emulation can be found in <file:arch/x86/math-emu/README>.

1465

1466

If you are not sure, say Y; apart from resulting in a 66 KB bigger

1467

If you are not sure, say Y; apart from resulting in a 66 KB bigger

1467

kernel, it won't hurt.

1468

kernel, it won't hurt.

1468

1469

config MTRR

1470

config MTRR

1470

def_bool y

1471

def_bool y

1471

prompt "MTRR (Memory Type Range Register) support" if EXPERT

1472

prompt "MTRR (Memory Type Range Register) support" if EXPERT

1472

---help---

1473

---help---

1473

On Intel P6 family processors (Pentium Pro, Pentium II and later)

1474

On Intel P6 family processors (Pentium Pro, Pentium II and later)

1474

the Memory Type Range Registers (MTRRs) may be used to control

1475

the Memory Type Range Registers (MTRRs) may be used to control

1475

processor access to memory ranges. This is most useful if you have

1476

processor access to memory ranges. This is most useful if you have

1476

a video (VGA) card on a PCI or AGP bus. Enabling write-combining

1477

a video (VGA) card on a PCI or AGP bus. Enabling write-combining

1477

allows bus write transfers to be combined into a larger transfer

1478

allows bus write transfers to be combined into a larger transfer

1478

before bursting over the PCI/AGP bus. This can increase performance

1479

before bursting over the PCI/AGP bus. This can increase performance

1479

of image write operations 2.5 times or more. Saying Y here creates a

1480

of image write operations 2.5 times or more. Saying Y here creates a

1480

/proc/mtrr file which may be used to manipulate your processor's

1481

/proc/mtrr file which may be used to manipulate your processor's

1481

MTRRs. Typically the X server should use this.

1482

MTRRs. Typically the X server should use this.

1482

1483

This code has a reasonably generic interface so that similar

1484

This code has a reasonably generic interface so that similar

1484

control registers on other processors can be easily supported

1485

control registers on other processors can be easily supported

1485

as well:

1486

as well:

1486

1487

The Cyrix 6x86, 6x86MX and M II processors have Address Range

1488

The Cyrix 6x86, 6x86MX and M II processors have Address Range

1488

Registers (ARRs) which provide a similar functionality to MTRRs. For

1489

Registers (ARRs) which provide a similar functionality to MTRRs. For

1489

these, the ARRs are used to emulate the MTRRs.

1490

these, the ARRs are used to emulate the MTRRs.

1490

The AMD K6-2 (stepping 8 and above) and K6-3 processors have two

1491

The AMD K6-2 (stepping 8 and above) and K6-3 processors have two

1491

MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing

1492

MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing

1492

write-combining. All of these processors are supported by this code

1493

write-combining. All of these processors are supported by this code

1493

and it makes sense to say Y here if you have one of them.

1494

and it makes sense to say Y here if you have one of them.

1494

1495

Saying Y here also fixes a problem with buggy SMP BIOSes which only

1496

Saying Y here also fixes a problem with buggy SMP BIOSes which only

1496

set the MTRRs for the boot CPU and not for the secondary CPUs. This

1497

set the MTRRs for the boot CPU and not for the secondary CPUs. This

1497

can lead to all sorts of problems, so it's good to say Y here.

1498

can lead to all sorts of problems, so it's good to say Y here.

1498

1499

You can safely say Y even if your machine doesn't have MTRRs, you'll

1500

You can safely say Y even if your machine doesn't have MTRRs, you'll

1500

just add about 9 KB to your kernel.

1501

just add about 9 KB to your kernel.

1501

1502

See <file:Documentation/x86/mtrr.txt> for more information.

1503

See <file:Documentation/x86/mtrr.txt> for more information.

1503

1504

config MTRR_SANITIZER

1505

config MTRR_SANITIZER

1505

def_bool y

1506

def_bool y

1506

prompt "MTRR cleanup support"

1507

prompt "MTRR cleanup support"

1507

depends on MTRR

1508

depends on MTRR

1508

---help---

1509

---help---

1509

Convert MTRR layout from continuous to discrete, so X drivers can

1510

Convert MTRR layout from continuous to discrete, so X drivers can

1510

add writeback entries.

1511

add writeback entries.

1511

1512

Can be disabled with disable_mtrr_cleanup on the kernel command line.

1513

Can be disabled with disable_mtrr_cleanup on the kernel command line.

1513

The largest mtrr entry size for a continuous block can be set with

1514

The largest mtrr entry size for a continuous block can be set with

1514

mtrr_chunk_size.

1515

mtrr_chunk_size.

1515

1516

If unsure, say Y.

1517

If unsure, say Y.

1517

1518

config MTRR_SANITIZER_ENABLE_DEFAULT

1519

config MTRR_SANITIZER_ENABLE_DEFAULT

1519

int "MTRR cleanup enable value (0-1)"

1520

int "MTRR cleanup enable value (0-1)"

1520

range 0 1

1521

range 0 1

1521

default "0"

1522

default "0"

1522

depends on MTRR_SANITIZER

1523

depends on MTRR_SANITIZER

1523

---help---

1524

---help---

1524

Enable mtrr cleanup default value

1525

Enable mtrr cleanup default value

1525

1526

config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT

1527

config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT

1527

int "MTRR cleanup spare reg num (0-7)"

1528

int "MTRR cleanup spare reg num (0-7)"

1528

range 0 7

1529

range 0 7

1529

default "1"

1530

default "1"

1530

depends on MTRR_SANITIZER

1531

depends on MTRR_SANITIZER

1531

---help---

1532

---help---

1532

mtrr cleanup spare entries default, it can be changed via

1533

mtrr cleanup spare entries default, it can be changed via

1533

mtrr_spare_reg_nr=N on the kernel command line.

1534

mtrr_spare_reg_nr=N on the kernel command line.

1534

1535

config X86_PAT

1536

config X86_PAT

1536

def_bool y

1537

def_bool y

1537

prompt "x86 PAT support" if EXPERT

1538

prompt "x86 PAT support" if EXPERT

1538

depends on MTRR

1539

depends on MTRR

1539

---help---

1540

---help---

1540

Use PAT attributes to setup page level cache control.

1541

Use PAT attributes to setup page level cache control.

1541

1542

PATs are the modern equivalents of MTRRs and are much more

1543

PATs are the modern equivalents of MTRRs and are much more

1543

flexible than MTRRs.

1544

flexible than MTRRs.

1544

1545

Say N here if you see bootup problems (boot crash, boot hang,

1546

Say N here if you see bootup problems (boot crash, boot hang,

1546

spontaneous reboots) or a non-working video driver.

1547

spontaneous reboots) or a non-working video driver.

1547

1548

If unsure, say Y.

1549

If unsure, say Y.

1549

1550

config ARCH_USES_PG_UNCACHED

1551

config ARCH_USES_PG_UNCACHED

1551

def_bool y

1552

def_bool y

1552

depends on X86_PAT

1553

depends on X86_PAT

1553

1554

config ARCH_RANDOM

1555

config ARCH_RANDOM

1555

def_bool y

1556

def_bool y

1556

prompt "x86 architectural random number generator" if EXPERT

1557

prompt "x86 architectural random number generator" if EXPERT

1557

---help---

1558

---help---

1558

Enable the x86 architectural RDRAND instruction

1559

Enable the x86 architectural RDRAND instruction

1559

(Intel Bull Mountain technology) to generate random numbers.

1560

(Intel Bull Mountain technology) to generate random numbers.

1560

If supported, this is a high bandwidth, cryptographically

1561

If supported, this is a high bandwidth, cryptographically

1561

secure hardware random number generator.

1562

secure hardware random number generator.

1562

1563

config X86_SMAP

1564

config X86_SMAP

1564

def_bool y

1565

def_bool y

1565

prompt "Supervisor Mode Access Prevention" if EXPERT

1566

prompt "Supervisor Mode Access Prevention" if EXPERT

1566

---help---

1567

---help---

1567

Supervisor Mode Access Prevention (SMAP) is a security

1568

Supervisor Mode Access Prevention (SMAP) is a security

1568

feature in newer Intel processors. There is a small

1569

feature in newer Intel processors. There is a small

1569

performance cost if this enabled and turned on; there is

1570

performance cost if this enabled and turned on; there is

1570

also a small increase in the kernel size if this is enabled.

1571

also a small increase in the kernel size if this is enabled.

1571

1572

If unsure, say Y.

1573

If unsure, say Y.

1573

1574

config EFI

1575

config EFI

1575

bool "EFI runtime service support"

1576

bool "EFI runtime service support"

1576

depends on ACPI

1577

depends on ACPI

1577

select UCS2_STRING

1578

select UCS2_STRING

1578

---help---

1579

---help---

1579

This enables the kernel to use EFI runtime services that are

1580

This enables the kernel to use EFI runtime services that are

1580

available (such as the EFI variable services).

1581

available (such as the EFI variable services).

1581

1582

This option is only useful on systems that have EFI firmware.

1583

This option is only useful on systems that have EFI firmware.

1583

In addition, you should use the latest ELILO loader available

1584

In addition, you should use the latest ELILO loader available

1584

at <http://elilo.sourceforge.net> in order to take advantage

1585

at <http://elilo.sourceforge.net> in order to take advantage

1585

of EFI runtime services. However, even with this option, the

1586

of EFI runtime services. However, even with this option, the

1586

resultant kernel should continue to boot on existing non-EFI

1587

resultant kernel should continue to boot on existing non-EFI

1587

platforms.

1588

platforms.

1588

1589

config EFI_STUB

1590

config EFI_STUB

1590

bool "EFI stub support"

1591

bool "EFI stub support"

1591

depends on EFI

1592

depends on EFI

1592

---help---

1593

---help---

1593

This kernel feature allows a bzImage to be loaded directly

1594

This kernel feature allows a bzImage to be loaded directly

1594

by EFI firmware without the use of a bootloader.

1595

by EFI firmware without the use of a bootloader.

1595

1596

See Documentation/x86/efi-stub.txt for more information.

1597

See Documentation/x86/efi-stub.txt for more information.

1597

1598

config SECCOMP

1599

config SECCOMP

1599

def_bool y

1600

def_bool y

1600

prompt "Enable seccomp to safely compute untrusted bytecode"

1601

prompt "Enable seccomp to safely compute untrusted bytecode"

1601

---help---

1602

---help---

1602

This kernel feature is useful for number crunching applications

1603

This kernel feature is useful for number crunching applications

1603

that may need to compute untrusted bytecode during their

1604

that may need to compute untrusted bytecode during their

1604

execution. By using pipes or other transports made available to

1605

execution. By using pipes or other transports made available to

1605

the process as file descriptors supporting the read/write

1606

the process as file descriptors supporting the read/write

1606

syscalls, it's possible to isolate those applications in

1607

syscalls, it's possible to isolate those applications in

1607

their own address space using seccomp. Once seccomp is

1608

their own address space using seccomp. Once seccomp is

1608

enabled via prctl(PR_SET_SECCOMP), it cannot be disabled

1609

enabled via prctl(PR_SET_SECCOMP), it cannot be disabled

1609

and the task is only allowed to execute a few safe syscalls

1610

and the task is only allowed to execute a few safe syscalls

1610

defined by each seccomp mode.

1611

defined by each seccomp mode.

1611

1612

If unsure, say Y. Only embedded should say N here.

1613

If unsure, say Y. Only embedded should say N here.

1613

1614

config CC_STACKPROTECTOR

1615

config CC_STACKPROTECTOR

1615

bool "Enable -fstack-protector buffer overflow detection"

1616

bool "Enable -fstack-protector buffer overflow detection"

1616

---help---

1617

---help---

1617

This option turns on the -fstack-protector GCC feature. This

1618

This option turns on the -fstack-protector GCC feature. This

1618

feature puts, at the beginning of functions, a canary value on

1619

feature puts, at the beginning of functions, a canary value on

1619

the stack just before the return address, and validates

1620

the stack just before the return address, and validates

1620

the value just before actually returning. Stack based buffer

1621

the value just before actually returning. Stack based buffer

1621

overflows (that need to overwrite this return address) now also

1622

overflows (that need to overwrite this return address) now also

1622

overwrite the canary, which gets detected and the attack is then

1623

overwrite the canary, which gets detected and the attack is then

1623

neutralized via a kernel panic.

1624

neutralized via a kernel panic.

1624

1625

This feature requires gcc version 4.2 or above, or a distribution

1626

This feature requires gcc version 4.2 or above, or a distribution

1626

gcc with the feature backported. Older versions are automatically

1627

gcc with the feature backported. Older versions are automatically

1627

detected and for those versions, this configuration option is

1628

detected and for those versions, this configuration option is

1628

ignored. (and a warning is printed during bootup)

1629

ignored. (and a warning is printed during bootup)

1629

1630

source kernel/Kconfig.hz

1631

source kernel/Kconfig.hz

1631

1632

config KEXEC

1633

config KEXEC

1633

bool "kexec system call"

1634

bool "kexec system call"

1634

---help---

1635

---help---

1635

kexec is a system call that implements the ability to shutdown your

1636

kexec is a system call that implements the ability to shutdown your

1636

current kernel, and to start another kernel. It is like a reboot

1637

current kernel, and to start another kernel. It is like a reboot

1637

but it is independent of the system firmware. And like a reboot

1638

but it is independent of the system firmware. And like a reboot

1638

you can start any kernel with it, not just Linux.

1639

you can start any kernel with it, not just Linux.

1639

1640

The name comes from the similarity to the exec system call.

1641

The name comes from the similarity to the exec system call.

1641

1642

It is an ongoing process to be certain the hardware in a machine

1643

It is an ongoing process to be certain the hardware in a machine

1643

is properly shutdown, so do not be surprised if this code does not

1644

is properly shutdown, so do not be surprised if this code does not

1644

initially work for you. As of this writing the exact hardware

1645

initially work for you. As of this writing the exact hardware

1645

interface is strongly in flux, so no good recommendation can be

1646

interface is strongly in flux, so no good recommendation can be

1646

made.

1647

made.

1647

1648

config CRASH_DUMP

1649

config CRASH_DUMP

1649

bool "kernel crash dumps"

1650

bool "kernel crash dumps"

1650

depends on X86_64 || (X86_32 && HIGHMEM)

1651

depends on X86_64 || (X86_32 && HIGHMEM)

1651

---help---

1652

---help---

1652

Generate crash dump after being started by kexec.

1653

Generate crash dump after being started by kexec.

1653

This should be normally only set in special crash dump kernels

1654

This should be normally only set in special crash dump kernels

1654

which are loaded in the main kernel with kexec-tools into

1655

which are loaded in the main kernel with kexec-tools into

1655

a specially reserved region and then later executed after

1656

a specially reserved region and then later executed after

1656

a crash by kdump/kexec. The crash dump kernel must be compiled

1657

a crash by kdump/kexec. The crash dump kernel must be compiled

1657

to a memory address not used by the main kernel or BIOS using

1658

to a memory address not used by the main kernel or BIOS using

1658

PHYSICAL_START, or it must be built as a relocatable image

1659

PHYSICAL_START, or it must be built as a relocatable image

1659

(CONFIG_RELOCATABLE=y).

1660

(CONFIG_RELOCATABLE=y).

1660

For more details see Documentation/kdump/kdump.txt

1661

For more details see Documentation/kdump/kdump.txt

1661

1662

config KEXEC_JUMP

1663

config KEXEC_JUMP

1663

bool "kexec jump"

1664

bool "kexec jump"

1664

depends on KEXEC && HIBERNATION

1665

depends on KEXEC && HIBERNATION

1665

---help---

1666

---help---

1666

Jump between original kernel and kexeced kernel and invoke

1667

Jump between original kernel and kexeced kernel and invoke

1667

code in physical address mode via KEXEC

1668

code in physical address mode via KEXEC

1668

1669

config PHYSICAL_START

1670

config PHYSICAL_START

1670

hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)

1671

hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)

1671

default "0x1000000"

1672

default "0x1000000"

1672

---help---

1673

---help---

1673

This gives the physical address where the kernel is loaded.

1674

This gives the physical address where the kernel is loaded.

1674

1675

If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then

1676

If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then

1676

bzImage will decompress itself to above physical address and

1677

bzImage will decompress itself to above physical address and

1677

run from there. Otherwise, bzImage will run from the address where

1678

run from there. Otherwise, bzImage will run from the address where

1678

it has been loaded by the boot loader and will ignore above physical

1679

it has been loaded by the boot loader and will ignore above physical

1679

address.

1680

address.

1680

1681

In normal kdump cases one does not have to set/change this option

1682

In normal kdump cases one does not have to set/change this option

1682

as now bzImage can be compiled as a completely relocatable image

1683

as now bzImage can be compiled as a completely relocatable image

1683

(CONFIG_RELOCATABLE=y) and be used to load and run from a different

1684

(CONFIG_RELOCATABLE=y) and be used to load and run from a different

1684

address. This option is mainly useful for the folks who don't want

1685

address. This option is mainly useful for the folks who don't want

1685

to use a bzImage for capturing the crash dump and want to use a

1686

to use a bzImage for capturing the crash dump and want to use a

1686

vmlinux instead. vmlinux is not relocatable hence a kernel needs

1687

vmlinux instead. vmlinux is not relocatable hence a kernel needs

1687

to be specifically compiled to run from a specific memory area

1688

to be specifically compiled to run from a specific memory area

1688

(normally a reserved region) and this option comes handy.

1689

(normally a reserved region) and this option comes handy.

1689

1690

So if you are using bzImage for capturing the crash dump,

1691

So if you are using bzImage for capturing the crash dump,

1691

leave the value here unchanged to 0x1000000 and set

1692

leave the value here unchanged to 0x1000000 and set

1692

CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux

1693

CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux

1693

for capturing the crash dump change this value to start of

1694

for capturing the crash dump change this value to start of

1694

the reserved region. In other words, it can be set based on

1695

the reserved region. In other words, it can be set based on

1695

the "X" value as specified in the "crashkernel=YM@XM"

1696

the "X" value as specified in the "crashkernel=YM@XM"

1696

command line boot parameter passed to the panic-ed

1697

command line boot parameter passed to the panic-ed

1697

kernel. Please take a look at Documentation/kdump/kdump.txt

1698

kernel. Please take a look at Documentation/kdump/kdump.txt

1698

for more details about crash dumps.

1699

for more details about crash dumps.

1699

1700

Usage of bzImage for capturing the crash dump is recommended as

1701

Usage of bzImage for capturing the crash dump is recommended as

1701

one does not have to build two kernels. Same kernel can be used

1702

one does not have to build two kernels. Same kernel can be used

1702

as production kernel and capture kernel. Above option should have

1703

as production kernel and capture kernel. Above option should have

1703

gone away after relocatable bzImage support is introduced. But it

1704

gone away after relocatable bzImage support is introduced. But it

1704

is present because there are users out there who continue to use

1705

is present because there are users out there who continue to use

1705

vmlinux for dump capture. This option should go away down the

1706

vmlinux for dump capture. This option should go away down the

1706

line.

1707

line.

1707

1708

Don't change this unless you know what you are doing.

1709

Don't change this unless you know what you are doing.

1709

1710

config RELOCATABLE

1711

config RELOCATABLE

1711

bool "Build a relocatable kernel"

1712

bool "Build a relocatable kernel"

1712

default y

1713

default y

1713

---help---

1714

---help---

1714

This builds a kernel image that retains relocation information

1715

This builds a kernel image that retains relocation information

1715

so it can be loaded someplace besides the default 1MB.

1716

so it can be loaded someplace besides the default 1MB.

1716

The relocations tend to make the kernel binary about 10% larger,

1717

The relocations tend to make the kernel binary about 10% larger,

1717

but are discarded at runtime.

1718

but are discarded at runtime.

1718

1719

One use is for the kexec on panic case where the recovery kernel

1720

One use is for the kexec on panic case where the recovery kernel

1720

must live at a different physical address than the primary

1721

must live at a different physical address than the primary

1721

kernel.

1722

kernel.

1722

1723

Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address

1724

Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address

1724

it has been loaded at and the compile time physical address

1725

it has been loaded at and the compile time physical address

1725

(CONFIG_PHYSICAL_START) is ignored.

1726

(CONFIG_PHYSICAL_START) is ignored.

1726

1727

# Relocation on x86-32 needs some additional build support

1728

# Relocation on x86-32 needs some additional build support

1728

config X86_NEED_RELOCS

1729

config X86_NEED_RELOCS

1729

def_bool y

1730

def_bool y

1730

depends on X86_32 && RELOCATABLE

1731

depends on X86_32 && RELOCATABLE

1731

1732

config PHYSICAL_ALIGN

1733

config PHYSICAL_ALIGN

1733

hex "Alignment value to which kernel should be aligned"

1734

hex "Alignment value to which kernel should be aligned"

1734

default "0x1000000"

1735

default "0x1000000"

1735

range 0x2000 0x1000000 if X86_32

1736

range 0x2000 0x1000000 if X86_32

1736

range 0x200000 0x1000000 if X86_64

1737

range 0x200000 0x1000000 if X86_64

1737

---help---

1738

---help---

1738

This value puts the alignment restrictions on physical address

1739

This value puts the alignment restrictions on physical address

1739

where kernel is loaded and run from. Kernel is compiled for an

1740

where kernel is loaded and run from. Kernel is compiled for an

1740

address which meets above alignment restriction.

1741

address which meets above alignment restriction.

1741

1742

If bootloader loads the kernel at a non-aligned address and

1743

If bootloader loads the kernel at a non-aligned address and

1743

CONFIG_RELOCATABLE is set, kernel will move itself to nearest

1744

CONFIG_RELOCATABLE is set, kernel will move itself to nearest

1744

address aligned to above value and run from there.

1745

address aligned to above value and run from there.

1745

1746

If bootloader loads the kernel at a non-aligned address and

1747

If bootloader loads the kernel at a non-aligned address and

1747

CONFIG_RELOCATABLE is not set, kernel will ignore the run time

1748

CONFIG_RELOCATABLE is not set, kernel will ignore the run time

1748

load address and decompress itself to the address it has been

1749

load address and decompress itself to the address it has been

1749

compiled for and run from there. The address for which kernel is

1750

compiled for and run from there. The address for which kernel is

1750

compiled already meets above alignment restrictions. Hence the

1751

compiled already meets above alignment restrictions. Hence the

1751

end result is that kernel runs from a physical address meeting

1752

end result is that kernel runs from a physical address meeting

1752

above alignment restrictions.

1753

above alignment restrictions.

1753

1754

On 32-bit this value must be a multiple of 0x2000. On 64-bit

1755

On 32-bit this value must be a multiple of 0x2000. On 64-bit

1755

this value must be a multiple of 0x200000.

1756

this value must be a multiple of 0x200000.

1756

1757

Don't change this unless you know what you are doing.

1758

Don't change this unless you know what you are doing.

1758

1759

config HOTPLUG_CPU

1760

config HOTPLUG_CPU

1760

bool "Support for hot-pluggable CPUs"

1761

bool "Support for hot-pluggable CPUs"

1761

depends on SMP

1762

depends on SMP

1762

---help---

1763

---help---

1763

Say Y here to allow turning CPUs off and on. CPUs can be

1764

Say Y here to allow turning CPUs off and on. CPUs can be

1764

controlled through /sys/devices/system/cpu.

1765

controlled through /sys/devices/system/cpu.

1765

( Note: power management support will enable this option

1766

( Note: power management support will enable this option

1766

automatically on SMP systems. )

1767

automatically on SMP systems. )

1767

Say N if you want to disable CPU hotplug.

1768

Say N if you want to disable CPU hotplug.

1768

1769

config BOOTPARAM_HOTPLUG_CPU0

1770

config BOOTPARAM_HOTPLUG_CPU0

1770

bool "Set default setting of cpu0_hotpluggable"

1771

bool "Set default setting of cpu0_hotpluggable"

1771

default n

1772

default n

1772

depends on HOTPLUG_CPU

1773

depends on HOTPLUG_CPU

1773

---help---

1774

---help---

1774

Set whether default state of cpu0_hotpluggable is on or off.

1775

Set whether default state of cpu0_hotpluggable is on or off.

1775

1776

Say Y here to enable CPU0 hotplug by default. If this switch

1777

Say Y here to enable CPU0 hotplug by default. If this switch

1777

is turned on, there is no need to give cpu0_hotplug kernel

1778

is turned on, there is no need to give cpu0_hotplug kernel

1778

parameter and the CPU0 hotplug feature is enabled by default.

1779

parameter and the CPU0 hotplug feature is enabled by default.

1779

1780

Please note: there are two known CPU0 dependencies if you want

1781

Please note: there are two known CPU0 dependencies if you want

1781

to enable the CPU0 hotplug feature either by this switch or by

1782

to enable the CPU0 hotplug feature either by this switch or by

1782

cpu0_hotplug kernel parameter.

1783

cpu0_hotplug kernel parameter.

1783

1784

First, resume from hibernate or suspend always starts from CPU0.

1785

First, resume from hibernate or suspend always starts from CPU0.

1785

So hibernate and suspend are prevented if CPU0 is offline.

1786

So hibernate and suspend are prevented if CPU0 is offline.

1786

1787

Second dependency is PIC interrupts always go to CPU0. CPU0 can not

1788

Second dependency is PIC interrupts always go to CPU0. CPU0 can not

1788

offline if any interrupt can not migrate out of CPU0. There may

1789

offline if any interrupt can not migrate out of CPU0. There may

1789

be other CPU0 dependencies.

1790

be other CPU0 dependencies.

1790

1791

Please make sure the dependencies are under your control before

1792

Please make sure the dependencies are under your control before

1792

you enable this feature.

1793

you enable this feature.

1793

1794

Say N if you don't want to enable CPU0 hotplug feature by default.

1795

Say N if you don't want to enable CPU0 hotplug feature by default.

1795

You still can enable the CPU0 hotplug feature at boot by kernel

1796

You still can enable the CPU0 hotplug feature at boot by kernel

1796

parameter cpu0_hotplug.

1797

parameter cpu0_hotplug.

1797

1798

config DEBUG_HOTPLUG_CPU0

1799

config DEBUG_HOTPLUG_CPU0

1799

def_bool n

1800

def_bool n

1800

prompt "Debug CPU0 hotplug"

1801

prompt "Debug CPU0 hotplug"

1801

depends on HOTPLUG_CPU

1802

depends on HOTPLUG_CPU

1802

---help---

1803

---help---

1803

Enabling this option offlines CPU0 (if CPU0 can be offlined) as

1804

Enabling this option offlines CPU0 (if CPU0 can be offlined) as

1804

soon as possible and boots up userspace with CPU0 offlined. User

1805

soon as possible and boots up userspace with CPU0 offlined. User

1805

can online CPU0 back after boot time.

1806

can online CPU0 back after boot time.

1806

1807

To debug CPU0 hotplug, you need to enable CPU0 offline/online

1808

To debug CPU0 hotplug, you need to enable CPU0 offline/online

1808

feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during

1809

feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during

1809

compilation or giving cpu0_hotplug kernel parameter at boot.

1810

compilation or giving cpu0_hotplug kernel parameter at boot.

1810

1811

If unsure, say N.

1812

If unsure, say N.

1812

1813

config COMPAT_VDSO

1814

config COMPAT_VDSO

1814

def_bool y

1815

def_bool y

1815

prompt "Compat VDSO support"

1816

prompt "Compat VDSO support"

1816

depends on X86_32 || IA32_EMULATION

1817

depends on X86_32 || IA32_EMULATION

1817

---help---

1818

---help---

1818

Map the 32-bit VDSO to the predictable old-style address too.

1819

Map the 32-bit VDSO to the predictable old-style address too.

1819

1820

Say N here if you are running a sufficiently recent glibc

1821

Say N here if you are running a sufficiently recent glibc

1821

version (2.3.3 or later), to remove the high-mapped

1822

version (2.3.3 or later), to remove the high-mapped

1822

VDSO mapping and to exclusively use the randomized VDSO.

1823

VDSO mapping and to exclusively use the randomized VDSO.

1823

1824

If unsure, say Y.

1825

If unsure, say Y.

1825

1826

config CMDLINE_BOOL

1827

config CMDLINE_BOOL

1827

bool "Built-in kernel command line"

1828

bool "Built-in kernel command line"

1828

---help---

1829

---help---

1829

Allow for specifying boot arguments to the kernel at

1830

Allow for specifying boot arguments to the kernel at

1830

build time. On some systems (e.g. embedded ones), it is

1831

build time. On some systems (e.g. embedded ones), it is

1831

necessary or convenient to provide some or all of the

1832

necessary or convenient to provide some or all of the

1832

kernel boot arguments with the kernel itself (that is,

1833

kernel boot arguments with the kernel itself (that is,

1833

to not rely on the boot loader to provide them.)

1834

to not rely on the boot loader to provide them.)

1834

1835

To compile command line arguments into the kernel,

1836

To compile command line arguments into the kernel,

1836

set this option to 'Y', then fill in the

1837

set this option to 'Y', then fill in the

1837

the boot arguments in CONFIG_CMDLINE.

1838

the boot arguments in CONFIG_CMDLINE.

1838

1839

Systems with fully functional boot loaders (i.e. non-embedded)

1840

Systems with fully functional boot loaders (i.e. non-embedded)

1840

should leave this option set to 'N'.

1841

should leave this option set to 'N'.

1841

1842

config CMDLINE

1843

config CMDLINE

1843

string "Built-in kernel command string"

1844

string "Built-in kernel command string"

1844

depends on CMDLINE_BOOL

1845

depends on CMDLINE_BOOL

1845

default ""

1846

default ""

1846

---help---

1847

---help---

1847

Enter arguments here that should be compiled into the kernel

1848

Enter arguments here that should be compiled into the kernel

1848

image and used at boot time. If the boot loader provides a

1849

image and used at boot time. If the boot loader provides a

1849

command line at boot time, it is appended to this string to

1850

command line at boot time, it is appended to this string to

1850

form the full kernel command line, when the system boots.

1851

form the full kernel command line, when the system boots.

1851

1852

However, you can use the CONFIG_CMDLINE_OVERRIDE option to

1853

However, you can use the CONFIG_CMDLINE_OVERRIDE option to

1853

change this behavior.

1854

change this behavior.

1854

1855

In most cases, the command line (whether built-in or provided

1856

In most cases, the command line (whether built-in or provided

1856

by the boot loader) should specify the device for the root

1857

by the boot loader) should specify the device for the root

1857

file system.

1858

file system.

1858

1859

config CMDLINE_OVERRIDE

1860

config CMDLINE_OVERRIDE

1860

bool "Built-in command line overrides boot loader arguments"

1861

bool "Built-in command line overrides boot loader arguments"

1861

depends on CMDLINE_BOOL

1862

depends on CMDLINE_BOOL

1862

---help---

1863

---help---

1863

Set this option to 'Y' to have the kernel ignore the boot loader

1864

Set this option to 'Y' to have the kernel ignore the boot loader

1864

command line, and use ONLY the built-in command line.

1865

command line, and use ONLY the built-in command line.

1865

1866

This is used to work around broken boot loaders. This should

1867

This is used to work around broken boot loaders. This should

1867

be set to 'N' under normal conditions.

1868

be set to 'N' under normal conditions.

1868

1869

endmenu

1870

endmenu

1870

1871

config ARCH_ENABLE_MEMORY_HOTPLUG

1872

config ARCH_ENABLE_MEMORY_HOTPLUG

1872

def_bool y

1873

def_bool y

1873

depends on X86_64 || (X86_32 && HIGHMEM)

1874

depends on X86_64 || (X86_32 && HIGHMEM)

1874

1875

config ARCH_ENABLE_MEMORY_HOTREMOVE

1876

config ARCH_ENABLE_MEMORY_HOTREMOVE

1876

def_bool y

1877

def_bool y

1877

depends on MEMORY_HOTPLUG

1878

depends on MEMORY_HOTPLUG

1878

1879

config USE_PERCPU_NUMA_NODE_ID

1880

config USE_PERCPU_NUMA_NODE_ID

1880

def_bool y

1881

def_bool y

1881

depends on NUMA

1882

depends on NUMA

1882

1883

menu "Power management and ACPI options"

1884

menu "Power management and ACPI options"

1884

1885

config ARCH_HIBERNATION_HEADER

1886

config ARCH_HIBERNATION_HEADER

1886

def_bool y

1887

def_bool y

1887

depends on X86_64 && HIBERNATION

1888

depends on X86_64 && HIBERNATION

1888

1889

source "kernel/power/Kconfig"

1890

source "kernel/power/Kconfig"

1890

1891

source "drivers/acpi/Kconfig"

1892

source "drivers/acpi/Kconfig"

1892

1893

source "drivers/sfi/Kconfig"

1894

source "drivers/sfi/Kconfig"

1894

1895

config X86_APM_BOOT

1896

config X86_APM_BOOT

1896

def_bool y

1897

def_bool y

1897

depends on APM

1898

depends on APM

1898

1899

menuconfig APM

1900

menuconfig APM

1900

tristate "APM (Advanced Power Management) BIOS support"

1901

tristate "APM (Advanced Power Management) BIOS support"

1901

depends on X86_32 && PM_SLEEP

1902

depends on X86_32 && PM_SLEEP

1902

---help---

1903

---help---

1903

APM is a BIOS specification for saving power using several different

1904

APM is a BIOS specification for saving power using several different

1904

techniques. This is mostly useful for battery powered laptops with

1905

techniques. This is mostly useful for battery powered laptops with

1905

APM compliant BIOSes. If you say Y here, the system time will be

1906

APM compliant BIOSes. If you say Y here, the system time will be

1906

reset after a RESUME operation, the /proc/apm device will provide

1907

reset after a RESUME operation, the /proc/apm device will provide

1907

battery status information, and user-space programs will receive

1908

battery status information, and user-space programs will receive

1908

notification of APM "events" (e.g. battery status change).

1909

notification of APM "events" (e.g. battery status change).

1909

1910

If you select "Y" here, you can disable actual use of the APM

1911

If you select "Y" here, you can disable actual use of the APM

1911

BIOS by passing the "apm=off" option to the kernel at boot time.

1912

BIOS by passing the "apm=off" option to the kernel at boot time.

1912

1913

Note that the APM support is almost completely disabled for

1914

Note that the APM support is almost completely disabled for

1914

machines with more than one CPU.

1915

machines with more than one CPU.

1915

1916

In order to use APM, you will need supporting software. For location

1917

In order to use APM, you will need supporting software. For location

1917

and more information, read <file:Documentation/power/apm-acpi.txt>

1918

and more information, read <file:Documentation/power/apm-acpi.txt>

1918

and the Battery Powered Linux mini-HOWTO, available from

1919

and the Battery Powered Linux mini-HOWTO, available from

1919

<http://www.tldp.org/docs.html#howto>.

1920

<http://www.tldp.org/docs.html#howto>.

1920

1921

This driver does not spin down disk drives (see the hdparm(8)

1922

This driver does not spin down disk drives (see the hdparm(8)

1922

manpage ("man 8 hdparm") for that), and it doesn't turn off

1923

manpage ("man 8 hdparm") for that), and it doesn't turn off

1923

VESA-compliant "green" monitors.

1924

VESA-compliant "green" monitors.

1924

1925

This driver does not support the TI 4000M TravelMate and the ACER

1926

This driver does not support the TI 4000M TravelMate and the ACER

1926

486/DX4/75 because they don't have compliant BIOSes. Many "green"

1927

486/DX4/75 because they don't have compliant BIOSes. Many "green"

1927

desktop machines also don't have compliant BIOSes, and this driver

1928

desktop machines also don't have compliant BIOSes, and this driver

1928

may cause those machines to panic during the boot phase.

1929

may cause those machines to panic during the boot phase.

1929

1930

Generally, if you don't have a battery in your machine, there isn't

1931

Generally, if you don't have a battery in your machine, there isn't

1931

much point in using this driver and you should say N. If you get

1932

much point in using this driver and you should say N. If you get

1932

random kernel OOPSes or reboots that don't seem to be related to

1933

random kernel OOPSes or reboots that don't seem to be related to

1933

anything, try disabling/enabling this option (or disabling/enabling

1934

anything, try disabling/enabling this option (or disabling/enabling

1934

APM in your BIOS).

1935

APM in your BIOS).

1935

1936

Some other things you should try when experiencing seemingly random,

1937

Some other things you should try when experiencing seemingly random,

1937

"weird" problems:

1938

"weird" problems:

1938

1939

1) make sure that you have enough swap space and that it is

1940

1) make sure that you have enough swap space and that it is

1940

enabled.

1941

enabled.

1941

2) pass the "no-hlt" option to the kernel

1942

2) pass the "no-hlt" option to the kernel

1942

3) switch on floating point emulation in the kernel and pass

1943

3) switch on floating point emulation in the kernel and pass

1943

the "no387" option to the kernel

1944

the "no387" option to the kernel

1944

4) pass the "floppy=nodma" option to the kernel

1945

4) pass the "floppy=nodma" option to the kernel

1945

5) pass the "mem=4M" option to the kernel (thereby disabling

1946

5) pass the "mem=4M" option to the kernel (thereby disabling

1946

all but the first 4 MB of RAM)

1947

all but the first 4 MB of RAM)

1947

6) make sure that the CPU is not over clocked.

1948

6) make sure that the CPU is not over clocked.

1948

7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>

1949

7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>

1949

8) disable the cache from your BIOS settings

1950

8) disable the cache from your BIOS settings

1950

9) install a fan for the video card or exchange video RAM

1951

9) install a fan for the video card or exchange video RAM

1951

10) install a better fan for the CPU

1952

10) install a better fan for the CPU

1952

11) exchange RAM chips

1953

11) exchange RAM chips

1953

12) exchange the motherboard.

1954

12) exchange the motherboard.

1954

1955

To compile this driver as a module, choose M here: the

1956

To compile this driver as a module, choose M here: the

1956

module will be called apm.

1957

module will be called apm.

1957

1958

if APM

1959

if APM

1959

1960

config APM_IGNORE_USER_SUSPEND

1961

config APM_IGNORE_USER_SUSPEND

1961

bool "Ignore USER SUSPEND"

1962

bool "Ignore USER SUSPEND"

1962

---help---

1963

---help---

1963

This option will ignore USER SUSPEND requests. On machines with a

1964

This option will ignore USER SUSPEND requests. On machines with a

1964

compliant APM BIOS, you want to say N. However, on the NEC Versa M

1965

compliant APM BIOS, you want to say N. However, on the NEC Versa M

1965

series notebooks, it is necessary to say Y because of a BIOS bug.

1966

series notebooks, it is necessary to say Y because of a BIOS bug.

1966

1967

config APM_DO_ENABLE

1968

config APM_DO_ENABLE

1968

bool "Enable PM at boot time"

1969

bool "Enable PM at boot time"

1969

---help---

1970

---help---

1970

Enable APM features at boot time. From page 36 of the APM BIOS

1971

Enable APM features at boot time. From page 36 of the APM BIOS

1971

specification: "When disabled, the APM BIOS does not automatically

1972

specification: "When disabled, the APM BIOS does not automatically

1972

power manage devices, enter the Standby State, enter the Suspend

1973

power manage devices, enter the Standby State, enter the Suspend

1973

State, or take power saving steps in response to CPU Idle calls."

1974

State, or take power saving steps in response to CPU Idle calls."

1974

This driver will make CPU Idle calls when Linux is idle (unless this

1975

This driver will make CPU Idle calls when Linux is idle (unless this

1975

feature is turned off -- see "Do CPU IDLE calls", below). This

1976

feature is turned off -- see "Do CPU IDLE calls", below). This

1976

should always save battery power, but more complicated APM features

1977

should always save battery power, but more complicated APM features

1977

will be dependent on your BIOS implementation. You may need to turn

1978

will be dependent on your BIOS implementation. You may need to turn

1978

this option off if your computer hangs at boot time when using APM

1979

this option off if your computer hangs at boot time when using APM

1979

support, or if it beeps continuously instead of suspending. Turn

1980

support, or if it beeps continuously instead of suspending. Turn

1980

this off if you have a NEC UltraLite Versa 33/C or a Toshiba

1981

this off if you have a NEC UltraLite Versa 33/C or a Toshiba

1981

T400CDT. This is off by default since most machines do fine without

1982

T400CDT. This is off by default since most machines do fine without

1982

this feature.

1983

this feature.

1983

1984

config APM_CPU_IDLE

1985

config APM_CPU_IDLE

1985

depends on CPU_IDLE

1986

depends on CPU_IDLE

1986

bool "Make CPU Idle calls when idle"

1987

bool "Make CPU Idle calls when idle"

1987

---help---

1988

---help---

1988

Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.

1989

Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.

1989

On some machines, this can activate improved power savings, such as

1990

On some machines, this can activate improved power savings, such as

1990

a slowed CPU clock rate, when the machine is idle. These idle calls

1991

a slowed CPU clock rate, when the machine is idle. These idle calls

1991

are made after the idle loop has run for some length of time (e.g.,

1992

are made after the idle loop has run for some length of time (e.g.,

1992

333 mS). On some machines, this will cause a hang at boot time or

1993

333 mS). On some machines, this will cause a hang at boot time or

1993

whenever the CPU becomes idle. (On machines with more than one CPU,

1994

whenever the CPU becomes idle. (On machines with more than one CPU,

1994

this option does nothing.)

1995

this option does nothing.)

1995

1996

config APM_DISPLAY_BLANK

1997

config APM_DISPLAY_BLANK

1997

bool "Enable console blanking using APM"

1998

bool "Enable console blanking using APM"

1998

---help---

1999

---help---

1999

Enable console blanking using the APM. Some laptops can use this to

2000

Enable console blanking using the APM. Some laptops can use this to

2000

turn off the LCD backlight when the screen blanker of the Linux

2001

turn off the LCD backlight when the screen blanker of the Linux

2001

virtual console blanks the screen. Note that this is only used by

2002

virtual console blanks the screen. Note that this is only used by

2002

the virtual console screen blanker, and won't turn off the backlight

2003

the virtual console screen blanker, and won't turn off the backlight

2003

when using the X Window system. This also doesn't have anything to

2004

when using the X Window system. This also doesn't have anything to

2004

do with your VESA-compliant power-saving monitor. Further, this

2005

do with your VESA-compliant power-saving monitor. Further, this

2005

option doesn't work for all laptops -- it might not turn off your

2006

option doesn't work for all laptops -- it might not turn off your

2006

backlight at all, or it might print a lot of errors to the console,

2007

backlight at all, or it might print a lot of errors to the console,

2007

especially if you are using gpm.

2008

especially if you are using gpm.

2008

2009

config APM_ALLOW_INTS

2010

config APM_ALLOW_INTS

2010

bool "Allow interrupts during APM BIOS calls"

2011

bool "Allow interrupts during APM BIOS calls"

2011

---help---

2012

---help---

2012

Normally we disable external interrupts while we are making calls to

2013

Normally we disable external interrupts while we are making calls to

2013

the APM BIOS as a measure to lessen the effects of a badly behaving

2014

the APM BIOS as a measure to lessen the effects of a badly behaving

2014

BIOS implementation. The BIOS should reenable interrupts if it

2015

BIOS implementation. The BIOS should reenable interrupts if it

2015

needs to. Unfortunately, some BIOSes do not -- especially those in

2016

needs to. Unfortunately, some BIOSes do not -- especially those in

2016

many of the newer IBM Thinkpads. If you experience hangs when you

2017

many of the newer IBM Thinkpads. If you experience hangs when you

2017

suspend, try setting this to Y. Otherwise, say N.

2018

suspend, try setting this to Y. Otherwise, say N.

2018

2019

endif # APM

2020

endif # APM

2020

2021

source "drivers/cpufreq/Kconfig"

2022

source "drivers/cpufreq/Kconfig"

2022

2023

source "drivers/cpuidle/Kconfig"

2024

source "drivers/cpuidle/Kconfig"

2024

2025

source "drivers/idle/Kconfig"

2026

source "drivers/idle/Kconfig"

2026

2027

endmenu

2028

endmenu

2028

2029

2030

menu "Bus options (PCI etc.)"

2031

menu "Bus options (PCI etc.)"

2031

2032

config PCI

2033

config PCI

2033

bool "PCI support"

2034

bool "PCI support"

2034

default y

2035

default y

2035

---help---

2036

---help---

2036

Find out whether you have a PCI motherboard. PCI is the name of a

2037

Find out whether you have a PCI motherboard. PCI is the name of a

2037

bus system, i.e. the way the CPU talks to the other stuff inside

2038

bus system, i.e. the way the CPU talks to the other stuff inside

2038

your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or

2039

your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or

2039

VESA. If you have PCI, say Y, otherwise N.

2040

VESA. If you have PCI, say Y, otherwise N.

2040

2041

choice

2042

choice

2042

prompt "PCI access mode"

2043

prompt "PCI access mode"

2043

depends on X86_32 && PCI

2044

depends on X86_32 && PCI

2044

default PCI_GOANY

2045

default PCI_GOANY

2045

---help---

2046

---help---

2046

On PCI systems, the BIOS can be used to detect the PCI devices and

2047

On PCI systems, the BIOS can be used to detect the PCI devices and

2047

determine their configuration. However, some old PCI motherboards

2048

determine their configuration. However, some old PCI motherboards

2048

have BIOS bugs and may crash if this is done. Also, some embedded

2049

have BIOS bugs and may crash if this is done. Also, some embedded

2049

PCI-based systems don't have any BIOS at all. Linux can also try to

2050

PCI-based systems don't have any BIOS at all. Linux can also try to

2050

detect the PCI hardware directly without using the BIOS.

2051

detect the PCI hardware directly without using the BIOS.

2051

2052

With this option, you can specify how Linux should detect the

2053

With this option, you can specify how Linux should detect the

2053

PCI devices. If you choose "BIOS", the BIOS will be used,

2054

PCI devices. If you choose "BIOS", the BIOS will be used,

2054

if you choose "Direct", the BIOS won't be used, and if you

2055

if you choose "Direct", the BIOS won't be used, and if you

2055

choose "MMConfig", then PCI Express MMCONFIG will be used.

2056

choose "MMConfig", then PCI Express MMCONFIG will be used.

2056

If you choose "Any", the kernel will try MMCONFIG, then the

2057

If you choose "Any", the kernel will try MMCONFIG, then the

2057

direct access method and falls back to the BIOS if that doesn't

2058

direct access method and falls back to the BIOS if that doesn't

2058

work. If unsure, go with the default, which is "Any".

2059

work. If unsure, go with the default, which is "Any".

2059

2060

config PCI_GOBIOS

2061

config PCI_GOBIOS

2061

bool "BIOS"

2062

bool "BIOS"

2062

2063

config PCI_GOMMCONFIG

2064

config PCI_GOMMCONFIG

2064

bool "MMConfig"

2065

bool "MMConfig"

2065

2066

config PCI_GODIRECT

2067

config PCI_GODIRECT

2067

bool "Direct"

2068

bool "Direct"

2068

2069

config PCI_GOOLPC

2070

config PCI_GOOLPC

2070

bool "OLPC XO-1"

2071

bool "OLPC XO-1"

2071

depends on OLPC

2072

depends on OLPC

2072

2073

config PCI_GOANY

2074

config PCI_GOANY

2074

bool "Any"

2075

bool "Any"

2075

2076

endchoice

2077

endchoice

2077

2078

config PCI_BIOS

2079

config PCI_BIOS

2079

def_bool y

2080

def_bool y

2080

depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)

2081

depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)

2081

2082

# x86-64 doesn't support PCI BIOS access from long mode so always go direct.

2083

# x86-64 doesn't support PCI BIOS access from long mode so always go direct.

2083

config PCI_DIRECT

2084

config PCI_DIRECT

2084

def_bool y

2085

def_bool y

2085

depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))

2086

depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))

2086

2087

config PCI_MMCONFIG

2088

config PCI_MMCONFIG

2088

def_bool y

2089

def_bool y

2089

depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)

2090

depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)

2090

2091

config PCI_OLPC

2092

config PCI_OLPC

2092

def_bool y

2093

def_bool y

2093

depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)

2094

depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)

2094

2095

config PCI_XEN

2096

config PCI_XEN

2096

def_bool y

2097

def_bool y

2097

depends on PCI && XEN

2098

depends on PCI && XEN

2098

select SWIOTLB_XEN

2099

select SWIOTLB_XEN

2099

2100

config PCI_DOMAINS

2101

config PCI_DOMAINS

2101

def_bool y

2102

def_bool y

2102

depends on PCI

2103

depends on PCI

2103

2104

config PCI_MMCONFIG

2105

config PCI_MMCONFIG

2105

bool "Support mmconfig PCI config space access"

2106

bool "Support mmconfig PCI config space access"

2106

depends on X86_64 && PCI && ACPI

2107

depends on X86_64 && PCI && ACPI

2107

2108

config PCI_CNB20LE_QUIRK

2109

config PCI_CNB20LE_QUIRK

2109

bool "Read CNB20LE Host Bridge Windows" if EXPERT

2110

bool "Read CNB20LE Host Bridge Windows" if EXPERT

2110

depends on PCI

2111

depends on PCI

2111

help

2112

help

2112

Read the PCI windows out of the CNB20LE host bridge. This allows

2113

Read the PCI windows out of the CNB20LE host bridge. This allows

2113

PCI hotplug to work on systems with the CNB20LE chipset which do

2114

PCI hotplug to work on systems with the CNB20LE chipset which do

2114

not have ACPI.

2115

not have ACPI.

2115

2116

There's no public spec for this chipset, and this functionality

2117

There's no public spec for this chipset, and this functionality

2117

is known to be incomplete.

2118

is known to be incomplete.

2118

2119

You should say N unless you know you need this.

2120

You should say N unless you know you need this.

2120

2121

source "drivers/pci/pcie/Kconfig"

2122

source "drivers/pci/pcie/Kconfig"

2122

2123

source "drivers/pci/Kconfig"

2124

source "drivers/pci/Kconfig"

2124

2125

# x86_64 have no ISA slots, but can have ISA-style DMA.

2126

# x86_64 have no ISA slots, but can have ISA-style DMA.

2126

config ISA_DMA_API

2127

config ISA_DMA_API

2127

bool "ISA-style DMA support" if (X86_64 && EXPERT)

2128

bool "ISA-style DMA support" if (X86_64 && EXPERT)

2128

default y

2129

default y

2129

help

2130

help

2130

Enables ISA-style DMA support for devices requiring such controllers.

2131

Enables ISA-style DMA support for devices requiring such controllers.

2131

If unsure, say Y.

2132

If unsure, say Y.

2132

2133

if X86_32

2134

if X86_32

2134

2135

config ISA

2136

config ISA

2136

bool "ISA support"

2137

bool "ISA support"

2137

---help---

2138

---help---

2138

Find out whether you have ISA slots on your motherboard. ISA is the

2139

Find out whether you have ISA slots on your motherboard. ISA is the

2139

name of a bus system, i.e. the way the CPU talks to the other stuff

2140

name of a bus system, i.e. the way the CPU talks to the other stuff

2140

inside your box. Other bus systems are PCI, EISA, MicroChannel

2141

inside your box. Other bus systems are PCI, EISA, MicroChannel

2141

(MCA) or VESA. ISA is an older system, now being displaced by PCI;

2142

(MCA) or VESA. ISA is an older system, now being displaced by PCI;

2142

newer boards don't support it. If you have ISA, say Y, otherwise N.

2143

newer boards don't support it. If you have ISA, say Y, otherwise N.

2143

2144

config EISA

2145

config EISA

2145

bool "EISA support"

2146

bool "EISA support"

2146

depends on ISA

2147

depends on ISA

2147

---help---

2148

---help---

2148

The Extended Industry Standard Architecture (EISA) bus was

2149

The Extended Industry Standard Architecture (EISA) bus was

2149

developed as an open alternative to the IBM MicroChannel bus.

2150

developed as an open alternative to the IBM MicroChannel bus.

2150

2151

The EISA bus provided some of the features of the IBM MicroChannel

2152

The EISA bus provided some of the features of the IBM MicroChannel

2152

bus while maintaining backward compatibility with cards made for

2153

bus while maintaining backward compatibility with cards made for

2153

the older ISA bus. The EISA bus saw limited use between 1988 and

2154

the older ISA bus. The EISA bus saw limited use between 1988 and

2154

1995 when it was made obsolete by the PCI bus.

2155

1995 when it was made obsolete by the PCI bus.

2155

2156

Say Y here if you are building a kernel for an EISA-based machine.

2157

Say Y here if you are building a kernel for an EISA-based machine.

2157

2158

Otherwise, say N.

2159

Otherwise, say N.

2159

2160

source "drivers/eisa/Kconfig"

2161

source "drivers/eisa/Kconfig"

2161

2162

config SCx200

2163

config SCx200

2163

tristate "NatSemi SCx200 support"

2164

tristate "NatSemi SCx200 support"

2164

---help---

2165

---help---

2165

This provides basic support for National Semiconductor's

2166

This provides basic support for National Semiconductor's

2166

(now AMD's) Geode processors. The driver probes for the

2167

(now AMD's) Geode processors. The driver probes for the

2167

PCI-IDs of several on-chip devices, so its a good dependency

2168

PCI-IDs of several on-chip devices, so its a good dependency

2168

for other scx200_* drivers.

2169

for other scx200_* drivers.

2169

2170

If compiled as a module, the driver is named scx200.

2171

If compiled as a module, the driver is named scx200.

2171

2172

config SCx200HR_TIMER

2173

config SCx200HR_TIMER

2173

tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"

2174

tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"

2174

depends on SCx200

2175

depends on SCx200

2175

default y

2176

default y

2176

---help---

2177

---help---

2177

This driver provides a clocksource built upon the on-chip

2178

This driver provides a clocksource built upon the on-chip

2178

27MHz high-resolution timer. Its also a workaround for

2179

27MHz high-resolution timer. Its also a workaround for

2179

NSC Geode SC-1100's buggy TSC, which loses time when the

2180

NSC Geode SC-1100's buggy TSC, which loses time when the

2180

processor goes idle (as is done by the scheduler). The

2181

processor goes idle (as is done by the scheduler). The

2181

other workaround is idle=poll boot option.

2182

other workaround is idle=poll boot option.

2182

2183

config OLPC

2184

config OLPC

2184

bool "One Laptop Per Child support"

2185

bool "One Laptop Per Child support"

2185

depends on !X86_PAE

2186

depends on !X86_PAE

2186

select GPIOLIB

2187

select GPIOLIB

2187

select OF

2188

select OF

2188

select OF_PROMTREE

2189

select OF_PROMTREE

2189

select IRQ_DOMAIN

2190

select IRQ_DOMAIN

2190

---help---

2191

---help---

2191

Add support for detecting the unique features of the OLPC

2192

Add support for detecting the unique features of the OLPC

2192

XO hardware.

2193

XO hardware.

2193

2194

config OLPC_XO1_PM

2195

config OLPC_XO1_PM

2195

bool "OLPC XO-1 Power Management"

2196

bool "OLPC XO-1 Power Management"

2196

depends on OLPC && MFD_CS5535 && PM_SLEEP

2197

depends on OLPC && MFD_CS5535 && PM_SLEEP

2197

select MFD_CORE

2198

select MFD_CORE

2198

---help---

2199

---help---

2199

Add support for poweroff and suspend of the OLPC XO-1 laptop.

2200

Add support for poweroff and suspend of the OLPC XO-1 laptop.

2200

2201

config OLPC_XO1_RTC

2202

config OLPC_XO1_RTC

2202

bool "OLPC XO-1 Real Time Clock"

2203

bool "OLPC XO-1 Real Time Clock"

2203

depends on OLPC_XO1_PM && RTC_DRV_CMOS

2204

depends on OLPC_XO1_PM && RTC_DRV_CMOS

2204

---help---

2205

---help---

2205

Add support for the XO-1 real time clock, which can be used as a

2206

Add support for the XO-1 real time clock, which can be used as a

2206

programmable wakeup source.

2207

programmable wakeup source.

2207

2208

config OLPC_XO1_SCI

2209

config OLPC_XO1_SCI

2209

bool "OLPC XO-1 SCI extras"

2210

bool "OLPC XO-1 SCI extras"

2210

depends on OLPC && OLPC_XO1_PM

2211

depends on OLPC && OLPC_XO1_PM

2211

depends on INPUT=y

2212

depends on INPUT=y

2212

select POWER_SUPPLY

2213

select POWER_SUPPLY

2213

select GPIO_CS5535

2214

select GPIO_CS5535

2214

select MFD_CORE

2215

select MFD_CORE

2215

---help---

2216

---help---

2216

Add support for SCI-based features of the OLPC XO-1 laptop:

2217

Add support for SCI-based features of the OLPC XO-1 laptop:

2217

- EC-driven system wakeups

2218

- EC-driven system wakeups

2218

- Power button

2219

- Power button

2219

- Ebook switch

2220

- Ebook switch

2220

- Lid switch

2221

- Lid switch

2221

- AC adapter status updates

2222

- AC adapter status updates

2222

- Battery status updates

2223

- Battery status updates

2223

2224

config OLPC_XO15_SCI

2225

config OLPC_XO15_SCI

2225

bool "OLPC XO-1.5 SCI extras"

2226

bool "OLPC XO-1.5 SCI extras"

2226

depends on OLPC && ACPI

2227

depends on OLPC && ACPI

2227

select POWER_SUPPLY

2228

select POWER_SUPPLY

2228

---help---

2229

---help---

2229

Add support for SCI-based features of the OLPC XO-1.5 laptop:

2230

Add support for SCI-based features of the OLPC XO-1.5 laptop:

2230

- EC-driven system wakeups

2231

- EC-driven system wakeups

2231

- AC adapter status updates

2232

- AC adapter status updates

2232

- Battery status updates

2233

- Battery status updates

2233

2234

config ALIX

2235

config ALIX

2235

bool "PCEngines ALIX System Support (LED setup)"

2236

bool "PCEngines ALIX System Support (LED setup)"

2236

select GPIOLIB

2237

select GPIOLIB

2237

---help---

2238

---help---

2238

This option enables system support for the PCEngines ALIX.

2239

This option enables system support for the PCEngines ALIX.

2239

At present this just sets up LEDs for GPIO control on

2240

At present this just sets up LEDs for GPIO control on

2240

ALIX2/3/6 boards. However, other system specific setup should

2241

ALIX2/3/6 boards. However, other system specific setup should

2241

get added here.

2242

get added here.

2242

2243

Note: You must still enable the drivers for GPIO and LED support

2244

Note: You must still enable the drivers for GPIO and LED support

2244

(GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs

2245

(GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs

2245

2246

Note: You have to set alix.force=1 for boards with Award BIOS.

2247

Note: You have to set alix.force=1 for boards with Award BIOS.

2247

2248

config NET5501

2249

config NET5501

2249

bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"

2250

bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"

2250

select GPIOLIB

2251

select GPIOLIB

2251

---help---

2252

---help---

2252

This option enables system support for the Soekris Engineering net5501.

2253

This option enables system support for the Soekris Engineering net5501.

2253

2254

config GEOS

2255

config GEOS

2255

bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"

2256

bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"

2256

select GPIOLIB

2257

select GPIOLIB

2257

depends on DMI

2258

depends on DMI

2258

---help---

2259

---help---

2259

This option enables system support for the Traverse Technologies GEOS.

2260

This option enables system support for the Traverse Technologies GEOS.

2260

2261

config TS5500

2262

config TS5500

2262

bool "Technologic Systems TS-5500 platform support"

2263

bool "Technologic Systems TS-5500 platform support"

2263

depends on MELAN

2264

depends on MELAN

2264

select CHECK_SIGNATURE

2265

select CHECK_SIGNATURE

2265

select NEW_LEDS

2266

select NEW_LEDS

2266

select LEDS_CLASS

2267

select LEDS_CLASS

2267

---help---

2268

---help---

2268

This option enables system support for the Technologic Systems TS-5500.

2269

This option enables system support for the Technologic Systems TS-5500.

2269

2270

endif # X86_32

2271

endif # X86_32

2271

2272

config AMD_NB

2273

config AMD_NB

2273

def_bool y

2274

def_bool y

2274

depends on CPU_SUP_AMD && PCI

2275

depends on CPU_SUP_AMD && PCI

2275

2276

source "drivers/pcmcia/Kconfig"

2277

source "drivers/pcmcia/Kconfig"

2277

2278

source "drivers/pci/hotplug/Kconfig"

2279

source "drivers/pci/hotplug/Kconfig"

2279

2280

config RAPIDIO

2281

config RAPIDIO

2281

tristate "RapidIO support"

2282

tristate "RapidIO support"

2282

depends on PCI

2283

depends on PCI

2283

default n

2284

default n

2284

help

2285

help

2285

If enabled this option will include drivers and the core

2286

If enabled this option will include drivers and the core

2286

infrastructure code to support RapidIO interconnect devices.

2287

infrastructure code to support RapidIO interconnect devices.

2287

2288

source "drivers/rapidio/Kconfig"

2289

source "drivers/rapidio/Kconfig"

2289

2290

config X86_SYSFB

2291

config X86_SYSFB

2291

bool "Mark VGA/VBE/EFI FB as generic system framebuffer"

2292

bool "Mark VGA/VBE/EFI FB as generic system framebuffer"

2292

help

2293

help

2293

Firmwares often provide initial graphics framebuffers so the BIOS,

2294

Firmwares often provide initial graphics framebuffers so the BIOS,

2294

bootloader or kernel can show basic video-output during boot for

2295

bootloader or kernel can show basic video-output during boot for

2295

user-guidance and debugging. Historically, x86 used the VESA BIOS

2296

user-guidance and debugging. Historically, x86 used the VESA BIOS

2296

Extensions and EFI-framebuffers for this, which are mostly limited

2297

Extensions and EFI-framebuffers for this, which are mostly limited

2297

to x86.

2298

to x86.

2298

This option, if enabled, marks VGA/VBE/EFI framebuffers as generic

2299

This option, if enabled, marks VGA/VBE/EFI framebuffers as generic

2299

framebuffers so the new generic system-framebuffer drivers can be

2300

framebuffers so the new generic system-framebuffer drivers can be

2300

used on x86. If the framebuffer is not compatible with the generic

2301

used on x86. If the framebuffer is not compatible with the generic

2301

modes, it is adverticed as fallback platform framebuffer so legacy

2302

modes, it is adverticed as fallback platform framebuffer so legacy

2302

drivers like efifb, vesafb and uvesafb can pick it up.

2303

drivers like efifb, vesafb and uvesafb can pick it up.

2303

If this option is not selected, all system framebuffers are always

2304

If this option is not selected, all system framebuffers are always

2304

marked as fallback platform framebuffers as usual.

2305

marked as fallback platform framebuffers as usual.

2305

2306

Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will

2307

Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will

2307

not be able to pick up generic system framebuffers if this option

2308

not be able to pick up generic system framebuffers if this option

2308

is selected. You are highly encouraged to enable simplefb as

2309

is selected. You are highly encouraged to enable simplefb as

2309

replacement if you select this option. simplefb can correctly deal

2310

replacement if you select this option. simplefb can correctly deal

2310

with generic system framebuffers. But you should still keep vesafb

2311

with generic system framebuffers. But you should still keep vesafb

2311

and others enabled as fallback if a system framebuffer is

2312

and others enabled as fallback if a system framebuffer is

2312

incompatible with simplefb.

2313

incompatible with simplefb.

2313

2314

If unsure, say Y.

2315

If unsure, say Y.

2315

2316

endmenu

2317

endmenu

2317

2318

2319

menu "Executable file formats / Emulations"

2320

menu "Executable file formats / Emulations"

2320

2321

source "fs/Kconfig.binfmt"

2322

source "fs/Kconfig.binfmt"

2322

2323

config IA32_EMULATION

2324

config IA32_EMULATION

2324

bool "IA32 Emulation"

2325

bool "IA32 Emulation"

2325

depends on X86_64

2326

depends on X86_64

2326

select BINFMT_ELF

2327

select BINFMT_ELF

2327

select COMPAT_BINFMT_ELF

2328

select COMPAT_BINFMT_ELF

2328

select HAVE_UID16

2329

select HAVE_UID16

2329

---help---

2330

---help---

2330

Include code to run legacy 32-bit programs under a

2331

Include code to run legacy 32-bit programs under a

2331

64-bit kernel. You should likely turn this on, unless you're

2332

64-bit kernel. You should likely turn this on, unless you're

2332

100% sure that you don't have any 32-bit programs left.

2333

100% sure that you don't have any 32-bit programs left.

2333

2334

config IA32_AOUT

2335

config IA32_AOUT

2335

tristate "IA32 a.out support"

2336

tristate "IA32 a.out support"

2336

depends on IA32_EMULATION

2337

depends on IA32_EMULATION

2337

---help---

2338

---help---

2338

Support old a.out binaries in the 32bit emulation.

2339

Support old a.out binaries in the 32bit emulation.

2339

2340

config X86_X32

2341

config X86_X32

2341

bool "x32 ABI for 64-bit mode"

2342

bool "x32 ABI for 64-bit mode"

2342

depends on X86_64 && IA32_EMULATION

2343

depends on X86_64 && IA32_EMULATION

2343

---help---

2344

---help---

2344

Include code to run binaries for the x32 native 32-bit ABI

2345

Include code to run binaries for the x32 native 32-bit ABI

2345

for 64-bit processors. An x32 process gets access to the

2346

for 64-bit processors. An x32 process gets access to the

2346

full 64-bit register file and wide data path while leaving

2347

full 64-bit register file and wide data path while leaving

2347

pointers at 32 bits for smaller memory footprint.

2348

pointers at 32 bits for smaller memory footprint.

2348

2349

You will need a recent binutils (2.22 or later) with

2350

You will need a recent binutils (2.22 or later) with

2350

elf32_x86_64 support enabled to compile a kernel with this

2351

elf32_x86_64 support enabled to compile a kernel with this

2351

option set.

2352

option set.

2352

2353

config COMPAT

2354

config COMPAT

2354

def_bool y

2355

def_bool y

2355

depends on IA32_EMULATION || X86_X32

2356

depends on IA32_EMULATION || X86_X32

2356

select ARCH_WANT_OLD_COMPAT_IPC

2357

select ARCH_WANT_OLD_COMPAT_IPC

2357

2358

if COMPAT

2359

if COMPAT

2359

config COMPAT_FOR_U64_ALIGNMENT

2360

config COMPAT_FOR_U64_ALIGNMENT

2360

def_bool y

2361

def_bool y

2361

2362

config SYSVIPC_COMPAT

2363

config SYSVIPC_COMPAT

2363

def_bool y

2364

def_bool y

2364

depends on SYSVIPC

2365

depends on SYSVIPC

2365

2366

config KEYS_COMPAT

2367

config KEYS_COMPAT

2367

def_bool y

2368

def_bool y

2368

depends on KEYS

2369

depends on KEYS

2369

endif

2370

endif

2370

2371

endmenu

2372

endmenu

2372

2373

2374

config HAVE_ATOMIC_IOMAP

2375

config HAVE_ATOMIC_IOMAP

2375

def_bool y

2376

def_bool y

2376

depends on X86_32

2377

depends on X86_32

2377

2378

config X86_DEV_DMA_OPS

2379

config X86_DEV_DMA_OPS

2379

bool

2380

bool

2380

depends on X86_64 || STA2X11

2381

depends on X86_64 || STA2X11

2381

2382

config X86_DMA_REMAP

2383

config X86_DMA_REMAP

2383

bool

2384

bool

2384

depends on STA2X11

2385

depends on STA2X11

2385

2386

source "net/Kconfig"

2387

source "net/Kconfig"

2387

2388

source "drivers/Kconfig"

2389

source "drivers/Kconfig"

2389

2390

source "drivers/firmware/Kconfig"

2391

source "drivers/firmware/Kconfig"

2391

2392

source "fs/Kconfig"

2393

source "fs/Kconfig"

2393

2394

source "arch/x86/Kconfig.debug"

2395

source "arch/x86/Kconfig.debug"

2395

2396

source "security/Kconfig"

2397

source "security/Kconfig"

2397

2398

source "crypto/Kconfig"

2399

source "crypto/Kconfig"

2399

2400

source "arch/x86/kvm/Kconfig"

2401

source "arch/x86/kvm/Kconfig"

2401

2402

source "lib/Kconfig"

2403

source "lib/Kconfig"

2403

2404

GITLAB

Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

 # Select 32 or 64 bit
 config 64BIT
 	bool "64-bit kernel" if ARCH = "x86"
 	default ARCH != "i386"
 	---help---
 	  Say yes to build a 64-bit kernel - formerly known as x86_64
 	  Say no to build a 32-bit kernel - formerly known as i386
 config X86_32
 	def_bool y
 	depends on !64BIT
 	select CLKSRC_I8253
 	select HAVE_UID16
 config X86_64
 	def_bool y
 	depends on 64BIT
 	select X86_DEV_DMA_OPS
 	select ARCH_USE_CMPXCHG_LOCKREF
 ### Arch settings
 config X86
 	def_bool y
 	select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
 	select HAVE_AOUT if X86_32
 	select HAVE_UNSTABLE_SCHED_CLOCK
 	select ARCH_SUPPORTS_NUMA_BALANCING
 	select ARCH_WANTS_PROT_NUMA_PROT_NONE
 	select HAVE_IDE
 	select HAVE_OPROFILE
 	select HAVE_PCSPKR_PLATFORM
 	select HAVE_PERF_EVENTS
 	select HAVE_IOREMAP_PROT
 	select HAVE_KPROBES
 	select HAVE_MEMBLOCK
 	select HAVE_MEMBLOCK_NODE_MAP
 	select ARCH_DISCARD_MEMBLOCK
 	select ARCH_WANT_OPTIONAL_GPIOLIB
 	select ARCH_WANT_FRAME_POINTERS
 	select HAVE_DMA_ATTRS
 	select HAVE_DMA_CONTIGUOUS if !SWIOTLB
 	select HAVE_KRETPROBES
 	select HAVE_OPTPROBES
 	select HAVE_KPROBES_ON_FTRACE
 	select HAVE_FTRACE_MCOUNT_RECORD
 	select HAVE_FENTRY if X86_64
 	select HAVE_C_RECORDMCOUNT
 	select HAVE_DYNAMIC_FTRACE
 	select HAVE_DYNAMIC_FTRACE_WITH_REGS
 	select HAVE_FUNCTION_TRACER
 	select HAVE_FUNCTION_GRAPH_TRACER
 	select HAVE_FUNCTION_GRAPH_FP_TEST
 	select HAVE_FUNCTION_TRACE_MCOUNT_TEST
 	select HAVE_SYSCALL_TRACEPOINTS
 	select SYSCTL_EXCEPTION_TRACE
 	select HAVE_KVM
 	select HAVE_ARCH_KGDB
 	select HAVE_ARCH_TRACEHOOK
 	select HAVE_GENERIC_DMA_COHERENT if X86_32
 	select HAVE_EFFICIENT_UNALIGNED_ACCESS
 	select USER_STACKTRACE_SUPPORT
 	select HAVE_REGS_AND_STACK_ACCESS_API
 	select HAVE_DMA_API_DEBUG
 	select HAVE_KERNEL_GZIP
 	select HAVE_KERNEL_BZIP2
 	select HAVE_KERNEL_LZMA
 	select HAVE_KERNEL_XZ
 	select HAVE_KERNEL_LZO
 	select HAVE_KERNEL_LZ4
 	select HAVE_HW_BREAKPOINT
 	select HAVE_MIXED_BREAKPOINTS_REGS
 	select PERF_EVENTS
 	select HAVE_PERF_EVENTS_NMI
 	select HAVE_PERF_REGS
 	select HAVE_PERF_USER_STACK_DUMP
 	select HAVE_DEBUG_KMEMLEAK
 	select ANON_INODES
 	select HAVE_ALIGNED_STRUCT_PAGE if SLUB
 	select HAVE_CMPXCHG_LOCAL
 	select HAVE_CMPXCHG_DOUBLE
 	select HAVE_ARCH_KMEMCHECK
 	select HAVE_USER_RETURN_NOTIFIER
 	select ARCH_BINFMT_ELF_RANDOMIZE_PIE
 	select HAVE_ARCH_JUMP_LABEL
 	select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
 	select SPARSE_IRQ
 	select GENERIC_FIND_FIRST_BIT
 	select GENERIC_IRQ_PROBE
 	select GENERIC_PENDING_IRQ if SMP
 	select GENERIC_IRQ_SHOW
 	select GENERIC_CLOCKEVENTS_MIN_ADJUST
 	select IRQ_FORCED_THREADING
 	select USE_GENERIC_SMP_HELPERS if SMP
 	select HAVE_BPF_JIT if X86_64
 	select HAVE_ARCH_TRANSPARENT_HUGEPAGE
 	select CLKEVT_I8253
 	select ARCH_HAVE_NMI_SAFE_CMPXCHG
 	select GENERIC_IOMAP
 	select DCACHE_WORD_ACCESS
 	select GENERIC_SMP_IDLE_THREAD
 	select ARCH_WANT_IPC_PARSE_VERSION if X86_32
 	select HAVE_ARCH_SECCOMP_FILTER
 	select BUILDTIME_EXTABLE_SORT
 	select GENERIC_CMOS_UPDATE
 	select HAVE_ARCH_SOFT_DIRTY
 	select CLOCKSOURCE_WATCHDOG
 	select GENERIC_CLOCKEVENTS
 	select ARCH_CLOCKSOURCE_DATA if X86_64
 	select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
 	select GENERIC_TIME_VSYSCALL if X86_64
 	select KTIME_SCALAR if X86_32
 	select GENERIC_STRNCPY_FROM_USER
 	select GENERIC_STRNLEN_USER
 	select HAVE_CONTEXT_TRACKING if X86_64
 	select HAVE_IRQ_TIME_ACCOUNTING
 	select VIRT_TO_BUS
 	select MODULES_USE_ELF_REL if X86_32
 	select MODULES_USE_ELF_RELA if X86_64
 	select CLONE_BACKWARDS if X86_32
 	select ARCH_USE_BUILTIN_BSWAP
 	select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION
 	select OLD_SIGACTION if X86_32
 	select COMPAT_OLD_SIGACTION if IA32_EMULATION
 	select RTC_LIB
 	select HAVE_DEBUG_STACKOVERFLOW
 config INSTRUCTION_DECODER
 	def_bool y
 	depends on KPROBES || PERF_EVENTS || UPROBES
 config OUTPUT_FORMAT
 	string
 	default "elf32-i386" if X86_32
 	default "elf64-x86-64" if X86_64
 config ARCH_DEFCONFIG
 	string
 	default "arch/x86/configs/i386_defconfig" if X86_32
 	default "arch/x86/configs/x86_64_defconfig" if X86_64
 config LOCKDEP_SUPPORT
 	def_bool y
 config STACKTRACE_SUPPORT
 	def_bool y
 config HAVE_LATENCYTOP_SUPPORT
 	def_bool y
 config MMU
 	def_bool y
 config SBUS
 	bool
 config NEED_DMA_MAP_STATE
 	def_bool y
 	depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG
 config NEED_SG_DMA_LENGTH
 	def_bool y
 config GENERIC_ISA_DMA
 	def_bool y
 	depends on ISA_DMA_API
 config GENERIC_BUG
 	def_bool y
 	depends on BUG
 	select GENERIC_BUG_RELATIVE_POINTERS if X86_64
 config GENERIC_BUG_RELATIVE_POINTERS
 	bool
 config GENERIC_HWEIGHT
 	def_bool y
 config ARCH_MAY_HAVE_PC_FDC
 	def_bool y
 	depends on ISA_DMA_API
 config RWSEM_XCHGADD_ALGORITHM
 	def_bool y
 config GENERIC_CALIBRATE_DELAY
 	def_bool y
 config ARCH_HAS_CPU_RELAX
 	def_bool y
 config ARCH_HAS_CACHE_LINE_SIZE
 	def_bool y
 config ARCH_HAS_CPU_AUTOPROBE
 	def_bool y
 config HAVE_SETUP_PER_CPU_AREA
 	def_bool y
 config NEED_PER_CPU_EMBED_FIRST_CHUNK
 	def_bool y
 config NEED_PER_CPU_PAGE_FIRST_CHUNK
 	def_bool y
 config ARCH_HIBERNATION_POSSIBLE
 	def_bool y
 config ARCH_SUSPEND_POSSIBLE
 	def_bool y
 config ARCH_WANT_HUGE_PMD_SHARE
 	def_bool y
 config ARCH_WANT_GENERAL_HUGETLB
 	def_bool y
 config ZONE_DMA32
 	bool
 	default X86_64
 config AUDIT_ARCH
 	bool
 	default X86_64
 config ARCH_SUPPORTS_OPTIMIZED_INLINING
 	def_bool y
 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
 	def_bool y
 config HAVE_INTEL_TXT
 	def_bool y
 	depends on INTEL_IOMMU && ACPI
 config X86_32_SMP
 	def_bool y
 	depends on X86_32 && SMP
 config X86_64_SMP
 	def_bool y
 	depends on X86_64 && SMP
 config X86_HT
 	def_bool y
 	depends on SMP
 config X86_32_LAZY_GS
 	def_bool y
 	depends on X86_32 && !CC_STACKPROTECTOR
 config ARCH_HWEIGHT_CFLAGS
 	string
 	default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
 	default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64
 config ARCH_CPU_PROBE_RELEASE
 	def_bool y
 	depends on HOTPLUG_CPU
 config ARCH_SUPPORTS_UPROBES
 	def_bool y
 source "init/Kconfig"
 source "kernel/Kconfig.freezer"
 menu "Processor type and features"
 config ZONE_DMA
 	bool "DMA memory allocation support" if EXPERT
 	default y
 	help
 	  DMA memory allocation support allows devices with less than 32-bit
 	  addressing to allocate within the first 16MB of address space.
 	  Disable if no such devices will be used.
 	  If unsure, say Y.
 config SMP
 	bool "Symmetric multi-processing support"
 	---help---
 	  This enables support for systems with more than one CPU. If you have
 	  a system with only one CPU, like most personal computers, say N. If
 	  you have a system with more than one CPU, say Y.
 	  If you say N here, the kernel will run on single and multiprocessor
 	  machines, but will use only one CPU of a multiprocessor machine. If
 	  you say Y here, the kernel will run on many, but not all,
 	  singleprocessor machines. On a singleprocessor machine, the kernel
 	  will run faster if you say N here.
 	  Note that if you say Y here and choose architecture "586" or
 	  "Pentium" under "Processor family", the kernel will not work on 486
 	  architectures. Similarly, multiprocessor kernels for the "PPro"
 	  architecture may not work on all Pentium based boards.
 	  People using multiprocessor machines who say Y here should also say
 	  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
 	  Management" code will be disabled if you say Y here.
 	  See also <file:Documentation/x86/i386/IO-APIC.txt>,
 	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
 	  <http://www.tldp.org/docs.html#howto>.
 	  If you don't know what to do here, say N.
 config X86_X2APIC
 	bool "Support x2apic"
 	depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
 	---help---
 	  This enables x2apic support on CPUs that have this feature.
 	  This allows 32-bit apic IDs (so it can support very large systems),
 	  and accesses the local apic via MSRs not via mmio.
 	  If you don't know what to do here, say N.
 config X86_MPPARSE
 	bool "Enable MPS table" if ACPI || SFI
 	default y
 	depends on X86_LOCAL_APIC
 	---help---
 	  For old smp systems that do not have proper acpi support. Newer systems
 	  (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
 config X86_BIGSMP
 	bool "Support for big SMP systems with more than 8 CPUs"
 	depends on X86_32 && SMP
 	---help---
 	  This option is needed for the systems that have more than 8 CPUs
 config GOLDFISH
        def_bool y
        depends on X86_GOLDFISH
 if X86_32
 config X86_EXTENDED_PLATFORM
 	bool "Support for extended (non-PC) x86 platforms"
 	default y
 	---help---
 	  If you disable this option then the kernel will only support
 	  standard PC platforms. (which covers the vast majority of
 	  systems out there.)
 	  If you enable this option then you'll be able to select support
 	  for the following (non-PC) 32 bit x86 platforms:
 		Goldfish (Android emulator)
 		AMD Elan
 		NUMAQ (IBM/Sequent)
 		RDC R-321x SoC
 		SGI 320/540 (Visual Workstation)
 		STA2X11-based (e.g. Northville)
 		Summit/EXA (IBM x440)
 		Unisys ES7000 IA32 series
 		Moorestown MID devices
 	  If you have one of these systems, or if you want to build a
 	  generic distribution kernel, say Y here - otherwise say N.
 endif
 if X86_64
 config X86_EXTENDED_PLATFORM
 	bool "Support for extended (non-PC) x86 platforms"
 	default y
 	---help---
 	  If you disable this option then the kernel will only support
 	  standard PC platforms. (which covers the vast majority of
 	  systems out there.)
 	  If you enable this option then you'll be able to select support
 	  for the following (non-PC) 64 bit x86 platforms:
 		Numascale NumaChip
 		ScaleMP vSMP
 		SGI Ultraviolet
 	  If you have one of these systems, or if you want to build a
 	  generic distribution kernel, say Y here - otherwise say N.
 endif
 # This is an alphabetically sorted list of 64 bit extended platforms
 # Please maintain the alphabetic order if and when there are additions
 config X86_NUMACHIP
 	bool "Numascale NumaChip"
 	depends on X86_64
 	depends on X86_EXTENDED_PLATFORM
 	depends on NUMA
 	depends on SMP
 	depends on X86_X2APIC
 	depends on PCI_MMCONFIG
 	---help---
 	  Adds support for Numascale NumaChip large-SMP systems. Needed to
 	  enable more than ~168 cores.
 	  If you don't have one of these, you should say N here.
 config X86_VSMP
 	bool "ScaleMP vSMP"
 	select HYPERVISOR_GUEST
 	select PARAVIRT
 	depends on X86_64 && PCI
 	depends on X86_EXTENDED_PLATFORM
 	depends on SMP
 	---help---
 	  Support for ScaleMP vSMP systems.  Say 'Y' here if this kernel is
 	  supposed to run on these EM64T-based machines.  Only choose this option
 	  if you have one of these machines.
 config X86_UV
 	bool "SGI Ultraviolet"
 	depends on X86_64
 	depends on X86_EXTENDED_PLATFORM
 	depends on NUMA
 	depends on X86_X2APIC
 	---help---
 	  This option is needed in order to support SGI Ultraviolet systems.
 	  If you don't have one of these, you should say N here.
 # Following is an alphabetically sorted list of 32 bit extended platforms
 # Please maintain the alphabetic order if and when there are additions
 config X86_GOLDFISH
        bool "Goldfish (Virtual Platform)"
        depends on X86_32
        depends on X86_EXTENDED_PLATFORM
        ---help---
 	 Enable support for the Goldfish virtual platform used primarily
 	 for Android development. Unless you are building for the Android
 	 Goldfish emulator say N here.
 config X86_INTEL_CE
 	bool "CE4100 TV platform"
 	depends on PCI
 	depends on PCI_GODIRECT
 	depends on X86_32
 	depends on X86_EXTENDED_PLATFORM
 	select X86_REBOOTFIXUPS
 	select OF
 	select OF_EARLY_FLATTREE
 	select IRQ_DOMAIN
 	---help---
 	  Select for the Intel CE media processor (CE4100) SOC.
 	  This option compiles in support for the CE4100 SOC for settop
 	  boxes and media devices.
 config X86_WANT_INTEL_MID
 	bool "Intel MID platform support"
 	depends on X86_32
 	depends on X86_EXTENDED_PLATFORM
 	---help---
 	  Select to build a kernel capable of supporting Intel MID platform
 	  systems which do not have the PCI legacy interfaces (Moorestown,
 	  Medfield). If you are building for a PC class system say N here.
 if X86_WANT_INTEL_MID
 config X86_INTEL_MID
 	bool
 config X86_MDFLD
        bool "Medfield MID platform"
 	depends on PCI
 	depends on PCI_GOANY
 	depends on X86_IO_APIC
 	select X86_INTEL_MID
 	select SFI
 	select DW_APB_TIMER
 	select APB_TIMER
 	select I2C
 	select SPI
 	select INTEL_SCU_IPC
 	select X86_PLATFORM_DEVICES
 	select MFD_INTEL_MSIC
 	---help---
 	  Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin
 	  Internet Device(MID) platform.
 	  Unlike standard x86 PCs, Medfield does not have many legacy devices
 	  nor standard legacy replacement devices/features. e.g. Medfield does
 	  not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
 endif
 config X86_INTEL_LPSS
 	bool "Intel Low Power Subsystem Support"
 	depends on ACPI
 	select COMMON_CLK
 	select PINCTRL
 	---help---
 	  Select to build support for Intel Low Power Subsystem such as
 	  found on Intel Lynxpoint PCH. Selecting this option enables
 	  things like clock tree (common clock framework) and pincontrol
 	  which are needed by the LPSS peripheral drivers.
 config X86_RDC321X
 	bool "RDC R-321x SoC"
 	depends on X86_32
 	depends on X86_EXTENDED_PLATFORM
 	select M486
 	select X86_REBOOTFIXUPS
 	---help---
 	  This option is needed for RDC R-321x system-on-chip, also known
 	  as R-8610-(G).
 	  If you don't have one of these chips, you should say N here.
 config X86_32_NON_STANDARD
 	bool "Support non-standard 32-bit SMP architectures"
 	depends on X86_32 && SMP
 	depends on X86_EXTENDED_PLATFORM
 	---help---
 	  This option compiles in the NUMAQ, Summit, bigsmp, ES7000,
 	  STA2X11, default subarchitectures.  It is intended for a generic
 	  binary kernel. If you select them all, kernel will probe it
 	  one by one and will fallback to default.
 # Alphabetically sorted list of Non standard 32 bit platforms
 config X86_NUMAQ
 	bool "NUMAQ (IBM/Sequent)"
 	depends on X86_32_NON_STANDARD
 	depends on PCI
 	select NUMA
 	select X86_MPPARSE
 	---help---
 	  This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
 	  NUMA multiquad box. This changes the way that processors are
 	  bootstrapped, and uses Clustered Logical APIC addressing mode instead
 	  of Flat Logical.  You will need a new lynxer.elf file to flash your
 	  firmware with - send email to <Martin.Bligh@us.ibm.com>.
 config X86_SUPPORTS_MEMORY_FAILURE
 	def_bool y
 	# MCE code calls memory_failure():
 	depends on X86_MCE
 	# On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
 	depends on !X86_NUMAQ
 	# On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
 	depends on X86_64 || !SPARSEMEM
 	select ARCH_SUPPORTS_MEMORY_FAILURE
 config X86_VISWS
 	bool "SGI 320/540 (Visual Workstation)"
 	depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
 	depends on X86_32_NON_STANDARD
 	---help---
 	  The SGI Visual Workstation series is an IA32-based workstation
 	  based on SGI systems chips with some legacy PC hardware attached.
 	  Say Y here to create a kernel to run on the SGI 320 or 540.
 	  A kernel compiled for the Visual Workstation will run on general
 	  PCs as well. See <file:Documentation/sgi-visws.txt> for details.
 config STA2X11
 	bool "STA2X11 Companion Chip Support"
 	depends on X86_32_NON_STANDARD && PCI
 	select X86_DEV_DMA_OPS
 	select X86_DMA_REMAP
 	select SWIOTLB
 	select MFD_STA2X11
 	select ARCH_REQUIRE_GPIOLIB
 	default n
 	---help---
 	  This adds support for boards based on the STA2X11 IO-Hub,
 	  a.k.a. "ConneXt". The chip is used in place of the standard
 	  PC chipset, so all "standard" peripherals are missing. If this
 	  option is selected the kernel will still be able to boot on
 	  standard PC machines.
 config X86_SUMMIT
 	bool "Summit/EXA (IBM x440)"
 	depends on X86_32_NON_STANDARD
 	---help---
 	  This option is needed for IBM systems that use the Summit/EXA chipset.
 	  In particular, it is needed for the x440.
 config X86_ES7000
 	bool "Unisys ES7000 IA32 series"
 	depends on X86_32_NON_STANDARD && X86_BIGSMP
 	---help---
 	  Support for Unisys ES7000 systems.  Say 'Y' here if this kernel is
 	  supposed to run on an IA32-based Unisys ES7000 system.
 config X86_32_IRIS
 	tristate "Eurobraille/Iris poweroff module"
 	depends on X86_32
 	---help---
 	  The Iris machines from EuroBraille do not have APM or ACPI support
 	  to shut themselves down properly.  A special I/O sequence is
 	  needed to do so, which is what this module does at
 	  kernel shutdown.
 	  This is only for Iris machines from EuroBraille.
 	  If unused, say N.
 config SCHED_OMIT_FRAME_POINTER
 	def_bool y
 	prompt "Single-depth WCHAN output"
 	depends on X86
 	---help---
 	  Calculate simpler /proc/<PID>/wchan values. If this option
 	  is disabled then wchan values will recurse back to the
 	  caller function. This provides more accurate wchan values,
 	  at the expense of slightly more scheduling overhead.
 	  If in doubt, say "Y".
 menuconfig HYPERVISOR_GUEST
 	bool "Linux guest support"
 	---help---
 	  Say Y here to enable options for running Linux under various hyper-
 	  visors. This option enables basic hypervisor detection and platform
 	  setup.
 	  If you say N, all options in this submenu will be skipped and
 	  disabled, and Linux guest support won't be built in.
 if HYPERVISOR_GUEST
 config PARAVIRT
 	bool "Enable paravirtualization code"
 	---help---
 	  This changes the kernel so it can modify itself when it is run
 	  under a hypervisor, potentially improving performance significantly
 	  over full virtualization.  However, when run without a hypervisor
 	  the kernel is theoretically slower and slightly larger.
 config PARAVIRT_DEBUG
 	bool "paravirt-ops debugging"
 	depends on PARAVIRT && DEBUG_KERNEL
 	---help---
 	  Enable to debug paravirt_ops internals.  Specifically, BUG if
 	  a paravirt_op is missing when it is called.
 config PARAVIRT_SPINLOCKS
 	bool "Paravirtualization layer for spinlocks"
 	depends on PARAVIRT && SMP
 	select UNINLINE_SPIN_UNLOCK
 	---help---
 	  Paravirtualized spinlocks allow a pvops backend to replace the
 	  spinlock implementation with something virtualization-friendly
 	  (for example, block the virtual CPU rather than spinning).
 	  Unfortunately the downside is an up to 5% performance hit on
 	  native kernels, with various workloads.
 	  If you are unsure how to answer this question, answer N.
 source "arch/x86/xen/Kconfig"
 config KVM_GUEST
 	bool "KVM Guest support (including kvmclock)"
 	depends on PARAVIRT
 	select PARAVIRT_CLOCK
 	default y
 	---help---
 	  This option enables various optimizations for running under the KVM
 	  hypervisor. It includes a paravirtualized clock, so that instead
 	  of relying on a PIT (or probably other) emulation by the
 	  underlying device model, the host provides the guest with
 	  timing infrastructure such as time of day, and system time
 config KVM_DEBUG_FS
 	bool "Enable debug information for KVM Guests in debugfs"
 	depends on KVM_GUEST && DEBUG_FS
 	default n
 	---help---
 	  This option enables collection of various statistics for KVM guest.
 	  Statistics are displayed in debugfs filesystem. Enabling this option
 	  may incur significant overhead.
 source "arch/x86/lguest/Kconfig"
 config PARAVIRT_TIME_ACCOUNTING
 	bool "Paravirtual steal time accounting"
 	depends on PARAVIRT
 	default n
 	---help---
 	  Select this option to enable fine granularity task steal time
 	  accounting. Time spent executing other tasks in parallel with
 	  the current vCPU is discounted from the vCPU power. To account for
 	  that, there can be a small performance impact.
 	  If in doubt, say N here.
 config PARAVIRT_CLOCK
 	bool
 endif #HYPERVISOR_GUEST
 config NO_BOOTMEM
 	def_bool y
 config MEMTEST
 	bool "Memtest"
 	---help---
 	  This option adds a kernel parameter 'memtest', which allows memtest
 	  to be set.
 	        memtest=0, mean disabled; -- default
 	        memtest=1, mean do 1 test pattern;
 	        ...
 	        memtest=4, mean do 4 test patterns.
 	  If you are unsure how to answer this question, answer N.
 config X86_SUMMIT_NUMA
 	def_bool y
 	depends on X86_32 && NUMA && X86_32_NON_STANDARD
 config X86_CYCLONE_TIMER
 	def_bool y
 	depends on X86_SUMMIT
 source "arch/x86/Kconfig.cpu"
 config HPET_TIMER
 	def_bool X86_64
 	prompt "HPET Timer Support" if X86_32
 	---help---
 	  Use the IA-PC HPET (High Precision Event Timer) to manage
 	  time in preference to the PIT and RTC, if a HPET is
 	  present.
 	  HPET is the next generation timer replacing legacy 8254s.
 	  The HPET provides a stable time base on SMP
 	  systems, unlike the TSC, but it is more expensive to access,
 	  as it is off-chip.  You can find the HPET spec at
 	  <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
 	  You can safely choose Y here.  However, HPET will only be
 	  activated if the platform and the BIOS support this feature.
 	  Otherwise the 8254 will be used for timing services.
 	  Choose N to continue using the legacy 8254 timer.
 config HPET_EMULATE_RTC
 	def_bool y
 	depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
 config APB_TIMER
        def_bool y if X86_INTEL_MID
        prompt "Intel MID APB Timer Support" if X86_INTEL_MID
        select DW_APB_TIMER
        depends on X86_INTEL_MID && SFI
        help
          APB timer is the replacement for 8254, HPET on X86 MID platforms.
          The APBT provides a stable time base on SMP
          systems, unlike the TSC, but it is more expensive to access,
          as it is off-chip. APB timers are always running regardless of CPU
          C states, they are used as per CPU clockevent device when possible.
 # Mark as expert because too many people got it wrong.
 # The code disables itself when not needed.
 config DMI
 	default y
 	bool "Enable DMI scanning" if EXPERT
 	---help---
 	  Enabled scanning of DMI to identify machine quirks. Say Y
 	  here unless you have verified that your setup is not
 	  affected by entries in the DMI blacklist. Required by PNP
 	  BIOS code.
 config GART_IOMMU
 	bool "GART IOMMU support" if EXPERT
 	default y
 	select SWIOTLB
 	depends on X86_64 && PCI && AMD_NB
 	---help---
 	  Support for full DMA access of devices with 32bit memory access only
 	  on systems with more than 3GB. This is usually needed for USB,
 	  sound, many IDE/SATA chipsets and some other devices.
 	  Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
 	  based hardware IOMMU and a software bounce buffer based IOMMU used
 	  on Intel systems and as fallback.
 	  The code is only active when needed (enough memory and limited
 	  device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
 	  too.
 config CALGARY_IOMMU
 	bool "IBM Calgary IOMMU support"
 	select SWIOTLB
 	depends on X86_64 && PCI
 	---help---
 	  Support for hardware IOMMUs in IBM's xSeries x366 and x460
 	  systems. Needed to run systems with more than 3GB of memory
 	  properly with 32-bit PCI devices that do not support DAC
 	  (Double Address Cycle). Calgary also supports bus level
 	  isolation, where all DMAs pass through the IOMMU.  This
 	  prevents them from going anywhere except their intended
 	  destination. This catches hard-to-find kernel bugs and
 	  mis-behaving drivers and devices that do not use the DMA-API
 	  properly to set up their DMA buffers.  The IOMMU can be
 	  turned off at boot time with the iommu=off parameter.
 	  Normally the kernel will make the right choice by itself.
 	  If unsure, say Y.
 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
 	def_bool y
 	prompt "Should Calgary be enabled by default?"
 	depends on CALGARY_IOMMU
 	---help---
 	  Should Calgary be enabled by default? if you choose 'y', Calgary
 	  will be used (if it exists). If you choose 'n', Calgary will not be
 	  used even if it exists. If you choose 'n' and would like to use
 	  Calgary anyway, pass 'iommu=calgary' on the kernel command line.
 	  If unsure, say Y.
 # need this always selected by IOMMU for the VIA workaround
 config SWIOTLB
 	def_bool y if X86_64
 	---help---
 	  Support for software bounce buffers used on x86-64 systems
 	  which don't have a hardware IOMMU. Using this PCI devices
 	  which can only access 32-bits of memory can be used on systems
 	  with more than 3 GB of memory.
 	  If unsure, say Y.
 config IOMMU_HELPER
 	def_bool y
 	depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU
 config MAXSMP
 	bool "Enable Maximum number of SMP Processors and NUMA Nodes"
 	depends on X86_64 && SMP && DEBUG_KERNEL
 	select CPUMASK_OFFSTACK
 	---help---
 	  Enable maximum number of CPUS and NUMA Nodes for this architecture.
 	  If unsure, say N.
 config NR_CPUS
 	int "Maximum number of CPUs" if SMP && !MAXSMP
 	range 2 8 if SMP && X86_32 && !X86_BIGSMP
 	range 2 512 if SMP && !MAXSMP
 	default "1" if !SMP
 	default "4096" if MAXSMP
 	default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
 	default "8" if SMP
 	---help---
 	  This allows you to specify the maximum number of CPUs which this
 	  kernel will support.  The maximum supported value is 512 and the
 	  minimum value which makes sense is 2.
 	  This is purely to save memory - each supported CPU adds
 	  approximately eight kilobytes to the kernel image.
 config SCHED_SMT
 	bool "SMT (Hyperthreading) scheduler support"
 	depends on X86_HT
 	---help---
 	  SMT scheduler support improves the CPU scheduler's decision making
 	  when dealing with Intel Pentium 4 chips with HyperThreading at a
 	  cost of slightly increased overhead in some places. If unsure say
 	  N here.
 config SCHED_MC
 	def_bool y
 	prompt "Multi-core scheduler support"
 	depends on X86_HT
 	---help---
 	  Multi-core scheduler support improves the CPU scheduler's decision
 	  making when dealing with multi-core CPU chips at a cost of slightly
 	  increased overhead in some places. If unsure say N here.
 source "kernel/Kconfig.preempt"
 config X86_UP_APIC
 	bool "Local APIC support on uniprocessors"
 	depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI
 	---help---
 	  A local APIC (Advanced Programmable Interrupt Controller) is an
 	  integrated interrupt controller in the CPU. If you have a single-CPU
 	  system which has a processor with a local APIC, you can say Y here to
 	  enable and use it. If you say Y here even though your machine doesn't
 	  have a local APIC, then the kernel will still run with no slowdown at
 	  all. The local APIC supports CPU-generated self-interrupts (timer,
 	  performance counters), and the NMI watchdog which detects hard
 	  lockups.
 config X86_UP_IOAPIC
 	bool "IO-APIC support on uniprocessors"
 	depends on X86_UP_APIC
 	---help---
 	  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
 	  SMP-capable replacement for PC-style interrupt controllers. Most
 	  SMP systems and many recent uniprocessor systems have one.
 	  If you have a single-CPU system with an IO-APIC, you can say Y here
 	  to use it. If you say Y here even though your machine doesn't have
 	  an IO-APIC, then the kernel will still run with no slowdown at all.
 config X86_LOCAL_APIC
 	def_bool y
 	depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
 config X86_IO_APIC
 	def_bool y
 	depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI
 config X86_VISWS_APIC
 	def_bool y
 	depends on X86_32 && X86_VISWS
 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
 	bool "Reroute for broken boot IRQs"
 	depends on X86_IO_APIC
 	---help---
 	  This option enables a workaround that fixes a source of
 	  spurious interrupts. This is recommended when threaded
 	  interrupt handling is used on systems where the generation of
 	  superfluous "boot interrupts" cannot be disabled.
 	  Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
 	  entry in the chipset's IO-APIC is masked (as, e.g. the RT
 	  kernel does during interrupt handling). On chipsets where this
 	  boot IRQ generation cannot be disabled, this workaround keeps
 	  the original IRQ line masked so that only the equivalent "boot
 	  IRQ" is delivered to the CPUs. The workaround also tells the
 	  kernel to set up the IRQ handler on the boot IRQ line. In this
 	  way only one interrupt is delivered to the kernel. Otherwise
 	  the spurious second interrupt may cause the kernel to bring
 	  down (vital) interrupt lines.
 	  Only affects "broken" chipsets. Interrupt sharing may be
 	  increased on these systems.
 config X86_MCE
 	bool "Machine Check / overheating reporting"
 	default y
 	---help---
 	  Machine Check support allows the processor to notify the
 	  kernel if it detects a problem (e.g. overheating, data corruption).
 	  The action the kernel takes depends on the severity of the problem,
 	  ranging from warning messages to halting the machine.
 config X86_MCE_INTEL
 	def_bool y
 	prompt "Intel MCE features"
 	depends on X86_MCE && X86_LOCAL_APIC
 	---help---
 	   Additional support for intel specific MCE features such as
 	   the thermal monitor.
 config X86_MCE_AMD
 	def_bool y
 	prompt "AMD MCE features"
 	depends on X86_MCE && X86_LOCAL_APIC
 	---help---
 	   Additional support for AMD specific MCE features such as
 	   the DRAM Error Threshold.
 config X86_ANCIENT_MCE
 	bool "Support for old Pentium 5 / WinChip machine checks"
 	depends on X86_32 && X86_MCE
 	---help---
 	  Include support for machine check handling on old Pentium 5 or WinChip
 	  systems. These typically need to be enabled explicitely on the command
 	  line.
 config X86_MCE_THRESHOLD
 	depends on X86_MCE_AMD || X86_MCE_INTEL
 	def_bool y
 config X86_MCE_INJECT
 	depends on X86_MCE
 	tristate "Machine check injector support"
 	---help---
 	  Provide support for injecting machine checks for testing purposes.
 	  If you don't know what a machine check is and you don't do kernel
 	  QA it is safe to say n.
 config X86_THERMAL_VECTOR
 	def_bool y
 	depends on X86_MCE_INTEL
 config VM86
 	bool "Enable VM86 support" if EXPERT
 	default y
 	depends on X86_32
 	---help---
 	  This option is required by programs like DOSEMU to run 16-bit legacy
 	  code on X86 processors. It also may be needed by software like
 	  XFree86 to initialize some video cards via BIOS. Disabling this
 	  option saves about 6k.
 config TOSHIBA
 	tristate "Toshiba Laptop support"
 	depends on X86_32
 	---help---
 	  This adds a driver to safely access the System Management Mode of
 	  the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
 	  not work on models with a Phoenix BIOS. The System Management Mode
 	  is used to set the BIOS and power saving options on Toshiba portables.
 	  For information on utilities to make use of this driver see the
 	  Toshiba Linux utilities web site at:
 	  <http://www.buzzard.org.uk/toshiba/>.
 	  Say Y if you intend to run this kernel on a Toshiba portable.
 	  Say N otherwise.
 config I8K
 	tristate "Dell laptop support"
 	select HWMON
 	---help---
 	  This adds a driver to safely access the System Management Mode
 	  of the CPU on the Dell Inspiron 8000. The System Management Mode
 	  is used to read cpu temperature and cooling fan status and to
 	  control the fans on the I8K portables.
 	  This driver has been tested only on the Inspiron 8000 but it may
 	  also work with other Dell laptops. You can force loading on other
 	  models by passing the parameter `force=1' to the module. Use at
 	  your own risk.
 	  For information on utilities to make use of this driver see the
 	  I8K Linux utilities web site at:
 	  <http://people.debian.org/~dz/i8k/>
 	  Say Y if you intend to run this kernel on a Dell Inspiron 8000.
 	  Say N otherwise.
 config X86_REBOOTFIXUPS
 	bool "Enable X86 board specific fixups for reboot"
 	depends on X86_32
 	---help---
 	  This enables chipset and/or board specific fixups to be done
 	  in order to get reboot to work correctly. This is only needed on
 	  some combinations of hardware and BIOS. The symptom, for which
 	  this config is intended, is when reboot ends with a stalled/hung
 	  system.
 	  Currently, the only fixup is for the Geode machines using
 	  CS5530A and CS5536 chipsets and the RDC R-321x SoC.
 	  Say Y if you want to enable the fixup. Currently, it's safe to
 	  enable this option even if you don't need it.
 	  Say N otherwise.
 config MICROCODE
 	tristate "CPU microcode loading support"
+	depends on CPU_SUP_AMD || CPU_SUP_INTEL
 	select FW_LOADER
 	---help---
 	  If you say Y here, you will be able to update the microcode on
 	  certain Intel and AMD processors. The Intel support is for the
 	  IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,
 	  Xeon etc. The AMD support is for families 0x10 and later. You will
 	  obviously need the actual microcode binary data itself which is not
 	  shipped with the Linux kernel.
 	  This option selects the general module only, you need to select
 	  at least one vendor specific module as well.
 	  To compile this driver as a module, choose M here: the module
 	  will be called microcode.
 config MICROCODE_INTEL
 	bool "Intel microcode loading support"
 	depends on MICROCODE
 	default MICROCODE
 	select FW_LOADER
 	---help---
 	  This options enables microcode patch loading support for Intel
 	  processors.
 	  For latest news and information on obtaining all the required
 	  Intel ingredients for this driver, check:
 	  <http://www.urbanmyth.org/microcode/>.
 config MICROCODE_AMD
 	bool "AMD microcode loading support"
 	depends on MICROCODE
 	select FW_LOADER
 	---help---
 	  If you select this option, microcode patch loading support for AMD
 	  processors will be enabled.
 config MICROCODE_OLD_INTERFACE
 	def_bool y
 	depends on MICROCODE
 config MICROCODE_INTEL_LIB
 	def_bool y
 	depends on MICROCODE_INTEL
 config MICROCODE_INTEL_EARLY
 	def_bool n
 config MICROCODE_AMD_EARLY
 	def_bool n
 config MICROCODE_EARLY
 	bool "Early load microcode"
 	depends on MICROCODE=y && BLK_DEV_INITRD
 	select MICROCODE_INTEL_EARLY if MICROCODE_INTEL
 	select MICROCODE_AMD_EARLY if MICROCODE_AMD
 	default y
 	help
 	  This option provides functionality to read additional microcode data
 	  at the beginning of initrd image. The data tells kernel to load
 	  microcode to CPU's as early as possible. No functional change if no
 	  microcode data is glued to the initrd, therefore it's safe to say Y.
 config X86_MSR
 	tristate "/dev/cpu/*/msr - Model-specific register support"
 	---help---
 	  This device gives privileged processes access to the x86
 	  Model-Specific Registers (MSRs).  It is a character device with
 	  major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
 	  MSR accesses are directed to a specific CPU on multi-processor
 	  systems.
 config X86_CPUID
 	tristate "/dev/cpu/*/cpuid - CPU information support"
 	---help---
 	  This device gives processes access to the x86 CPUID instruction to
 	  be executed on a specific processor.  It is a character device
 	  with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
 	  /dev/cpu/31/cpuid.
 choice
 	prompt "High Memory Support"
 	default HIGHMEM64G if X86_NUMAQ
 	default HIGHMEM4G
 	depends on X86_32
 config NOHIGHMEM
 	bool "off"
 	depends on !X86_NUMAQ
 	---help---
 	  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
 	  However, the address space of 32-bit x86 processors is only 4
 	  Gigabytes large. That means that, if you have a large amount of
 	  physical memory, not all of it can be "permanently mapped" by the
 	  kernel. The physical memory that's not permanently mapped is called
 	  "high memory".
 	  If you are compiling a kernel which will never run on a machine with
 	  more than 1 Gigabyte total physical RAM, answer "off" here (default
 	  choice and suitable for most users). This will result in a "3GB/1GB"
 	  split: 3GB are mapped so that each process sees a 3GB virtual memory
 	  space and the remaining part of the 4GB virtual memory space is used
 	  by the kernel to permanently map as much physical memory as
 	  possible.
 	  If the machine has between 1 and 4 Gigabytes physical RAM, then
 	  answer "4GB" here.
 	  If more than 4 Gigabytes is used then answer "64GB" here. This
 	  selection turns Intel PAE (Physical Address Extension) mode on.
 	  PAE implements 3-level paging on IA32 processors. PAE is fully
 	  supported by Linux, PAE mode is implemented on all recent Intel
 	  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
 	  then the kernel will not boot on CPUs that don't support PAE!
 	  The actual amount of total physical memory will either be
 	  auto detected or can be forced by using a kernel command line option
 	  such as "mem=256M". (Try "man bootparam" or see the documentation of
 	  your boot loader (lilo or loadlin) about how to pass options to the
 	  kernel at boot time.)
 	  If unsure, say "off".
 config HIGHMEM4G
 	bool "4GB"
 	depends on !X86_NUMAQ
 	---help---
 	  Select this if you have a 32-bit processor and between 1 and 4
 	  gigabytes of physical RAM.
 config HIGHMEM64G
 	bool "64GB"
 	depends on !M486
 	select X86_PAE
 	---help---
 	  Select this if you have a 32-bit processor and more than 4
 	  gigabytes of physical RAM.
 endchoice
 choice
 	prompt "Memory split" if EXPERT
 	default VMSPLIT_3G
 	depends on X86_32
 	---help---
 	  Select the desired split between kernel and user memory.
 	  If the address range available to the kernel is less than the
 	  physical memory installed, the remaining memory will be available
 	  as "high memory". Accessing high memory is a little more costly
 	  than low memory, as it needs to be mapped into the kernel first.
 	  Note that increasing the kernel address space limits the range
 	  available to user programs, making the address space there
 	  tighter.  Selecting anything other than the default 3G/1G split
 	  will also likely make your kernel incompatible with binary-only
 	  kernel modules.
 	  If you are not absolutely sure what you are doing, leave this
 	  option alone!
 	config VMSPLIT_3G
 		bool "3G/1G user/kernel split"
 	config VMSPLIT_3G_OPT
 		depends on !X86_PAE
 		bool "3G/1G user/kernel split (for full 1G low memory)"
 	config VMSPLIT_2G
 		bool "2G/2G user/kernel split"
 	config VMSPLIT_2G_OPT
 		depends on !X86_PAE
 		bool "2G/2G user/kernel split (for full 2G low memory)"
 	config VMSPLIT_1G
 		bool "1G/3G user/kernel split"
 endchoice
 config PAGE_OFFSET
 	hex
 	default 0xB0000000 if VMSPLIT_3G_OPT
 	default 0x80000000 if VMSPLIT_2G
 	default 0x78000000 if VMSPLIT_2G_OPT
 	default 0x40000000 if VMSPLIT_1G
 	default 0xC0000000
 	depends on X86_32
 config HIGHMEM
 	def_bool y
 	depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
 config X86_PAE
 	bool "PAE (Physical Address Extension) Support"
 	depends on X86_32 && !HIGHMEM4G
 	---help---
 	  PAE is required for NX support, and furthermore enables
 	  larger swapspace support for non-overcommit purposes. It
 	  has the cost of more pagetable lookup overhead, and also
 	  consumes more pagetable space per process.
 config ARCH_PHYS_ADDR_T_64BIT
 	def_bool y
 	depends on X86_64 || X86_PAE
 config ARCH_DMA_ADDR_T_64BIT
 	def_bool y
 	depends on X86_64 || HIGHMEM64G
 config DIRECT_GBPAGES
 	bool "Enable 1GB pages for kernel pagetables" if EXPERT
 	default y
 	depends on X86_64
 	---help---
 	  Allow the kernel linear mapping to use 1GB pages on CPUs that
 	  support it. This can improve the kernel's performance a tiny bit by
 	  reducing TLB pressure. If in doubt, say "Y".
 # Common NUMA Features
 config NUMA
 	bool "Numa Memory Allocation and Scheduler Support"
 	depends on SMP
 	depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI))
 	default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
 	---help---
 	  Enable NUMA (Non Uniform Memory Access) support.
 	  The kernel will try to allocate memory used by a CPU on the
 	  local memory controller of the CPU and add some more
 	  NUMA awareness to the kernel.
 	  For 64-bit this is recommended if the system is Intel Core i7
 	  (or later), AMD Opteron, or EM64T NUMA.
 	  For 32-bit this is only needed on (rare) 32-bit-only platforms
 	  that support NUMA topologies, such as NUMAQ / Summit, or if you
 	  boot a 32-bit kernel on a 64-bit NUMA platform.
 	  Otherwise, you should say N.
 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
 	depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
 config AMD_NUMA
 	def_bool y
 	prompt "Old style AMD Opteron NUMA detection"
 	depends on X86_64 && NUMA && PCI
 	---help---
 	  Enable AMD NUMA node topology detection.  You should say Y here if
 	  you have a multi processor AMD system. This uses an old method to
 	  read the NUMA configuration directly from the builtin Northbridge
 	  of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
 	  which also takes priority if both are compiled in.
 config X86_64_ACPI_NUMA
 	def_bool y
 	prompt "ACPI NUMA detection"
 	depends on X86_64 && NUMA && ACPI && PCI
 	select ACPI_NUMA
 	---help---
 	  Enable ACPI SRAT based node topology detection.
 # Some NUMA nodes have memory ranges that span
 # other nodes.  Even though a pfn is valid and
 # between a node's start and end pfns, it may not
 # reside on that node.  See memmap_init_zone()
 # for details.
 config NODES_SPAN_OTHER_NODES
 	def_bool y
 	depends on X86_64_ACPI_NUMA
 config NUMA_EMU
 	bool "NUMA emulation"
 	depends on NUMA
 	---help---
 	  Enable NUMA emulation. A flat machine will be split
 	  into virtual nodes when booted with "numa=fake=N", where N is the
 	  number of nodes. This is only useful for debugging.
 config NODES_SHIFT
 	int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
 	range 1 10
 	default "10" if MAXSMP
 	default "6" if X86_64
 	default "4" if X86_NUMAQ
 	default "3"
 	depends on NEED_MULTIPLE_NODES
 	---help---
 	  Specify the maximum number of NUMA Nodes available on the target
 	  system.  Increases memory reserved to accommodate various tables.
 config ARCH_HAVE_MEMORY_PRESENT
 	def_bool y
 	depends on X86_32 && DISCONTIGMEM
 config NEED_NODE_MEMMAP_SIZE
 	def_bool y
 	depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
 config ARCH_FLATMEM_ENABLE
 	def_bool y
 	depends on X86_32 && !NUMA
 config ARCH_DISCONTIGMEM_ENABLE
 	def_bool y
 	depends on NUMA && X86_32
 config ARCH_DISCONTIGMEM_DEFAULT
 	def_bool y
 	depends on NUMA && X86_32
 config ARCH_SPARSEMEM_ENABLE
 	def_bool y
 	depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
 	select SPARSEMEM_STATIC if X86_32
 	select SPARSEMEM_VMEMMAP_ENABLE if X86_64
 config ARCH_SPARSEMEM_DEFAULT
 	def_bool y
 	depends on X86_64
 config ARCH_SELECT_MEMORY_MODEL
 	def_bool y
 	depends on ARCH_SPARSEMEM_ENABLE
 config ARCH_MEMORY_PROBE
 	bool "Enable sysfs memory/probe interface"
 	depends on X86_64 && MEMORY_HOTPLUG
 	help
 	  This option enables a sysfs memory/probe interface for testing.
 	  See Documentation/memory-hotplug.txt for more information.
 	  If you are unsure how to answer this question, answer N.
 config ARCH_PROC_KCORE_TEXT
 	def_bool y
 	depends on X86_64 && PROC_KCORE
 config ILLEGAL_POINTER_VALUE
        hex
        default 0 if X86_32
        default 0xdead000000000000 if X86_64
 source "mm/Kconfig"
 config HIGHPTE
 	bool "Allocate 3rd-level pagetables from highmem"
 	depends on HIGHMEM
 	---help---
 	  The VM uses one page table entry for each page of physical memory.
 	  For systems with a lot of RAM, this can be wasteful of precious
 	  low memory.  Setting this option will put user-space page table
 	  entries in high memory.
 config X86_CHECK_BIOS_CORRUPTION
 	bool "Check for low memory corruption"
 	---help---
 	  Periodically check for memory corruption in low memory, which
 	  is suspected to be caused by BIOS.  Even when enabled in the
 	  configuration, it is disabled at runtime.  Enable it by
 	  setting "memory_corruption_check=1" on the kernel command
 	  line.  By default it scans the low 64k of memory every 60
 	  seconds; see the memory_corruption_check_size and
 	  memory_corruption_check_period parameters in
 	  Documentation/kernel-parameters.txt to adjust this.
 	  When enabled with the default parameters, this option has
 	  almost no overhead, as it reserves a relatively small amount
 	  of memory and scans it infrequently.  It both detects corruption
 	  and prevents it from affecting the running system.
 	  It is, however, intended as a diagnostic tool; if repeatable
 	  BIOS-originated corruption always affects the same memory,
 	  you can use memmap= to prevent the kernel from using that
 	  memory.
 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
 	bool "Set the default setting of memory_corruption_check"
 	depends on X86_CHECK_BIOS_CORRUPTION
 	default y
 	---help---
 	  Set whether the default state of memory_corruption_check is
 	  on or off.
 config X86_RESERVE_LOW
 	int "Amount of low memory, in kilobytes, to reserve for the BIOS"
 	default 64
 	range 4 640
 	---help---
 	  Specify the amount of low memory to reserve for the BIOS.
 	  The first page contains BIOS data structures that the kernel
 	  must not use, so that page must always be reserved.
 	  By default we reserve the first 64K of physical RAM, as a
 	  number of BIOSes are known to corrupt that memory range
 	  during events such as suspend/resume or monitor cable
 	  insertion, so it must not be used by the kernel.
 	  You can set this to 4 if you are absolutely sure that you
 	  trust the BIOS to get all its memory reservations and usages
 	  right.  If you know your BIOS have problems beyond the
 	  default 64K area, you can set this to 640 to avoid using the
 	  entire low memory range.
 	  If you have doubts about the BIOS (e.g. suspend/resume does
 	  not work or there's kernel crashes after certain hardware
 	  hotplug events) then you might want to enable
 	  X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
 	  typical corruption patterns.
 	  Leave this to the default value of 64 if you are unsure.
 config MATH_EMULATION
 	bool
 	prompt "Math emulation" if X86_32
 	---help---
 	  Linux can emulate a math coprocessor (used for floating point
 	  operations) if you don't have one. 486DX and Pentium processors have
 	  a math coprocessor built in, 486SX and 386 do not, unless you added
 	  a 487DX or 387, respectively. (The messages during boot time can
 	  give you some hints here ["man dmesg"].) Everyone needs either a
 	  coprocessor or this emulation.
 	  If you don't have a math coprocessor, you need to say Y here; if you
 	  say Y here even though you have a coprocessor, the coprocessor will
 	  be used nevertheless. (This behavior can be changed with the kernel
 	  command line option "no387", which comes handy if your coprocessor
 	  is broken. Try "man bootparam" or see the documentation of your boot
 	  loader (lilo or loadlin) about how to pass options to the kernel at
 	  boot time.) This means that it is a good idea to say Y here if you
 	  intend to use this kernel on different machines.
 	  More information about the internals of the Linux math coprocessor
 	  emulation can be found in <file:arch/x86/math-emu/README>.
 	  If you are not sure, say Y; apart from resulting in a 66 KB bigger
 	  kernel, it won't hurt.
 config MTRR
 	def_bool y
 	prompt "MTRR (Memory Type Range Register) support" if EXPERT
 	---help---
 	  On Intel P6 family processors (Pentium Pro, Pentium II and later)
 	  the Memory Type Range Registers (MTRRs) may be used to control
 	  processor access to memory ranges. This is most useful if you have
 	  a video (VGA) card on a PCI or AGP bus. Enabling write-combining
 	  allows bus write transfers to be combined into a larger transfer
 	  before bursting over the PCI/AGP bus. This can increase performance
 	  of image write operations 2.5 times or more. Saying Y here creates a
 	  /proc/mtrr file which may be used to manipulate your processor's
 	  MTRRs. Typically the X server should use this.
 	  This code has a reasonably generic interface so that similar
 	  control registers on other processors can be easily supported
 	  as well:
 	  The Cyrix 6x86, 6x86MX and M II processors have Address Range
 	  Registers (ARRs) which provide a similar functionality to MTRRs. For
 	  these, the ARRs are used to emulate the MTRRs.
 	  The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
 	  MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
 	  write-combining. All of these processors are supported by this code
 	  and it makes sense to say Y here if you have one of them.
 	  Saying Y here also fixes a problem with buggy SMP BIOSes which only
 	  set the MTRRs for the boot CPU and not for the secondary CPUs. This
 	  can lead to all sorts of problems, so it's good to say Y here.
 	  You can safely say Y even if your machine doesn't have MTRRs, you'll
 	  just add about 9 KB to your kernel.
 	  See <file:Documentation/x86/mtrr.txt> for more information.
 config MTRR_SANITIZER
 	def_bool y
 	prompt "MTRR cleanup support"
 	depends on MTRR
 	---help---
 	  Convert MTRR layout from continuous to discrete, so X drivers can
 	  add writeback entries.
 	  Can be disabled with disable_mtrr_cleanup on the kernel command line.
 	  The largest mtrr entry size for a continuous block can be set with
 	  mtrr_chunk_size.
 	  If unsure, say Y.
 config MTRR_SANITIZER_ENABLE_DEFAULT
 	int "MTRR cleanup enable value (0-1)"
 	range 0 1
 	default "0"
 	depends on MTRR_SANITIZER
 	---help---
 	  Enable mtrr cleanup default value
 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
 	int "MTRR cleanup spare reg num (0-7)"
 	range 0 7
 	default "1"
 	depends on MTRR_SANITIZER
 	---help---
 	  mtrr cleanup spare entries default, it can be changed via
 	  mtrr_spare_reg_nr=N on the kernel command line.
 config X86_PAT
 	def_bool y
 	prompt "x86 PAT support" if EXPERT
 	depends on MTRR
 	---help---
 	  Use PAT attributes to setup page level cache control.
 	  PATs are the modern equivalents of MTRRs and are much more
 	  flexible than MTRRs.
 	  Say N here if you see bootup problems (boot crash, boot hang,
 	  spontaneous reboots) or a non-working video driver.
 	  If unsure, say Y.
 config ARCH_USES_PG_UNCACHED
 	def_bool y
 	depends on X86_PAT
 config ARCH_RANDOM
 	def_bool y
 	prompt "x86 architectural random number generator" if EXPERT
 	---help---
 	  Enable the x86 architectural RDRAND instruction
 	  (Intel Bull Mountain technology) to generate random numbers.
 	  If supported, this is a high bandwidth, cryptographically
 	  secure hardware random number generator.
 config X86_SMAP
 	def_bool y
 	prompt "Supervisor Mode Access Prevention" if EXPERT
 	---help---
 	  Supervisor Mode Access Prevention (SMAP) is a security
 	  feature in newer Intel processors.  There is a small
 	  performance cost if this enabled and turned on; there is
 	  also a small increase in the kernel size if this is enabled.
 	  If unsure, say Y.
 config EFI
 	bool "EFI runtime service support"
 	depends on ACPI
 	select UCS2_STRING
 	---help---
 	  This enables the kernel to use EFI runtime services that are
 	  available (such as the EFI variable services).
 	  This option is only useful on systems that have EFI firmware.
 	  In addition, you should use the latest ELILO loader available
 	  at <http://elilo.sourceforge.net> in order to take advantage
 	  of EFI runtime services. However, even with this option, the
 	  resultant kernel should continue to boot on existing non-EFI
 	  platforms.
 config EFI_STUB
        bool "EFI stub support"
        depends on EFI
        ---help---
           This kernel feature allows a bzImage to be loaded directly
 	  by EFI firmware without the use of a bootloader.
 	  See Documentation/x86/efi-stub.txt for more information.
 config SECCOMP
 	def_bool y
 	prompt "Enable seccomp to safely compute untrusted bytecode"
 	---help---
 	  This kernel feature is useful for number crunching applications
 	  that may need to compute untrusted bytecode during their
 	  execution. By using pipes or other transports made available to
 	  the process as file descriptors supporting the read/write
 	  syscalls, it's possible to isolate those applications in
 	  their own address space using seccomp. Once seccomp is
 	  enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
 	  and the task is only allowed to execute a few safe syscalls
 	  defined by each seccomp mode.
 	  If unsure, say Y. Only embedded should say N here.
 config CC_STACKPROTECTOR
 	bool "Enable -fstack-protector buffer overflow detection"
 	---help---
 	  This option turns on the -fstack-protector GCC feature. This
 	  feature puts, at the beginning of functions, a canary value on
 	  the stack just before the return address, and validates
 	  the value just before actually returning.  Stack based buffer
 	  overflows (that need to overwrite this return address) now also
 	  overwrite the canary, which gets detected and the attack is then
 	  neutralized via a kernel panic.
 	  This feature requires gcc version 4.2 or above, or a distribution
 	  gcc with the feature backported. Older versions are automatically
 	  detected and for those versions, this configuration option is
 	  ignored. (and a warning is printed during bootup)
 source kernel/Kconfig.hz
 config KEXEC
 	bool "kexec system call"
 	---help---
 	  kexec is a system call that implements the ability to shutdown your
 	  current kernel, and to start another kernel.  It is like a reboot
 	  but it is independent of the system firmware.   And like a reboot
 	  you can start any kernel with it, not just Linux.
 	  The name comes from the similarity to the exec system call.
 	  It is an ongoing process to be certain the hardware in a machine
 	  is properly shutdown, so do not be surprised if this code does not
 	  initially work for you.  As of this writing the exact hardware
 	  interface is strongly in flux, so no good recommendation can be
 	  made.
 config CRASH_DUMP
 	bool "kernel crash dumps"
 	depends on X86_64 || (X86_32 && HIGHMEM)
 	---help---
 	  Generate crash dump after being started by kexec.
 	  This should be normally only set in special crash dump kernels
 	  which are loaded in the main kernel with kexec-tools into
 	  a specially reserved region and then later executed after
 	  a crash by kdump/kexec. The crash dump kernel must be compiled
 	  to a memory address not used by the main kernel or BIOS using
 	  PHYSICAL_START, or it must be built as a relocatable image
 	  (CONFIG_RELOCATABLE=y).
 	  For more details see Documentation/kdump/kdump.txt
 config KEXEC_JUMP
 	bool "kexec jump"
 	depends on KEXEC && HIBERNATION
 	---help---
 	  Jump between original kernel and kexeced kernel and invoke
 	  code in physical address mode via KEXEC
 config PHYSICAL_START
 	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
 	default "0x1000000"
 	---help---
 	  This gives the physical address where the kernel is loaded.
 	  If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
 	  bzImage will decompress itself to above physical address and
 	  run from there. Otherwise, bzImage will run from the address where
 	  it has been loaded by the boot loader and will ignore above physical
 	  address.
 	  In normal kdump cases one does not have to set/change this option
 	  as now bzImage can be compiled as a completely relocatable image
 	  (CONFIG_RELOCATABLE=y) and be used to load and run from a different
 	  address. This option is mainly useful for the folks who don't want
 	  to use a bzImage for capturing the crash dump and want to use a
 	  vmlinux instead. vmlinux is not relocatable hence a kernel needs
 	  to be specifically compiled to run from a specific memory area
 	  (normally a reserved region) and this option comes handy.
 	  So if you are using bzImage for capturing the crash dump,
 	  leave the value here unchanged to 0x1000000 and set
 	  CONFIG_RELOCATABLE=y.  Otherwise if you plan to use vmlinux
 	  for capturing the crash dump change this value to start of
 	  the reserved region.  In other words, it can be set based on
 	  the "X" value as specified in the "crashkernel=YM@XM"
 	  command line boot parameter passed to the panic-ed
 	  kernel. Please take a look at Documentation/kdump/kdump.txt
 	  for more details about crash dumps.
 	  Usage of bzImage for capturing the crash dump is recommended as
 	  one does not have to build two kernels. Same kernel can be used
 	  as production kernel and capture kernel. Above option should have
 	  gone away after relocatable bzImage support is introduced. But it
 	  is present because there are users out there who continue to use
 	  vmlinux for dump capture. This option should go away down the
 	  line.
 	  Don't change this unless you know what you are doing.
 config RELOCATABLE
 	bool "Build a relocatable kernel"
 	default y
 	---help---
 	  This builds a kernel image that retains relocation information
 	  so it can be loaded someplace besides the default 1MB.
 	  The relocations tend to make the kernel binary about 10% larger,
 	  but are discarded at runtime.
 	  One use is for the kexec on panic case where the recovery kernel
 	  must live at a different physical address than the primary
 	  kernel.
 	  Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
 	  it has been loaded at and the compile time physical address
 	  (CONFIG_PHYSICAL_START) is ignored.
 # Relocation on x86-32 needs some additional build support
 config X86_NEED_RELOCS
 	def_bool y
 	depends on X86_32 && RELOCATABLE
 config PHYSICAL_ALIGN
 	hex "Alignment value to which kernel should be aligned"
 	default "0x1000000"
 	range 0x2000 0x1000000 if X86_32
 	range 0x200000 0x1000000 if X86_64
 	---help---
 	  This value puts the alignment restrictions on physical address
 	  where kernel is loaded and run from. Kernel is compiled for an
 	  address which meets above alignment restriction.
 	  If bootloader loads the kernel at a non-aligned address and
 	  CONFIG_RELOCATABLE is set, kernel will move itself to nearest
 	  address aligned to above value and run from there.
 	  If bootloader loads the kernel at a non-aligned address and
 	  CONFIG_RELOCATABLE is not set, kernel will ignore the run time
 	  load address and decompress itself to the address it has been
 	  compiled for and run from there. The address for which kernel is
 	  compiled already meets above alignment restrictions. Hence the
 	  end result is that kernel runs from a physical address meeting
 	  above alignment restrictions.
 	  On 32-bit this value must be a multiple of 0x2000. On 64-bit
 	  this value must be a multiple of 0x200000.
 	  Don't change this unless you know what you are doing.
 config HOTPLUG_CPU
 	bool "Support for hot-pluggable CPUs"
 	depends on SMP
 	---help---
 	  Say Y here to allow turning CPUs off and on. CPUs can be
 	  controlled through /sys/devices/system/cpu.
 	  ( Note: power management support will enable this option
 	    automatically on SMP systems. )
 	  Say N if you want to disable CPU hotplug.
 config BOOTPARAM_HOTPLUG_CPU0
 	bool "Set default setting of cpu0_hotpluggable"
 	default n
 	depends on HOTPLUG_CPU
 	---help---
 	  Set whether default state of cpu0_hotpluggable is on or off.
 	  Say Y here to enable CPU0 hotplug by default. If this switch
 	  is turned on, there is no need to give cpu0_hotplug kernel
 	  parameter and the CPU0 hotplug feature is enabled by default.
 	  Please note: there are two known CPU0 dependencies if you want
 	  to enable the CPU0 hotplug feature either by this switch or by
 	  cpu0_hotplug kernel parameter.
 	  First, resume from hibernate or suspend always starts from CPU0.
 	  So hibernate and suspend are prevented if CPU0 is offline.
 	  Second dependency is PIC interrupts always go to CPU0. CPU0 can not
 	  offline if any interrupt can not migrate out of CPU0. There may
 	  be other CPU0 dependencies.
 	  Please make sure the dependencies are under your control before
 	  you enable this feature.
 	  Say N if you don't want to enable CPU0 hotplug feature by default.
 	  You still can enable the CPU0 hotplug feature at boot by kernel
 	  parameter cpu0_hotplug.
 config DEBUG_HOTPLUG_CPU0
 	def_bool n
 	prompt "Debug CPU0 hotplug"
 	depends on HOTPLUG_CPU
 	---help---
 	  Enabling this option offlines CPU0 (if CPU0 can be offlined) as
 	  soon as possible and boots up userspace with CPU0 offlined. User
 	  can online CPU0 back after boot time.
 	  To debug CPU0 hotplug, you need to enable CPU0 offline/online
 	  feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
 	  compilation or giving cpu0_hotplug kernel parameter at boot.
 	  If unsure, say N.
 config COMPAT_VDSO
 	def_bool y
 	prompt "Compat VDSO support"
 	depends on X86_32 || IA32_EMULATION
 	---help---
 	  Map the 32-bit VDSO to the predictable old-style address too.
 	  Say N here if you are running a sufficiently recent glibc
 	  version (2.3.3 or later), to remove the high-mapped
 	  VDSO mapping and to exclusively use the randomized VDSO.
 	  If unsure, say Y.
 config CMDLINE_BOOL
 	bool "Built-in kernel command line"
 	---help---
 	  Allow for specifying boot arguments to the kernel at
 	  build time.  On some systems (e.g. embedded ones), it is
 	  necessary or convenient to provide some or all of the
 	  kernel boot arguments with the kernel itself (that is,
 	  to not rely on the boot loader to provide them.)
 	  To compile command line arguments into the kernel,
 	  set this option to 'Y', then fill in the
 	  the boot arguments in CONFIG_CMDLINE.
 	  Systems with fully functional boot loaders (i.e. non-embedded)
 	  should leave this option set to 'N'.
 config CMDLINE
 	string "Built-in kernel command string"
 	depends on CMDLINE_BOOL
 	default ""
 	---help---
 	  Enter arguments here that should be compiled into the kernel
 	  image and used at boot time.  If the boot loader provides a
 	  command line at boot time, it is appended to this string to
 	  form the full kernel command line, when the system boots.
 	  However, you can use the CONFIG_CMDLINE_OVERRIDE option to
 	  change this behavior.
 	  In most cases, the command line (whether built-in or provided
 	  by the boot loader) should specify the device for the root
 	  file system.
 config CMDLINE_OVERRIDE
 	bool "Built-in command line overrides boot loader arguments"
 	depends on CMDLINE_BOOL
 	---help---
 	  Set this option to 'Y' to have the kernel ignore the boot loader
 	  command line, and use ONLY the built-in command line.
 	  This is used to work around broken boot loaders.  This should
 	  be set to 'N' under normal conditions.
 endmenu
 config ARCH_ENABLE_MEMORY_HOTPLUG
 	def_bool y
 	depends on X86_64 || (X86_32 && HIGHMEM)
 config ARCH_ENABLE_MEMORY_HOTREMOVE
 	def_bool y
 	depends on MEMORY_HOTPLUG
 config USE_PERCPU_NUMA_NODE_ID
 	def_bool y
 	depends on NUMA
 menu "Power management and ACPI options"
 config ARCH_HIBERNATION_HEADER
 	def_bool y
 	depends on X86_64 && HIBERNATION
 source "kernel/power/Kconfig"
 source "drivers/acpi/Kconfig"
 source "drivers/sfi/Kconfig"
 config X86_APM_BOOT
 	def_bool y
 	depends on APM
 menuconfig APM
 	tristate "APM (Advanced Power Management) BIOS support"
 	depends on X86_32 && PM_SLEEP
 	---help---
 	  APM is a BIOS specification for saving power using several different
 	  techniques. This is mostly useful for battery powered laptops with
 	  APM compliant BIOSes. If you say Y here, the system time will be
 	  reset after a RESUME operation, the /proc/apm device will provide
 	  battery status information, and user-space programs will receive
 	  notification of APM "events" (e.g. battery status change).
 	  If you select "Y" here, you can disable actual use of the APM
 	  BIOS by passing the "apm=off" option to the kernel at boot time.
 	  Note that the APM support is almost completely disabled for
 	  machines with more than one CPU.
 	  In order to use APM, you will need supporting software. For location
 	  and more information, read <file:Documentation/power/apm-acpi.txt>
 	  and the Battery Powered Linux mini-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  This driver does not spin down disk drives (see the hdparm(8)
 	  manpage ("man 8 hdparm") for that), and it doesn't turn off
 	  VESA-compliant "green" monitors.
 	  This driver does not support the TI 4000M TravelMate and the ACER
 	  486/DX4/75 because they don't have compliant BIOSes. Many "green"
 	  desktop machines also don't have compliant BIOSes, and this driver
 	  may cause those machines to panic during the boot phase.
 	  Generally, if you don't have a battery in your machine, there isn't
 	  much point in using this driver and you should say N. If you get
 	  random kernel OOPSes or reboots that don't seem to be related to
 	  anything, try disabling/enabling this option (or disabling/enabling
 	  APM in your BIOS).
 	  Some other things you should try when experiencing seemingly random,
 	  "weird" problems:
 	  1) make sure that you have enough swap space and that it is
 	  enabled.
 	  2) pass the "no-hlt" option to the kernel
 	  3) switch on floating point emulation in the kernel and pass
 	  the "no387" option to the kernel
 	  4) pass the "floppy=nodma" option to the kernel
 	  5) pass the "mem=4M" option to the kernel (thereby disabling
 	  all but the first 4 MB of RAM)
 	  6) make sure that the CPU is not over clocked.
 	  7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
 	  8) disable the cache from your BIOS settings
 	  9) install a fan for the video card or exchange video RAM
 	  10) install a better fan for the CPU
 	  11) exchange RAM chips
 	  12) exchange the motherboard.
 	  To compile this driver as a module, choose M here: the
 	  module will be called apm.
 if APM
 config APM_IGNORE_USER_SUSPEND
 	bool "Ignore USER SUSPEND"
 	---help---
 	  This option will ignore USER SUSPEND requests. On machines with a
 	  compliant APM BIOS, you want to say N. However, on the NEC Versa M
 	  series notebooks, it is necessary to say Y because of a BIOS bug.
 config APM_DO_ENABLE
 	bool "Enable PM at boot time"
 	---help---
 	  Enable APM features at boot time. From page 36 of the APM BIOS
 	  specification: "When disabled, the APM BIOS does not automatically
 	  power manage devices, enter the Standby State, enter the Suspend
 	  State, or take power saving steps in response to CPU Idle calls."
 	  This driver will make CPU Idle calls when Linux is idle (unless this
 	  feature is turned off -- see "Do CPU IDLE calls", below). This
 	  should always save battery power, but more complicated APM features
 	  will be dependent on your BIOS implementation. You may need to turn
 	  this option off if your computer hangs at boot time when using APM
 	  support, or if it beeps continuously instead of suspending. Turn
 	  this off if you have a NEC UltraLite Versa 33/C or a Toshiba
 	  T400CDT. This is off by default since most machines do fine without
 	  this feature.
 config APM_CPU_IDLE
 	depends on CPU_IDLE
 	bool "Make CPU Idle calls when idle"
 	---help---
 	  Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
 	  On some machines, this can activate improved power savings, such as
 	  a slowed CPU clock rate, when the machine is idle. These idle calls
 	  are made after the idle loop has run for some length of time (e.g.,
 	  333 mS). On some machines, this will cause a hang at boot time or
 	  whenever the CPU becomes idle. (On machines with more than one CPU,
 	  this option does nothing.)
 config APM_DISPLAY_BLANK
 	bool "Enable console blanking using APM"
 	---help---
 	  Enable console blanking using the APM. Some laptops can use this to
 	  turn off the LCD backlight when the screen blanker of the Linux
 	  virtual console blanks the screen. Note that this is only used by
 	  the virtual console screen blanker, and won't turn off the backlight
 	  when using the X Window system. This also doesn't have anything to
 	  do with your VESA-compliant power-saving monitor. Further, this
 	  option doesn't work for all laptops -- it might not turn off your
 	  backlight at all, or it might print a lot of errors to the console,
 	  especially if you are using gpm.
 config APM_ALLOW_INTS
 	bool "Allow interrupts during APM BIOS calls"
 	---help---
 	  Normally we disable external interrupts while we are making calls to
 	  the APM BIOS as a measure to lessen the effects of a badly behaving
 	  BIOS implementation.  The BIOS should reenable interrupts if it
 	  needs to.  Unfortunately, some BIOSes do not -- especially those in
 	  many of the newer IBM Thinkpads.  If you experience hangs when you
 	  suspend, try setting this to Y.  Otherwise, say N.
 endif # APM
 source "drivers/cpufreq/Kconfig"
 source "drivers/cpuidle/Kconfig"
 source "drivers/idle/Kconfig"
 endmenu
 menu "Bus options (PCI etc.)"
 config PCI
 	bool "PCI support"
 	default y
 	---help---
 	  Find out whether you have a PCI motherboard. PCI is the name of a
 	  bus system, i.e. the way the CPU talks to the other stuff inside
 	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
 	  VESA. If you have PCI, say Y, otherwise N.
 choice
 	prompt "PCI access mode"
 	depends on X86_32 && PCI
 	default PCI_GOANY
 	---help---
 	  On PCI systems, the BIOS can be used to detect the PCI devices and
 	  determine their configuration. However, some old PCI motherboards
 	  have BIOS bugs and may crash if this is done. Also, some embedded
 	  PCI-based systems don't have any BIOS at all. Linux can also try to
 	  detect the PCI hardware directly without using the BIOS.
 	  With this option, you can specify how Linux should detect the
 	  PCI devices. If you choose "BIOS", the BIOS will be used,
 	  if you choose "Direct", the BIOS won't be used, and if you
 	  choose "MMConfig", then PCI Express MMCONFIG will be used.
 	  If you choose "Any", the kernel will try MMCONFIG, then the
 	  direct access method and falls back to the BIOS if that doesn't
 	  work. If unsure, go with the default, which is "Any".
 config PCI_GOBIOS
 	bool "BIOS"
 config PCI_GOMMCONFIG
 	bool "MMConfig"
 config PCI_GODIRECT
 	bool "Direct"
 config PCI_GOOLPC
 	bool "OLPC XO-1"
 	depends on OLPC
 config PCI_GOANY
 	bool "Any"
 endchoice
 config PCI_BIOS
 	def_bool y
 	depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
 config PCI_DIRECT
 	def_bool y
 	depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
 config PCI_MMCONFIG
 	def_bool y
 	depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
 config PCI_OLPC
 	def_bool y
 	depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
 config PCI_XEN
 	def_bool y
 	depends on PCI && XEN
 	select SWIOTLB_XEN
 config PCI_DOMAINS
 	def_bool y
 	depends on PCI
 config PCI_MMCONFIG
 	bool "Support mmconfig PCI config space access"
 	depends on X86_64 && PCI && ACPI
 config PCI_CNB20LE_QUIRK
 	bool "Read CNB20LE Host Bridge Windows" if EXPERT
 	depends on PCI
 	help
 	  Read the PCI windows out of the CNB20LE host bridge. This allows
 	  PCI hotplug to work on systems with the CNB20LE chipset which do
 	  not have ACPI.
 	  There's no public spec for this chipset, and this functionality
 	  is known to be incomplete.
 	  You should say N unless you know you need this.
 source "drivers/pci/pcie/Kconfig"
 source "drivers/pci/Kconfig"
 # x86_64 have no ISA slots, but can have ISA-style DMA.
 config ISA_DMA_API
 	bool "ISA-style DMA support" if (X86_64 && EXPERT)
 	default y
 	help
 	  Enables ISA-style DMA support for devices requiring such controllers.
 	  If unsure, say Y.
 if X86_32
 config ISA
 	bool "ISA support"
 	---help---
 	  Find out whether you have ISA slots on your motherboard.  ISA is the
 	  name of a bus system, i.e. the way the CPU talks to the other stuff
 	  inside your box.  Other bus systems are PCI, EISA, MicroChannel
 	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
 	  newer boards don't support it.  If you have ISA, say Y, otherwise N.
 config EISA
 	bool "EISA support"
 	depends on ISA
 	---help---
 	  The Extended Industry Standard Architecture (EISA) bus was
 	  developed as an open alternative to the IBM MicroChannel bus.
 	  The EISA bus provided some of the features of the IBM MicroChannel
 	  bus while maintaining backward compatibility with cards made for
 	  the older ISA bus.  The EISA bus saw limited use between 1988 and
 	  1995 when it was made obsolete by the PCI bus.
 	  Say Y here if you are building a kernel for an EISA-based machine.
 	  Otherwise, say N.
 source "drivers/eisa/Kconfig"
 config SCx200
 	tristate "NatSemi SCx200 support"
 	---help---
 	  This provides basic support for National Semiconductor's
 	  (now AMD's) Geode processors.  The driver probes for the
 	  PCI-IDs of several on-chip devices, so its a good dependency
 	  for other scx200_* drivers.
 	  If compiled as a module, the driver is named scx200.
 config SCx200HR_TIMER
 	tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
 	depends on SCx200
 	default y
 	---help---
 	  This driver provides a clocksource built upon the on-chip
 	  27MHz high-resolution timer.  Its also a workaround for
 	  NSC Geode SC-1100's buggy TSC, which loses time when the
 	  processor goes idle (as is done by the scheduler).  The
 	  other workaround is idle=poll boot option.
 config OLPC
 	bool "One Laptop Per Child support"
 	depends on !X86_PAE
 	select GPIOLIB
 	select OF
 	select OF_PROMTREE
 	select IRQ_DOMAIN
 	---help---
 	  Add support for detecting the unique features of the OLPC
 	  XO hardware.
 config OLPC_XO1_PM
 	bool "OLPC XO-1 Power Management"
 	depends on OLPC && MFD_CS5535 && PM_SLEEP
 	select MFD_CORE
 	---help---
 	  Add support for poweroff and suspend of the OLPC XO-1 laptop.
 config OLPC_XO1_RTC
 	bool "OLPC XO-1 Real Time Clock"
 	depends on OLPC_XO1_PM && RTC_DRV_CMOS
 	---help---
 	  Add support for the XO-1 real time clock, which can be used as a
 	  programmable wakeup source.
 config OLPC_XO1_SCI
 	bool "OLPC XO-1 SCI extras"
 	depends on OLPC && OLPC_XO1_PM
 	depends on INPUT=y
 	select POWER_SUPPLY
 	select GPIO_CS5535
 	select MFD_CORE
 	---help---
 	  Add support for SCI-based features of the OLPC XO-1 laptop:
 	   - EC-driven system wakeups
 	   - Power button
 	   - Ebook switch
 	   - Lid switch
 	   - AC adapter status updates
 	   - Battery status updates
 config OLPC_XO15_SCI
 	bool "OLPC XO-1.5 SCI extras"
 	depends on OLPC && ACPI
 	select POWER_SUPPLY
 	---help---
 	  Add support for SCI-based features of the OLPC XO-1.5 laptop:
 	   - EC-driven system wakeups
 	   - AC adapter status updates
 	   - Battery status updates
 config ALIX
 	bool "PCEngines ALIX System Support (LED setup)"
 	select GPIOLIB
 	---help---
 	  This option enables system support for the PCEngines ALIX.
 	  At present this just sets up LEDs for GPIO control on
 	  ALIX2/3/6 boards.  However, other system specific setup should
 	  get added here.
 	  Note: You must still enable the drivers for GPIO and LED support
 	  (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
 	  Note: You have to set alix.force=1 for boards with Award BIOS.
 config NET5501
 	bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
 	select GPIOLIB
 	---help---
 	  This option enables system support for the Soekris Engineering net5501.
 config GEOS
 	bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
 	select GPIOLIB
 	depends on DMI
 	---help---
 	  This option enables system support for the Traverse Technologies GEOS.
 config TS5500
 	bool "Technologic Systems TS-5500 platform support"
 	depends on MELAN
 	select CHECK_SIGNATURE
 	select NEW_LEDS
 	select LEDS_CLASS
 	---help---
 	  This option enables system support for the Technologic Systems TS-5500.
 endif # X86_32
 config AMD_NB
 	def_bool y
 	depends on CPU_SUP_AMD && PCI
 source "drivers/pcmcia/Kconfig"
 source "drivers/pci/hotplug/Kconfig"
 config RAPIDIO
 	tristate "RapidIO support"
 	depends on PCI
 	default n
 	help
 	  If enabled this option will include drivers and the core
 	  infrastructure code to support RapidIO interconnect devices.
 source "drivers/rapidio/Kconfig"
 config X86_SYSFB
 	bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
 	help
 	  Firmwares often provide initial graphics framebuffers so the BIOS,
 	  bootloader or kernel can show basic video-output during boot for
 	  user-guidance and debugging. Historically, x86 used the VESA BIOS
 	  Extensions and EFI-framebuffers for this, which are mostly limited
 	  to x86.
 	  This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
 	  framebuffers so the new generic system-framebuffer drivers can be
 	  used on x86. If the framebuffer is not compatible with the generic
 	  modes, it is adverticed as fallback platform framebuffer so legacy
 	  drivers like efifb, vesafb and uvesafb can pick it up.
 	  If this option is not selected, all system framebuffers are always
 	  marked as fallback platform framebuffers as usual.
 	  Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
 	  not be able to pick up generic system framebuffers if this option
 	  is selected. You are highly encouraged to enable simplefb as
 	  replacement if you select this option. simplefb can correctly deal
 	  with generic system framebuffers. But you should still keep vesafb
 	  and others enabled as fallback if a system framebuffer is
 	  incompatible with simplefb.
 	  If unsure, say Y.
 endmenu
 menu "Executable file formats / Emulations"
 source "fs/Kconfig.binfmt"
 config IA32_EMULATION
 	bool "IA32 Emulation"
 	depends on X86_64
 	select BINFMT_ELF
 	select COMPAT_BINFMT_ELF
 	select HAVE_UID16
 	---help---
 	  Include code to run legacy 32-bit programs under a
 	  64-bit kernel. You should likely turn this on, unless you're
 	  100% sure that you don't have any 32-bit programs left.
 config IA32_AOUT
 	tristate "IA32 a.out support"
 	depends on IA32_EMULATION
 	---help---
 	  Support old a.out binaries in the 32bit emulation.
 config X86_X32
 	bool "x32 ABI for 64-bit mode"
 	depends on X86_64 && IA32_EMULATION
 	---help---
 	  Include code to run binaries for the x32 native 32-bit ABI
 	  for 64-bit processors.  An x32 process gets access to the
 	  full 64-bit register file and wide data path while leaving
 	  pointers at 32 bits for smaller memory footprint.
 	  You will need a recent binutils (2.22 or later) with
 	  elf32_x86_64 support enabled to compile a kernel with this
 	  option set.
 config COMPAT
 	def_bool y
 	depends on IA32_EMULATION || X86_X32
 	select ARCH_WANT_OLD_COMPAT_IPC
 if COMPAT
 config COMPAT_FOR_U64_ALIGNMENT
 	def_bool y
 config SYSVIPC_COMPAT
 	def_bool y
 	depends on SYSVIPC
 config KEYS_COMPAT
 	def_bool y
 	depends on KEYS
 endif
 endmenu
 config HAVE_ATOMIC_IOMAP
 	def_bool y
 	depends on X86_32
 config X86_DEV_DMA_OPS
 	bool
 	depends on X86_64 || STA2X11
 config X86_DMA_REMAP
 	bool
 	depends on STA2X11
 source "net/Kconfig"
 source "drivers/Kconfig"
 source "drivers/firmware/Kconfig"
 source "fs/Kconfig"
 source "arch/x86/Kconfig.debug"
 source "security/Kconfig"
 source "crypto/Kconfig"
 source "arch/x86/kvm/Kconfig"
 source "lib/Kconfig"

1	/*	1	/*
2	* This file is subject to the terms and conditions of the GNU General Public	2	* This file is subject to the terms and conditions of the GNU General Public
3	* License. See the file "COPYING" in the main directory of this archive	3	* License. See the file "COPYING" in the main directory of this archive
4	* for more details.	4	* for more details.
5	*	5	*
6	* SGI UV APIC functions (note: not an Intel compatible APIC)	6	* SGI UV APIC functions (note: not an Intel compatible APIC)
7	*	7	*
8	* Copyright (C) 2007-2013 Silicon Graphics, Inc. All rights reserved.	8	* Copyright (C) 2007-2013 Silicon Graphics, Inc. All rights reserved.
9	*/	9	*/
10	#include <linux/cpumask.h>	10	#include <linux/cpumask.h>
11	#include <linux/hardirq.h>	11	#include <linux/hardirq.h>
12	#include <linux/proc_fs.h>	12	#include <linux/proc_fs.h>
13	#include <linux/threads.h>	13	#include <linux/threads.h>
14	#include <linux/kernel.h>	14	#include <linux/kernel.h>
15	#include <linux/module.h>	15	#include <linux/module.h>
16	#include <linux/string.h>	16	#include <linux/string.h>
17	#include <linux/ctype.h>	17	#include <linux/ctype.h>
18	#include <linux/sched.h>	18	#include <linux/sched.h>
19	#include <linux/timer.h>	19	#include <linux/timer.h>
20	#include <linux/slab.h>	20	#include <linux/slab.h>
21	#include <linux/cpu.h>	21	#include <linux/cpu.h>
22	#include <linux/init.h>	22	#include <linux/init.h>
23	#include <linux/io.h>	23	#include <linux/io.h>
24	#include <linux/pci.h>	24	#include <linux/pci.h>
25	#include <linux/kdebug.h>	25	#include <linux/kdebug.h>
26	#include <linux/delay.h>	26	#include <linux/delay.h>
27	#include <linux/crash_dump.h>	27	#include <linux/crash_dump.h>
28	#include <linux/reboot.h>	28	#include <linux/reboot.h>
29		29
30	#include <asm/uv/uv_mmrs.h>	30	#include <asm/uv/uv_mmrs.h>
31	#include <asm/uv/uv_hub.h>	31	#include <asm/uv/uv_hub.h>
32	#include <asm/current.h>	32	#include <asm/current.h>
33	#include <asm/pgtable.h>	33	#include <asm/pgtable.h>
34	#include <asm/uv/bios.h>	34	#include <asm/uv/bios.h>
35	#include <asm/uv/uv.h>	35	#include <asm/uv/uv.h>
36	#include <asm/apic.h>	36	#include <asm/apic.h>
37	#include <asm/ipi.h>	37	#include <asm/ipi.h>
38	#include <asm/smp.h>	38	#include <asm/smp.h>
39	#include <asm/x86_init.h>	39	#include <asm/x86_init.h>
40	#include <asm/nmi.h>	40	#include <asm/nmi.h>