|
Server : Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.17 System : Linux localhost 2.6.18-419.el5 #1 SMP Fri Feb 24 22:47:42 UTC 2017 x86_64 User : nobody ( 99) PHP Version : 5.2.17 Disable Function : NONE Directory : /proc/21572/root/lib/modules/2.6.18-308.4.1.el5/build/drivers/xenpv_hvm/ |
Upload File : |
# # This Kconfig describe xen options # # add other arch's if needed in depends below ... menu "Xen PV-ON-HVM Configuration" config XEN_PV_ON_HVM # when/if ia64 xen-hfiles added to rhel4 sources # depends on !XEN && (X86_64 || X86 || IA64) bool "XEN_PV_ON_HVM Support" default y if (!X86_XEN && (X86 || X86_64)) help Support for Xen paravirtualized drivers on fully-virtualized guest config XEN_BLKDEV_FRONTEND tristate "Block-device frontend driver" depends on XEN_PV_ON_HVM default y help The block-device frontend driver allows the kernel to access block devices mounted within another guest OS. Unless you are building a dedicated device-driver domain, or your master control domain (domain 0), then you almost certainly want to say Y here. config XEN_NETDEV_FRONTEND tristate "Network-device frontend driver" depends on XEN_PV_ON_HVM default y help The network-device frontend driver allows the kernel to access network interfaces within another guest OS. Unless you are building a dedicated device-driver domain, or your master control domain (domain 0), then you almost certainly want to say Y here. endmenu #config HAVE_ARCH_ALLOC_SKB # bool # default y #config HAVE_ARCH_DEV_ALLOC_SKB # bool # default y