Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932261AbdLQVrq (ORCPT ); Sun, 17 Dec 2017 16:47:46 -0500 Received: from mail.skyhub.de ([5.9.137.197]:33650 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932193AbdLQVrp (ORCPT ); Sun, 17 Dec 2017 16:47:45 -0500 Date: Sun, 17 Dec 2017 22:47:35 +0100 From: Borislav Petkov To: Baoquan He Cc: Jiri Bohac , Toshi Kani , David Airlie , Dave Young , joro@8bytes.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar , "H. Peter Anvin" , Bjorn Helgaas , Thomas Gleixner , yinghai@kernel.org, Vivek Goyal Subject: Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore Message-ID: <20171217214735.nuxq5zo2eknqpbpi@pd.tnic> References: <20171216001514.x5eg37ad4aa2fwqt@dwarf.suse.cz> <20171216010142.GK12442@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20171216010142.GK12442@x1> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 900 Lines: 24 On Sat, Dec 16, 2017 at 09:01:42AM +0800, Baoquan He wrote: > 2) If firmware is broken, you can't enable gart in firmware, will > firmware engineer fix this since it's a firmware bug? Slow down and get a reality check first please! A firmware engineer will fix a 10yr old BIOS?!? Yeah right. And I'll get a pink pony for Christmas. Geez. We need a reliable way to tell the second kernel not to access the gart range. And frankly, the best thing to do would be to teach the *second* kernel to simply avoid the gart range. Regardless of what it gets told by the ELF header. Because there are some ranges which it shouldn't touch. Maybe we can reuse the gart detection code to do that in the second kernel too. But I haven't looked at it, might be hairy. Need to deal with this PTI madness first. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.