From: Andy Lutomirski <luto@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Aubrey Li <aubrey.li@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@linux.intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
aubrey.li@intel.com, Linux API <linux-api@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v15 1/3] /proc/pid/status: Add support for architecture specific output
Date: Wed, 17 Apr 2019 12:45:18 -0700 [thread overview]
Message-ID: <CALCETrUjF9PBmkzH1J86vw4ZW785DP7FtcT+gcSrx29=BUnjoQ@mail.gmail.com> (raw)
In-Reply-To: <20190416160143.8292ced993dc803aae7fa0da@linux-foundation.org>
On Tue, Apr 16, 2019 at 4:01 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 16 Apr 2019 14:32:48 +0800 Aubrey Li <aubrey.li@linux.intel.com> 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
next prev parent reply other threads:[~2019-04-17 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:32 [PATCH v15 1/3] /proc/pid/status: Add support for architecture specific output Aubrey Li
2019-04-16 6:32 ` [PATCH v15 2/3] x86,/proc/pid/status: Add AVX-512 usage elapsed time Aubrey Li
2019-04-16 6:32 ` [PATCH v15 3/3] Documentation/filesystems/proc.txt: add AVX512_elapsed_ms Aubrey Li
2019-04-16 23:01 ` [PATCH v15 1/3] /proc/pid/status: Add support for architecture specific output Andrew Morton
2019-04-17 10:07 ` Li, Aubrey
2019-04-17 19:45 ` Andy Lutomirski [this message]
2019-04-18 13:00 ` Thomas Gleixner
2019-04-19 11:42 ` Li, Aubrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALCETrUjF9PBmkzH1J86vw4ZW785DP7FtcT+gcSrx29=BUnjoQ@mail.gmail.com' \
--to=luto@kernel.org \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=aubrey.li@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).