Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed

[Baoquan He]

On 07/22/15 at 04:47pm, Yinghai Lu wrote:
> On Tue, Jul 21, 2015 at 5:59 PM, Baoquan He <bhe@xxxxxxxxxx> wrote:
> >> That commit should only be used to workaround some systems that
> >> have partial iommu support.
> >
> > Those big servers mostly has hardware iommu. But they still can
> > enable swiotlb suport. Then low memory is needed.
> 
> Do you have whole bootlog? I don't understand why those system can not use
> full iommu. BIOS problem or HW/silicon limitation?

Sorry for late reply. This problem is reported by customers. They usulay
don't like to make these things public. While for those systems with
good hard iommu support, it could also fail to initialize hw iommu and
then use swiotlb again, E.g in kdump kernel case. You can see in
intel_iommu_init() swiotlb is assigned to 0 only if intel iommu (namely vt-d)
is initialized successfully. There's possibility that hw iommu
initialization will fail, in this case kdump kernel will fail to boot
if no any low memory is given. So we can't make assumption that system
can boot always well without low memory.

Thanks
Baoquan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/