[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190523201822.cc554d68ec567164bec781e1@linux-foundation.org>
Date: Thu, 23 May 2019 20:18:22 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Aubrey Li <aubrey.li@...ux.intel.com>
Cc: tglx@...utronix.de, mingo@...hat.com, peterz@...radead.org,
hpa@...or.com, ak@...ux.intel.com, tim.c.chen@...ux.intel.com,
dave.hansen@...el.com, arjan@...ux.intel.com, adobriyan@...il.com,
aubrey.li@...el.com, linux-api@...r.kernel.org,
linux-kernel@...r.kernel.org, Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v18 1/3] proc: add /proc/<pid>/arch_status
On Thu, 25 Apr 2019 22:32:17 +0800 Aubrey Li <aubrey.li@...ux.intel.com> wrote:
> The architecture specific information of the running processes
> could be useful to the userland. Add /proc/<pid>/arch_status
> interface support to examine process architecture specific
> information externally.
I'll give this an
Acked-by: Andrew Morton <akpm@...ux-foundation.org>
from a procfs POV and shall let the x86 maintainers worry about it.
I must say I'm a bit surprised that we don't already provide some form
of per-process CPU-specific info anywhere in procfs. Something to
piggy-back this onto. But I can't find such a thing.
I assume we've already discussed why this is a new procfs file rather
than merely a new line in /proc/<pid>/status. If so, please add the
reasoning to the changelog. If not, please discuss now ;)
Powered by blists - more mailing lists