1 Subject: xen3 xen-kconfig
2 From: http://xenbits.xensource.com/linux-2.6.18-xen.hg (tip 728:832aac894efd)
3 Patch-mainline: obsolete
4 Acked-by: jbeulich@novell.com
6 --- sle11-2009-06-04.orig/arch/x86/Kconfig 2009-06-04 10:17:50.000000000 +0200
7 +++ sle11-2009-06-04/arch/x86/Kconfig 2009-06-04 10:18:21.000000000 +0200
8 @@ -44,6 +44,7 @@ config GENERIC_LOCKBREAK
14 config GENERIC_CMOS_UPDATE
16 @@ -191,7 +192,7 @@ config X86_64_SMP
21 + depends on SMP && !XEN
22 depends on (X86_32 && !X86_VOYAGER) || X86_64
25 @@ -203,6 +204,17 @@ config X86_BIOS_REBOOT
28 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
34 + depends on X86_XEN || X86_64_XEN
39 + depends on X86_XEN || X86_64_XEN
43 @@ -271,6 +283,17 @@ config X86_PC
45 Choose this option if your computer is a standard PC or compatible.
48 + bool "Xen-compatible"
51 + select X86_UP_APIC if !SMP && XEN_PRIVILEGED_GUEST
52 + select X86_UP_IOAPIC if !SMP && XEN_PRIVILEGED_GUEST
55 + Choose this option if you plan to run this kernel on top of the
61 @@ -338,6 +361,13 @@ config X86_BIGSMP
66 + bool "Enable Xen compatible kernel"
70 + This option will compile a kernel compatible with Xen hypervisor
73 bool "Support for ScaleMP vSMP"
75 @@ -478,6 +508,7 @@ source "arch/x86/Kconfig.cpu"
78 prompt "HPET Timer Support" if X86_32
79 + depends on !X86_XEN && !X86_64_XEN
81 Use the IA-PC HPET (High Precision Event Timer) to manage
82 time in preference to the PIT and RTC, if a HPET is
83 @@ -514,7 +545,7 @@ config GART_IOMMU
87 - depends on X86_64 && PCI
88 + depends on X86_64 && PCI && !X86_64_XEN
90 Support for full DMA access of devices with 32bit memory access only
91 on systems with more than 3GB. This is usually needed for USB,
92 @@ -529,7 +560,7 @@ config GART_IOMMU
94 bool "IBM Calgary IOMMU support"
96 - depends on X86_64 && PCI && EXPERIMENTAL
97 + depends on X86_64 && PCI && !X86_64_XEN && EXPERIMENTAL
99 Support for hardware IOMMUs in IBM's xSeries x366 and x460
100 systems. Needed to run systems with more than 3GB of memory
101 @@ -597,6 +628,7 @@ config NR_CPUS
103 default "4096" if MAXSMP
104 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
105 + default "16" if X86_64_XEN
108 This allows you to specify the maximum number of CPUs which this
109 @@ -652,7 +684,7 @@ config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
112 bool "Local APIC support on uniprocessors"
113 - depends on X86_32 && !SMP && !(X86_VOYAGER || X86_GENERICARCH)
114 + depends on X86_32 && !SMP && !(X86_VOYAGER || X86_GENERICARCH || XEN_UNPRIVILEGED_GUEST)
116 A local APIC (Advanced Programmable Interrupt Controller) is an
117 integrated interrupt controller in the CPU. If you have a single-CPU
118 @@ -678,18 +710,25 @@ config X86_UP_IOAPIC
119 config X86_LOCAL_APIC
121 depends on X86_64 || (X86_32 && (X86_UP_APIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
122 + depends on !XEN_UNPRIVILEGED_GUEST
126 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
127 + depends on !XEN_UNPRIVILEGED_GUEST
129 config X86_VISWS_APIC
131 depends on X86_32 && X86_VISWS
133 +config X86_XEN_GENAPIC
135 + depends on X86_64_XEN
139 bool "Machine Check Exception"
140 - depends on !X86_VOYAGER
141 + depends on !(X86_VOYAGER || XEN)
143 Machine Check Exception support allows the processor to notify the
144 kernel if it detects a problem (e.g. overheating, component failure).
145 @@ -789,7 +828,7 @@ config I8K
146 config X86_REBOOTFIXUPS
148 prompt "Enable X86 board specific fixups for reboot"
149 - depends on X86_32 && X86
150 + depends on X86_32 && !X86_XEN
152 This enables chipset and/or board specific fixups to be done
153 in order to get reboot to work correctly. This is only needed on
154 @@ -806,6 +845,7 @@ config X86_REBOOTFIXUPS
157 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
158 + depends on !XEN_UNPRIVILEGED_GUEST
161 If you say Y here, you will be able to update the microcode on
162 @@ -973,7 +1013,7 @@ config DIRECT_GBPAGES
163 # Common NUMA Features
165 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
167 + depends on SMP && !XEN
168 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
170 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
171 @@ -1075,7 +1115,7 @@ config ARCH_SPARSEMEM_DEFAULT
173 config ARCH_SPARSEMEM_ENABLE
175 - depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
176 + depends on (X86_64 && !X86_64_XEN) || NUMA || (EXPERIMENTAL && X86_PC)
177 select SPARSEMEM_STATIC if X86_32
178 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
180 @@ -1121,6 +1161,7 @@ config X86_RESERVE_LOW_64K
181 config MATH_EMULATION
183 prompt "Math emulation" if X86_32
184 + depends on !X86_XEN
186 Linux can emulate a math coprocessor (used for floating point
187 operations) if you don't have one. 486DX and Pentium processors have
188 @@ -1146,6 +1187,7 @@ config MATH_EMULATION
191 bool "MTRR (Memory Type Range Register) support"
192 + depends on !XEN_UNPRIVILEGED_GUEST
194 On Intel P6 family processors (Pentium Pro, Pentium II and later)
195 the Memory Type Range Registers (MTRRs) may be used to control
196 @@ -1227,7 +1269,7 @@ config X86_PAT
199 prompt "EFI runtime service support"
201 + depends on ACPI && !X86_XEN && !X86_64_XEN
203 This enables the kernel to use EFI runtime services that are
204 available (such as the EFI variable services).
205 @@ -1242,7 +1284,7 @@ config EFI
208 prompt "Enable kernel irq balancing"
209 - depends on X86_32 && SMP && X86_IO_APIC
210 + depends on X86_32 && SMP && X86_IO_APIC && !X86_XEN
212 The default yes will allow the kernel to do irq load balancing.
213 Saying no will keep the kernel from doing irq load balancing.
214 @@ -1305,6 +1347,7 @@ source kernel/Kconfig.hz
216 bool "kexec system call"
217 depends on X86_BIOS_REBOOT
218 + depends on !XEN_UNPRIVILEGED_GUEST
220 kexec is a system call that implements the ability to shutdown your
221 current kernel, and to start another kernel. It is like a reboot
222 @@ -1322,6 +1365,7 @@ config KEXEC
224 bool "kernel crash dumps"
225 depends on X86_64 || (X86_32 && HIGHMEM)
228 Generate crash dump after being started by kexec.
229 This should be normally only set in special crash dump kernels
230 @@ -1440,6 +1484,7 @@ config COMPAT_VDSO
232 prompt "Compat VDSO support"
233 depends on X86_32 || IA32_EMULATION
234 + depends on !X86_XEN
236 Map the 32-bit VDSO to the predictable old-style address too.
238 @@ -1462,7 +1507,7 @@ config HAVE_ARCH_EARLY_PFN_TO_NID
241 menu "Power management options"
242 - depends on !X86_VOYAGER
243 + depends on !(X86_VOYAGER || XEN_UNPRIVILEGED_GUEST)
245 config ARCH_HIBERNATION_HEADER
247 @@ -1479,7 +1524,7 @@ config X86_APM_BOOT
250 tristate "APM (Advanced Power Management) BIOS support"
251 - depends on X86_32 && PM_SLEEP
252 + depends on X86_32 && PM_SLEEP && !XEN
254 APM is a BIOS specification for saving power using several different
255 techniques. This is mostly useful for battery powered laptops with
256 @@ -1645,6 +1690,7 @@ choice
260 + depends on !X86_XEN
262 config PCI_GOMMCONFIG
264 @@ -1656,6 +1702,13 @@ config PCI_GOOLPC
269 + bool "Xen PCI Frontend"
272 + The PCI device frontend driver allows the kernel to import arbitrary
273 + PCI devices from a PCI backend to support PCI driver domains.
278 @@ -1663,7 +1716,7 @@ endchoice
282 - depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
283 + depends on X86_32 && PCI && !XEN && (PCI_GOBIOS || PCI_GOANY)
285 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
287 @@ -1686,6 +1739,22 @@ config PCI_MMCONFIG
288 bool "Support mmconfig PCI config space access"
289 depends on X86_64 && PCI && ACPI
291 +config XEN_PCIDEV_FRONTEND
292 + bool "Xen PCI Frontend" if X86_64
293 + depends on PCI && ((X86_XEN && (PCI_GOXEN_FE || PCI_GOANY)) || X86_64_XEN)
297 + The PCI device frontend driver allows the kernel to import arbitrary
298 + PCI devices from a PCI backend to support PCI driver domains.
300 +config XEN_PCIDEV_FE_DEBUG
301 + bool "Xen PCI Frontend Debugging"
302 + depends on XEN_PCIDEV_FRONTEND
305 + Enables some debug statements within the PCI Frontend.
308 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
309 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
310 @@ -1736,7 +1805,7 @@ if X86_32
314 - depends on !X86_VOYAGER
315 + depends on !X86_VOYAGER && !XEN
317 Find out whether you have ISA slots on your motherboard. ISA is the
318 name of a bus system, i.e. the way the CPU talks to the other stuff
319 @@ -1763,7 +1832,7 @@ config EISA
320 source "drivers/eisa/Kconfig"
323 - bool "MCA support" if !X86_VOYAGER
324 + bool "MCA support" if !X86_VOYAGER && !XEN
325 default y if X86_VOYAGER
327 MicroChannel Architecture is found in some IBM PS/2 machines and
328 @@ -1875,4 +1944,6 @@ source "crypto/Kconfig"
330 source "arch/x86/kvm/Kconfig"
332 +source "drivers/xen/Kconfig"
335 --- sle11-2009-06-04.orig/arch/x86/Kconfig.cpu 2009-06-04 10:17:50.000000000 +0200
336 +++ sle11-2009-06-04/arch/x86/Kconfig.cpu 2009-06-04 10:18:21.000000000 +0200
337 @@ -340,7 +340,7 @@ config X86_PPRO_FENCE
341 - depends on M586MMX || M586TSC || M586 || M486 || M386
342 + depends on (M586MMX || M586TSC || M586 || M486 || M386) && !X86_NO_IDT
344 config X86_WP_WORKS_OK
346 @@ -397,6 +397,7 @@ config X86_P6_NOP
349 depends on ((MWINCHIP3D || MWINCHIP2 || MCRUSOE || MEFFICEON || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || MK8 || MVIAC3_2 || MVIAC7 || MGEODEGX1 || MGEODE_LX || MCORE2) && !X86_NUMAQ) || X86_64
354 --- sle11-2009-06-04.orig/arch/x86/Kconfig.debug 2009-06-04 10:17:50.000000000 +0200
355 +++ sle11-2009-06-04/arch/x86/Kconfig.debug 2009-06-04 10:18:21.000000000 +0200
356 @@ -143,7 +143,7 @@ config 4KSTACKS
359 bool "Enable doublefault exception handler" if EMBEDDED
361 + depends on X86_32 && !X86_NO_TSS
363 This option allows trapping of rare doublefault exceptions that
364 would otherwise cause a system to silently reboot. Disabling this
365 --- sle11-2009-06-04.orig/drivers/acpi/Kconfig 2009-06-04 10:17:50.000000000 +0200
366 +++ sle11-2009-06-04/drivers/acpi/Kconfig 2009-06-04 10:18:21.000000000 +0200
367 @@ -362,6 +362,7 @@ config ACPI_SYSTEM
369 bool "Power Management Timer Support" if EMBEDDED
374 The Power Management Timer is available on all ACPI-capable,
375 @@ -415,4 +416,13 @@ config ACPI_SBS
376 This driver adds support for the Smart Battery System, another
377 type of access to battery information, found on some laptops.
379 +config ACPI_PV_SLEEP
381 + depends on X86 && XEN && ACPI_SLEEP
384 +config PROCESSOR_EXTERNAL_CONTROL
386 + depends on (X86 || IA64) && XEN
389 --- sle11-2009-06-04.orig/drivers/char/Kconfig 2009-06-04 10:17:50.000000000 +0200
390 +++ sle11-2009-06-04/drivers/char/Kconfig 2009-06-04 10:18:21.000000000 +0200
391 @@ -1037,7 +1037,7 @@ config MAX_RAW_DEVS
393 bool "HPET - High Precision Event Timer" if (X86 || IA64)
396 + depends on ACPI && !XEN
398 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
399 open selects one of the timers supported by the HPET. The timers are
400 --- sle11-2009-06-04.orig/drivers/char/tpm/Kconfig 2009-06-04 10:17:50.000000000 +0200
401 +++ sle11-2009-06-04/drivers/char/tpm/Kconfig 2009-06-04 10:18:21.000000000 +0200
402 @@ -57,4 +57,13 @@ config TCG_INFINEON
403 Further information on this driver and the supported hardware
404 can be found at http://www.prosec.rub.de/tpm
407 + tristate "XEN TPM Interface"
410 + If you want to make TPM support available to a Xen user domain,
411 + say Yes and it will be accessible from within Linux.
412 + To compile this driver as a module, choose M here; the module
413 + will be called tpm_xenu.
416 --- sle11-2009-06-04.orig/drivers/cpufreq/Kconfig 2009-06-04 10:17:50.000000000 +0200
417 +++ sle11-2009-06-04/drivers/cpufreq/Kconfig 2009-06-04 10:18:21.000000000 +0200
420 bool "CPU Frequency scaling"
421 + depends on !PROCESSOR_EXTERNAL_CONTROL
423 CPU Frequency scaling allows you to change the clock speed of
424 CPUs on the fly. This is a nice method to save power, because
425 --- sle11-2009-06-04.orig/drivers/serial/Kconfig 2009-06-04 10:17:50.000000000 +0200
426 +++ sle11-2009-06-04/drivers/serial/Kconfig 2009-06-04 10:18:21.000000000 +0200
427 @@ -10,6 +10,7 @@ menu "Serial drivers"
429 tristate "8250/16550 and compatible serial support"
430 depends on (BROKEN || !SPARC)
431 + depends on !XEN_DISABLE_SERIAL
434 This selects whether you want to include the driver for the standard
435 --- sle11-2009-06-04.orig/drivers/video/Kconfig 2009-06-04 10:17:50.000000000 +0200
436 +++ sle11-2009-06-04/drivers/video/Kconfig 2009-06-04 10:18:21.000000000 +0200
437 @@ -1583,7 +1583,7 @@ config FB_CYBLA
438 tristate "Cyberblade/i1 support"
439 depends on FB && PCI && X86_32 && !64BIT
440 select FB_CFB_IMAGEBLIT
441 - select VIDEO_SELECT
442 + select VIDEO_SELECT if !XEN
444 This driver is supposed to support the Trident Cyberblade/i1
445 graphics core integrated in the VIA VT8601A North Bridge,
446 --- sle11-2009-06-04.orig/drivers/video/console/Kconfig 2009-06-04 10:17:50.000000000 +0200
447 +++ sle11-2009-06-04/drivers/video/console/Kconfig 2009-06-04 10:18:21.000000000 +0200
448 @@ -46,6 +46,7 @@ config VGACON_SOFT_SCROLLBACK_SIZE
450 bool "Video mode selection support"
451 depends on X86 && VGA_CONSOLE
454 This enables support for text mode selection on kernel startup. If
455 you want to take advantage of some high-resolution text mode your
456 --- sle11-2009-06-04.orig/drivers/xen/Kconfig 2009-06-04 10:17:50.000000000 +0200
457 +++ sle11-2009-06-04/drivers/xen/Kconfig 2009-06-04 10:18:21.000000000 +0200
460 +# This Kconfig describe xen options
463 +mainmenu "Xen Configuration"
469 +config XEN_INTERFACE_VERSION
475 +config XEN_PRIVILEGED_GUEST
476 + bool "Privileged Guest (domain 0)"
477 + select PCI_REASSIGN if PCI
479 + Support for privileged operation (domain 0)
481 +config XEN_UNPRIVILEGED_GUEST
482 + def_bool !XEN_PRIVILEGED_GUEST
488 +config XEN_XENBUS_DEV
492 +config XEN_NETDEV_ACCEL_SFC_UTIL
497 + tristate "Backend driver support"
498 + default XEN_PRIVILEGED_GUEST
500 + Support for backend device drivers that provide I/O services
501 + to other virtual machines.
503 +config XEN_BLKDEV_BACKEND
504 + tristate "Block-device backend driver"
505 + depends on XEN_BACKEND
506 + default XEN_BACKEND
508 + The block-device backend driver allows the kernel to export its
509 + block devices to other guests via a high-performance shared-memory
512 +config XEN_BLKDEV_TAP
513 + tristate "Block-device tap backend driver"
514 + depends on XEN_BACKEND
515 + default XEN_BACKEND
517 + The block tap driver is an alternative to the block back driver
518 + and allows VM block requests to be redirected to userspace through
519 + a device interface. The tap allows user-space development of
520 + high-performance block backends, where disk images may be implemented
521 + as files, in memory, or on other hosts across the network. This
522 + driver can safely coexist with the existing blockback driver.
524 +config XEN_NETDEV_BACKEND
525 + tristate "Network-device backend driver"
526 + depends on XEN_BACKEND && NET
527 + default XEN_BACKEND
529 + The network-device backend driver allows the kernel to export its
530 + network devices to other guests via a high-performance shared-memory
533 +config XEN_NETDEV_PIPELINED_TRANSMITTER
534 + bool "Pipelined transmitter (DANGEROUS)"
535 + depends on XEN_NETDEV_BACKEND
537 + If the net backend is a dumb domain, such as a transparent Ethernet
538 + bridge with no local IP interface, it is safe to say Y here to get
539 + slightly lower network overhead.
540 + If the backend has a local IP interface; or may be doing smart things
541 + like reassembling packets to perform firewall filtering; or if you
542 + are unsure; or if you experience network hangs when this option is
543 + enabled; then you must say N here.
545 +config XEN_NETDEV_ACCEL_SFC_BACKEND
546 + tristate "Network-device backend driver acceleration for Solarflare NICs"
547 + depends on XEN_NETDEV_BACKEND && SFC && SFC_RESOURCE && X86
548 + select XEN_NETDEV_ACCEL_SFC_UTIL
551 +config XEN_NETDEV_LOOPBACK
552 + tristate "Network-device loopback driver"
553 + depends on XEN_NETDEV_BACKEND
555 + A two-interface loopback device to emulate a local netfront-netback
556 + connection. If unsure, it is probably safe to say N here.
558 +config XEN_PCIDEV_BACKEND
559 + tristate "PCI-device backend driver"
560 + depends on PCI && XEN_BACKEND
561 + default XEN_BACKEND
563 + The PCI device backend driver allows the kernel to export arbitrary
564 + PCI devices to other guests. If you select this to be a module, you
565 + will need to make sure no other driver has bound to the device(s)
566 + you want to make visible to other guests.
569 + prompt "PCI Backend Mode"
570 + depends on XEN_PCIDEV_BACKEND
571 + default XEN_PCIDEV_BACKEND_VPCI if !IA64
572 + default XEN_PCIDEV_BACKEND_CONTROLLER if IA64
574 +config XEN_PCIDEV_BACKEND_VPCI
577 + This PCI Backend hides the true PCI topology and makes the frontend
578 + think there is a single PCI bus with only the exported devices on it.
579 + For example, a device at 03:05.0 will be re-assigned to 00:00.0. A
580 + second device at 02:1a.1 will be re-assigned to 00:01.1.
582 +config XEN_PCIDEV_BACKEND_PASS
585 + This PCI Backend provides a real view of the PCI topology to the
586 + frontend (for example, a device at 06:01.b will still appear at
587 + 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed
588 + PCI devices to its driver domains. This may be required for drivers
589 + which depend on finding their hardward in certain bus/slot
592 +config XEN_PCIDEV_BACKEND_SLOT
595 + This PCI Backend hides the true PCI topology and makes the frontend
596 + think there is a single PCI bus with only the exported devices on it.
597 + Contrary to the virtual PCI backend, a function becomes a new slot.
598 + For example, a device at 03:05.2 will be re-assigned to 00:00.0. A
599 + second device at 02:1a.1 will be re-assigned to 00:01.0.
601 +config XEN_PCIDEV_BACKEND_CONTROLLER
605 + This PCI backend virtualizes the PCI bus topology by providing a
606 + virtual bus per PCI root device. Devices which are physically under
607 + the same root bus will appear on the same virtual bus. For systems
608 + with complex I/O addressing, this is the only backend which supports
609 + extended I/O port spaces and MMIO translation offsets. This backend
610 + also supports slot virtualization. For example, a device at
611 + 0000:01:02.1 will be re-assigned to 0000:00:00.0. A second device
612 + at 0000:02:05.0 (behind a P2P bridge on bus 0000:01) will be
613 + re-assigned to 0000:00:01.0. A third device at 0000:16:05.0 (under
614 + a different PCI root bus) will be re-assigned to 0000:01:00.0.
618 +config XEN_PCIDEV_BE_DEBUG
619 + bool "PCI Backend Debugging"
620 + depends on XEN_PCIDEV_BACKEND
622 +config XEN_TPMDEV_BACKEND
623 + tristate "TPM-device backend driver"
624 + depends on XEN_BACKEND
626 + The TPM-device backend driver
628 +config XEN_SCSI_BACKEND
629 + tristate "SCSI backend driver"
630 + depends on SCSI && XEN_BACKEND
633 + The SCSI backend driver allows the kernel to export its SCSI Devices
634 + to other guests via a high-performance shared-memory interface.
636 +config XEN_BLKDEV_FRONTEND
637 + tristate "Block-device frontend driver"
640 + The block-device frontend driver allows the kernel to access block
641 + devices mounted within another guest OS. Unless you are building a
642 + dedicated device-driver domain, or your master control domain
643 + (domain 0), then you almost certainly want to say Y here.
645 +config XEN_NETDEV_FRONTEND
646 + tristate "Network-device frontend driver"
650 + The network-device frontend driver allows the kernel to access
651 + network interfaces within another guest OS. Unless you are building a
652 + dedicated device-driver domain, or your master control domain
653 + (domain 0), then you almost certainly want to say Y here.
655 +config XEN_NETDEV_ACCEL_SFC_FRONTEND
656 + tristate "Network-device frontend driver acceleration for Solarflare NICs"
657 + depends on XEN_NETDEV_FRONTEND && X86
658 + select XEN_NETDEV_ACCEL_SFC_UTIL
661 +config XEN_SCSI_FRONTEND
662 + tristate "SCSI frontend driver"
666 + The SCSI frontend driver allows the kernel to access SCSI Devices
667 + within another guest OS.
669 +config XEN_GRANT_DEV
670 + tristate "User-space granted page access driver"
671 + default XEN_PRIVILEGED_GUEST
673 + Device for accessing (in user-space) pages that have been granted
676 +config XEN_FRAMEBUFFER
677 + tristate "Framebuffer-device frontend driver"
679 + select FB_CFB_FILLRECT
680 + select FB_CFB_COPYAREA
681 + select FB_CFB_IMAGEBLIT
684 + The framebuffer-device frontend drivers allows the kernel to create a
685 + virtual framebuffer. This framebuffer can be viewed in another
686 + domain. Unless this domain has access to a real video card, you
687 + probably want to say Y here.
690 + tristate "Keyboard-device frontend driver"
691 + depends on XEN_FRAMEBUFFER && INPUT
694 + The keyboard-device frontend driver allows the kernel to create a
695 + virtual keyboard. This keyboard can then be driven by another
696 + domain. If you've said Y to CONFIG_XEN_FRAMEBUFFER, you probably
697 + want to say Y here.
699 +config XEN_DISABLE_SERIAL
700 + bool "Disable serial port drivers"
703 + Disable serial port drivers, allowing the Xen console driver
704 + to provide a serial console at ttyS0.
707 + tristate "Export Xen attributes in sysfs"
709 + select SYS_HYPERVISOR
712 + Xen hypervisor attributes will show up under /sys/hypervisor/.
715 + prompt "Xen version compatibility"
716 + default XEN_COMPAT_030002_AND_LATER
718 + config XEN_COMPAT_030002_AND_LATER
719 + bool "3.0.2 and later"
721 + config XEN_COMPAT_030004_AND_LATER
722 + bool "3.0.4 and later"
724 + config XEN_COMPAT_030100_AND_LATER
725 + bool "3.1.0 and later"
727 + config XEN_COMPAT_LATEST_ONLY
728 + bool "no compatibility code"
734 + default 0xffffff if XEN_COMPAT_LATEST_ONLY
735 + default 0x030100 if XEN_COMPAT_030100_AND_LATER
736 + default 0x030004 if XEN_COMPAT_030004_AND_LATER
737 + default 0x030002 if XEN_COMPAT_030002_AND_LATER
742 +config HAVE_IRQ_IGNORE_UNHANDLED
750 + depends on SMP && !PPC_XEN
761 - bool "Xen memory balloon driver"
763 + bool "Xen memory balloon driver" if PARAVIRT_XEN
764 + depends on (XEN && !PPC_XEN) || PARAVIRT_XEN
767 The balloon driver allows the Xen domain to request more memory from
768 @@ -8,12 +309,14 @@ config XEN_BALLOON
769 return unneeded memory to the system.
771 config XEN_SCRUB_PAGES
772 - bool "Scrub pages before returning them to system"
773 - depends on XEN_BALLOON
774 + bool "Scrub memory before freeing it to Xen"
775 + depends on XEN || XEN_BALLOON
778 - Scrub pages before returning them to the system for reuse by
779 - other domains. This makes sure that any confidential data
780 - is not accidentally visible to other domains. Is it more
781 - secure, but slightly less efficient.
782 + Erase memory contents before freeing it back to Xen's global
783 + pool. This ensures that any secrets contained within that
784 + memory (e.g., private keys) cannot be found by other guests that
785 + may be running on the machine. Most people will want to say Y here.
786 + If security is not a concern then you may increase performance by
788 If in doubt, say yes.
789 --- sle11-2009-06-04.orig/fs/Kconfig 2009-06-04 10:17:50.000000000 +0200
790 +++ sle11-2009-06-04/fs/Kconfig 2009-06-04 10:18:21.000000000 +0200
791 @@ -1011,6 +1011,7 @@ config HUGETLBFS
792 bool "HugeTLB file system support"
793 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
794 (S390 && 64BIT) || BROKEN
797 hugetlbfs is a filesystem backing for HugeTLB pages, based on
798 ramfs. For architectures that support it, say Y here and read
799 --- sle11-2009-06-04.orig/kernel/Kconfig.preempt 2009-06-04 10:17:50.000000000 +0200
800 +++ sle11-2009-06-04/kernel/Kconfig.preempt 2009-06-04 10:18:21.000000000 +0200
801 @@ -35,6 +35,7 @@ config PREEMPT_VOLUNTARY
804 bool "Preemptible Kernel (Low-Latency Desktop)"
807 This option reduces the latency of the kernel by making
808 all kernel code (that is not executing in a critical section)