From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753223AbdJUAus (ORCPT ); Fri, 20 Oct 2017 20:50:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59990 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753008AbdJUAur (ORCPT ); Fri, 20 Oct 2017 20:50:47 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D71F48763C Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jcm@redhat.com Subject: Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable To: Mark Rutland , Al Stone References: <20170926222324.17409-1-ahs3@redhat.com> <20170927103406.GC32150@leverpostej> <20171013142724.GA5893@leverpostej> <20171020161053.ujw3spzizhgu4g7b@lakrids.cambridge.arm.com> Cc: Timur Tabi , "linux-arm-kernel@lists.infradead.org" , lkml , rruigrok@codeaurora.org From: Jon Masters Message-ID: <626f32d8-c6df-7c25-0391-f912be5665cf@redhat.com> Date: Fri, 20 Oct 2017 20:50:42 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Sat, 21 Oct 2017 00:50:47 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/20/2017 01:24 PM, Jon Masters wrote: > 1). The first thing people do when they get an Arm server is to cat > /proc/cpuinfo. They then come complaining that it's not like x86. They > can't get the output their looking for and this results in bug filing, > and countless hours on phone calls discussing over and over again. > Worse, there are some parts of the stack that really need this. Within 6 hours of sending this, I get a ping about this week's "Works On Arm" newsletter and...people reporting bugs with not getting CPU capabilities in /proc/cpuinfo. This madness is going to end. Soon. Jon. -- Computer Architect | Sent from my Fedora powered laptop From mboxrd@z Thu Jan 1 00:00:00 1970 From: jcm@redhat.com (Jon Masters) Date: Fri, 20 Oct 2017 20:50:42 -0400 Subject: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable In-Reply-To: References: <20170926222324.17409-1-ahs3@redhat.com> <20170927103406.GC32150@leverpostej> <20171013142724.GA5893@leverpostej> <20171020161053.ujw3spzizhgu4g7b@lakrids.cambridge.arm.com> Message-ID: <626f32d8-c6df-7c25-0391-f912be5665cf@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 10/20/2017 01:24 PM, Jon Masters wrote: > 1). The first thing people do when they get an Arm server is to cat > /proc/cpuinfo. They then come complaining that it's not like x86. They > can't get the output their looking for and this results in bug filing, > and countless hours on phone calls discussing over and over again. > Worse, there are some parts of the stack that really need this. Within 6 hours of sending this, I get a ping about this week's "Works On Arm" newsletter and...people reporting bugs with not getting CPU capabilities in /proc/cpuinfo. This madness is going to end. Soon. Jon. -- Computer Architect | Sent from my Fedora powered laptop