From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@linux.intel.com
Cc: acme@kernel.org, peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, namhyung@kernel.org,
ak@linux.intel.com, sunil.k.pandey@intel.com
Subject: Re: [PATCH] perf evlist: Fix error out while applying initial delay and LBR
Date: Mon, 9 Jul 2018 17:20:54 +0200 [thread overview]
Message-ID: <20180709152054.GA11886@krava> (raw)
In-Reply-To: <1531145722-16404-1-git-send-email-kan.liang@linux.intel.com>
On Mon, Jul 09, 2018 at 07:15:22AM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> Perf record will error out if both --delay and LBR are applied.
> For example:
> perf record -D 1000 -a -e cycles -j any -- sleep 2
> Error:
> dummy:HG: PMU Hardware doesn't support sampling/overflow-interrupts.
> Try 'perf stat'
>
> A dummy event is added implicitly for initial delay, which has the same
> configurations as real sampling events. The dummy event is a software
> event. If LBR is configured, perf must error out.
>
> The dummy event only be used to track PERF_RECORD_MMAP while perf waits
> for the initial delay to enable the real events. The BRANCH_STACK bit
> can be safely cleared for the dummy event.
>
> After applying the patch:
> perf record -D 1000 -a -e cycles -j any -- sleep 2
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.054 MB perf.data (828 samples) ]
>
> Reported-by: Pandey, Sunil K <sunil.k.pandey@intel.com>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2018-07-09 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:15 [PATCH] perf evlist: Fix error out while applying initial delay and LBR kan.liang
2018-07-09 15:20 ` Jiri Olsa [this message]
2018-07-26 12:51 ` Arnaldo Carvalho de Melo
2018-08-02 8:07 ` [tip:perf/core] " tip-bot for Kan Liang
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=20180709152054.GA11886@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sunil.k.pandey@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