[lkml]   [2019]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v15 1/3] /proc/pid/status: Add support for architecture specific output
On Tue, Apr 16, 2019 at 4:01 PM Andrew Morton <> wrote:
> On Tue, 16 Apr 2019 14:32:48 +0800 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.
> The implementation looks just fine to me. Have you had any feedback on
> the overall desirability of adding this feature?

I think I've been the most outspoken, and my not-all-that-strong
opinion is that I don't really like it. /proc/PID/status is already a
bit of a mess, and I don't think we really want it to be a mess that
is different on different architectures. Hence my suggestion of
/proc/PID/x86_status instead. Or we could do /proc/PID/arch_status, I
suppose, and make sure that everything in it is namespaced. (We could
easily end up with a situation where status fields from more than one
architecture are present. Think i386 + x86_64. Thata's also the case
where qemu userspace emulation is used to run binaries meant for one
architecture on a different architecture's kernel.)


 \ /
  Last update: 2019-04-17 21:46    [W:0.127 / U:6.496 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site