summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorBorislav Petkov <bp@amd64.org>2010-03-12 15:43:03 +0100
committerIngo Molnar <mingo@elte.hu>2010-03-13 08:36:16 +0100
commit0e152cd7c16832bd5cadee0c2e41d9959bc9b6f9 (patch)
treec84df0d86adf5347268939be88426394cd28e18e /crypto
parent8447b360a3897bdfb0677107564d1dd9ab6e63be (diff)
downloadop-kernel-dev-0e152cd7c16832bd5cadee0c2e41d9959bc9b6f9.zip
op-kernel-dev-0e152cd7c16832bd5cadee0c2e41d9959bc9b6f9.tar.gz
x86, k8 nb: Fix boot crash: enable k8_northbridges unconditionally on AMD systems
de957628ce7c84764ff41331111036b3ae5bad0f changed setting of the x86_init.iommu.iommu_init function ptr only when GART IOMMU is found. One side effect of it is that num_k8_northbridges is not initialized anymore if not explicitly called. This resulted in uninitialized pointers in <arch/x86/kernel/cpu/intel_cacheinfo.c:amd_calc_l3_indices()>, for example, which uses the num_k8_northbridges thing through node_to_k8_nb_misc(). Fix that through an initcall that runs right after the PCI subsystem and does all the scanning. Then, remove initialization in gart_iommu_init() which is a rootfs_initcall and we're running before that. What is more, since num_k8_northbridges is being used in other places beside GART IOMMU, include it whenever we add AMD CPU support. The previous dependency chain in kconfig contained K8_NB depends on AGP_AMD64|GART_IOMMU which was clearly incorrect. The more natural way in terms of hardware dependency should be AGP_AMD64|GART_IOMMU depends on K8_NB depends on CPU_SUP_AMD && PCI. Make it so Number One! Signed-off-by: Borislav Petkov <borislav.petkov@amd.com> Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Cc: Joerg Roedel <joerg.roedel@amd.com> LKML-Reference: <20100312144303.GA29262@aftab> Signed-off-by: Ingo Molnar <mingo@elte.hu> Tested-by: Joerg Roedel <joerg.roedel@amd.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud