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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 8F420C43603 for ; Wed, 11 Dec 2019 14:12:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 59D31214AF for ; Wed, 11 Dec 2019 14:12:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729778AbfLKOMy (ORCPT ); Wed, 11 Dec 2019 09:12:54 -0500 Received: from mx2.suse.de ([195.135.220.15]:39800 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727554AbfLKOMy (ORCPT ); Wed, 11 Dec 2019 09:12:54 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 6CC3FB232; Wed, 11 Dec 2019 14:12:52 +0000 (UTC) From: Thomas Renninger To: Greg KH Cc: Thomas Gleixner , Felix Schnizlein , 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 Subject: Re: [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86 Date: Wed, 11 Dec 2019 15:12:51 +0100 Message-ID: <22533595.7ohjOCJ8As@skinner.arch.suse.de> In-Reply-To: <20191211135619.GA538980@kroah.com> References: <20191206162421.15050-1-trenn@suse.de> <4737004.4U1sY2OxSp@skinner.arch.suse.de> <20191211135619.GA538980@kroah.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, December 11, 2019 2:56:19 PM CET Greg KH wrote: > On Wed, Dec 11, 2019 at 11:42:35AM +0100, Thomas Renninger wrote: > > If Greg (and others) are ok, I would add "page size exceeding" handling. > > Hm, quick searching for an example I realize that debugfs can exceed page > > size. Is it that hard to expose a sysfs file larger than page size? > > No, there is a simple way to do it, but I'm not going to show you how as > it is NOT how to use sysfs at all :) > > Why are you wanting to dump this whole mess into one file I wouldn't call a whitespace separated list of CPU feature flags a mess... > and then parse > it, it's no different from having 100+ different sysfs files and then > doing a readdir(3) on the thing, right? If this is the way it "has to"/should/"is designed for" to export such (not that complex) data via sysfs... I do not have such a strong opinion on the how, this is up to maintainers to discuss. I hope it is agreed that this info is worth exporting via sysfs. So I wait for the "how are CPU feature flags/bugs data" to be exported via sysfs and I volunteer to pick it up and submit a patch out of it. Thanks, Thomas