(2013/04/15 19:18), Joerg Roedel wrote: > On Mon, Apr 15, 2013 at 06:00:13PM +0900, Takao Indoh wrote: >> On DMAR initialization during kdump boot, do you guys agree to change >> order like this? >> >> Current order: >> (1) Disable translation >> (2) PCI initialization >> (3) Make pgtable and enable translation. >> >> Order I'm proposing: >> (1) PCI initialization >> (2) Disable translation >> (3) Make pgtable and enable translation. > > I think this should work. In fact, translation only needs to be disabled > while the IOMMU hardware is reprogrammed to the new data structures the > kdump kernel set up. Ok, I agree. > >> As Joerg said, if we need to consider the case that kdump kernel is >> compiled without dma-remapping(CONFIG_INTEL_IOMMU is off?), I can update >> my patch to handle such a case properly by adding ifdef >> CONFIG_INTEL_IOMMU. > > Thinking about it, this case is a bit more special. If the kdump kernel > has no IOMMU driver at all there is also no code to disable it. So > unless we want to force the kdump kernel to have the driver when the > first kernel had it, I think we also want some quirk (depending on > !CONFIG_INTEL_IOMMU) that disables translation at boot. > > I know, its complicated :) yeah complicated. hmm..., this isn't limited only to iommu case, there are many problems which are caused by difference of config between first kernel and second one. So, to make code simple, I think we don't need to care such a exceptional case. I mean, I think it is a matter of user and user has to compile second kernel with dma-remapping if user want to use it in first kernel. Thanks, Takao Indoh
