On Tue, Apr 16, 2019 at 4:01 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, 16 Apr 2019 14:32:48 +0800 Aubrey Li <aubrey.li@xxxxxxxxxxxxxxx> 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.) --Andy
