From: Zhengyu Shen <zhengyu.shen@nxp.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Zhi Li <lznuaa@gmail.com>,
Frank Li <frank.li@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
kernel list <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>
Subject: RE: [PATCH v3] Added perf functionality to mmdc driver
Date: Wed, 31 Aug 2016 13:46:55 +0000 [thread overview]
Message-ID: <AM3PR04MB1426758359C2B769A28C3B849FE30@AM3PR04MB1426.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20160831102937.GC4783@leverpostej>
> > Mmdc was only responsible for one crash which I fixed (had to remove
> > the event from the pmu properly).
>
> Ok. I take it that there will be a v4 appearing shortly with that fix?
Hopefully I'll get that out by the end of today.
> Crashes are very bad. Do you have any logs from those crashes in other
> drivers that you can share?
It seems my kernel source was out of date, updating it seems to have fixed
The issue.
next prev parent reply other threads:[~2016-08-31 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 19:42 [PATCH v3] Added perf functionality to mmdc driver Zhengyu Shen
2016-08-29 16:06 ` Zhi Li
2016-08-30 11:43 ` Shawn Guo
2016-08-30 12:54 ` Mark Rutland
2016-08-30 20:01 ` Zhengyu Shen
2016-08-31 10:30 ` Mark Rutland
2016-08-31 13:46 ` Zhengyu Shen [this message]
2016-08-30 14:06 ` Shawn Guo
2016-08-31 13:08 ` Suzuki K Poulose
2016-08-31 16:20 ` Suzuki K Poulose
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=AM3PR04MB1426758359C2B769A28C3B849FE30@AM3PR04MB1426.eurprd04.prod.outlook.com \
--to=zhengyu.shen@nxp.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=frank.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shawnguo@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).