Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751891AbdL2Uep (ORCPT ); Fri, 29 Dec 2017 15:34:45 -0500 Received: from mail-it0-f52.google.com ([209.85.214.52]:36127 "EHLO mail-it0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751412AbdL2Uen (ORCPT ); Fri, 29 Dec 2017 15:34:43 -0500 X-Google-Smtp-Source: ACJfBospLBcHXTt6oKgPl1huRATsV3MgNT8nwXSIHE4lto2fi9CdXVUWdRLawPiNfhbxtXFjeJq3kTPcFeO6G49TAoQ= MIME-Version: 1.0 In-Reply-To: <1514578936.28262.11.camel@tsoy.me> References: <1514453602.6251.8.camel@tsoy.me> <20171229091741.GC18441@kroah.com> <1514557888.28262.1.camel@tsoy.me> <1514558513.28262.3.camel@tsoy.me> <1b4569ee-8c06-4480-447b-2af8f6804053@intel.com> <1514578936.28262.11.camel@tsoy.me> From: Linus Torvalds Date: Fri, 29 Dec 2017 12:34:42 -0800 X-Google-Sender-Auth: Xb7EYdTgN7jzxo_iVv6a5rKEZtI Message-ID: Subject: Re: 4.14.9 with CONFIG_MCORE2 fails to boot To: Alexander Tsoy Cc: Dave Hansen , Greg KH , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Boris Ostrovsky , Borislav Petkov , Borislav Petkov , Brian Gerst , Dave Hansen , David Laight , Denys Vlasenko , Eduardo Valentin , Greg KH , "H. Peter Anvin" , Josh Poimboeuf , Juergen Gross , Peter Zijlstra , Rik van Riel , Will Deacon , "Liguori, Anthony" , Daniel Gruss , Hugh Dickins , Kees Cook , Kernel Mailing List , stable Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 24 On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy wrote: >> But double-checking that "-march=core2" case is definitely worth >> looking into. Especially since there are clear indications that it's >> gcc version-dependent anyway. Alexander? > > Yes, the change suggested by Dave makes the problem go away. Ok, that's good information. It doesn't really explain *why* that commit 7f2590a110b8 ("x86/entry/64: Use a per-CPU trampoline stack for IDT entries") ends up being sensitive to that compiler option, though. So it narrows the cause down, but it doesn't really root-cause the problem. It tends to be almost impossible to find differences in code generation, because they are generally all over. Ho humm. What happens if you change the "-march=core2" to "-mtune=core2"? Does it still boot? Because maybe the actual differences that "-march=core2" generates might be easier to see when compared to "-mtune=core2". Linus