mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
	Don Zickus <dzickus@redhat.com>, Joe Mario <jmario@redhat.com>
Subject: Re: [PATCH v3 2/2] perf tool: Fix ppid for synthesized fork events
Date: Tue, 31 Mar 2015 16:17:52 +0200	[thread overview]
Message-ID: <20150331141751.GA31798@krava.brq.redhat.com> (raw)
In-Reply-To: <20150331141026.GC3777@krava.brq.redhat.com>

On Tue, Mar 31, 2015 at 04:10:26PM +0200, Jiri Olsa wrote:
> On Mon, Mar 30, 2015 at 02:35:58PM -0600, David Ahern wrote:
> > 363b785f38 added synthesized fork events and set a thread's parent id
> > to itself. Since we are already processing /proc/<pid>/status the ppid
> > can be determined properly. Make it so.
> > 
> > Signed-off-by: David Ahern <dsahern@gmail.com>
> > Cc: Don Zickus <dzickus@redhat.com>
> > Cc: Joe Mario <jmario@redhat.com>
> > Cc: Jiri Olsa <jolsa@redhat.com>
> > ---
> > v3
> > - removed isspace and newline checks; added brackets per Arnaldo's comments
> > 
> > v2:
> > - removed changes to function signature for perf_event__synthesize_comm as
> >   noted by Jiri
> > 
> >  tools/perf/util/event.c | 83 +++++++++++++++++++++++++++++--------------------
> >  1 file changed, 50 insertions(+), 33 deletions(-)
> > 
> > diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
> > index 023dd3548a94..5516236df6ab 100644
> > --- a/tools/perf/util/event.c
> > +++ b/tools/perf/util/event.c
> > @@ -51,29 +51,32 @@ static struct perf_sample synth_sample = {
> >  
> >  /*
> >   * Assumes that the first 4095 bytes of /proc/pid/stat contains
> > - * the comm and tgid.
> > + * the comm, tgid and ppid.
> >   */
> > -static pid_t perf_event__get_comm_tgid(pid_t pid, char *comm, size_t len)
> > +static int perf_event__get_comm_ids(pid_t pid, char *comm, size_t len,
> > +				    pid_t *tgid, pid_t *ppid)
> >  {
> >  	char filename[PATH_MAX];
> >  	char bf[4096];
> >  	int fd;
> >  	size_t size = 0, n;
> > -	pid_t tgid = -1;
> > -	char *nl, *name, *tgids;
> > +	char *nl, *name, *tgids, *ppids;
> > +
> > +	*tgid = -1;
> > +	*ppid = -1;
> >  
> >  	snprintf(filename, sizeof(filename), "/proc/%d/status", pid);
> >  
> >  	fd = open(filename, O_RDONLY);
> >  	if (fd < 0) {
> >  		pr_debug("couldn't open %s\n", filename);
> > -		return 0;
> > +		return -1;
> 
> hum, missed this one in previous version.. why did not we fail before?

sigh, it was the tgid before, now it's err..  ;-) ook

jirka

  reply	other threads:[~2015-03-31 14:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 20:35 [PATCH v2 1/2] perf tool: Refactor comm/tgid lookup David Ahern
2015-03-30 20:35 ` [PATCH v3 2/2] perf tool: Fix ppid for synthesized fork events David Ahern
2015-03-31 14:10   ` Jiri Olsa
2015-03-31 14:17     ` Jiri Olsa [this message]
2015-03-31 14:35   ` Jiri Olsa
2015-03-31 16:23   ` Don Zickus
2015-04-02 12:23   ` [tip:perf/core] perf tools: " tip-bot for David Ahern
2015-03-31 14:35 ` [PATCH v2 1/2] perf tool: Refactor comm/tgid lookup Jiri Olsa
2015-03-31 15:55   ` Arnaldo Carvalho de Melo
2015-03-31 16:22 ` Don Zickus
2015-04-02 12:23 ` [tip:perf/core] perf tools: " tip-bot for David Ahern

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=20150331141751.GA31798@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=jmario@redhat.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®