From: Sasha Levin <sashal@kernel.org>
To: Jinpu Wang <jinpuwang@gmail.com>
Cc: "Greensky, James J" <james.j.greensky@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"v3.14+, only the raid10 part" <stable@vger.kernel.org>
Subject: Re: Fix "perf tools: Synthesize GROUP_DESC feature in pipe mode" in the LT 4.14 branch
Date: Fri, 21 Dec 2018 19:27:18 -0500 [thread overview]
Message-ID: <20181222002718.GL86645@sasha-vm> (raw)
In-Reply-To: <CAD9gYJKvcn5kzMKhHU2UO=99Vdus_v=5D-fZb6-+Fy=gDokZFA@mail.gmail.com>
On Fri, Dec 21, 2018 at 11:57:53AM +0100, Jinpu Wang wrote:
>+cc Greg, stable
>
>Greensky, James J <james.j.greensky@intel.com> 于2018年12月21日周五 上午11:48写道：
>>
>> Commit d38d272592737ea88a20 ("perf tools: Synthesize GROUP_DESC feature in pipe mode") broke the LT 4.14 branch when using event groups in pipe-mode.
>>
>> # perf record -e '{cycles,instructions,branches}' -- sleep 4 | perf report
>> # To display the perf.data header info, please use --header/--header-only options
>> #
>> Oxd7c [0x60]: failed to process type: 80
>> Error:
>> Failed to process sample
>>
>> Commit a2015516c5c0be932a69 ("perf record: Synthesize features before events in pipe mode") is the fix. Can we get this cherry-picked and applied?
I've queued d38d272592737ea88a20 for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-22 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05BD5679F4A9234798A0693ABF94E75ADFF7F3A5@ORSMSX101.amr.corp.intel.com>
2018-12-21 10:57 ` Fix "perf tools: Synthesize GROUP_DESC feature in pipe mode" in the LT 4.14 branch Jinpu Wang
2018-12-21 22:43 ` Greensky, James J
2018-12-22 0:27 ` Sasha Levin [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=20181222002718.GL86645@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.j.greensky@intel.com \
--cc=jinpuwang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).