* PCI warning on boot 3.8.0-rc1
@ 2013-01-16 22:38 Stephen Hemminger
2013-01-30 21:59 ` Bjorn Helgaas
0 siblings, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2013-01-16 22:38 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: linux-pci
I see this on boot in dmesg
[ 0.574494] DMAR: No ATSR found
[ 0.574549] IOMMU 0 0xfed90000: using Queued invalidation
[ 0.574550] IOMMU 1 0xfed91000: using Queued invalidation
[ 0.574554] IOMMU: Setting RMRR:
[ 0.574583] IOMMU: Setting identity map for device 0000:00:02.0 [0xcf000000 -
0xdf1fffff]
[ 0.575748] IOMMU: Setting identity map for device 0000:00:1d.0 [0xcd551000 -
0xcd56dfff]
[ 0.575767] IOMMU: Setting identity map for device 0000:00:1a.0 [0xcd551000 -
0xcd56dfff]
[ 0.575786] IOMMU: Setting identity map for device 0000:00:14.0 [0xcd551000 -
0xcd56dfff]
[ 0.575797] IOMMU: Prepare 0-16MiB unity mapping for LPC
[ 0.575806] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffff
ff]
[ 0.576186] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[ 0.576337] ------------[ cut here ]------------
[ 0.576342] WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge
+0x59/0x71()
[ 0.576343] Hardware name: System Product Name
[ 0.576344] Modules linked in:
[ 0.576347] Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc1-net-next+ #4
[ 0.576348] Call Trace:
[ 0.576352] [<ffffffff81074261>] warn_slowpath_common+0x83/0x9c
[ 0.576355] [<ffffffff813fae71>] ? bus_set_iommu+0x49/0x49
[ 0.576357] [<ffffffff81074294>] warn_slowpath_null+0x1a/0x1c
[ 0.576360] [<ffffffff812db618>] pci_find_upstream_pcie_bridge+0x59/0x71
[ 0.576362] [<ffffffff813fd247>] intel_iommu_add_device+0x4d/0x17a
[ 0.576364] [<ffffffff813faeab>] add_iommu_group+0x3a/0x48
[ 0.576368] [<ffffffff8135d490>] bus_for_each_dev+0x57/0x89
[ 0.576370] [<ffffffff813fae6a>] bus_set_iommu+0x42/0x49
[ 0.576374] [<ffffffff81b1b1a5>] intel_iommu_init+0xa27/0xb44
[ 0.576377] [<ffffffff8105dcf3>] ? free_init_pages+0xf5/0x10d
[ 0.576379] [<ffffffff81aeb87d>] ? maybe_link.part.2+0x10b/0x10b
[ 0.576382] [<ffffffff81aeef53>] ? memblock_find_dma_reserve+0x133/0x133
[ 0.576384] [<ffffffff81aeef66>] pci_iommu_init+0x13/0x3e
[ 0.576387] [<ffffffff8100023c>] do_one_initcall+0x7f/0x133
[ 0.576390] [<ffffffff814d0c2c>] kernel_init+0x146/0x29b
[ 0.576393] [<ffffffff81aea52f>] ? do_early_param+0x8c/0x8c
[ 0.576395] [<ffffffff814d0ae6>] ? rest_init+0xda/0xda
[ 0.576398] [<ffffffff814ed4dc>] ret_from_fork+0x7c/0xb0
[ 0.576400] [<ffffffff814d0ae6>] ? rest_init+0xda/0xda
[ 0.576406] ---[ end trace f709d1eb2b66cbf5 ]---
$ sudo lspci -t -vv
-[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller
+-01.0-[01-02]----00.0 Intel Corporation Ethernet Controller 10-Gigabit X540-AT2
+-02.0 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
+-14.0 Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
+-16.0 Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1
+-1a.0 Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2
+-1b.0 Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller
+-1c.0-[03]--
+-1c.4-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
+-1c.5-[05-06]----00.0-[06]--
+-1d.0 Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1
+-1f.0 Intel Corporation Z77 Express Chipset LPC Controller
+-1f.2 Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
\-1f.3 Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.8.0-rc1 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_GPIO=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_CPU_AUTOPROBE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION="-net-next"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_FHANDLE=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
# CONFIG_AUDIT_LOGINUID_IMMUTABLE is not set
CONFIG_HAVE_GENERIC_HARDIRQS=y
#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_RCU_USER_QS is not set
CONFIG_RCU_FANOUT=64
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
CONFIG_RCU_FAST_NO_HZ=y
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_NOCB_CPU is not set
CONFIG_IKCONFIG=m
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_ARCH_WANTS_PROT_NUMA_PROT_NONE=y
# CONFIG_NUMA_BALANCING is not set
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
# CONFIG_PROC_PID_CPUSET is not set
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_MEMCG is not set
# CONFIG_CGROUP_HUGETLB is not set
# CONFIG_CGROUP_PERF is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_UIDGID_CONVERTED=y
# CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EXPERT is not set
CONFIG_HAVE_UID16=y
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
# CONFIG_COMPAT_BRK is not set
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_PROFILING is not set
CONFIG_TRACEPOINTS=y
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y
CONFIG_JUMP_LABEL=y
CONFIG_OPTPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_MODULES_USE_ELF_RELA=y
CONFIG_GENERIC_SIGALTSTACK=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
# CONFIG_BLK_DEV_THROTTLING is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CFQ_GROUP_IOSCHED=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_ZONE_DMA=y
CONFIG_SMP=y
CONFIG_X86_X2APIC=y
CONFIG_X86_MPPARSE=y
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
CONFIG_MCORE2=y
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_P6_NOP=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=512
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_COUNT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
# CONFIG_AMD_NUMA is not set
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
CONFIG_NUMA_EMU=y
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
CONFIG_ARCH_DISCARD_MEMBLOCK=y
CONFIG_MEMORY_ISOLATION=y
# CONFIG_MOVABLE_NODE is not set
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=999999
CONFIG_BALLOON_COMPACTION=y
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_HWPOISON_INJECT is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_ARCH_RANDOM=y
CONFIG_X86_SMAP=y
CONFIG_EFI=y
# CONFIG_EFI_STUB is not set
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
#
# Power management and ACPI options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM_RUNTIME=y
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_PROCFS_POWER is not set
# CONFIG_ACPI_EC_DEBUGFS is not set
# CONFIG_ACPI_PROC_EVENT is not set
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_I2C=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
# CONFIG_ACPI_INITRD_TABLE_OVERRIDE is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=m
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_ACPI_SBS=m
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_CUSTOM_METHOD is not set
CONFIG_ACPI_BGRT=y
CONFIG_ACPI_APEI=y
# CONFIG_ACPI_APEI_GHES is not set
CONFIG_ACPI_APEI_PCIEAER=y
# CONFIG_ACPI_APEI_MEMORY_FAILURE is not set
# CONFIG_ACPI_APEI_EINJ is not set
# CONFIG_ACPI_APEI_ERST_DEBUG is not set
CONFIG_SFI=y
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
#
# x86 CPU frequency scaling drivers
#
# CONFIG_X86_PCC_CPUFREQ is not set
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_ACPI_CPUFREQ_CPB is not set
CONFIG_X86_POWERNOW_K8=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_MULTIPLE_DRIVERS is not set
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set
CONFIG_INTEL_IDLE=y
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
# CONFIG_PCIEASPM_DEFAULT is not set
# CONFIG_PCIEASPM_POWERSAVE is not set
CONFIG_PCIEASPM_PERFORMANCE=y
CONFIG_PCIE_PME=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
CONFIG_PCI_REALLOC_ENABLE_AUTO=y
CONFIG_PCI_STUB=m
CONFIG_HT_IRQ=y
CONFIG_PCI_ATS=y
CONFIG_PCI_IOV=y
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
CONFIG_PCI_IOAPIC=m
CONFIG_PCI_LABEL=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_RAPIDIO is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=m
CONFIG_COREDUMP=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
# CONFIG_X86_X32 is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_KEYS_COMPAT=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_X86_DEV_DMA_OPS=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_DIAG=m
CONFIG_UNIX=y
CONFIG_UNIX_DIAG=m
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=m
# CONFIG_XFRM_USER is not set
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_CLASSID=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE_DEMUX=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_NET_IPVTI is not set
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=m
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_INET_UDP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=y
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_SIT_6RD=y
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_GRE=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
# CONFIG_NETLABEL is not set
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_ACCT=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
# CONFIG_NF_CONNTRACK_ZONES is not set
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_BROADCAST=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_SNMP=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NF_CT_NETLINK_TIMEOUT=m
# CONFIG_NETFILTER_NETLINK_QUEUE_CT is not set
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_SIP=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=m
#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
CONFIG_NETFILTER_XT_CONNMARK=m
CONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_AUDIT=m
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_CT=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
# CONFIG_NETFILTER_XT_TARGET_HMARK is not set
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
CONFIG_NETFILTER_XT_TARGET_LOG=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NETMAP=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_REDIRECT=m
CONFIG_NETFILTER_XT_TARGET_TEE=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_CPU=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ECN=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_NFACCT=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_IP_SET=m
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=m
CONFIG_IP_SET_BITMAP_IPMAC=m
CONFIG_IP_SET_BITMAP_PORT=m
CONFIG_IP_SET_HASH_IP=m
CONFIG_IP_SET_HASH_IPPORT=m
CONFIG_IP_SET_HASH_IPPORTIP=m
CONFIG_IP_SET_HASH_IPPORTNET=m
CONFIG_IP_SET_HASH_NET=m
CONFIG_IP_SET_HASH_NETPORT=m
CONFIG_IP_SET_HASH_NETIFACE=m
CONFIG_IP_SET_LIST_SET=m
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_RPFILTER=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT_IPV4=m
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV6=m
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RPFILTER=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
CONFIG_NF_NAT_IPV6=m
CONFIG_IP6_NF_TARGET_MASQUERADE=m
CONFIG_IP6_NF_TARGET_NPT=m
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_IP_DCCP is not set
CONFIG_IP_SCTP=m
# CONFIG_NET_SCTPPROBE is not set
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1 is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set
CONFIG_SCTP_COOKIE_HMAC_MD5=y
# CONFIG_SCTP_COOKIE_HMAC_SHA1 is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_L2TP=m
CONFIG_L2TP_DEBUGFS=m
CONFIG_L2TP_V3=y
CONFIG_L2TP_IP=m
CONFIG_L2TP_ETH=m
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_BRIDGE=m
CONFIG_BRIDGE_IGMP_SNOOPING=y
CONFIG_HAVE_NET_DSA=y
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=m
CONFIG_LLC2=m
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFB=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_DRR=m
CONFIG_NET_SCH_MQPRIO=m
CONFIG_NET_SCH_CHOKE=m
CONFIG_NET_SCH_QFQ=m
# CONFIG_NET_SCH_CODEL is not set
# CONFIG_NET_SCH_FQ_CODEL is not set
CONFIG_NET_SCH_INGRESS=m
# CONFIG_NET_SCH_PLUG is not set
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_CLS_CGROUP=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
# CONFIG_NET_EMATCH_TEXT is not set
# CONFIG_NET_EMATCH_IPSET is not set
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_ACT_SKBEDIT=m
CONFIG_NET_ACT_CSUM=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
# CONFIG_DNS_RESOLVER is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
CONFIG_NETPRIO_CGROUP=m
CONFIG_BQL=y
CONFIG_BPF_JIT=y
#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_NET_TCPPROBE=m
CONFIG_NET_DROP_MONITOR=y
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
CONFIG_BT_ATH3K=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
CONFIG_HAVE_BPF_JIT=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_GENERIC_CPU_DEVICES is not set
CONFIG_DMA_SHARED_BUFFER=y
#
# Bus devices
#
CONFIG_CONNECTOR=m
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_NVME=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_BLK_DEV_RBD is not set
#
# Misc devices
#
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_AD525X_DPOT is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_INTEL_MID_PTI is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_TI_DAC7512 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_BMP085_I2C is not set
# CONFIG_BMP085_SPI is not set
# CONFIG_PCH_PHUB is not set
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_CB710_CORE is not set
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# CONFIG_SENSORS_LIS3_I2C is not set
#
# Altera FPGA firmware download module
#
# CONFIG_ALTERA_STAPL is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=y
CONFIG_SCSI_SAS_LIBSAS=y
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_SCSI_BNX2X_FCOE is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
CONFIG_SCSI_MVSAS=y
# CONFIG_SCSI_MVSAS_DEBUG is not set
CONFIG_SCSI_MVSAS_TASKLET=y
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_VMWARE_PVSCSI is not set
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_FCOE_FNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_ISCI is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_CHELSIO_FCOE is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=m
# CONFIG_SATA_HIGHBANK is not set
CONFIG_SATA_MV=m
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARASAN_CF is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
CONFIG_PATA_MARVELL=m
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
CONFIG_PATA_OLDPIIX=m
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SCH=m
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
CONFIG_PATA_MPIIX=m
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MULTICORE_RAID456=y
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
# CONFIG_DM_THIN_PROVISIONING is not set
CONFIG_DM_MIRROR=m
CONFIG_DM_RAID=m
# CONFIG_DM_LOG_USERSPACE is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
# CONFIG_FIREWIRE_OHCI is not set
# CONFIG_FIREWIRE_SBP2 is not set
# CONFIG_FIREWIRE_NET is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
CONFIG_BONDING=m
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not set
CONFIG_MII=m
CONFIG_IFB=m
# CONFIG_NET_TEAM is not set
CONFIG_MACVLAN=m
CONFIG_MACVTAP=m
CONFIG_VXLAN=m
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_TUN=m
CONFIG_VETH=m
# CONFIG_VIRTIO_NET is not set
# CONFIG_ARCNET is not set
#
# CAIF transport drivers
#
#
# Distributed Switch Architecture drivers
#
# CONFIG_NET_DSA_MV88E6XXX is not set
# CONFIG_NET_DSA_MV88E6060 is not set
# CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set
# CONFIG_NET_DSA_MV88E6131 is not set
# CONFIG_NET_DSA_MV88E6123_61_65 is not set
CONFIG_ETHERNET=y
CONFIG_MDIO=m
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_NET_VENDOR_AMD is not set
# CONFIG_NET_VENDOR_ATHEROS is not set
CONFIG_NET_CADENCE=y
# CONFIG_ARM_AT91_ETHER is not set
# CONFIG_MACB is not set
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_BROCADE is not set
# CONFIG_NET_CALXEDA_XGMAC is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_CISCO is not set
# CONFIG_DNET is not set
# CONFIG_NET_VENDOR_DEC is not set
# CONFIG_NET_VENDOR_DLINK is not set
# CONFIG_NET_VENDOR_EMULEX is not set
# CONFIG_NET_VENDOR_EXAR is not set
# CONFIG_NET_VENDOR_HP is not set
CONFIG_NET_VENDOR_INTEL=y
CONFIG_E100=m
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IGB=m
CONFIG_IGB_DCA=y
CONFIG_IGBVF=m
CONFIG_IXGB=m
CONFIG_IXGBE=m
CONFIG_IXGBE_HWMON=y
CONFIG_IXGBE_DCA=y
CONFIG_IXGBEVF=m
# CONFIG_NET_VENDOR_I825XX is not set
# CONFIG_IP1000 is not set
# CONFIG_JME is not set
CONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
CONFIG_SKGE=m
CONFIG_SKGE_DEBUG=y
CONFIG_SKGE_GENESIS=y
CONFIG_SKY2=m
CONFIG_SKY2_DEBUG=y
# CONFIG_NET_VENDOR_MELLANOX is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
# CONFIG_NET_VENDOR_MYRI is not set
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_NVIDIA is not set
# CONFIG_NET_VENDOR_OKI is not set
# CONFIG_ETHOC is not set
# CONFIG_NET_PACKET_ENGINE is not set
# CONFIG_NET_VENDOR_QLOGIC is not set
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_R8169=m
# CONFIG_NET_VENDOR_RDC is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_SFC is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
# CONFIG_NET_VENDOR_VIA is not set
CONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_PHYLIB is not set
# CONFIG_MICREL_KS8995MA is not set
CONFIG_PPP=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOE=m
CONFIG_PPTP=m
CONFIG_PPPOL2TP=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_WLAN is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
# CONFIG_WAN is not set
CONFIG_VMXNET3=m
# CONFIG_ISDN is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_MOUSE_SYNAPTICS_USB=m
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_MPU3050 is not set
# CONFIG_INPUT_GP2A is not set
# CONFIG_INPUT_GPIO_TILT_POLLED is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_CMA3000 is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_NOZOMI is not set
# CONFIG_ISI is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
# CONFIG_DEVKMEM is not set
CONFIG_STALDRV=y
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_MFD_HSU is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=m
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EG20T is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_INTEL_MID is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX_PCI is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_TOPCLIFF_PCH is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_HSI is not set
#
# PPS support
#
CONFIG_PPS=m
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_GPIO is not set
#
# PPS generators support
#
#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=m
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
# CONFIG_PTP_1588_CLOCK_PCH is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_ACPI=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO drivers:
#
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_IT8761E is not set
# CONFIG_GPIO_TS5500 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_ICH is not set
# CONFIG_GPIO_VX855 is not set
#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_ADP5588 is not set
#
# PCI GPIO expanders:
#
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_LANGWELL is not set
# CONFIG_GPIO_PCH is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_RDC321X is not set
#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MCP23S08 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_74X164 is not set
#
# AC97 GPIO expanders:
#
#
# MODULbus GPIO expanders:
#
#
# USB GPIO expanders:
#
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_SMB347 is not set
# CONFIG_POWER_RESET is not set
# CONFIG_POWER_AVS is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_FAM15H_POWER is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_LINEAGE is not set
CONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH56XX_COMMON is not set
# CONFIG_SENSORS_ADS1015 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_APPLESMC is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
CONFIG_SENSORS_ATK0110=m
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_FAIR_SHARE is not set
CONFIG_STEP_WISE=y
# CONFIG_USER_SPACE is not set
# CONFIG_CPU_THERMAL is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_RTSX_PCI is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_UCB1400_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_CS5535 is not set
# CONFIG_MFD_TIMBERDALE is not set
# CONFIG_LPC_SCH is not set
# CONFIG_LPC_ICH is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_REGULATOR is not set
CONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
# CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set
# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set
# CONFIG_MEDIA_RADIO_SUPPORT is not set
# CONFIG_MEDIA_RC_SUPPORT is not set
# CONFIG_MEDIA_CONTROLLER is not set
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2=m
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
#
# Media drivers
#
# CONFIG_MEDIA_USB_SUPPORT is not set
# CONFIG_MEDIA_PCI_SUPPORT is not set
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_V4L_TEST_DRIVERS is not set
#
# Supported MMC/SDIO adapters
#
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
#
# Media ancillary drivers (tuners, sensors, i2c, frontends)
#
#
# Audio decoders, processors and mixers
#
#
# RDS decoders
#
#
# Video decoders
#
#
# Video and audio decoders
#
#
# MPEG video encoders
#
#
# Video encoders
#
#
# Camera sensor devices
#
#
# Flash devices
#
#
# Video improvement chips
#
#
# Miscelaneous helper chips
#
#
# Sensors used on soc_camera driver
#
#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_SIS=y
CONFIG_AGP_VIA=y
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
CONFIG_VGA_SWITCHEROO=y
CONFIG_DRM=m
CONFIG_DRM_USB=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
CONFIG_DRM_TTM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_KMS=y
# CONFIG_DRM_NOUVEAU is not set
#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I810 is not set
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_DRM_VMWGFX is not set
# CONFIG_DRM_GMA500 is not set
CONFIG_DRM_UDL=m
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_STUB_POULSBO is not set
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_WMT_GE_ROPS is not set
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
CONFIG_FB_CYBER2000=m
CONFIG_FB_CYBER2000_DDC=y
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
# CONFIG_FB_NVIDIA_I2C is not set
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
# CONFIG_FB_RIVA is not set
CONFIG_FB_I740=m
# CONFIG_FB_LE80578 is not set
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
# CONFIG_FB_MATROX_MAVEN is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
CONFIG_FB_S3=m
CONFIG_FB_S3_DDC=y
CONFIG_FB_SAVAGE=m
# CONFIG_FB_SAVAGE_I2C is not set
# CONFIG_FB_SAVAGE_ACCEL is not set
# CONFIG_FB_SIS is not set
CONFIG_FB_VIA=m
# CONFIG_FB_VIA_DIRECT_PROCFS is not set
CONFIG_FB_VIA_X_COMPATIBILITY=y
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_3DFX_I2C=y
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_AUO_K190X is not set
# CONFIG_EXYNOS_VIDEO is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630 is not set
# CONFIG_BACKLIGHT_LM3639 is not set
CONFIG_BACKLIGHT_LP855X=m
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
# CONFIG_SOUND_OSS_CORE_PRECLAIM is not set
CONFIG_SND=y
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
# CONFIG_SND_MIXER_OSS is not set
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_HRTIMER=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_KCTL_JACK=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_OPL3_LIB_SEQ=m
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
CONFIG_SND_EMU10K1_SEQ=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
CONFIG_SND_PCSP=m
CONFIG_SND_DUMMY=m
CONFIG_SND_ALOOP=m
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB16_DSP=m
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ASIHPI=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CS5530=m
CONFIG_SND_CS5535AUDIO=m
CONFIG_SND_CTXFI=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_INDIGOIOX=m
CONFIG_SND_INDIGODJX=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_ES1968_INPUT=y
# CONFIG_SND_ES1968_RADIO is not set
CONFIG_SND_FM801=m
# CONFIG_SND_FM801_TEA575X_BOOL is not set
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=1
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_HDMI=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CA0132=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_LOLA=m
CONFIG_SND_LX6464ES=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MAESTRO3_INPUT=y
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_UA101=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=m
CONFIG_SND_USB_6FIRE=m
CONFIG_SND_FIREWIRE=y
CONFIG_SND_FIREWIRE_LIB=m
CONFIG_SND_FIREWIRE_SPEAKERS=m
CONFIG_SND_ISIGHT=m
# CONFIG_SND_SCS1X is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
#
# HID support
#
CONFIG_HID=m
CONFIG_HIDRAW=y
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=m
#
# Special HID drivers
#
CONFIG_HID_A4TECH=m
# CONFIG_HID_ACRUX is not set
CONFIG_HID_APPLE=m
# CONFIG_HID_AUREAL is not set
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
# CONFIG_HID_PRODIKEYS is not set
CONFIG_HID_CYPRESS=m
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
CONFIG_HID_EZKEY=m
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_KEYTOUCH is not set
CONFIG_HID_KYE=m
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=m
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LENOVO_TPKBD is not set
CONFIG_HID_LOGITECH=m
CONFIG_HID_LOGITECH_DJ=m
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_LOGIG940_FF=y
CONFIG_LOGIWHEELS_FF=y
# CONFIG_HID_MAGICMOUSE is not set
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_PS3REMOTE is not set
# CONFIG_HID_ROCCAT is not set
CONFIG_HID_SAITEK=m
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
#
# USB HID support
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# I2C HID support
#
# CONFIG_I2C_HID is not set
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=m
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_CHIPIDEA is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB port drivers
#
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP210X=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
# CONFIG_USB_SERIAL_F81232 is not set
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_METRO is not set
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MOTOROLA=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
CONFIG_USB_SERIAL_QCAUX=m
CONFIG_USB_SERIAL_QUALCOMM=m
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIEMENS_MPI=m
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_SYMBOL=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_VIVOPAY_SERIAL=m
CONFIG_USB_SERIAL_ZIO=m
# CONFIG_USB_SERIAL_ZTE is not set
CONFIG_USB_SERIAL_SSU100=m
# CONFIG_USB_SERIAL_QT2 is not set
CONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
CONFIG_USB_EZUSB_FX2=m
#
# USB Physical Layer drivers
#
# CONFIG_USB_ISP1301 is not set
# CONFIG_USB_RCAR_PHY is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
CONFIG_EDAC_LEGACY_SYSFS=y
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_DECODE_MCE is not set
CONFIG_EDAC_MM_EDAC=m
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I3200 is not set
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
CONFIG_EDAC_I7CORE=m
# CONFIG_EDAC_I5000 is not set
# CONFIG_EDAC_I5100 is not set
# CONFIG_EDAC_I7300 is not set
# CONFIG_EDAC_SBRIDGE is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_DS2404 is not set
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
# CONFIG_INTEL_MID_DMAC is not set
CONFIG_INTEL_IOATDMA=m
# CONFIG_TIMB_DMA is not set
# CONFIG_PCH_DMA is not set
CONFIG_DMA_ENGINE=y
#
# DMA Clients
#
CONFIG_NET_DMA=y
CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not set
CONFIG_DCA=m
# CONFIG_AUXDISPLAY is not set
CONFIG_UIO=m
# CONFIG_UIO_CIF is not set
# CONFIG_UIO_PDRV is not set
# CONFIG_UIO_PDRV_GENIRQ is not set
# CONFIG_UIO_DMEM_GENIRQ is not set
# CONFIG_UIO_AEC is not set
# CONFIG_UIO_SERCOS3 is not set
# CONFIG_UIO_PCI_GENERIC is not set
# CONFIG_UIO_NETX is not set
CONFIG_VFIO_IOMMU_TYPE1=m
CONFIG_VFIO=m
CONFIG_VFIO_PCI=m
CONFIG_VIRTIO=m
#
# Virtio drivers
#
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
CONFIG_VIRTIO_MMIO=m
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
# CONFIG_STAGING is not set
# CONFIG_X86_PLATFORM_DEVICES is not set
#
# Hardware Spinlock drivers
#
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
# CONFIG_AMD_IOMMU is not set
CONFIG_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_DEFAULT_ON=y
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
CONFIG_IRQ_REMAP=y
#
# Remoteproc drivers (EXPERIMENTAL)
#
# CONFIG_STE_MODEM_RPROC is not set
#
# Rpmsg drivers (EXPERIMENTAL)
#
CONFIG_VIRT_DRIVERS=y
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
# CONFIG_IIO is not set
# CONFIG_VME_BUS is not set
# CONFIG_PWM is not set
# CONFIG_IPACK_BUS is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_EFI_VARS is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set
CONFIG_ISCSI_IBFT_FIND=y
# CONFIG_ISCSI_IBFT is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT23=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_BTRFS_FS=y
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
# CONFIG_QUOTA is not set
# CONFIG_QUOTACTL is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=m
# CONFIG_CUSE is not set
CONFIG_GENERIC_ACL=y
#
# Caches
#
CONFIG_FSCACHE=m
CONFIG_FSCACHE_STATS=y
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not set
# CONFIG_CACHEFILES is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
CONFIG_SQUASHFS=m
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_PSTORE=y
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_FTRACE is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_F2FS_FS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
CONFIG_NLS_UTF8=m
# CONFIG_DLM is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_READABLE_ASM is not set
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
# CONFIG_PROVE_RCU is not set
# CONFIG_SPARSE_RCU_POINTER is not set
CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_ATOMIC_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_RCU_CPU_STALL_INFO is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_LKDTM is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_FENTRY=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACER_MAX_TRACE=y
CONFIG_TRACE_CLOCK=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
# CONFIG_EVENT_POWER_TRACING_DEPRECATED is not set
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
CONFIG_FUNCTION_TRACER=y
CONFIG_FUNCTION_GRAPH_TRACER=y
CONFIG_IRQSOFF_TRACER=y
CONFIG_SCHED_TRACER=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
CONFIG_STACK_TRACER=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_KPROBE_EVENT=y
# CONFIG_UPROBE_EVENT is not set
CONFIG_PROBE_EVENTS=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_FUNCTION_PROFILER=y
CONFIG_FTRACE_MCOUNT_RECORD=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_ASYNC_RAID6_TEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_TEST_KSTRTOX is not set
CONFIG_STRICT_DEVMEM=y
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
CONFIG_DEBUG_SET_MODULE_RONX=y
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_DEBUG_TLBFLUSH is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
# CONFIG_X86_DECODER_SELFTEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
# CONFIG_DEBUG_NMI_SELFTEST is not set
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_ENCRYPTED_KEYS is not set
CONFIG_KEYS_DEBUG_PROC_KEYS=y
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_PATH=y
# CONFIG_INTEL_TXT is not set
# CONFIG_SECURITY_SELINUX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_IMA is not set
# CONFIG_EVM is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y
CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=m
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_PCRYPT=m
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
CONFIG_CRYPTO_ABLK_HELPER_X86=y
CONFIG_CRYPTO_GLUE_HELPER_X86=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_LRW=y
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=y
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=m
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_VMAC=m
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32C_X86_64=y
CONFIG_CRYPTO_CRC32C_INTEL=y
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA1_SSSE3=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
CONFIG_CRYPTO_AES_NI_INTEL=y
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_BLOWFISH_COMMON=m
CONFIG_CRYPTO_BLOWFISH_X86_64=m
CONFIG_CRYPTO_CAMELLIA=m
# CONFIG_CRYPTO_CAMELLIA_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64 is not set
CONFIG_CRYPTO_CAST_COMMON=m
CONFIG_CRYPTO_CAST5=m
# CONFIG_CRYPTO_CAST5_AVX_X86_64 is not set
CONFIG_CRYPTO_CAST6=m
# CONFIG_CRYPTO_CAST6_AVX_X86_64 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_X86_64=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m
# CONFIG_CRYPTO_SERPENT_AVX_X86_64 is not set
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_X86_64=m
CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m
# CONFIG_CRYPTO_TWOFISH_AVX_X86_64 is not set
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_ZLIB=m
CONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_USER_API=m
CONFIG_CRYPTO_USER_API_HASH=m
CONFIG_CRYPTO_USER_API_SKCIPHER=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
# CONFIG_ASYMMETRIC_KEY_TYPE is not set
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_HAVE_KVM_MSI=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
# CONFIG_KVM_AMD is not set
# CONFIG_KVM_MMU_AUDIT is not set
CONFIG_VHOST_NET=m
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_RAID6_PQ=m
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_PERCPU_RWSEM=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
# CONFIG_CRC8 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_NLATTR=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
CONFIG_AVERAGE=y
# CONFIG_CORDIC is not set
# CONFIG_DDR is not set
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-01-16 22:38 PCI warning on boot 3.8.0-rc1 Stephen Hemminger
@ 2013-01-30 21:59 ` Bjorn Helgaas
2013-02-04 18:36 ` Stephen Hemminger
0 siblings, 1 reply; 17+ messages in thread
From: Bjorn Helgaas @ 2013-01-30 21:59 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: linux-pci, David Woodhouse, iommu, alex.williamson
On Wed, Jan 16, 2013 at 3:38 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> I see this on boot in dmesg
>
> [ 0.574494] DMAR: No ATSR found
> [ 0.574549] IOMMU 0 0xfed90000: using Queued invalidation
> [ 0.574550] IOMMU 1 0xfed91000: using Queued invalidation
> [ 0.574554] IOMMU: Setting RMRR:
> [ 0.574583] IOMMU: Setting identity map for device 0000:00:02.0 [0xcf000000 -
> 0xdf1fffff]
> [ 0.575748] IOMMU: Setting identity map for device 0000:00:1d.0 [0xcd551000 -
> 0xcd56dfff]
> [ 0.575767] IOMMU: Setting identity map for device 0000:00:1a.0 [0xcd551000 -
> 0xcd56dfff]
> [ 0.575786] IOMMU: Setting identity map for device 0000:00:14.0 [0xcd551000 -
> 0xcd56dfff]
> [ 0.575797] IOMMU: Prepare 0-16MiB unity mapping for LPC
> [ 0.575806] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffff
> ff]
> [ 0.576186] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
> [ 0.576337] ------------[ cut here ]------------
> [ 0.576342] WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge
> +0x59/0x71()
> [ 0.576343] Hardware name: System Product Name
> [ 0.576344] Modules linked in:
> [ 0.576347] Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc1-net-next+ #4
> [ 0.576348] Call Trace:
> [ 0.576352] [<ffffffff81074261>] warn_slowpath_common+0x83/0x9c
> [ 0.576355] [<ffffffff813fae71>] ? bus_set_iommu+0x49/0x49
> [ 0.576357] [<ffffffff81074294>] warn_slowpath_null+0x1a/0x1c
> [ 0.576360] [<ffffffff812db618>] pci_find_upstream_pcie_bridge+0x59/0x71
> [ 0.576362] [<ffffffff813fd247>] intel_iommu_add_device+0x4d/0x17a
> [ 0.576364] [<ffffffff813faeab>] add_iommu_group+0x3a/0x48
> [ 0.576368] [<ffffffff8135d490>] bus_for_each_dev+0x57/0x89
> [ 0.576370] [<ffffffff813fae6a>] bus_set_iommu+0x42/0x49
> [ 0.576374] [<ffffffff81b1b1a5>] intel_iommu_init+0xa27/0xb44
> [ 0.576377] [<ffffffff8105dcf3>] ? free_init_pages+0xf5/0x10d
> [ 0.576379] [<ffffffff81aeb87d>] ? maybe_link.part.2+0x10b/0x10b
> [ 0.576382] [<ffffffff81aeef53>] ? memblock_find_dma_reserve+0x133/0x133
> [ 0.576384] [<ffffffff81aeef66>] pci_iommu_init+0x13/0x3e
> [ 0.576387] [<ffffffff8100023c>] do_one_initcall+0x7f/0x133
> [ 0.576390] [<ffffffff814d0c2c>] kernel_init+0x146/0x29b
> [ 0.576393] [<ffffffff81aea52f>] ? do_early_param+0x8c/0x8c
> [ 0.576395] [<ffffffff814d0ae6>] ? rest_init+0xda/0xda
> [ 0.576398] [<ffffffff814ed4dc>] ret_from_fork+0x7c/0xb0
> [ 0.576400] [<ffffffff814d0ae6>] ? rest_init+0xda/0xda
> [ 0.576406] ---[ end trace f709d1eb2b66cbf5 ]---
>
> $ sudo lspci -t -vv
> -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller
> +-01.0-[01-02]----00.0 Intel Corporation Ethernet Controller 10-Gigabit X540-AT2
> +-02.0 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
> +-14.0 Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
> +-16.0 Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1
> +-1a.0 Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2
> +-1b.0 Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller
> +-1c.0-[03]--
> +-1c.4-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
> +-1c.5-[05-06]----00.0-[06]--
> +-1d.0 Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1
> +-1f.0 Intel Corporation Z77 Express Chipset LPC Controller
> +-1f.2 Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
> \-1f.3 Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller
I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
this the first time you've turned on the IOMMU on that box?
It's the same warning as in this bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
it's just a quirk that turns off VT-d if we find certain broken
bridges. It doesn't look like you have any of those (although I don't
know what you have at 05:00.0).
Bjorn
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-01-30 21:59 ` Bjorn Helgaas
@ 2013-02-04 18:36 ` Stephen Hemminger
2013-02-04 20:28 ` Alex Williamson
0 siblings, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2013-02-04 18:36 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: linux-pci, David Woodhouse, iommu, alex.williamson
> I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> this the first time you've turned on the IOMMU on that box?
It exists in 3.7 and earlier kernels, just haven't turned on same config.
> It's the same warning as in this bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> it's just a quirk that turns off VT-d if we find certain broken
> bridges. It doesn't look like you have any of those (although I don't
> know what you have at 05:00.0).
>
> Bjorn
This is a standard ASUS motherboard, and don't want to disable VT-d.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 18:36 ` Stephen Hemminger
@ 2013-02-04 20:28 ` Alex Williamson
2013-02-04 20:30 ` Stephen Hemminger
2013-02-04 22:41 ` Alex Williamson
0 siblings, 2 replies; 17+ messages in thread
From: Alex Williamson @ 2013-02-04 20:28 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > this the first time you've turned on the IOMMU on that box?
>
> It exists in 3.7 and earlier kernels, just haven't turned on same config.
>
> > It's the same warning as in this bugzilla:
> > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > it's just a quirk that turns off VT-d if we find certain broken
> > bridges. It doesn't look like you have any of those (although I don't
> > know what you have at 05:00.0).
> >
> > Bjorn
>
> This is a standard ASUS motherboard, and don't want to disable VT-d.
Stephen,
Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
seen before? Does the patch below help?
Bjorn, I think we need to quirk it somehow. So far they've all been
PCI-to-PCI bridges attached to root ports where we expect it's actually
a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
to a downstream port. The patch below avoids the WARN and gives us a
device, but of course pci_is_pcie reports wrong for this device and may
cause some trickle down breakage. A more complete option might be to
add a is_pcie flag to the device that can be set independent of
pcie_cap. We'd need to check all the callers for assumptions, but then
we could put the quirk in one place and hopefully fix everything.
Thoughts? Thanks,
Alex
diff --git a/drivers/pci/search.c b/drivers/pci/search.c
index bf969ba..65ae270 100644
--- a/drivers/pci/search.c
+++ b/drivers/pci/search.c
@@ -42,6 +42,15 @@ pci_find_upstream_pcie_bridge(struct pci_dev *pdev)
}
/* PCI device should connect to a PCIe bridge */
if (pci_pcie_type(pdev) != PCI_EXP_TYPE_PCI_BRIDGE) {
+ /*
+ * Not all PCIe-to-PCI bridges expose a PCIe
+ * capability. If we make it to a PCIe root port
+ * and the previous device was a PCI-to-PCI bridge,
+ * assume it was really a PCIe-to-PCI bridge.
+ */
+ if (pci_pcie_type(pdev) == PCI_EXP_TYPE_ROOT_PORT &&
+ tmp && tmp->hdr_type == PCI_HEADER_TYPE_BRIDGE)
+ return tmp;
/* Busted hardware? */
WARN_ON_ONCE(1);
return NULL;
^ permalink raw reply related [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 20:28 ` Alex Williamson
@ 2013-02-04 20:30 ` Stephen Hemminger
2013-02-04 20:36 ` Alex Williamson
2013-02-04 22:41 ` Alex Williamson
1 sibling, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2013-02-04 20:30 UTC (permalink / raw)
To: Alex Williamson; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 04 Feb 2013 13:28:04 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > this the first time you've turned on the IOMMU on that box?
> >
> > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> >
> > > It's the same warning as in this bugzilla:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > it's just a quirk that turns off VT-d if we find certain broken
> > > bridges. It doesn't look like you have any of those (although I don't
> > > know what you have at 05:00.0).
> > >
> > > Bjorn
> >
> > This is a standard ASUS motherboard, and don't want to disable VT-d.
>
> Stephen,
>
> Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> seen before? Does the patch below help?
$ sudo lspci -vvv -s 5:00.0
05:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [c0] Subsystem: ASUSTeK Computer Inc. Device 8489
> Bjorn, I think we need to quirk it somehow. So far they've all been
> PCI-to-PCI bridges attached to root ports where we expect it's actually
> a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> to a downstream port. The patch below avoids the WARN and gives us a
> device, but of course pci_is_pcie reports wrong for this device and may
> cause some trickle down breakage. A more complete option might be to
> add a is_pcie flag to the device that can be set independent of
> pcie_cap. We'd need to check all the callers for assumptions, but then
> we could put the quirk in one place and hopefully fix everything.
> Thoughts? Thanks,
>
> Alex
>
>
> diff --git a/drivers/pci/search.c b/drivers/pci/search.c
> index bf969ba..65ae270 100644
> --- a/drivers/pci/search.c
> +++ b/drivers/pci/search.c
> @@ -42,6 +42,15 @@ pci_find_upstream_pcie_bridge(struct pci_dev *pdev)
> }
> /* PCI device should connect to a PCIe bridge */
> if (pci_pcie_type(pdev) != PCI_EXP_TYPE_PCI_BRIDGE) {
> + /*
> + * Not all PCIe-to-PCI bridges expose a PCIe
> + * capability. If we make it to a PCIe root port
> + * and the previous device was a PCI-to-PCI bridge,
> + * assume it was really a PCIe-to-PCI bridge.
> + */
> + if (pci_pcie_type(pdev) == PCI_EXP_TYPE_ROOT_PORT &&
> + tmp && tmp->hdr_type == PCI_HEADER_TYPE_BRIDGE)
> + return tmp;
> /* Busted hardware? */
> WARN_ON_ONCE(1);
> return NULL;
>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 20:30 ` Stephen Hemminger
@ 2013-02-04 20:36 ` Alex Williamson
0 siblings, 0 replies; 17+ messages in thread
From: Alex Williamson @ 2013-02-04 20:36 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 2013-02-04 at 12:30 -0800, Stephen Hemminger wrote:
> On Mon, 04 Feb 2013 13:28:04 -0700
> Alex Williamson <alex.williamson@redhat.com> wrote:
>
> > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > this the first time you've turned on the IOMMU on that box?
> > >
> > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > >
> > > > It's the same warning as in this bugzilla:
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > bridges. It doesn't look like you have any of those (although I don't
> > > > know what you have at 05:00.0).
> > > >
> > > > Bjorn
> > >
> > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> >
> > Stephen,
> >
> > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > seen before? Does the patch below help?
>
>
> $ sudo lspci -vvv -s 5:00.0
> 05:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) (prog-if 01 [Subtractive decode])
Someone has even decided to name this one a PCIe-to-PCI bridge despite
it lacking a PCIe capability. Thanks,
Alex
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
> I/O behind bridge: 0000f000-00000fff
> Memory behind bridge: fff00000-000fffff
> Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
> Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
> Capabilities: [c0] Subsystem: ASUSTeK Computer Inc. Device 8489
>
>
> > Bjorn, I think we need to quirk it somehow. So far they've all been
> > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > to a downstream port. The patch below avoids the WARN and gives us a
> > device, but of course pci_is_pcie reports wrong for this device and may
> > cause some trickle down breakage. A more complete option might be to
> > add a is_pcie flag to the device that can be set independent of
> > pcie_cap. We'd need to check all the callers for assumptions, but then
> > we could put the quirk in one place and hopefully fix everything.
> > Thoughts? Thanks,
> >
> > Alex
> >
> >
> > diff --git a/drivers/pci/search.c b/drivers/pci/search.c
> > index bf969ba..65ae270 100644
> > --- a/drivers/pci/search.c
> > +++ b/drivers/pci/search.c
> > @@ -42,6 +42,15 @@ pci_find_upstream_pcie_bridge(struct pci_dev *pdev)
> > }
> > /* PCI device should connect to a PCIe bridge */
> > if (pci_pcie_type(pdev) != PCI_EXP_TYPE_PCI_BRIDGE) {
> > + /*
> > + * Not all PCIe-to-PCI bridges expose a PCIe
> > + * capability. If we make it to a PCIe root port
> > + * and the previous device was a PCI-to-PCI bridge,
> > + * assume it was really a PCIe-to-PCI bridge.
> > + */
> > + if (pci_pcie_type(pdev) == PCI_EXP_TYPE_ROOT_PORT &&
> > + tmp && tmp->hdr_type == PCI_HEADER_TYPE_BRIDGE)
> > + return tmp;
> > /* Busted hardware? */
> > WARN_ON_ONCE(1);
> > return NULL;
> >
> >
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 20:28 ` Alex Williamson
2013-02-04 20:30 ` Stephen Hemminger
@ 2013-02-04 22:41 ` Alex Williamson
2013-02-05 1:36 ` Stephen Hemminger
2013-02-06 15:49 ` Stephen Hemminger
1 sibling, 2 replies; 17+ messages in thread
From: Alex Williamson @ 2013-02-04 22:41 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > this the first time you've turned on the IOMMU on that box?
> >
> > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> >
> > > It's the same warning as in this bugzilla:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > it's just a quirk that turns off VT-d if we find certain broken
> > > bridges. It doesn't look like you have any of those (although I don't
> > > know what you have at 05:00.0).
> > >
> > > Bjorn
> >
> > This is a standard ASUS motherboard, and don't want to disable VT-d.
>
> Stephen,
>
> Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> seen before? Does the patch below help?
>
> Bjorn, I think we need to quirk it somehow. So far they've all been
> PCI-to-PCI bridges attached to root ports where we expect it's actually
> a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> to a downstream port. The patch below avoids the WARN and gives us a
> device, but of course pci_is_pcie reports wrong for this device and may
> cause some trickle down breakage. A more complete option might be to
> add a is_pcie flag to the device that can be set independent of
> pcie_cap. We'd need to check all the callers for assumptions, but then
> we could put the quirk in one place and hopefully fix everything.
> Thoughts? Thanks,
This latter approach seems like it might be easier than I expected since
all the users are so well filtered through the access functions. A
quick look through who uses pci_is_pcie seems like this might be
complete, but more eyes are required. I'll upload this to the bz for
those reporters to test as well. Thoughts? Thanks,
Alex
commit 60d668a3cdeeb0e29570cf0043736436c146bde8
Author: Alex Williamson <alex.williamson@redhat.com>
Date: Mon Feb 4 15:34:34 2013 -0700
pci: Handle unadvertised PCIe bridges
There seem to be several PCIe-to-PCI bridges out in the wild that
blatantly ignore the PCIe specification and do not expose a PCIe
capability. We can attempt to deduce their existence by looking
for PCI bridges directly connected to root ports or downstream
ports. What this means is that pci_is_pcie() does not imply PCIe
capability and we un-deprecate is_pcie to denote the difference.
All the accesses seem to go through pcie_capability_reg_implemented,
so we can significantly limit the footprint of this change by
checking things there.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
diff --git a/drivers/pci/access.c b/drivers/pci/access.c
index 3af0478..3df24e7 100644
--- a/drivers/pci/access.c
+++ b/drivers/pci/access.c
@@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
{
- if (!pci_is_pcie(dev))
+ if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
return false;
switch (pos) {
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 6186f03..0a87b6b 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
dev->irq = irq;
}
+static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
+{
+ struct pci_dev *parent;
+
+ if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
+ pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
+ pci_is_root_bus(pdev->bus))
+ return false;
+
+ parent = pdev->bus->self;
+
+ if (pci_is_pcie(parent) &&
+ (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
+ pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
+ pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
+ pci_name(pdev));
+ return true;
+ }
+
+ return false;
+}
+
void set_pcie_port_type(struct pci_dev *pdev)
{
int pos;
- u16 reg16;
+ u16 flags, caps = 0;
pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
- if (!pos)
+ if (pos) {
+ pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
+ pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
+ } else if (is_unadvertised_pcie_bridge(pdev))
+ flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
+ else
return;
+
pdev->is_pcie = 1;
pdev->pcie_cap = pos;
- pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
- pdev->pcie_flags_reg = reg16;
- pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
- pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
+ pdev->pcie_flags_reg = flags;
+ pdev->pcie_mpss = caps & PCI_EXP_DEVCAP_PAYLOAD;
}
void set_pcie_hotplug_bridge(struct pci_dev *pdev)
diff --git a/include/linux/pci.h b/include/linux/pci.h
index 15472d6..c9ef42c 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -300,8 +300,8 @@ struct pci_dev {
unsigned int msix_enabled:1;
unsigned int ari_enabled:1; /* ARI forwarding */
unsigned int is_managed:1;
- unsigned int is_pcie:1; /* Obsolete. Will be removed.
- Use pci_is_pcie() instead */
+ unsigned int is_pcie:1; /* Don't access directly,
+ use pci_is_pcie() instead */
unsigned int needs_freset:1; /* Dev requires fundamental reset */
unsigned int state_saved:1;
unsigned int is_physfn:1;
@@ -1689,7 +1689,7 @@ static inline int pci_pcie_cap(struct pci_dev *dev)
*/
static inline bool pci_is_pcie(struct pci_dev *dev)
{
- return !!pci_pcie_cap(dev);
+ return dev->is_pcie;
}
/**
^ permalink raw reply related [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 22:41 ` Alex Williamson
@ 2013-02-05 1:36 ` Stephen Hemminger
2013-02-06 15:49 ` Stephen Hemminger
1 sibling, 0 replies; 17+ messages in thread
From: Stephen Hemminger @ 2013-02-05 1:36 UTC (permalink / raw)
To: Alex Williamson; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 04 Feb 2013 15:41:24 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> +
> + if (pci_is_pcie(parent) &&
> + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
> + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
> + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
> + pci_name(pdev));
Too whiny!
Two short lines seems to be more the enough. Users can't do anything about
hardware not following spec. Put any outher stuff into comments.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-04 22:41 ` Alex Williamson
2013-02-05 1:36 ` Stephen Hemminger
@ 2013-02-06 15:49 ` Stephen Hemminger
2013-02-06 15:58 ` Alex Williamson
1 sibling, 1 reply; 17+ messages in thread
From: Stephen Hemminger @ 2013-02-06 15:49 UTC (permalink / raw)
To: Alex Williamson; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 04 Feb 2013 15:41:24 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > this the first time you've turned on the IOMMU on that box?
> > >
> > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > >
> > > > It's the same warning as in this bugzilla:
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > bridges. It doesn't look like you have any of those (although I don't
> > > > know what you have at 05:00.0).
> > > >
> > > > Bjorn
> > >
> > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> >
> > Stephen,
> >
> > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > seen before? Does the patch below help?
> >
> > Bjorn, I think we need to quirk it somehow. So far they've all been
> > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > to a downstream port. The patch below avoids the WARN and gives us a
> > device, but of course pci_is_pcie reports wrong for this device and may
> > cause some trickle down breakage. A more complete option might be to
> > add a is_pcie flag to the device that can be set independent of
> > pcie_cap. We'd need to check all the callers for assumptions, but then
> > we could put the quirk in one place and hopefully fix everything.
> > Thoughts? Thanks,
>
> This latter approach seems like it might be easier than I expected since
> all the users are so well filtered through the access functions. A
> quick look through who uses pci_is_pcie seems like this might be
> complete, but more eyes are required. I'll upload this to the bz for
> those reporters to test as well. Thoughts? Thanks,
>
> Alex
On my hardware this gives:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.0-rc6+ (shemminger@nehalam) (gcc version 4.7.2 (Debian 4.7.2-5) ) #3 SMP Tue Feb 5 20:34:31 PST 2013
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-rc6+ root=UUID=1772a2c4-c197-4b0a-84dd-9982243242b7 ro quiet pci=assign-busses
...
[ 0.226369] ACPI: No dock devices found.
[ 0.226373] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.226734] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 0.226737] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.227337] pci_root PNP0A08:00: Requesting ACPI _OSC control (0x1d)
[ 0.227688] pci_root PNP0A08:00: ACPI _OSC control (0x18) granted
[ 0.229268] PCI host bridge to bus 0000:00
[ 0.229271] pci_bus 0000:00: root bus resource [bus 00-3e]
[ 0.229273] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.229275] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.229276] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.229278] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
[ 0.229280] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
[ 0.229281] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
[ 0.229283] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
[ 0.229286] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
[ 0.229287] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
[ 0.229289] pci_bus 0000:00: root bus resource [mem 0xdf200000-0xfeafffff]
[ 0.229316] pci 0000:00:00.0: [8086:0150] type 00 class 0x060000
[ 0.229386] pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
[ 0.229427] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.229470] pci 0000:00:02.0: [8086:0162] type 00 class 0x030000
[ 0.229482] pci 0000:00:02.0: reg 10: [mem 0xf7800000-0xf7bfffff 64bit]
[ 0.229490] pci 0000:00:02.0: reg 18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.229495] pci 0000:00:02.0: reg 20: [io 0xf000-0xf03f]
[ 0.229560] pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
[ 0.229584] pci 0000:00:14.0: reg 10: [mem 0xf7d00000-0xf7d0ffff 64bit]
[ 0.229667] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.229693] pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
[ 0.229719] pci 0000:00:16.0: reg 10: [mem 0xf7d1a000-0xf7d1a00f 64bit]
[ 0.229805] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.229844] pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
[ 0.229868] pci 0000:00:1a.0: reg 10: [mem 0xf7d18000-0xf7d183ff]
[ 0.229972] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.230002] pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
[ 0.230018] pci 0000:00:1b.0: reg 10: [mem 0xf7d10000-0xf7d13fff 64bit]
[ 0.230098] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.230126] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
[ 0.230217] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.230250] pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
[ 0.230340] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.230370] pci 0000:00:1c.5: [8086:244e] type 01 class 0x060401
[ 0.230461] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.230498] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
[ 0.230525] pci 0000:00:1d.0: reg 10: [mem 0xf7d17000-0xf7d173ff]
[ 0.230629] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.230659] pci 0000:00:1f.0: [8086:1e44] type 00 class 0x060100
[ 0.230799] pci 0000:00:1f.2: [8086:1e02] type 00 class 0x010601
[ 0.230820] pci 0000:00:1f.2: reg 10: [io 0xf0b0-0xf0b7]
[ 0.230828] pci 0000:00:1f.2: reg 14: [io 0xf0a0-0xf0a3]
[ 0.230837] pci 0000:00:1f.2: reg 18: [io 0xf090-0xf097]
[ 0.230845] pci 0000:00:1f.2: reg 1c: [io 0xf080-0xf083]
[ 0.230853] pci 0000:00:1f.2: reg 20: [io 0xf060-0xf07f]
[ 0.230862] pci 0000:00:1f.2: reg 24: [mem 0xf7d16000-0xf7d167ff]
[ 0.230915] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.230936] pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
[ 0.230952] pci 0000:00:1f.3: reg 10: [mem 0xf7d15000-0xf7d150ff 64bit]
[ 0.230976] pci 0000:00:1f.3: reg 20: [io 0xf040-0xf05f]
[ 0.231054] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
[ 0.231071] pci 0000:01:00.0: [8086:1528] type 00 class 0x020000
[ 0.231084] pci 0000:01:00.0: reg 10: [mem 0xf0000000-0xf01fffff 64bit pref]
[ 0.231108] pci 0000:01:00.0: reg 20: [mem 0xf0200000-0xf0203fff 64bit pref]
[ 0.231115] pci 0000:01:00.0: reg 30: [mem 0xf7c00000-0xf7c7ffff pref]
[ 0.231154] pci 0000:01:00.0: PME# supported from D0 D3hot
[ 0.231185] pci 0000:01:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 0.231200] pci 0000:01:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 0.238547] pci 0000:00:01.0: PCI bridge to [bus 01-ff]
[ 0.238565] pci 0000:00:01.0: bridge window [mem 0xf7c00000-0xf7cfffff]
[ 0.238568] pci 0000:00:01.0: bridge window [mem 0xf0000000-0xf02fffff 64bit pref]
[ 0.238571] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 02
[ 0.238623] pci_bus 0000:03: busn_res: can not insert [bus 03-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
[ 0.238628] pci 0000:00:1c.0: PCI bridge to [bus 03-ff]
[ 0.238639] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[ 0.238690] pci_bus 0000:04: busn_res: can not insert [bus 04-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
[ 0.238719] pci 0000:04:00.0: [10ec:8168] type 00 class 0x020000
[ 0.238740] pci 0000:04:00.0: reg 10: [io 0xe000-0xe0ff]
[ 0.238777] pci 0000:04:00.0: reg 18: [mem 0xf0404000-0xf0404fff 64bit pref]
[ 0.238800] pci 0000:04:00.0: reg 20: [mem 0xf0400000-0xf0403fff 64bit pref]
[ 0.238902] pci 0000:04:00.0: supports D1 D2
[ 0.238903] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.254537] pci 0000:00:1c.4: PCI bridge to [bus 04-ff]
[ 0.254544] pci 0000:00:1c.4: bridge window [io 0xe000-0xefff]
[ 0.254566] pci 0000:00:1c.4: bridge window [mem 0xf0400000-0xf04fffff 64bit pref]
[ 0.254568] pci_bus 0000:04: busn_res: [bus 04-ff] end is updated to 04
[ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
[ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
[ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
[ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
[ 0.254647] PCI express capability structure is required for PCI express device
[ 0.254647] functions.
[ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
[ 0.266521] pci 0000:00:1c.5: PCI bridge to [bus 05-ff] (subtractive decode)
[ 0.266540] pci 0000:00:1c.5: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 0.266543] pci 0000:00:1c.5: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.266547] pci 0000:00:1c.5: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.266550] pci 0000:00:1c.5: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
[ 0.266554] pci 0000:00:1c.5: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
[ 0.266566] pci 0000:00:1c.5: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
[ 0.266567] pci 0000:00:1c.5: bridge window [mem 0x000dc000-0x000dffff] (subtractive decode)
[ 0.266569] pci 0000:00:1c.5: bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
[ 0.266570] pci 0000:00:1c.5: bridge window [mem 0x000e4000-0x000e7fff] (subtractive decode)
[ 0.266572] pci 0000:00:1c.5: bridge window [mem 0xdf200000-0xfeafffff] (subtractive decode)
[ 0.266576] pci 0000:05:00.0: bridge configuration invalid ([bus 05-05]), reconfiguring
[ 0.266715] pci 0000:05:00.0: PCI bridge to [bus 06-ff] (subtractive decode)
[ 0.266739] pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
[ 0.266740] pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
[ 0.266742] pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
[ 0.266744] pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
[ 0.266745] pci 0000:05:00.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 0.266747] pci 0000:05:00.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.266748] pci 0000:05:00.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.266750] pci 0000:05:00.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
[ 0.266752] pci 0000:05:00.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
[ 0.266753] pci 0000:05:00.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
[ 0.266755] pci 0000:05:00.0: bridge window [mem 0x000dc000-0x000dffff] (subtractive decode)
[ 0.266756] pci 0000:05:00.0: bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
[ 0.266758] pci 0000:05:00.0: bridge window [mem 0x000e4000-0x000e7fff] (subtractive decode)
[ 0.266760] pci 0000:05:00.0: bridge window [mem 0xdf200000-0xfeafffff] (subtractive decode)
[ 0.266761] pci_bus 0000:06: busn_res: [bus 06-ff] end is updated to 06
[ 0.266768] pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 06
[ 0.266814] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
[ 0.266887] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
[ 0.266946] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
[ 0.267008] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06.P9PE._PRT]
[ 0.267103] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG0._PRT]
[ 0.275012] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.275086] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 0.275157] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *10 11 12 14 15)
[ 0.275227] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
[ 0.275298] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 0.275369] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 *10 11 12 14 15)
[ 0.275444] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 10 11 12 14 15)
[ 0.275514] ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 10 11 12 14 15)
[ 0.275748] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.275754] vgaarb: loaded
[ 0.275755] vgaarb: bridge control possible 0000:00:02.0
[ 0.275888] SCSI subsystem initialized
[ 0.275890] ACPI: bus type scsi registered
[ 0.275938] libata version 3.00 loaded.
[ 0.275947] ACPI: bus type usb registered
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-06 15:49 ` Stephen Hemminger
@ 2013-02-06 15:58 ` Alex Williamson
2013-02-12 4:15 ` Alex Williamson
2013-04-10 22:36 ` Bjorn Helgaas
0 siblings, 2 replies; 17+ messages in thread
From: Alex Williamson @ 2013-02-06 15:58 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> On Mon, 04 Feb 2013 15:41:24 -0700
> Alex Williamson <alex.williamson@redhat.com> wrote:
>
> > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > > this the first time you've turned on the IOMMU on that box?
> > > >
> > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > > >
> > > > > It's the same warning as in this bugzilla:
> > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > > bridges. It doesn't look like you have any of those (although I don't
> > > > > know what you have at 05:00.0).
> > > > >
> > > > > Bjorn
> > > >
> > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> > >
> > > Stephen,
> > >
> > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > > seen before? Does the patch below help?
> > >
> > > Bjorn, I think we need to quirk it somehow. So far they've all been
> > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > > to a downstream port. The patch below avoids the WARN and gives us a
> > > device, but of course pci_is_pcie reports wrong for this device and may
> > > cause some trickle down breakage. A more complete option might be to
> > > add a is_pcie flag to the device that can be set independent of
> > > pcie_cap. We'd need to check all the callers for assumptions, but then
> > > we could put the quirk in one place and hopefully fix everything.
> > > Thoughts? Thanks,
> >
> > This latter approach seems like it might be easier than I expected since
> > all the users are so well filtered through the access functions. A
> > quick look through who uses pci_is_pcie seems like this might be
> > complete, but more eyes are required. I'll upload this to the bz for
> > those reporters to test as well. Thoughts? Thanks,
> >
> > Alex
>
> On my hardware this gives:
> [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> [ 0.254647] PCI express capability structure is required for PCI express device
> [ 0.254647] functions.
> [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
I guess I must be calling pci_name() before it's set. The warning
message needs some work too, it's mainly meant for hardware vendors with
the hope that they might test Linux and see it before shipping these
broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
Alex
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-06 15:58 ` Alex Williamson
@ 2013-02-12 4:15 ` Alex Williamson
2013-02-12 18:33 ` Stephen Hemminger
2013-04-10 22:36 ` Bjorn Helgaas
1 sibling, 1 reply; 17+ messages in thread
From: Alex Williamson @ 2013-02-12 4:15 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Wed, 2013-02-06 at 08:58 -0700, Alex Williamson wrote:
> On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> > On Mon, 04 Feb 2013 15:41:24 -0700
> > Alex Williamson <alex.williamson@redhat.com> wrote:
> >
> > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > > > this the first time you've turned on the IOMMU on that box?
> > > > >
> > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > > > >
> > > > > > It's the same warning as in this bugzilla:
> > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > > > bridges. It doesn't look like you have any of those (although I don't
> > > > > > know what you have at 05:00.0).
> > > > > >
> > > > > > Bjorn
> > > > >
> > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> > > >
> > > > Stephen,
> > > >
> > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > > > seen before? Does the patch below help?
> > > >
> > > > Bjorn, I think we need to quirk it somehow. So far they've all been
> > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > > > to a downstream port. The patch below avoids the WARN and gives us a
> > > > device, but of course pci_is_pcie reports wrong for this device and may
> > > > cause some trickle down breakage. A more complete option might be to
> > > > add a is_pcie flag to the device that can be set independent of
> > > > pcie_cap. We'd need to check all the callers for assumptions, but then
> > > > we could put the quirk in one place and hopefully fix everything.
> > > > Thoughts? Thanks,
> > >
> > > This latter approach seems like it might be easier than I expected since
> > > all the users are so well filtered through the access functions. A
> > > quick look through who uses pci_is_pcie seems like this might be
> > > complete, but more eyes are required. I'll upload this to the bz for
> > > those reporters to test as well. Thoughts? Thanks,
> > >
> > > Alex
> >
> > On my hardware this gives:
>
> > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> > [ 0.254647] PCI express capability structure is required for PCI express device
> > [ 0.254647] functions.
> > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
>
> I guess I must be calling pci_name() before it's set. The warning
> message needs some work too, it's mainly meant for hardware vendors with
> the hope that they might test Linux and see it before shipping these
> broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
I don't know if it sways how we handle this devices, but a couple notes
on the asmedia chip. I have one in a non-VT-d capable system and an
add-in legacy PCI NIC shows up behind it when added to the system. The
chip is visible on the board and is an ASM1083. Asmedia's website of
course claims this device is fully compliant with the PCIe-to-PCI bridge
spec, ignoring the multiple statements the spec contains requiring such
devices to support a PCIe capability.
Additionally, if you google for ASM1083 you'll find the next highest
links after the product links are bug reports that not only is this
device non-spec complaint, but it doesn't work. There seems to be an
issue with how INTx is de-asserted (or not) leading to interrupt storms
and requiring the use of irqpoll. Sure enough, the tulip card I
installed generated some of these and is operating in polling mode. The
threads indicate that these issues are not isolated to Linux and Windows
users also complain about devices not working or having poor performance
installed behind this bridge. All in all, it's an absurdly broken piece
of hardware.
I wonder if instead of trying to work around it, we should just
blacklist the device and ignore that it even exists. Stop the bus walk
with some kind of dmesg error and provide a boot time option to scan it.
It's not the most user friendly option, but a) most people don't seem to
have anything behind it, b) it barely works if they do. Thanks,
Alex
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-12 4:15 ` Alex Williamson
@ 2013-02-12 18:33 ` Stephen Hemminger
0 siblings, 0 replies; 17+ messages in thread
From: Stephen Hemminger @ 2013-02-12 18:33 UTC (permalink / raw)
To: Alex Williamson; +Cc: Bjorn Helgaas, linux-pci, David Woodhouse, iommu
On Mon, 11 Feb 2013 21:15:56 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> On Wed, 2013-02-06 at 08:58 -0700, Alex Williamson wrote:
> > On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> > > On Mon, 04 Feb 2013 15:41:24 -0700
> > > Alex Williamson <alex.williamson@redhat.com> wrote:
> > >
> > > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > > > > this the first time you've turned on the IOMMU on that box?
> > > > > >
> > > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > > > > >
> > > > > > > It's the same warning as in this bugzilla:
> > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > > > > bridges. It doesn't look like you have any of those (although I don't
> > > > > > > know what you have at 05:00.0).
> > > > > > >
> > > > > > > Bjorn
> > > > > >
> > > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> > > > >
> > > > > Stephen,
> > > > >
> > > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > > > > seen before? Does the patch below help?
> > > > >
> > > > > Bjorn, I think we need to quirk it somehow. So far they've all been
> > > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > > > > to a downstream port. The patch below avoids the WARN and gives us a
> > > > > device, but of course pci_is_pcie reports wrong for this device and may
> > > > > cause some trickle down breakage. A more complete option might be to
> > > > > add a is_pcie flag to the device that can be set independent of
> > > > > pcie_cap. We'd need to check all the callers for assumptions, but then
> > > > > we could put the quirk in one place and hopefully fix everything.
> > > > > Thoughts? Thanks,
> > > >
> > > > This latter approach seems like it might be easier than I expected since
> > > > all the users are so well filtered through the access functions. A
> > > > quick look through who uses pci_is_pcie seems like this might be
> > > > complete, but more eyes are required. I'll upload this to the bz for
> > > > those reporters to test as well. Thoughts? Thanks,
> > > >
> > > > Alex
> > >
> > > On my hardware this gives:
> >
> > > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> > > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> > > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> > > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> > > [ 0.254647] PCI express capability structure is required for PCI express device
> > > [ 0.254647] functions.
> > > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
> >
> > I guess I must be calling pci_name() before it's set. The warning
> > message needs some work too, it's mainly meant for hardware vendors with
> > the hope that they might test Linux and see it before shipping these
> > broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
>
> I don't know if it sways how we handle this devices, but a couple notes
> on the asmedia chip. I have one in a non-VT-d capable system and an
> add-in legacy PCI NIC shows up behind it when added to the system. The
> chip is visible on the board and is an ASM1083. Asmedia's website of
> course claims this device is fully compliant with the PCIe-to-PCI bridge
> spec, ignoring the multiple statements the spec contains requiring such
> devices to support a PCIe capability.
>
> Additionally, if you google for ASM1083 you'll find the next highest
> links after the product links are bug reports that not only is this
> device non-spec complaint, but it doesn't work. There seems to be an
> issue with how INTx is de-asserted (or not) leading to interrupt storms
> and requiring the use of irqpoll. Sure enough, the tulip card I
> installed generated some of these and is operating in polling mode. The
> threads indicate that these issues are not isolated to Linux and Windows
> users also complain about devices not working or having poor performance
> installed behind this bridge. All in all, it's an absurdly broken piece
> of hardware.
>
> I wonder if instead of trying to work around it, we should just
> blacklist the device and ignore that it even exists. Stop the bus walk
> with some kind of dmesg error and provide a boot time option to scan it.
> It's not the most user friendly option, but a) most people don't seem to
> have anything behind it, b) it barely works if they do. Thanks,
Having special case quirk makes a lot of sense, but it needs to be done
with care. For people like me who don't use the PCI slots, a simple one
line warning is enough (and blacklist).
Fully ignoring it would probably break users that are attempting to
use the PCI slots. If there are devices on that PCI bus, the kernel should
print out a big warning and engage some sort of fallback like irqpoll.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-02-06 15:58 ` Alex Williamson
2013-02-12 4:15 ` Alex Williamson
@ 2013-04-10 22:36 ` Bjorn Helgaas
2013-04-11 0:01 ` Alex Williamson
1 sibling, 1 reply; 17+ messages in thread
From: Bjorn Helgaas @ 2013-04-10 22:36 UTC (permalink / raw)
To: Alex Williamson; +Cc: Stephen Hemminger, linux-pci, David Woodhouse, iommu
On Wed, Feb 06, 2013 at 08:58:41AM -0700, Alex Williamson wrote:
> On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> > On Mon, 04 Feb 2013 15:41:24 -0700
> > Alex Williamson <alex.williamson@redhat.com> wrote:
> >
> > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > > > this the first time you've turned on the IOMMU on that box?
> > > > >
> > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > > > >
> > > > > > It's the same warning as in this bugzilla:
> > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > > > bridges. It doesn't look like you have any of those (although I don't
> > > > > > know what you have at 05:00.0).
> > > > > >
> > > > > > Bjorn
> > > > >
> > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> > > >
> > > > Stephen,
> > > >
> > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > > > seen before? Does the patch below help?
> > > >
> > > > Bjorn, I think we need to quirk it somehow. So far they've all been
> > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > > > to a downstream port. The patch below avoids the WARN and gives us a
> > > > device, but of course pci_is_pcie reports wrong for this device and may
> > > > cause some trickle down breakage. A more complete option might be to
> > > > add a is_pcie flag to the device that can be set independent of
> > > > pcie_cap. We'd need to check all the callers for assumptions, but then
> > > > we could put the quirk in one place and hopefully fix everything.
> > > > Thoughts? Thanks,
> > >
> > > This latter approach seems like it might be easier than I expected since
> > > all the users are so well filtered through the access functions. A
> > > quick look through who uses pci_is_pcie seems like this might be
> > > complete, but more eyes are required. I'll upload this to the bz for
> > > those reporters to test as well. Thoughts? Thanks,
> > >
> > > Alex
> >
> > On my hardware this gives:
>
> > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> > [ 0.254647] PCI express capability structure is required for PCI express device
> > [ 0.254647] functions.
> > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
>
> I guess I must be calling pci_name() before it's set. The warning
> message needs some work too, it's mainly meant for hardware vendors with
> the hope that they might test Linux and see it before shipping these
> broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
Sorry I dropped this for so long. I'm looking at the patch
here: https://bugzilla.kernel.org/attachment.cgi?id=92521,
appended for convenience.
In case anybody else needs the context, I think we have
this scenario (from John Wehin's original report at
https://bugzilla.kernel.org/show_bug.cgi?id=44881):
pci 0000:00:1c.4: PCI bridge to [bus 03-04] # PCIe root port
pci 0000:03:00.0: PCI bridge to [bus 04] # no PCIe cap
...
pci 0000:03:00.0: expected upstream PCIe bridge; 0000:00:1c.4 is type 0x4
We called pci_find_upstream_pcie_bridge(03:00.0), which generated
the warning because:
- 03:00.0 is not a PCIe device, and
- 00:1c.4 (its upstream bridge) *is* a PCIe device, and
- 00:1c.4 is a Root Port (PCI_EXP_TYPE_ROOT_PORT == 0x4),
not a PCIe-to-PCI bridge (PCI_EXP_TYPE_PCI_BRIDGE == 0x7)
as we expected
> commit 60d668a3cdeeb0e29570cf0043736436c146bde8
> Author: Alex Williamson <alex.williamson@redhat.com>
> Date: Mon Feb 4 15:34:34 2013 -0700
>
> pci: Handle unadvertised PCIe bridges
>
> There seem to be several PCIe-to-PCI bridges out in the wild that
> blatantly ignore the PCIe specification and do not expose a PCIe
> capability. We can attempt to deduce their existence by looking
> for PCI bridges directly connected to root ports or downstream
> ports. What this means is that pci_is_pcie() does not imply PCIe
> capability and we un-deprecate is_pcie to denote the difference.
> All the accesses seem to go through pcie_capability_reg_implemented,
> so we can significantly limit the footprint of this change by
> checking things there.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>
> diff --git a/drivers/pci/access.c b/drivers/pci/access.c
> index 3af0478..3df24e7 100644
> --- a/drivers/pci/access.c
> +++ b/drivers/pci/access.c
> @@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
>
> static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
> {
> - if (!pci_is_pcie(dev))
> + if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
> return false;
>
> switch (pos) {
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 6186f03..0a87b6b 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
> dev->irq = irq;
> }
>
> +static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
> +{
> + struct pci_dev *parent;
> +
> + if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
> + pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
> + pci_is_root_bus(pdev->bus))
> + return false;
> +
> + parent = pdev->bus->self;
> +
> + if (pci_is_pcie(parent) &&
> + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
> + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
> + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
> + pci_name(pdev));
Vendors might see this warning, but I'm doubtful they'll do anything
about it. I suspect it will result in a lot of emails from concerned
users to LKML and linux-pci, and we really can't do anything other
than say "yup, it's broken, report it to your vendor."
And since the hardware seems to actually *work* if we just pretend that
the problem device (e.g., 03:00.0 above) is PCIe, it's doubtful that
the vendor would do anything anyway, so maybe a dev_info() would be
sufficient.
> + return true;
> + }
> +
> + return false;
> +}
> +
> void set_pcie_port_type(struct pci_dev *pdev)
> {
> int pos;
> - u16 reg16;
> + u16 flags, caps = 0;
>
> pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
> - if (!pos)
> + if (pos) {
> + pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
> + pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
> + } else if (is_unadvertised_pcie_bridge(pdev))
> + flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
> + else
> return;
> +
> pdev->is_pcie = 1;
> pdev->pcie_cap = pos;
> - pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
> - pdev->pcie_flags_reg = reg16;
> - pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
> - pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
> + pdev->pcie_flags_reg = flags;
If we can avoid it, I'd prefer not to complicate the meaning of
"pci_is_pcie()" -- it used to mean "this device has a PCIe
capability and you can do PCIe things with it." But now it
means something else, and we can't do PCIe things with these
problem devices anyway.
Could we accomplish basically the same thing by making
pci_find_upstream_pcie_bridge() look like this?
if (pci_is_pcie(pdev))
return NULL;
+ bridge = pdev->bus->self;
+ if (bridge && pci_is_pcie(bridge) &&
+ (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT ||
+ pci_pcie_type(bridge) == PCI_EXP_TYPE_DOWNSTREAM))
+ return NULL;
while (1) {
...
Bjorn
> + pdev->pcie_mpss = caps & PCI_EXP_DEVCAP_PAYLOAD;
> }
>
> void set_pcie_hotplug_bridge(struct pci_dev *pdev)
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 15472d6..c9ef42c 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -300,8 +300,8 @@ struct pci_dev {
> unsigned int msix_enabled:1;
> unsigned int ari_enabled:1; /* ARI forwarding */
> unsigned int is_managed:1;
> - unsigned int is_pcie:1; /* Obsolete. Will be removed.
> - Use pci_is_pcie() instead */
> + unsigned int is_pcie:1; /* Don't access directly,
> + use pci_is_pcie() instead */
> unsigned int needs_freset:1; /* Dev requires fundamental reset */
> unsigned int state_saved:1;
> unsigned int is_physfn:1;
> @@ -1689,7 +1689,7 @@ static inline int pci_pcie_cap(struct pci_dev *dev)
> */
> static inline bool pci_is_pcie(struct pci_dev *dev)
> {
> - return !!pci_pcie_cap(dev);
> + return dev->is_pcie;
> }
>
> /**
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-04-10 22:36 ` Bjorn Helgaas
@ 2013-04-11 0:01 ` Alex Williamson
2013-04-11 17:23 ` Bjorn Helgaas
0 siblings, 1 reply; 17+ messages in thread
From: Alex Williamson @ 2013-04-11 0:01 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: Stephen Hemminger, linux-pci, David Woodhouse, iommu
On Wed, 2013-04-10 at 16:36 -0600, Bjorn Helgaas wrote:
> On Wed, Feb 06, 2013 at 08:58:41AM -0700, Alex Williamson wrote:
> > On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> > > On Mon, 04 Feb 2013 15:41:24 -0700
> > > Alex Williamson <alex.williamson@redhat.com> wrote:
> > >
> > > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> > > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> > > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> > > > > > > this the first time you've turned on the IOMMU on that box?
> > > > > >
> > > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> > > > > >
> > > > > > > It's the same warning as in this bugzilla:
> > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> > > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> > > > > > > it's just a quirk that turns off VT-d if we find certain broken
> > > > > > > bridges. It doesn't look like you have any of those (although I don't
> > > > > > > know what you have at 05:00.0).
> > > > > > >
> > > > > > > Bjorn
> > > > > >
> > > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> > > > >
> > > > > Stephen,
> > > > >
> > > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> > > > > seen before? Does the patch below help?
> > > > >
> > > > > Bjorn, I think we need to quirk it somehow. So far they've all been
> > > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> > > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> > > > > to a downstream port. The patch below avoids the WARN and gives us a
> > > > > device, but of course pci_is_pcie reports wrong for this device and may
> > > > > cause some trickle down breakage. A more complete option might be to
> > > > > add a is_pcie flag to the device that can be set independent of
> > > > > pcie_cap. We'd need to check all the callers for assumptions, but then
> > > > > we could put the quirk in one place and hopefully fix everything.
> > > > > Thoughts? Thanks,
> > > >
> > > > This latter approach seems like it might be easier than I expected since
> > > > all the users are so well filtered through the access functions. A
> > > > quick look through who uses pci_is_pcie seems like this might be
> > > > complete, but more eyes are required. I'll upload this to the bz for
> > > > those reporters to test as well. Thoughts? Thanks,
> > > >
> > > > Alex
> > >
> > > On my hardware this gives:
> >
> > > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> > > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> > > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> > > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> > > [ 0.254647] PCI express capability structure is required for PCI express device
> > > [ 0.254647] functions.
> > > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
> >
> > I guess I must be calling pci_name() before it's set. The warning
> > message needs some work too, it's mainly meant for hardware vendors with
> > the hope that they might test Linux and see it before shipping these
> > broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
>
> Sorry I dropped this for so long. I'm looking at the patch
> here: https://bugzilla.kernel.org/attachment.cgi?id=92521,
> appended for convenience.
>
> In case anybody else needs the context, I think we have
> this scenario (from John Wehin's original report at
> https://bugzilla.kernel.org/show_bug.cgi?id=44881):
>
> pci 0000:00:1c.4: PCI bridge to [bus 03-04] # PCIe root port
> pci 0000:03:00.0: PCI bridge to [bus 04] # no PCIe cap
> ...
> pci 0000:03:00.0: expected upstream PCIe bridge; 0000:00:1c.4 is type 0x4
>
> We called pci_find_upstream_pcie_bridge(03:00.0), which generated
> the warning because:
>
> - 03:00.0 is not a PCIe device, and
> - 00:1c.4 (its upstream bridge) *is* a PCIe device, and
> - 00:1c.4 is a Root Port (PCI_EXP_TYPE_ROOT_PORT == 0x4),
> not a PCIe-to-PCI bridge (PCI_EXP_TYPE_PCI_BRIDGE == 0x7)
> as we expected
>
> > commit 60d668a3cdeeb0e29570cf0043736436c146bde8
> > Author: Alex Williamson <alex.williamson@redhat.com>
> > Date: Mon Feb 4 15:34:34 2013 -0700
> >
> > pci: Handle unadvertised PCIe bridges
> >
> > There seem to be several PCIe-to-PCI bridges out in the wild that
> > blatantly ignore the PCIe specification and do not expose a PCIe
> > capability. We can attempt to deduce their existence by looking
> > for PCI bridges directly connected to root ports or downstream
> > ports. What this means is that pci_is_pcie() does not imply PCIe
> > capability and we un-deprecate is_pcie to denote the difference.
> > All the accesses seem to go through pcie_capability_reg_implemented,
> > so we can significantly limit the footprint of this change by
> > checking things there.
> >
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > diff --git a/drivers/pci/access.c b/drivers/pci/access.c
> > index 3af0478..3df24e7 100644
> > --- a/drivers/pci/access.c
> > +++ b/drivers/pci/access.c
> > @@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
> >
> > static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
> > {
> > - if (!pci_is_pcie(dev))
> > + if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
> > return false;
> >
> > switch (pos) {
> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > index 6186f03..0a87b6b 100644
> > --- a/drivers/pci/probe.c
> > +++ b/drivers/pci/probe.c
> > @@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
> > dev->irq = irq;
> > }
> >
> > +static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
> > +{
> > + struct pci_dev *parent;
> > +
> > + if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
> > + pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
> > + pci_is_root_bus(pdev->bus))
> > + return false;
> > +
> > + parent = pdev->bus->self;
> > +
> > + if (pci_is_pcie(parent) &&
> > + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
> > + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
> > + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
> > + pci_name(pdev));
>
> Vendors might see this warning, but I'm doubtful they'll do anything
> about it. I suspect it will result in a lot of emails from concerned
> users to LKML and linux-pci, and we really can't do anything other
> than say "yup, it's broken, report it to your vendor."
>
> And since the hardware seems to actually *work* if we just pretend that
> the problem device (e.g., 03:00.0 above) is PCIe, it's doubtful that
> the vendor would do anything anyway, so maybe a dev_info() would be
> sufficient.
>
> > + return true;
> > + }
> > +
> > + return false;
> > +}
> > +
> > void set_pcie_port_type(struct pci_dev *pdev)
> > {
> > int pos;
> > - u16 reg16;
> > + u16 flags, caps = 0;
> >
> > pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
> > - if (!pos)
> > + if (pos) {
> > + pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
> > + pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
> > + } else if (is_unadvertised_pcie_bridge(pdev))
> > + flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
> > + else
> > return;
> > +
> > pdev->is_pcie = 1;
> > pdev->pcie_cap = pos;
> > - pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
> > - pdev->pcie_flags_reg = reg16;
> > - pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
> > - pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
> > + pdev->pcie_flags_reg = flags;
>
> If we can avoid it, I'd prefer not to complicate the meaning of
> "pci_is_pcie()" -- it used to mean "this device has a PCIe
> capability and you can do PCIe things with it." But now it
> means something else, and we can't do PCIe things with these
> problem devices anyway.
>
> Could we accomplish basically the same thing by making
> pci_find_upstream_pcie_bridge() look like this?
>
> if (pci_is_pcie(pdev))
> return NULL;
>
> + bridge = pdev->bus->self;
> + if (bridge && pci_is_pcie(bridge) &&
> + (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT ||
> + pci_pcie_type(bridge) == PCI_EXP_TYPE_DOWNSTREAM))
> + return NULL;
>
> while (1) {
> ...
This only solves pci_find_upstream_pcie_bridge(3:00.0), I think it still
fails for any devices found on subordinate buses below that. Thanks,
Alex
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-04-11 0:01 ` Alex Williamson
@ 2013-04-11 17:23 ` Bjorn Helgaas
2013-04-15 19:12 ` Alex Williamson
0 siblings, 1 reply; 17+ messages in thread
From: Bjorn Helgaas @ 2013-04-11 17:23 UTC (permalink / raw)
To: Alex Williamson
Cc: Stephen Hemminger, linux-pci, David Woodhouse,
open list:INTEL IOMMU (VT-d)
On Wed, Apr 10, 2013 at 6:01 PM, Alex Williamson
<alex.williamson@redhat.com> wrote:
> On Wed, 2013-04-10 at 16:36 -0600, Bjorn Helgaas wrote:
>> On Wed, Feb 06, 2013 at 08:58:41AM -0700, Alex Williamson wrote:
>> > On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
>> > > On Mon, 04 Feb 2013 15:41:24 -0700
>> > > Alex Williamson <alex.williamson@redhat.com> wrote:
>> > >
>> > > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
>> > > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
>> > > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
>> > > > > > > this the first time you've turned on the IOMMU on that box?
>> > > > > >
>> > > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
>> > > > > >
>> > > > > > > It's the same warning as in this bugzilla:
>> > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
>> > > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
>> > > > > > > it's just a quirk that turns off VT-d if we find certain broken
>> > > > > > > bridges. It doesn't look like you have any of those (although I don't
>> > > > > > > know what you have at 05:00.0).
>> > > > > > >
>> > > > > > > Bjorn
>> > > > > >
>> > > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
>> > > > >
>> > > > > Stephen,
>> > > > >
>> > > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
>> > > > > seen before? Does the patch below help?
>> > > > >
>> > > > > Bjorn, I think we need to quirk it somehow. So far they've all been
>> > > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
>> > > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
>> > > > > to a downstream port. The patch below avoids the WARN and gives us a
>> > > > > device, but of course pci_is_pcie reports wrong for this device and may
>> > > > > cause some trickle down breakage. A more complete option might be to
>> > > > > add a is_pcie flag to the device that can be set independent of
>> > > > > pcie_cap. We'd need to check all the callers for assumptions, but then
>> > > > > we could put the quirk in one place and hopefully fix everything.
>> > > > > Thoughts? Thanks,
>> > > >
>> > > > This latter approach seems like it might be easier than I expected since
>> > > > all the users are so well filtered through the access functions. A
>> > > > quick look through who uses pci_is_pcie seems like this might be
>> > > > complete, but more eyes are required. I'll upload this to the bz for
>> > > > those reporters to test as well. Thoughts? Thanks,
>> > > >
>> > > > Alex
>> > >
>> > > On my hardware this gives:
>> >
>> > > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
>> > > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
>> > > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
>> > > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
>> > > [ 0.254647] PCI express capability structure is required for PCI express device
>> > > [ 0.254647] functions.
>> > > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
>> >
>> > I guess I must be calling pci_name() before it's set. The warning
>> > message needs some work too, it's mainly meant for hardware vendors with
>> > the hope that they might test Linux and see it before shipping these
>> > broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
>>
>> Sorry I dropped this for so long. I'm looking at the patch
>> here: https://bugzilla.kernel.org/attachment.cgi?id=92521,
>> appended for convenience.
>>
>> In case anybody else needs the context, I think we have
>> this scenario (from John Wehin's original report at
>> https://bugzilla.kernel.org/show_bug.cgi?id=44881):
>>
>> pci 0000:00:1c.4: PCI bridge to [bus 03-04] # PCIe root port
>> pci 0000:03:00.0: PCI bridge to [bus 04] # no PCIe cap
>> ...
>> pci 0000:03:00.0: expected upstream PCIe bridge; 0000:00:1c.4 is type 0x4
>>
>> We called pci_find_upstream_pcie_bridge(03:00.0), which generated
>> the warning because:
>>
>> - 03:00.0 is not a PCIe device, and
>> - 00:1c.4 (its upstream bridge) *is* a PCIe device, and
>> - 00:1c.4 is a Root Port (PCI_EXP_TYPE_ROOT_PORT == 0x4),
>> not a PCIe-to-PCI bridge (PCI_EXP_TYPE_PCI_BRIDGE == 0x7)
>> as we expected
>>
>> > commit 60d668a3cdeeb0e29570cf0043736436c146bde8
>> > Author: Alex Williamson <alex.williamson@redhat.com>
>> > Date: Mon Feb 4 15:34:34 2013 -0700
>> >
>> > pci: Handle unadvertised PCIe bridges
>> >
>> > There seem to be several PCIe-to-PCI bridges out in the wild that
>> > blatantly ignore the PCIe specification and do not expose a PCIe
>> > capability. We can attempt to deduce their existence by looking
>> > for PCI bridges directly connected to root ports or downstream
>> > ports. What this means is that pci_is_pcie() does not imply PCIe
>> > capability and we un-deprecate is_pcie to denote the difference.
>> > All the accesses seem to go through pcie_capability_reg_implemented,
>> > so we can significantly limit the footprint of this change by
>> > checking things there.
>> >
>> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>> >
>> > diff --git a/drivers/pci/access.c b/drivers/pci/access.c
>> > index 3af0478..3df24e7 100644
>> > --- a/drivers/pci/access.c
>> > +++ b/drivers/pci/access.c
>> > @@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
>> >
>> > static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
>> > {
>> > - if (!pci_is_pcie(dev))
>> > + if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
>> > return false;
>> >
>> > switch (pos) {
>> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>> > index 6186f03..0a87b6b 100644
>> > --- a/drivers/pci/probe.c
>> > +++ b/drivers/pci/probe.c
>> > @@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
>> > dev->irq = irq;
>> > }
>> >
>> > +static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
>> > +{
>> > + struct pci_dev *parent;
>> > +
>> > + if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
>> > + pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
>> > + pci_is_root_bus(pdev->bus))
>> > + return false;
>> > +
>> > + parent = pdev->bus->self;
>> > +
>> > + if (pci_is_pcie(parent) &&
>> > + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
>> > + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
>> > + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
>> > + pci_name(pdev));
>>
>> Vendors might see this warning, but I'm doubtful they'll do anything
>> about it. I suspect it will result in a lot of emails from concerned
>> users to LKML and linux-pci, and we really can't do anything other
>> than say "yup, it's broken, report it to your vendor."
>>
>> And since the hardware seems to actually *work* if we just pretend that
>> the problem device (e.g., 03:00.0 above) is PCIe, it's doubtful that
>> the vendor would do anything anyway, so maybe a dev_info() would be
>> sufficient.
>>
>> > + return true;
>> > + }
>> > +
>> > + return false;
>> > +}
>> > +
>> > void set_pcie_port_type(struct pci_dev *pdev)
>> > {
>> > int pos;
>> > - u16 reg16;
>> > + u16 flags, caps = 0;
>> >
>> > pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
>> > - if (!pos)
>> > + if (pos) {
>> > + pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
>> > + pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
>> > + } else if (is_unadvertised_pcie_bridge(pdev))
>> > + flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
>> > + else
>> > return;
>> > +
>> > pdev->is_pcie = 1;
>> > pdev->pcie_cap = pos;
>> > - pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
>> > - pdev->pcie_flags_reg = reg16;
>> > - pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
>> > - pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
>> > + pdev->pcie_flags_reg = flags;
>>
>> If we can avoid it, I'd prefer not to complicate the meaning of
>> "pci_is_pcie()" -- it used to mean "this device has a PCIe
>> capability and you can do PCIe things with it." But now it
>> means something else, and we can't do PCIe things with these
>> problem devices anyway.
>>
>> Could we accomplish basically the same thing by making
>> pci_find_upstream_pcie_bridge() look like this?
>>
>> if (pci_is_pcie(pdev))
>> return NULL;
>>
>> + bridge = pdev->bus->self;
>> + if (bridge && pci_is_pcie(bridge) &&
>> + (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT ||
>> + pci_pcie_type(bridge) == PCI_EXP_TYPE_DOWNSTREAM))
>> + return NULL;
>>
>> while (1) {
>> ...
>
> This only solves pci_find_upstream_pcie_bridge(3:00.0), I think it still
> fails for any devices found on subordinate buses below that. Thanks,
Can't we apply the same approach throughout the whole tree with some
reworking of pci_find_upstream_pcie_bridge()?
It seems like pci_find_upstream_pcie_bridge() (and some code in
callers) is really trying to figure out the requester-ID for use as
the IOMMU's source-ID, but the current code organization seems a bit
confusing. I suspect cleaning that up a bit would make it more
obvious how to fix this.
Bjorn
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-04-11 17:23 ` Bjorn Helgaas
@ 2013-04-15 19:12 ` Alex Williamson
2013-04-15 19:29 ` Bjorn Helgaas
0 siblings, 1 reply; 17+ messages in thread
From: Alex Williamson @ 2013-04-15 19:12 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Stephen Hemminger, linux-pci, David Woodhouse,
open list:INTEL IOMMU (VT-d)
On Thu, 2013-04-11 at 11:23 -0600, Bjorn Helgaas wrote:
> On Wed, Apr 10, 2013 at 6:01 PM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > On Wed, 2013-04-10 at 16:36 -0600, Bjorn Helgaas wrote:
> >> On Wed, Feb 06, 2013 at 08:58:41AM -0700, Alex Williamson wrote:
> >> > On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
> >> > > On Mon, 04 Feb 2013 15:41:24 -0700
> >> > > Alex Williamson <alex.williamson@redhat.com> wrote:
> >> > >
> >> > > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
> >> > > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
> >> > > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
> >> > > > > > > this the first time you've turned on the IOMMU on that box?
> >> > > > > >
> >> > > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
> >> > > > > >
> >> > > > > > > It's the same warning as in this bugzilla:
> >> > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
> >> > > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
> >> > > > > > > it's just a quirk that turns off VT-d if we find certain broken
> >> > > > > > > bridges. It doesn't look like you have any of those (although I don't
> >> > > > > > > know what you have at 05:00.0).
> >> > > > > > >
> >> > > > > > > Bjorn
> >> > > > > >
> >> > > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
> >> > > > >
> >> > > > > Stephen,
> >> > > > >
> >> > > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
> >> > > > > seen before? Does the patch below help?
> >> > > > >
> >> > > > > Bjorn, I think we need to quirk it somehow. So far they've all been
> >> > > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
> >> > > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
> >> > > > > to a downstream port. The patch below avoids the WARN and gives us a
> >> > > > > device, but of course pci_is_pcie reports wrong for this device and may
> >> > > > > cause some trickle down breakage. A more complete option might be to
> >> > > > > add a is_pcie flag to the device that can be set independent of
> >> > > > > pcie_cap. We'd need to check all the callers for assumptions, but then
> >> > > > > we could put the quirk in one place and hopefully fix everything.
> >> > > > > Thoughts? Thanks,
> >> > > >
> >> > > > This latter approach seems like it might be easier than I expected since
> >> > > > all the users are so well filtered through the access functions. A
> >> > > > quick look through who uses pci_is_pcie seems like this might be
> >> > > > complete, but more eyes are required. I'll upload this to the bz for
> >> > > > those reporters to test as well. Thoughts? Thanks,
> >> > > >
> >> > > > Alex
> >> > >
> >> > > On my hardware this gives:
> >> >
> >> > > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
> >> > > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
> >> > > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
> >> > > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
> >> > > [ 0.254647] PCI express capability structure is required for PCI express device
> >> > > [ 0.254647] functions.
> >> > > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
> >> >
> >> > I guess I must be calling pci_name() before it's set. The warning
> >> > message needs some work too, it's mainly meant for hardware vendors with
> >> > the hope that they might test Linux and see it before shipping these
> >> > broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
> >>
> >> Sorry I dropped this for so long. I'm looking at the patch
> >> here: https://bugzilla.kernel.org/attachment.cgi?id=92521,
> >> appended for convenience.
> >>
> >> In case anybody else needs the context, I think we have
> >> this scenario (from John Wehin's original report at
> >> https://bugzilla.kernel.org/show_bug.cgi?id=44881):
> >>
> >> pci 0000:00:1c.4: PCI bridge to [bus 03-04] # PCIe root port
> >> pci 0000:03:00.0: PCI bridge to [bus 04] # no PCIe cap
> >> ...
> >> pci 0000:03:00.0: expected upstream PCIe bridge; 0000:00:1c.4 is type 0x4
> >>
> >> We called pci_find_upstream_pcie_bridge(03:00.0), which generated
> >> the warning because:
> >>
> >> - 03:00.0 is not a PCIe device, and
> >> - 00:1c.4 (its upstream bridge) *is* a PCIe device, and
> >> - 00:1c.4 is a Root Port (PCI_EXP_TYPE_ROOT_PORT == 0x4),
> >> not a PCIe-to-PCI bridge (PCI_EXP_TYPE_PCI_BRIDGE == 0x7)
> >> as we expected
> >>
> >> > commit 60d668a3cdeeb0e29570cf0043736436c146bde8
> >> > Author: Alex Williamson <alex.williamson@redhat.com>
> >> > Date: Mon Feb 4 15:34:34 2013 -0700
> >> >
> >> > pci: Handle unadvertised PCIe bridges
> >> >
> >> > There seem to be several PCIe-to-PCI bridges out in the wild that
> >> > blatantly ignore the PCIe specification and do not expose a PCIe
> >> > capability. We can attempt to deduce their existence by looking
> >> > for PCI bridges directly connected to root ports or downstream
> >> > ports. What this means is that pci_is_pcie() does not imply PCIe
> >> > capability and we un-deprecate is_pcie to denote the difference.
> >> > All the accesses seem to go through pcie_capability_reg_implemented,
> >> > so we can significantly limit the footprint of this change by
> >> > checking things there.
> >> >
> >> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >> >
> >> > diff --git a/drivers/pci/access.c b/drivers/pci/access.c
> >> > index 3af0478..3df24e7 100644
> >> > --- a/drivers/pci/access.c
> >> > +++ b/drivers/pci/access.c
> >> > @@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
> >> >
> >> > static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
> >> > {
> >> > - if (!pci_is_pcie(dev))
> >> > + if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
> >> > return false;
> >> >
> >> > switch (pos) {
> >> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> >> > index 6186f03..0a87b6b 100644
> >> > --- a/drivers/pci/probe.c
> >> > +++ b/drivers/pci/probe.c
> >> > @@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
> >> > dev->irq = irq;
> >> > }
> >> >
> >> > +static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
> >> > +{
> >> > + struct pci_dev *parent;
> >> > +
> >> > + if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
> >> > + pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
> >> > + pci_is_root_bus(pdev->bus))
> >> > + return false;
> >> > +
> >> > + parent = pdev->bus->self;
> >> > +
> >> > + if (pci_is_pcie(parent) &&
> >> > + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
> >> > + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
> >> > + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
> >> > + pci_name(pdev));
> >>
> >> Vendors might see this warning, but I'm doubtful they'll do anything
> >> about it. I suspect it will result in a lot of emails from concerned
> >> users to LKML and linux-pci, and we really can't do anything other
> >> than say "yup, it's broken, report it to your vendor."
> >>
> >> And since the hardware seems to actually *work* if we just pretend that
> >> the problem device (e.g., 03:00.0 above) is PCIe, it's doubtful that
> >> the vendor would do anything anyway, so maybe a dev_info() would be
> >> sufficient.
> >>
> >> > + return true;
> >> > + }
> >> > +
> >> > + return false;
> >> > +}
> >> > +
> >> > void set_pcie_port_type(struct pci_dev *pdev)
> >> > {
> >> > int pos;
> >> > - u16 reg16;
> >> > + u16 flags, caps = 0;
> >> >
> >> > pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
> >> > - if (!pos)
> >> > + if (pos) {
> >> > + pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
> >> > + pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
> >> > + } else if (is_unadvertised_pcie_bridge(pdev))
> >> > + flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
> >> > + else
> >> > return;
> >> > +
> >> > pdev->is_pcie = 1;
> >> > pdev->pcie_cap = pos;
> >> > - pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
> >> > - pdev->pcie_flags_reg = reg16;
> >> > - pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
> >> > - pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
> >> > + pdev->pcie_flags_reg = flags;
> >>
> >> If we can avoid it, I'd prefer not to complicate the meaning of
> >> "pci_is_pcie()" -- it used to mean "this device has a PCIe
> >> capability and you can do PCIe things with it." But now it
> >> means something else, and we can't do PCIe things with these
> >> problem devices anyway.
> >>
> >> Could we accomplish basically the same thing by making
> >> pci_find_upstream_pcie_bridge() look like this?
> >>
> >> if (pci_is_pcie(pdev))
> >> return NULL;
> >>
> >> + bridge = pdev->bus->self;
> >> + if (bridge && pci_is_pcie(bridge) &&
> >> + (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT ||
> >> + pci_pcie_type(bridge) == PCI_EXP_TYPE_DOWNSTREAM))
> >> + return NULL;
> >>
> >> while (1) {
> >> ...
> >
> > This only solves pci_find_upstream_pcie_bridge(3:00.0), I think it still
> > fails for any devices found on subordinate buses below that. Thanks,
>
> Can't we apply the same approach throughout the whole tree with some
> reworking of pci_find_upstream_pcie_bridge()?
>
> It seems like pci_find_upstream_pcie_bridge() (and some code in
> callers) is really trying to figure out the requester-ID for use as
> the IOMMU's source-ID, but the current code organization seems a bit
> confusing. I suspect cleaning that up a bit would make it more
> obvious how to fix this.
But the bug is really that the bridge is a PCIe device but does not
expose a PCIe capability. So yes, we can add hacks all around this path
to fix it, but we lose the general ability to identify these devices as
PCIe. Maybe a compromise is a version of pci_is_pcie() that is a little
more flexible, pci_is_probably_pcie()? Then we could use it when we
don't actually want to access the capability, but want to test the
device type. Thanks,
Alex
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: PCI warning on boot 3.8.0-rc1
2013-04-15 19:12 ` Alex Williamson
@ 2013-04-15 19:29 ` Bjorn Helgaas
0 siblings, 0 replies; 17+ messages in thread
From: Bjorn Helgaas @ 2013-04-15 19:29 UTC (permalink / raw)
To: Alex Williamson
Cc: Stephen Hemminger, linux-pci, David Woodhouse,
open list:INTEL IOMMU (VT-d)
On Mon, Apr 15, 2013 at 1:12 PM, Alex Williamson
<alex.williamson@redhat.com> wrote:
> On Thu, 2013-04-11 at 11:23 -0600, Bjorn Helgaas wrote:
>> On Wed, Apr 10, 2013 at 6:01 PM, Alex Williamson
>> <alex.williamson@redhat.com> wrote:
>> > On Wed, 2013-04-10 at 16:36 -0600, Bjorn Helgaas wrote:
>> >> On Wed, Feb 06, 2013 at 08:58:41AM -0700, Alex Williamson wrote:
>> >> > On Wed, 2013-02-06 at 07:49 -0800, Stephen Hemminger wrote:
>> >> > > On Mon, 04 Feb 2013 15:41:24 -0700
>> >> > > Alex Williamson <alex.williamson@redhat.com> wrote:
>> >> > >
>> >> > > > On Mon, 2013-02-04 at 13:28 -0700, Alex Williamson wrote:
>> >> > > > > On Mon, 2013-02-04 at 10:36 -0800, Stephen Hemminger wrote:
>> >> > > > > > > I think drivers/pci/search.c is identical between 3.7 and 3.8-rc1. Is
>> >> > > > > > > this the first time you've turned on the IOMMU on that box?
>> >> > > > > >
>> >> > > > > > It exists in 3.7 and earlier kernels, just haven't turned on same config.
>> >> > > > > >
>> >> > > > > > > It's the same warning as in this bugzilla:
>> >> > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=44881, and there's a patch
>> >> > > > > > > there at https://bugzilla.kernel.org/show_bug.cgi?id=44881#c11, but
>> >> > > > > > > it's just a quirk that turns off VT-d if we find certain broken
>> >> > > > > > > bridges. It doesn't look like you have any of those (although I don't
>> >> > > > > > > know what you have at 05:00.0).
>> >> > > > > > >
>> >> > > > > > > Bjorn
>> >> > > > > >
>> >> > > > > > This is a standard ASUS motherboard, and don't want to disable VT-d.
>> >> > > > >
>> >> > > > > Stephen,
>> >> > > > >
>> >> > > > > Can you give the lspci -vvv of device 5:00.0 to see if it's one we've
>> >> > > > > seen before? Does the patch below help?
>> >> > > > >
>> >> > > > > Bjorn, I think we need to quirk it somehow. So far they've all been
>> >> > > > > PCI-to-PCI bridges attached to root ports where we expect it's actually
>> >> > > > > a PCIe-to-PCI bridge. Seems like maybe we could have the same attached
>> >> > > > > to a downstream port. The patch below avoids the WARN and gives us a
>> >> > > > > device, but of course pci_is_pcie reports wrong for this device and may
>> >> > > > > cause some trickle down breakage. A more complete option might be to
>> >> > > > > add a is_pcie flag to the device that can be set independent of
>> >> > > > > pcie_cap. We'd need to check all the callers for assumptions, but then
>> >> > > > > we could put the quirk in one place and hopefully fix everything.
>> >> > > > > Thoughts? Thanks,
>> >> > > >
>> >> > > > This latter approach seems like it might be easier than I expected since
>> >> > > > all the users are so well filtered through the access functions. A
>> >> > > > quick look through who uses pci_is_pcie seems like this might be
>> >> > > > complete, but more eyes are required. I'll upload this to the bz for
>> >> > > > those reporters to test as well. Thoughts? Thanks,
>> >> > > >
>> >> > > > Alex
>> >> > >
>> >> > > On my hardware this gives:
>> >> >
>> >> > > [ 0.254621] pci_bus 0000:05: busn_res: can not insert [bus 05-ff] under [bus 00-3e] (conflicts with (null) [bus 00-3e])
>> >> > > [ 0.254647] WARNING: Your hardware is broken, device (null) appears to be a
>> >> > > [ 0.254647] Legacy PCI device attached directly to a PCIe device which is not a
>> >> > > [ 0.254647] PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the
>> >> > > [ 0.254647] PCI express capability structure is required for PCI express device
>> >> > > [ 0.254647] functions.
>> >> > > [ 0.254653] pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
>> >> >
>> >> > I guess I must be calling pci_name() before it's set. The warning
>> >> > message needs some work too, it's mainly meant for hardware vendors with
>> >> > the hope that they might test Linux and see it before shipping these
>> >> > broken devices. Bjorn, does this approach seem worth pursuing? Thanks,
>> >>
>> >> Sorry I dropped this for so long. I'm looking at the patch
>> >> here: https://bugzilla.kernel.org/attachment.cgi?id=92521,
>> >> appended for convenience.
>> >>
>> >> In case anybody else needs the context, I think we have
>> >> this scenario (from John Wehin's original report at
>> >> https://bugzilla.kernel.org/show_bug.cgi?id=44881):
>> >>
>> >> pci 0000:00:1c.4: PCI bridge to [bus 03-04] # PCIe root port
>> >> pci 0000:03:00.0: PCI bridge to [bus 04] # no PCIe cap
>> >> ...
>> >> pci 0000:03:00.0: expected upstream PCIe bridge; 0000:00:1c.4 is type 0x4
>> >>
>> >> We called pci_find_upstream_pcie_bridge(03:00.0), which generated
>> >> the warning because:
>> >>
>> >> - 03:00.0 is not a PCIe device, and
>> >> - 00:1c.4 (its upstream bridge) *is* a PCIe device, and
>> >> - 00:1c.4 is a Root Port (PCI_EXP_TYPE_ROOT_PORT == 0x4),
>> >> not a PCIe-to-PCI bridge (PCI_EXP_TYPE_PCI_BRIDGE == 0x7)
>> >> as we expected
>> >>
>> >> > commit 60d668a3cdeeb0e29570cf0043736436c146bde8
>> >> > Author: Alex Williamson <alex.williamson@redhat.com>
>> >> > Date: Mon Feb 4 15:34:34 2013 -0700
>> >> >
>> >> > pci: Handle unadvertised PCIe bridges
>> >> >
>> >> > There seem to be several PCIe-to-PCI bridges out in the wild that
>> >> > blatantly ignore the PCIe specification and do not expose a PCIe
>> >> > capability. We can attempt to deduce their existence by looking
>> >> > for PCI bridges directly connected to root ports or downstream
>> >> > ports. What this means is that pci_is_pcie() does not imply PCIe
>> >> > capability and we un-deprecate is_pcie to denote the difference.
>> >> > All the accesses seem to go through pcie_capability_reg_implemented,
>> >> > so we can significantly limit the footprint of this change by
>> >> > checking things there.
>> >> >
>> >> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>> >> >
>> >> > diff --git a/drivers/pci/access.c b/drivers/pci/access.c
>> >> > index 3af0478..3df24e7 100644
>> >> > --- a/drivers/pci/access.c
>> >> > +++ b/drivers/pci/access.c
>> >> > @@ -511,7 +511,7 @@ static inline bool pcie_cap_has_rtctl(const struct pci_dev *dev)
>> >> >
>> >> > static bool pcie_capability_reg_implemented(struct pci_dev *dev, int pos)
>> >> > {
>> >> > - if (!pci_is_pcie(dev))
>> >> > + if (!pci_is_pcie(dev) || !pci_pcie_cap(dev))
>> >> > return false;
>> >> >
>> >> > switch (pos) {
>> >> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>> >> > index 6186f03..0a87b6b 100644
>> >> > --- a/drivers/pci/probe.c
>> >> > +++ b/drivers/pci/probe.c
>> >> > @@ -926,20 +926,46 @@ static void pci_read_irq(struct pci_dev *dev)
>> >> > dev->irq = irq;
>> >> > }
>> >> >
>> >> > +static bool is_unadvertised_pcie_bridge(struct pci_dev *pdev)
>> >> > +{
>> >> > + struct pci_dev *parent;
>> >> > +
>> >> > + if (pdev->hdr_type != PCI_HEADER_TYPE_BRIDGE ||
>> >> > + pci_find_capability(pdev, PCI_CAP_ID_EXP) ||
>> >> > + pci_is_root_bus(pdev->bus))
>> >> > + return false;
>> >> > +
>> >> > + parent = pdev->bus->self;
>> >> > +
>> >> > + if (pci_is_pcie(parent) &&
>> >> > + (pci_pcie_type(parent) == PCI_EXP_TYPE_ROOT_PORT ||
>> >> > + pci_pcie_type(parent) == PCI_EXP_TYPE_DOWNSTREAM)) {
>> >> > + pr_warn("WARNING: Your hardware is broken, device %s appears to be a\n Legacy PCI device attached directly to a PCIe device which is not a\n PCIe-to-PCI bridge. Per section 7.8 of the PCI Express 3.0 spec, the\n PCI express capability structure is required for PCI express device\nfunctions.\n",
>> >> > + pci_name(pdev));
>> >>
>> >> Vendors might see this warning, but I'm doubtful they'll do anything
>> >> about it. I suspect it will result in a lot of emails from concerned
>> >> users to LKML and linux-pci, and we really can't do anything other
>> >> than say "yup, it's broken, report it to your vendor."
>> >>
>> >> And since the hardware seems to actually *work* if we just pretend that
>> >> the problem device (e.g., 03:00.0 above) is PCIe, it's doubtful that
>> >> the vendor would do anything anyway, so maybe a dev_info() would be
>> >> sufficient.
>> >>
>> >> > + return true;
>> >> > + }
>> >> > +
>> >> > + return false;
>> >> > +}
>> >> > +
>> >> > void set_pcie_port_type(struct pci_dev *pdev)
>> >> > {
>> >> > int pos;
>> >> > - u16 reg16;
>> >> > + u16 flags, caps = 0;
>> >> >
>> >> > pos = pci_find_capability(pdev, PCI_CAP_ID_EXP);
>> >> > - if (!pos)
>> >> > + if (pos) {
>> >> > + pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &flags);
>> >> > + pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, &caps);
>> >> > + } else if (is_unadvertised_pcie_bridge(pdev))
>> >> > + flags = PCI_EXP_TYPE_PCI_BRIDGE << 4;
>> >> > + else
>> >> > return;
>> >> > +
>> >> > pdev->is_pcie = 1;
>> >> > pdev->pcie_cap = pos;
>> >> > - pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, ®16);
>> >> > - pdev->pcie_flags_reg = reg16;
>> >> > - pci_read_config_word(pdev, pos + PCI_EXP_DEVCAP, ®16);
>> >> > - pdev->pcie_mpss = reg16 & PCI_EXP_DEVCAP_PAYLOAD;
>> >> > + pdev->pcie_flags_reg = flags;
>> >>
>> >> If we can avoid it, I'd prefer not to complicate the meaning of
>> >> "pci_is_pcie()" -- it used to mean "this device has a PCIe
>> >> capability and you can do PCIe things with it." But now it
>> >> means something else, and we can't do PCIe things with these
>> >> problem devices anyway.
>> >>
>> >> Could we accomplish basically the same thing by making
>> >> pci_find_upstream_pcie_bridge() look like this?
>> >>
>> >> if (pci_is_pcie(pdev))
>> >> return NULL;
>> >>
>> >> + bridge = pdev->bus->self;
>> >> + if (bridge && pci_is_pcie(bridge) &&
>> >> + (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT ||
>> >> + pci_pcie_type(bridge) == PCI_EXP_TYPE_DOWNSTREAM))
>> >> + return NULL;
>> >>
>> >> while (1) {
>> >> ...
>> >
>> > This only solves pci_find_upstream_pcie_bridge(3:00.0), I think it still
>> > fails for any devices found on subordinate buses below that. Thanks,
>>
>> Can't we apply the same approach throughout the whole tree with some
>> reworking of pci_find_upstream_pcie_bridge()?
>>
>> It seems like pci_find_upstream_pcie_bridge() (and some code in
>> callers) is really trying to figure out the requester-ID for use as
>> the IOMMU's source-ID, but the current code organization seems a bit
>> confusing. I suspect cleaning that up a bit would make it more
>> obvious how to fix this.
>
> But the bug is really that the bridge is a PCIe device but does not
> expose a PCIe capability. So yes, we can add hacks all around this path
> to fix it, but we lose the general ability to identify these devices as
> PCIe. Maybe a compromise is a version of pci_is_pcie() that is a little
> more flexible, pci_is_probably_pcie()? Then we could use it when we
> don't actually want to access the capability, but want to test the
> device type. Thanks,
What good is it to know that "this is really a PCIe device" when it
doesn't have a PCIe capability? There's no PCIe operation we can
perform on such a device -- we can't determine or set link speed,
control ASPM, use AER, etc.
As far as the rest of the kernel is concerned, I think it's merely a
PCI device. The requester-ID thing is the only thing I know about
that makes it slightly more than PCI. That seems like such a special
case thing that it's not worth trying to make a general PCI concept
out of it.
Bjorn
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2013-04-15 19:29 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-16 22:38 PCI warning on boot 3.8.0-rc1 Stephen Hemminger
2013-01-30 21:59 ` Bjorn Helgaas
2013-02-04 18:36 ` Stephen Hemminger
2013-02-04 20:28 ` Alex Williamson
2013-02-04 20:30 ` Stephen Hemminger
2013-02-04 20:36 ` Alex Williamson
2013-02-04 22:41 ` Alex Williamson
2013-02-05 1:36 ` Stephen Hemminger
2013-02-06 15:49 ` Stephen Hemminger
2013-02-06 15:58 ` Alex Williamson
2013-02-12 4:15 ` Alex Williamson
2013-02-12 18:33 ` Stephen Hemminger
2013-04-10 22:36 ` Bjorn Helgaas
2013-04-11 0:01 ` Alex Williamson
2013-04-11 17:23 ` Bjorn Helgaas
2013-04-15 19:12 ` Alex Williamson
2013-04-15 19:29 ` Bjorn Helgaas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).