From: peter enderborg <peter.enderborg@sony.com>
To: Michal Hocko <mhocko@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Harry Wentland <Harry.Wentland@amd.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tony Cheng <Tony.Cheng@amd.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: Re: [PATCH] Add slowpath enter/exit trace events
Date: Fri, 24 Nov 2017 09:38:31 +0100 [thread overview]
Message-ID: <dfd93744-4854-cf63-e357-6bfcf505a62f@sony.com> (raw)
In-Reply-To: <20171123140127.7z5z6awj2ti6lozh@dhcp22.suse.cz>
On 11/23/2017 03:01 PM, Michal Hocko wrote:
> I am not sure adding a probe on a production system will fly in many
> cases. A static tracepoint would be much easier in that case. But I
> agree there are other means to accomplish the same thing. My main point
> was to have an easy out-of-the-box way to check latencies. But that is
> not something I would really insist on.
>
In android tracefs (or part of it) is the way for the system to control to what developers can access to the linux system on commercial devices. So it is very much used on production systems, it is even a requirement from google to be certified as android. Things like dmesg is not. However, this probe is at the moment not in that scope.
My point is that you need to condense the information as much as possible but still be useful before making the effort to copy it to userspace. And for this the trace-event are very useful for small systems since the cost is very low for events where no one is listening.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-24 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 10:43 peter.enderborg
2017-11-23 12:25 ` Michal Hocko
2017-11-23 12:35 ` peter enderborg
2017-11-23 12:47 ` Michal Hocko
2017-11-23 13:03 ` peter enderborg
2017-11-23 13:47 ` Michal Hocko
2017-11-23 13:36 ` Mel Gorman
2017-11-23 13:43 ` Tetsuo Handa
2017-11-24 7:43 ` peter enderborg
2017-11-23 14:01 ` Michal Hocko
2017-11-23 15:09 ` Mel Gorman
2017-11-24 8:38 ` peter enderborg [this message]
2017-11-23 13:00 ` Tetsuo Handa
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=dfd93744-4854-cf63-e357-6bfcf505a62f@sony.com \
--to=peter.enderborg@sony.com \
--cc=Harry.Wentland@amd.com \
--cc=Tony.Cheng@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=rostedt@goodmis.org \
--cc=vbabka@suse.cz \
/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