From: kan.liang@intel.com
To: acme@kernel.org, linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org, jolsa@kernel.org,
adrian.hunter@intel.com, andi@firstfloor.org,
Kan Liang <kan.liang@intel.com>
Subject: [PATCH] perf tools: ignore zombie process for user profile
Date: Wed, 14 Dec 2016 12:48:05 -0500 [thread overview]
Message-ID: <1481737685-24595-1-git-send-email-kan.liang@intel.com> (raw)
From: Kan Liang <kan.liang@intel.com>
If user has zombie process, the perf record -u will error out.
Here is an example.
$ ./testd &
[1] 23796
$ sudo perf record -e cycles -u kan
Error:
The sys_perf_event_open() syscall returned with 3 (No such process) for
event (cycles).
/bin/dmesg may provide additional information.
No CONFIG_PERF_EVENTS=y kernel support configured?
The source code of testd is as below.
int main() {
if (fork())
{
while (1);
}
return 0;
}
Zombie process is dead process. It is meaningless to profile it.
It's better to ignore it for user profile.
Signed-off-by: Kan Liang <kan.liang@intel.com>
---
tools/perf/util/thread_map.c | 36 ++++++++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/tools/perf/util/thread_map.c b/tools/perf/util/thread_map.c
index 40585f5..4643b69 100644
--- a/tools/perf/util/thread_map.c
+++ b/tools/perf/util/thread_map.c
@@ -89,6 +89,39 @@ struct thread_map *thread_map__new_by_tid(pid_t tid)
return threads;
}
+static bool is_zombie_process(pid_t pid)
+{
+ char filename[PATH_MAX];
+ char comm[PATH_MAX];
+ char bf[BUFSIZ];
+ char s_state;
+ int s_pid;
+ FILE *fp;
+ ssize_t n;
+
+ snprintf(filename, sizeof(filename), "/proc/%d/stat", pid);
+ fp = fopen(filename, "r");
+ if (!fp) {
+ pr_warning("couldn't open %s\n", filename);
+ return false;
+ }
+ if (fgets(bf, sizeof(bf), fp) == NULL) {
+ pr_warning("Couldn't read stat for pid %d\n", pid);
+ fclose(fp);
+ return false;
+ }
+ fclose(fp);
+
+ n = sscanf(bf, "%d %s %c ", &s_pid, comm, &s_state);
+ if (n < 3)
+ return false;
+
+ if (s_state == 'Z')
+ return true;
+
+ return false;
+}
+
struct thread_map *thread_map__new_by_uid(uid_t uid)
{
DIR *proc;
@@ -124,6 +157,9 @@ struct thread_map *thread_map__new_by_uid(uid_t uid)
if (st.st_uid != uid)
continue;
+ if (is_zombie_process(pid))
+ continue;
+
snprintf(path, sizeof(path), "/proc/%d/task", pid);
items = scandir(path, &namelist, filter, NULL);
if (items <= 0)
--
2.4.3
next reply other threads:[~2016-12-14 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 17:48 kan.liang [this message]
2016-12-14 17:59 ` Jiri Olsa
2016-12-14 18:26 ` Liang, Kan
2016-12-14 19:13 ` acme
2016-12-14 19:19 ` Liang, Kan
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=1481737685-24595-1-git-send-email-kan.liang@intel.com \
--to=kan.liang@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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
Powered by JetHome