Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5869961ybl; Tue, 10 Dec 2019 12:55:42 -0800 (PST) X-Google-Smtp-Source: APXvYqwXsJC52jbhSNhYSnBOWluisinxzjiPWppZPbaMYWSC4hiLpgmLF0wPFuRJhK5S79Cy1xhp X-Received: by 2002:aca:5785:: with SMTP id l127mr770241oib.168.1576011341903; Tue, 10 Dec 2019 12:55:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576011341; cv=none; d=google.com; s=arc-20160816; b=HACb7lBQ69db7bM6A7VVn1HCw19YOBxYohfaYSrY6x1EHHDVGih5X0qsppzMkRL7T3 kuEFir3G94mqm/EQ1JuEQrENt5g09iQTQsODEGgIlnf65KDJjcg+5xrq1ENbTlW+/ZQU lnY0tKkwQagwsWeaAfMy7W2Tgj1vL+WPIfkBUzOA4ld3ZRWAO+QMvnWXuGN7rCS2K093 EDSFSckj5uMKe59NiOgLl0vTGIJnmBrfiZK9P3XJ5Drs2ZJCQbElRfN6MEm3M6YK1N9r oqZZDxqdZl8EyRG5y1aTc7Qx7NkgB2iA5pLeIpMZQKqg1Y6vEz28p1FtEWKZUwpiNUcx HqLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=GS0AX6Kz4D5Zrp7AnlF8EY9vasGaGgI9Wi+s56+cYRw=; b=NSPqrceQCN2VdzOPNc/3iSRC+8Pc16umRLmCSKNPgHH3Otc0/OJIqJbtMhJi+tRhZu j+BHHpFlxAhMkxCc3mzxxCzQQPbmLxxSj2+EWcRNK5ZOfow4L9r8oBmsQrlENDgrRjnZ leJT+s1t0Oy5ufrDYenud86jqpG69LW58O8/1q6zU5Tt19EjIYeW6PauVaXtzvnUMESF Z1tFvO5UWz6VQOGNSJ8TdvkBdiraN1nR4zrvNT5t5LALagl7MILCxLNneK90yrRJnQ1V jgawU0xGmIE74Ni4FmuD6l/EUEHolnLEXb6AbvEV9+ze8eKPJ61+4osRqtDJazOakQiI YXFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MJ+yXHaw; 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 s2si2983373otd.190.2019.12.10.12.55.28; Tue, 10 Dec 2019 12:55:41 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=MJ+yXHaw; 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 S1726826AbfLJUxv (ORCPT + 99 others); Tue, 10 Dec 2019 15:53:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:35496 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725999AbfLJUxv (ORCPT ); Tue, 10 Dec 2019 15:53:51 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 29D62206EC; Tue, 10 Dec 2019 20:53:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576011230; bh=fkev4MRGf9Lhg8tjRG4U3dQfBAMe6/SLbFZByzfr46g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MJ+yXHaw9iREFbIOuodzq9CaRUiVqEoOvWrbIbVYlqase9BSf1E/o1d2VepJuxPi7 HpJGb0VaGyHQqtvI3TkQSv9hCyYi13p0TSkCuatWGyaC+Em5K+XQyZQTbrlDOSL+by yWHyMPXWVUIXKnQdNnauCUuUp64VlKwmpHHt09r4= Date: Tue, 10 Dec 2019 21:53:48 +0100 From: Greg KH To: Thomas Gleixner Cc: Thomas Renninger , linux-kernel@vger.kernel.org, Felix Schnizlein , linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk, will.deacon@arm.com, x86@kernel.org, fschnitzlein@suse.de, Felix Schnizlein , Thomas Renninger Subject: Re: [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86 Message-ID: <20191210205348.GA4080658@kroah.com> References: <20191206162421.15050-1-trenn@suse.de> <20191206162421.15050-3-trenn@suse.de> <20191206163656.GC86904@kroah.com> <87sglroqix.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87sglroqix.fsf@nanos.tec.linutronix.de> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 10, 2019 at 09:48:54PM +0100, Thomas Gleixner wrote: > Greg KH writes: > > On Fri, Dec 06, 2019 at 05:24:20PM +0100, Thomas Renninger wrote: > >> From: Felix Schnizlein > >> ==> flags <== > >> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat umip > > > > One file with all of that? We are going to run into problems > > eventually, that should be split up. > > > > Just like bugs, that's going to just grow over time and eventually > > overflow PAGE_SIZE :( > > > > Make this: > > ├── flags > > │   ├── fpu > > │   ├── vme > > ... > > > > Much simpler to parse, right? > > Well, I'm not really sure whether 100+ files are simpler to parse. > > Aside of that I really don't see the value for 100+ files per CPU which > are just returning 1 or True or whatever as long as you are not > suggesting to provide real feature files which have 0/1 or True/False > content. > > But I still don't get the whole thing. The only "argument" I've seen so > far is the 'proc moves to sys' mantra, but that does not make it any > better. That is not a valid mantra, as I tried to explain later in this thread. I don't understand the need for this patchset either, all I was trying to do was to at least make it sane from a sysfs-point-of-view if people really wanted to do this type of thing. > We won't get rid of /proc/cpuinfo for a very long time simply because > too much userspace uses it. Introducing a mess in /sys/ in parallel just > for following the mantra does not help much. Again, invalid mantra, not a valid reason :) I think this is a patchset in search of a problem, which is why it was dropped all those years ago... thanks, greg k-h