Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1849130imm; Sat, 18 Aug 2018 05:52:18 -0700 (PDT) X-Google-Smtp-Source: AA+uWPx44z0+CEznDxkwHJkaaD5Ty1ky2HeHqMXUNlAfE0c8gaMMu91XVTk5d8FAg+MOlk0x4tj5 X-Received: by 2002:a17:902:6e16:: with SMTP id u22-v6mr37089641plk.13.1534596738615; Sat, 18 Aug 2018 05:52:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534596738; cv=none; d=google.com; s=arc-20160816; b=BIMwuutNVQ2C6NNCpnI7ZfQOgiiWiEOGYrnvdZotpG6Alw5DNwLjoa8LdkcH9kD3iv 2tf2/hR2oezGwToXlsrsqqhxsq1fcjOSArcBhdAsHQctk9gGtiCM+C5pivrNFmik/ll2 EfGPYKNvudva+iDVpbKnKcsbj8czHvvYGFv3zlXeNhPDRUoET3I9TfL6192SxSqBD7HG zEMgedMVjvjbDs8gzfyEfSGwTh5dwK8wHjntnpdKkB37ZvJtswWZ7uXhHLvRmuU3UVRE bGnRhIQOCRbuWPeq+L3gX3hHg1w+Vjo+ICLFnKF0IONPoXMRm83C74JJe4gVDghM3D3s lA2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=0yH3O+H1P32uvn/U5IhyZz/K1iQ54fIy29uXAE+2MSw=; b=qAprx+qw+MgpFmeVoHgZjC30MTQLgxNuIhOu+Kq33Nwdf0GN+IVbKpv8n+zZJgG0OQ HBXYczBVAinthXgQTOx48W90DN4WCBVH7+xhdRFazkK0dBOuwiZejALnKE1+QHel4UK5 H3Ha4Iwe1kuSKBQJJymyH7tvOXUb1U11AOp1iCXTlxeAWnkCmTPuKsIjWC+/nGyk2QzS 6MPZxUo7UuBkp9PRHlxSAVFP2RdjjvzUFbDWpwoJhcb6umZaJJ+mf+qEdV9fpre2qZsx /5r7CugMkwWip/tWE1IfTcY1VF9szvjJYVQhkIPnDkMaguG+qgLiU6z3Il84n/fX/TwK Sujg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y13-v6si2750542pgr.573.2018.08.18.05.52.03; Sat, 18 Aug 2018 05:52:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726332AbeHRP63 (ORCPT + 99 others); Sat, 18 Aug 2018 11:58:29 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:52385 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725886AbeHRP62 (ORCPT ); Sat, 18 Aug 2018 11:58:28 -0400 Received: from p4fea45ac.dip0.t-ipconnect.de ([79.234.69.172] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fr0gr-0002VB-KL; Sat, 18 Aug 2018 14:50:49 +0200 Date: Sat, 18 Aug 2018 14:50:49 +0200 (CEST) From: Thomas Gleixner To: Greg Kroah-Hartman cc: Jinpu Wang , stable , linux-kernel@vger.kernel.org, Ingo Molnar , konrad.wilk@oracle.com Subject: Re: [BUG]smt sysfs dir missing on 4.4.148 and 4.14.63 In-Reply-To: <20180817170129.GE24945@kroah.com> Message-ID: References: <20180816155126.GA18296@kroah.com> <20180816163937.GA5105@kroah.com> <20180817170129.GE24945@kroah.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 Aug 2018, Greg Kroah-Hartman wrote: > On Fri, Aug 17, 2018 at 02:39:00PM +0200, Jinpu Wang wrote: > > > > I found the problem, CONFIG_HOTPLUG_SMT is enable due to CONFIG_SMP, > > but I did explicitly enable CONFIG_HOTPLUG_CPU. > > > > That's why the smt dir is missing, and kernel panic when I boot with > > 'nosmt' or 'l1tf=full' probably also other combination. > > > > With CONFIG_HOTPLUG_CPU=y, it works fine so far. > > So do we need a new configuration dependancy here to resolve this > problem? Why is this not an issue in Linus's tree? That's probably the same problem on Linus tree. Have not tested it yet though. I'll have a look. Thanks, tglx