lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Nov 2009 21:35:17 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: mingo@...e.hu Cc: fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org, chrisw@...s-sol.org, dwmw2@...radead.org, joerg.roedel@....com, muli@...ibm.com Subject: Re: [PATCH v2 0/9] x86: handle HW IOMMU initialization failure gracefully On Tue, 10 Nov 2009 12:55:55 +0100 Ingo Molnar <mingo@...e.hu> wrote: > > hm, one of the swiotlb patches caused this bootup crash: Sorry about that. I totally forgot about x86_32. the following patch fixes this? Sorry that I'm away from the workplace and can't test it. diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c index a234e63..63eebee 100644 --- a/arch/x86/kernel/pci-dma.c +++ b/arch/x86/kernel/pci-dma.c @@ -129,6 +129,8 @@ void __init pci_iommu_alloc(void) #ifdef CONFIG_X86_64 /* free the range so iommu could get some range less than 4G */ dma32_free_bootmem(); +#else + dma_ops = &nommu_dma_ops; #endif pci_swiotlb_init(); if (use_swiotlb) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists