From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753040AbbJEKOA (ORCPT ); Mon, 5 Oct 2015 06:14:00 -0400 Received: from mail.skyhub.de ([78.46.96.112]:49815 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752846AbbJEKN7 (ORCPT ); Mon, 5 Oct 2015 06:13:59 -0400 Date: Mon, 5 Oct 2015 12:14:31 +0200 From: Borislav Petkov To: =?utf-8?B?5rKz5ZCI6Iux5a6PIC8gS0FXQUnvvIxISURFSElSTw==?= Cc: "'Peter Zijlstra'" , Jonathan Corbet , Ingo Molnar , "Eric W. Biederman" , "H. Peter Anvin" , Andrew Morton , Thomas Gleixner , Vivek Goyal , "linux-doc@vger.kernel.org" , "x86@kernel.org" , "kexec@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Michal Hocko , Ingo Molnar , =?utf-8?B?5bmz5p2+6ZuF5bezIC8gSElSQU1BVFXvvIxNQVNBTUk=?= Subject: Re: [V4 PATCH 4/4] x86/apic: Introduce noextnmi boot option Message-ID: <20151005101431.GC23259@nazgul.tnic> References: <20151001062733.GL2881@worktop.programming.kicks-ass.net> <04EAB7311EE43145B2D3536183D1A8445499D30D@GSjpTKYDCembx31.service.hitachi.net> <20151001084335.GA3764@pd.tnic> <04EAB7311EE43145B2D3536183D1A8445499DB92@GSjpTKYDCembx31.service.hitachi.net> <20151001110110.GA3544@pd.tnic> <04EAB7311EE43145B2D3536183D1A8445499ED83@GSjpTKYDCembx31.service.hitachi.net> <20151002074721.GA16538@pd.tnic> <04EAB7311EE43145B2D3536183D1A844549A4557@GSjpTKYDCembx31.service.hitachi.net> <20151005082704.GA23259@nazgul.tnic> <04EAB7311EE43145B2D3536183D1A844549A48D3@GSjpTKYDCembx31.service.hitachi.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <04EAB7311EE43145B2D3536183D1A844549A48D3@GSjpTKYDCembx31.service.hitachi.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 05, 2015 at 09:21:02AM +0000, 河合英宏 / KAWAI,HIDEHIRO wrote: > So, the problem for you is that "noextnmi" option is visible and effective > in the first kernel, isn't it? No, such an option shouldn't exist at all. You should be passing information *in* *a* *different* *manner* to the kdump kernel - not with a kernel command line option. I get the feeling I'm starting to sound like a broken record on this mail thread... :-( One other thing we could probably try to do is use boot_params which is, IIUC, passed to the second kernel. So we can add another bit to boot_params.hdr.loadflags or so and use that. Or something similar. Not particularly crazy about it but it is still much better than a command line param... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --