From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Stephane Eranian <eranian@google.com>,
Jin Yao <yao.jin@linux.intel.com>
Subject: Re: [PATCH v3 1/2] perf tools: Allow to control synthesize during record
Date: Wed, 15 Sep 2021 17:22:09 -0700 [thread overview]
Message-ID: <CAM9d7ci-jbWCjud-tzk5A899iSfe1JmWmMCqi3XWNfCpeZ3F1Q@mail.gmail.com> (raw)
In-Reply-To: <YRTmshairdxxiFo2@krava>
Hi Arnaldo,
On Thu, Aug 12, 2021 at 2:15 AM Jiri Olsa <jolsa@redhat.com> wrote:
>
> On Tue, Aug 10, 2021 at 09:46:57PM -0700, Namhyung Kim wrote:
> > Depending on the use case, it might require some kind of synthesize
> > and some not. Make it controllable to turn off heavy operations like
> > MMAP for all tasks.
> >
> > Currently all users are converted to enable all the synthesis by
> > default. It'll be updated in the later patch.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> for both patches
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Could you please take these patches?
Thanks,
Namhyung
prev parent reply other threads:[~2021-09-16 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 4:46 [PATCH v3 1/2] perf tools: Allow to control synthesize during record Namhyung Kim
2021-08-11 4:46 ` [PATCH v3 2/2] perf record: Add --synth option Namhyung Kim
2021-09-17 11:58 ` Arnaldo Carvalho de Melo
2021-08-12 9:15 ` [PATCH v3 1/2] perf tools: Allow to control synthesize during record Jiri Olsa
2021-09-16 0:22 ` Namhyung Kim [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=CAM9d7ci-jbWCjud-tzk5A899iSfe1JmWmMCqi3XWNfCpeZ3F1Q@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@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).