From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0080EC43381 for ; Wed, 27 Mar 2019 11:14:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BB26A2087C for ; Wed, 27 Mar 2019 11:14:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="HPBuI6zp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732942AbfC0LOv (ORCPT ); Wed, 27 Mar 2019 07:14:51 -0400 Received: from mail.skyhub.de ([5.9.137.197]:44386 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729489AbfC0LOv (ORCPT ); Wed, 27 Mar 2019 07:14:51 -0400 Received: from zn.tnic (p200300EC2F098000329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f09:8000:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 1E4161EC0428; Wed, 27 Mar 2019 12:14:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553685290; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=dc0vaMLNDTywpiZTPp+4509zisE8B0qa4I4qrOBwXEw=; b=HPBuI6zprx08DUThKIn0c7Ie6Jt5KRg5tjTDWnpZBYUvbLO15uB2NmzUy+l08gchrOc8Nd TJo+MpVdnYpKondiQ5DQZ+9AaawPZyfZHnJCo4z1eKa8Awbw3sXLjBk3lni6aXc3QpP1XC Lysz/rGAUd/czttbEkhtMIjvUYeziUk= Date: Wed, 27 Mar 2019 12:14:52 +0100 From: Borislav Petkov To: Leon Romanovsky Cc: Joe Perches , "Rafael J . Wysocki" , Thomas Gleixner , Ingo Molnar , x86 , "H. Peter Anvin" , linux-pm , LKML Subject: Re: [PATCH -next v1] x86/apic: Reduce print level of CPU limit announcement Message-ID: <20190327111452.GC32571@zn.tnic> References: <20190327090905.5588-1-leon@kernel.org> <20190327093844.GO22899@mtr-leonro.mtl.com> <55774b1a8c82e94b2796c992889929f1da905d9b.camel@perches.com> <20190327095337.GP22899@mtr-leonro.mtl.com> <20190327101133.GQ22899@mtr-leonro.mtl.com> <20190327101815.GB32571@zn.tnic> <20190327105024.GR22899@mtr-leonro.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190327105024.GR22899@mtr-leonro.mtl.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 27, 2019 at 12:50:24PM +0200, Leon Romanovsky wrote: > It is how we are internally running verification and development, > with KERN_DEBUG level, we need it to catch bugs. And what is the big deal with seeing those messages? Why are *exactly* those two such a big problem and the gazillion other debug messages are fine? > This "some config option" is dynamic debug prints and most probably it > is enabled in your or any kernel developer in the world. I personally don't use it because it only gets in the way. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.