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=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 25980C10F0E for ; Mon, 8 Apr 2019 02:33:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F085520857 for ; Mon, 8 Apr 2019 02:33:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726612AbfDHCdh (ORCPT ); Sun, 7 Apr 2019 22:33:37 -0400 Received: from mga18.intel.com ([134.134.136.126]:58264 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726349AbfDHCdg (ORCPT ); Sun, 7 Apr 2019 22:33:36 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2019 19:33:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,323,1549958400"; d="scan'208";a="162276380" Received: from cli6-desk1.ccr.corp.intel.com (HELO [10.239.161.118]) ([10.239.161.118]) by fmsmga001.fm.intel.com with ESMTP; 07 Apr 2019 19:33:33 -0700 Subject: Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output To: Andy Lutomirski Cc: Thomas Gleixner , 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 References: <20190224044400.34975-1-aubrey.li@linux.intel.com> From: "Li, Aubrey" Message-ID: Date: Mon, 8 Apr 2019 10:33:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/4/8 9:52, Andy Lutomirski wrote: > On Sun, Apr 7, 2019 at 5:38 PM Li, Aubrey wrote: >> >> 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. >> > > Why is that a problem? It could exist on x86 and not exist on other > arches until needed. > I placed it in tid_base_stuff, under live_patch entry, so it exists for all arches, is there a better way to do this? Thanks, -Aubrey