From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] Early use of boot service memory Date: Thu, 14 Nov 2013 10:45:42 -0800 Message-ID: <52851A56.1040709@zytor.com> References: <1384222558-38527-1-git-send-email-jerry.hoemann@hp.com> <20131113224503.GB25344@anatevka.fc.hp.com> <52840206.5020006@zytor.com> <20131113235708.GC25344@anatevka.fc.hp.com> <20131114180455.GA32212@anatevka.fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: Pekka Enberg , Jerry Hoemann Cc: Rob Landley , Thomas Gleixner , Ingo Molnar , x86 maintainers , Matt Fleming , Yinghai Lu , Andrew Morton , "list@ebiederm.org:DOCUMENTATION" , "list@ebiederm.org:MEMORY MANAGEMENT" linux-doc@vger.kernel.org, linux-efi@vger.kernel.org, Vivek Goyal , LKML List-Id: linux-efi@vger.kernel.org On 11/14/2013 10:44 AM, Pekka Enberg wrote: > On Thu, Nov 14, 2013 at 8:04 PM, wrote: >> Making this issue a quirk will be a lot more practical. Its a small, focused >> change whose implications are limited and more easily understood. > > There's nothing practical with requiring users to pass a kernel option > to make kdump work. It's a workaround, sure, but it's not a proper > fix. And once you have to do that anyway, you might as well just do the kdump load high... -hpa -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755788Ab3KNSqa (ORCPT ); Thu, 14 Nov 2013 13:46:30 -0500 Received: from terminus.zytor.com ([198.137.202.10]:41920 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754646Ab3KNSqV (ORCPT ); Thu, 14 Nov 2013 13:46:21 -0500 Message-ID: <52851A56.1040709@zytor.com> Date: Thu, 14 Nov 2013 10:45:42 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Pekka Enberg , Jerry Hoemann CC: Rob Landley , Thomas Gleixner , Ingo Molnar , x86 maintainers , Matt Fleming , Yinghai Lu , Andrew Morton , "list@ebiederm.org:DOCUMENTATION" , "list@ebiederm.org:MEMORY MANAGEMENT" , linux-doc@vger.kernel.org, linux-efi@vger.kernel.org, Vivek Goyal , LKML Subject: Re: [PATCH 0/3] Early use of boot service memory References: <1384222558-38527-1-git-send-email-jerry.hoemann@hp.com> <20131113224503.GB25344@anatevka.fc.hp.com> <52840206.5020006@zytor.com> <20131113235708.GC25344@anatevka.fc.hp.com> <20131114180455.GA32212@anatevka.fc.hp.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/14/2013 10:44 AM, Pekka Enberg wrote: > On Thu, Nov 14, 2013 at 8:04 PM, wrote: >> Making this issue a quirk will be a lot more practical. Its a small, focused >> change whose implications are limited and more easily understood. > > There's nothing practical with requiring users to pass a kernel option > to make kdump work. It's a workaround, sure, but it's not a proper > fix. And once you have to do that anyway, you might as well just do the kdump load high... -hpa