From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752869AbbANNfZ (ORCPT ); Wed, 14 Jan 2015 08:35:25 -0500 Received: from 8bytes.org ([81.169.241.247]:34403 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752669AbbANNfX (ORCPT ); Wed, 14 Jan 2015 08:35:23 -0500 Date: Wed, 14 Jan 2015 14:35:21 +0100 From: Joerg Roedel To: Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Konrad Rzeszutek Wilk Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Joerg Roedel Subject: Re: [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Message-ID: <20150114133521.GI6343@8bytes.org> References: <1420555874-11506-1-git-send-email-joro@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1420555874-11506-1-git-send-email-joro@8bytes.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ping. On Tue, Jan 06, 2015 at 03:51:11PM +0100, Joerg Roedel wrote: > v1->v2: > > * Updated comments based on feedback from Konrad > * Added Acked-bys > * Rebased to v3.19-rc3 > > Hi, > > here is a patch-set to fix failed kdump kernel boots when > the systems was booted with crashkernel=X,high. On those > systems the kernel allocates only 72MiB of low-memory for > DMA buffers, which showed to be too low on some systems. > > The problem is that 64MiB of the low-memory is allocated by > swiotlb, leaving 8MB for the page-allocator. But swiotlb > tries to allocate DMA memory from the page-allocator first, > which fails pretty fast in the boot sequence, causing > warnings. This patch-set removes these warnings. > > But even the 64MiB for swiotlb are eaten up on some systems, > so that the default of low-memory allocated for the > crash-kernel is increase from 72MB to 256MB (only changing > the defaults, can still be overwritten by crashkernel=X,low). > > This number comes from experiments on the affected systems, > 128MiB low-memory was still not enough there, thus I set the > value to 256MiB to fix the issues. > > Any feedback appreciated. > > Thanks, > > Joerg > > Joerg Roedel (3): > swiotlb: Warn on allocation failure in swiotlb_alloc_coherent > x86, swiotlb: Try coherent allocations with __GFP_NOWARN > x86, crash: Allocate enough low-mem when crashkernel=high > > arch/x86/kernel/pci-swiotlb.c | 8 ++++++++ > arch/x86/kernel/setup.c | 5 ++++- > lib/swiotlb.c | 11 +++++++++-- > 3 files changed, 21 insertions(+), 3 deletions(-) > > -- > 1.9.1 > > Joerg Roedel (3): > swiotlb: Warn on allocation failure in swiotlb_alloc_coherent > x86, swiotlb: Try coherent allocations with __GFP_NOWARN > x86, crash: Allocate enough low-mem when crashkernel=high > > arch/x86/kernel/pci-swiotlb.c | 8 ++++++++ > arch/x86/kernel/setup.c | 5 ++++- > lib/swiotlb.c | 11 +++++++++-- > 3 files changed, 21 insertions(+), 3 deletions(-) > > -- > 1.9.1