From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Li, Aubrey" Subject: Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output Date: Mon, 8 Apr 2019 08:38:40 +0800 Message-ID: References: <20190224044400.34975-1-aubrey.li@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski , Thomas Gleixner Cc: Ingo Molnar , Peter Zijlstra , "H. Peter Anvin" , Andi Kleen , Tim Chen , Dave Hansen , Arjan van de Ven , aubrey.li@intel.com, LKML , Linux API , Alexey Dobriyan , Andrew Morton List-Id: linux-api@vger.kernel.org On 2019/4/8 1:34, Andy Lutomirski wrote: > On Fri, Apr 5, 2019 at 12:32 PM Thomas Gleixner wrote: >> >> On Sun, 24 Feb 2019, Aubrey Li wrote: >> >>> The architecture specific information of the running processes could >>> be useful to the userland. Add support to examine process architecture >>> specific information externally. >>> >>> Signed-off-by: Aubrey Li >>> Cc: Peter Zijlstra >>> Cc: Andi Kleen >>> Cc: Tim Chen >>> Cc: Dave Hansen >>> Cc: Arjan van de Ven >> >> This really lacks >> >> Cc: Linux API >> Cc: Alexey Dobriyan >> Cc: Andrew Morton >> >> Cc'ed now. >> > > I certainly understand why you want to expose this info, but would it > make more sense to instead add an arch_status file in /proc with > architecture-specific info? Or maybe an x86_status field for x86 > status, etc. > I tried this, but no other architecture showed interest in arch_status under /proc. Thanks, -Aubrey