linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Raul Silvera <rsilvera@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Dave Marchevsky <davemarchevsky@fb.com>,
	Colin Ian King <colin.king@intel.com>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf: Adjust perf-inject output data offset for backward compatibility
Date: Thu, 23 Jun 2022 11:46:36 -0300	[thread overview]
Message-ID: <YrR8zDls7y//T7zI@kernel.org> (raw)
In-Reply-To: <b7de807d-5ec3-3d8d-59ba-4058e1193a96@intel.com>

Em Wed, Jun 22, 2022 at 11:36:58AM +0300, Adrian Hunter escreveu:
> On 21/06/22 18:27, Raul Silvera wrote:
> > When perf inject creates a new file, it reuses the data offset from the
> > input file. If there has been a change on the size of the header, as
> > happened in v5.12 -> v5.13, the new offsets will be wrong, resulting in
> > a corrupted output file.
> > 
> > This change adds the function perf_session__data_offset to compute the
> > data offset based on the current header size, and uses that instead of
> > the offset from the original input file.
> > 
> > Signed-off-by: Raul Silvera <rsilvera@google.com>
> 
> Acked-by: Adrian Hunter <adrian.hunter@intel.com>

Thanks, applied.

- Arnaldo

 
> > ---
> > Changes since v1:
> >  - Use the adjusted header->data_offset in do_write_header instead of
> >    recomputing it.
> > ---
> >  tools/perf/builtin-inject.c |  2 +-
> >  tools/perf/util/header.c    | 14 ++++++++++++++
> >  tools/perf/util/header.h    |  2 ++
> >  3 files changed, 17 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
> > index a75bf11585b5..1dfdcef36607 100644
> > --- a/tools/perf/builtin-inject.c
> > +++ b/tools/perf/builtin-inject.c
> > @@ -916,7 +916,7 @@ static int __cmd_inject(struct perf_inject *inject)
> >  		inject->tool.tracing_data = perf_event__repipe_tracing_data;
> >  	}
> >  
> > -	output_data_offset = session->header.data_offset;
> > +	output_data_offset = perf_session__data_offset(session->evlist);
> >  
> >  	if (inject->build_id_all) {
> >  		inject->tool.mmap	  = perf_event__repipe_buildid_mmap;
> > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > index 53332da100e8..6ad629db63b7 100644
> > --- a/tools/perf/util/header.c
> > +++ b/tools/perf/util/header.c
> > @@ -3686,6 +3686,20 @@ int perf_session__write_header(struct perf_session *session,
> >  	return perf_session__do_write_header(session, evlist, fd, at_exit, NULL);
> >  }
> >  
> > +size_t perf_session__data_offset(const struct evlist *evlist)
> > +{
> > +	struct evsel *evsel;
> > +	size_t data_offset;
> > +
> > +	data_offset = sizeof(struct perf_file_header);
> > +	evlist__for_each_entry(evlist, evsel) {
> > +		data_offset += evsel->core.ids * sizeof(u64);
> > +	}
> > +	data_offset += evlist->core.nr_entries * sizeof(struct perf_file_attr);
> > +
> > +	return data_offset;
> > +}
> > +
> >  int perf_session__inject_header(struct perf_session *session,
> >  				struct evlist *evlist,
> >  				int fd,
> > diff --git a/tools/perf/util/header.h b/tools/perf/util/header.h
> > index 08563c1f1bff..56916dabce7b 100644
> > --- a/tools/perf/util/header.h
> > +++ b/tools/perf/util/header.h
> > @@ -136,6 +136,8 @@ int perf_session__inject_header(struct perf_session *session,
> >  				int fd,
> >  				struct feat_copier *fc);
> >  
> > +size_t perf_session__data_offset(const struct evlist *evlist);
> > +
> >  void perf_header__set_feat(struct perf_header *header, int feat);
> >  void perf_header__clear_feat(struct perf_header *header, int feat);
> >  bool perf_header__has_feat(const struct perf_header *header, int feat);

-- 

- Arnaldo

      reply	other threads:[~2022-06-23 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 15:27 [PATCH v2] perf: Adjust perf-inject output data offset for backward compatibility Raul Silvera
2022-06-22  8:36 ` Adrian Hunter
2022-06-23 14:46   ` Arnaldo Carvalho de Melo [this message]

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=YrR8zDls7y//T7zI@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=colin.king@intel.com \
    --cc=davemarchevsky@fb.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rsilvera@google.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).