Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp699072ybl; Wed, 11 Dec 2019 06:14:00 -0800 (PST) X-Google-Smtp-Source: APXvYqyBQLz9JTRbJSgKrUr9oQvmHwzq5m1SbKZjTymshKw+VSEuSbg7NmE26lqRkFaAeFEU7op3 X-Received: by 2002:aca:2808:: with SMTP id 8mr3015052oix.27.1576073639858; Wed, 11 Dec 2019 06:13:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576073639; cv=none; d=google.com; s=arc-20160816; b=UbH6bO7Ik2U7yv88ivWm9ZczPQJnPY/bFL92WJfqF6m7Ydsgfa99ht/g7Fz1wDyRKD 9icNUxRcQypKFCvDkeYMngA+1slbt3jcciKmlj5GsMApC0sWntOpWMrf3ASniuRoBKxD Cgr3A0nH44VZ7MtYlaLhxGNNl3jgp2NQ/6QzjYWqyEEC5JRJbS0UendQI3reuexvsEqt YADmFZ2lvQGtI7yqgKD7VecRGRNfOrThpnuyavkUIrv95s0kTbTqjAG0sjW/Vq93zRfl Uisz+SpXwx2C42R0F6SjTykL/AOAV4AVRU8XN6HEQNWVov156YUh97ndbME6B40BLmJ+ GDjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=HIsgCMEHh8skkzQAV2VWKGh5EPln8+IaFRu+VIR4vXw=; b=NP3iiJq7ux6Y2vyvuQ+y0XSDgkoaCiHboGsmoYwwewJ/dEjyshBzppx9Q6qCJpAcyx G//rdajGof/pKuj3duaLNfCpFmpfjG/CkWRgfv4T6FZOeNQMxhNEboP3jQ7kr6jffK4n iGzKbnkYXpzm6dGAKT8VkU9z9i9M1Mzhl0Hf01Z4NPZHGOmrArwo5B5IIDCddd6XCNpv C2WOiF77WS7bWlFUnnZeE1LUuTfo+MP4bkoxm/LPlxylkRHsGiNNlOXbE3weovrxrbbJ zo2cr39mbsrwX6t3FIgzxQC5uoB6gD21i4eMh7hVgjU5OiLdmZzPdNXA9CuZeOYZ1BUH oVCA== 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 k17si1207882oiw.238.2019.12.11.06.13.47; Wed, 11 Dec 2019 06:13:59 -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; 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 S1729767AbfLKOMy (ORCPT + 99 others); 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