From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754185AbaIHTKD (ORCPT ); Mon, 8 Sep 2014 15:10:03 -0400 Received: from terminus.zytor.com ([198.137.202.10]:59078 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753963AbaIHTKB (ORCPT ); Mon, 8 Sep 2014 15:10:01 -0400 Message-ID: <540DFED8.5080909@zytor.com> Date: Mon, 08 Sep 2014 12:09:12 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Borislav Petkov , Fenghua Yu CC: Ingo Molnar , Thomas Gleixner , Henrique de Moraes Holschuh , linux-kernel , x86 Subject: Re: [PATCH] x86/microcode: add parameter dis_ucode_ldr in kernel-paramenters.txt References: <1409857626-55464-1-git-send-email-fenghua.yu@intel.com> <20140905085709.GC11432@nazgul.tnic> In-Reply-To: <20140905085709.GC11432@nazgul.tnic> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/05/2014 01:57 AM, Borislav Petkov wrote: > >> This patch adds the explanation for this parameter in >> Documentation/kernel-parameters.txt for user convenience. > > As I said earlier, I don't want to do exactly that because this > parameter should be used only to rule out microcode loading causes a > problem and not regularly. I know, it doesn't stop people from looking > at the code but still. > Are you genuinely saying we shouldn't document this command line parameter? Sorry, it really doesn't work that way. -hpa