From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752221AbbJBHrr (ORCPT ); Fri, 2 Oct 2015 03:47:47 -0400 Received: from mail.skyhub.de ([78.46.96.112]:46898 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751208AbbJBHr0 (ORCPT ); Fri, 2 Oct 2015 03:47:26 -0400 Date: Fri, 2 Oct 2015 09:47:21 +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: <20151002074721.GA16538@pd.tnic> References: <20150925112803.4258.94241.stgit@softrs> <20150925112811.4258.54494.stgit@softrs> <20150930115548.GI2881@worktop.programming.kicks-ass.net> <04EAB7311EE43145B2D3536183D1A8445499CD11@GSjpTKYDCembx31.service.hitachi.net> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <04EAB7311EE43145B2D3536183D1A8445499ED83@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 Fri, Oct 02, 2015 at 12:58:02AM +0000, 河合英宏 / KAWAI,HIDEHIRO wrote: > > On Thu, Oct 01, 2015 at 10:24:19AM +0000, 河合英宏 / KAWAI,HIDEHIRO wrote: > > > But how do we check if the starting kernel is a dump capture kernel? > > > > How does that first kernel pass info to the capture kernel? > > As I described in the previous mail, I meant: "How does the first kernel pass info to the capture kernel by *not* using the kernel command line"? The kernel command line is not the channel to pass data to the kdump kernel. > Yes, your first kernel doesn't get external NMIs, but basically > you don't have to set "noextnmi" option to the first kernel. So it doesn't belong there as a kernel command line parameter in the first place. IOW, you need a different method to pass data to the second kernel. Be it an ELF header, be it a shared page, whatever. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.