From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: zhangzhiqiang <zhangzhiqiang.zhang@huawei.com>,
Mark Rutland <Mark.Rutland@arm.com>,
"cov@codeaurora.org" <cov@codeaurora.org>,
"lizefan@huawei.com" <lizefan@huawei.com>,
"wangnan0@huawei.com" <wangnan0@huawei.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: armv7: perf: fix armv7 ref-cycles error
Date: Wed, 8 Oct 2014 06:31:47 -0700 [thread overview]
Message-ID: <20141008133147.GC5119@kroah.com> (raw)
In-Reply-To: <20141008091741.GC26140@arm.com>
On Wed, Oct 08, 2014 at 10:17:41AM +0100, Will Deacon wrote:
> On Wed, Oct 08, 2014 at 04:06:12AM +0100, zhangzhiqiang wrote:
> > hi all,
> > ----------------------------------------
> >
> > ref-cycles event is specially to Intel core, but can still used in arm architecture
> > with the wrong return value with 3.10 stable. for instance:
> >
> > perf stat -e ref-cycles sleep 1
> >
> > Performance counter stats for 'sleep 1':
> >
> > 0 ref-cycles
> >
> > 1.002381916 seconds time elapsed
> >
> > this patch fix the bug and make it return NOT SUPPORTED
> > distinctly.
> >
> > In upstream this bug has been fixed by other way(not primary for the bug), which changes more than one file
> > and more than 1000 lines. the primary commit is 6b7658ec8a100b608e59e3cde353434db51f5be0.
> > besides we can not simply cherry-pick.
>
> I thought I saw Greg pick this up the other day?
Yes, it's in 3.16.4, did I do something wrong by accepting it?
confused,
greg k-h
next prev parent reply other threads:[~2014-10-08 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 3:06 [PATCH] arm: armv7: perf: fix armv7 ref-cycles error zhangzhiqiang
2014-10-08 9:17 ` Will Deacon
2014-10-08 13:31 ` gregkh [this message]
2014-10-08 13:38 ` Will Deacon
2014-10-09 3:07 ` zhangzhiqiang
2014-10-09 3:41 ` gregkh
2014-10-09 7:13 ` zhangzhiqiang
2014-10-09 13:51 ` gregkh
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=20141008133147.GC5119@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Mark.Rutland@arm.com \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.org \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.com \
--cc=zhangzhiqiang.zhang@huawei.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).