view block/Kconfig @ 890:2e94884f0e8d

Dom0 PCI: fix a regression introduced by the SR-IOV change

The device class may be changed during the early fixup. So need to
re-read the device class from pci_dev after the fixup.

The patch "PCI: centralize device setup code" (c/s 825) wrongly
cleaned up the device class re-read. This patch reverts that change.

Signed-off-by: Yu Zhao <yu.zhao@intel.com>
author Keir Fraser <keir.fraser@citrix.com>
date Wed Jun 03 11:21:52 2009 +0100 (2009-06-03)
parents 831230e53067
line source
1 #
2 # Block layer core configuration
3 #
4 #XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
5 #for instance.
6 config LBD
7 bool "Support for Large Block Devices"
8 depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
9 help
10 Say Y here if you want to attach large (bigger than 2TB) discs to
11 your machine, or if you want to have a raid or loopback device
12 bigger than 2TB. Otherwise say N.
14 config BLK_DEV_IO_TRACE
15 bool "Support for tracing block io actions"
16 depends on SYSFS
17 select RELAY
18 select DEBUG_FS
19 help
20 Say Y here, if you want to be able to trace the block layer actions
21 on a given queue. Tracing allows you to see any traffic happening
22 on a block device queue. For more information (and the user space
23 support tools needed), fetch the blktrace app from:
25 git://brick.kernel.dk/data/git/blktrace.git
27 config LSF
28 bool "Support for Large Single Files"
29 depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
30 help
31 Say Y here if you want to be able to handle very large files (bigger
32 than 2TB), otherwise say N.
34 If unsure, say Y.
36 source block/Kconfig.iosched