Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933634AbcLSRb3 (ORCPT ); Mon, 19 Dec 2016 12:31:29 -0500 Received: from mail.skyhub.de ([78.46.96.112]:41532 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932659AbcLSRb2 (ORCPT ); Mon, 19 Dec 2016 12:31:28 -0500 Date: Mon, 19 Dec 2016 18:31:23 +0100 From: Borislav Petkov To: Gustavo da Silva Cc: linux-kernel@vger.kernel.org, x86@vger.kernel.org Subject: Re: [RFC] arch/x86/Kconfig.cpu: Update with new gcc disponible 64bits CPU uarchs. Message-ID: <20161219173123.tyw4gni6i7fnl3uu@pd.tnic> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 630 Lines: 23 On Mon, Dec 19, 2016 at 03:09:50PM -0200, Gustavo da Silva wrote: > Good afternon! > > Are there reasons to 'Kconfig.cpu' and 'Makefile' not contains the > 'gcc -mtune=???' > recent options? This keeps popping up every couple of months. I was wondering when it is going to appear again and there you are. :) Here's a major reason: 99% of the kernels are built with -m(arch|tune)=generic. Think distros. Also, I am still waiting for a proof that CPU-optimized kernels have any advantages compared to the =generic ones. HTH. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.