From: Zhi Li <lznuaa@gmail.com>
To: Tiberiu Breana <andrei-tiberiu.breana@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, 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>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
acme@kernel.org, alexander.shishkin@linux.intel.com,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 1/2] Fix mmdc_pmu_write_accesses event definition
Date: Tue, 14 Feb 2017 09:24:15 -0600 [thread overview]
Message-ID: <CAHrpEqQh9vTmiLdrDHsOeuJ37Kq2PUGEdO=t6RZkjMMpMRhbJw@mail.gmail.com> (raw)
In-Reply-To: <1487062873-27641-2-git-send-email-andrei-tiberiu.breana@nxp.com>
Subject should add prefix like:
ARM: imx: fix xxxx
best regards
Frank Li
On Tue, Feb 14, 2017 at 3:01 AM, Tiberiu Breana
<andrei-tiberiu.breana@nxp.com> wrote:
> Fixed an error in the "write-accesses" event definition.
>
> Signed-off-by: Tiberiu Breana <andrei-tiberiu.breana@nxp.com>
> ---
> arch/arm/mach-imx/mmdc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/mmdc.c b/arch/arm/mach-imx/mmdc.c
> index c03bf28..89a926f 100644
> --- a/arch/arm/mach-imx/mmdc.c
> +++ b/arch/arm/mach-imx/mmdc.c
> @@ -87,7 +87,7 @@ static DEFINE_IDA(mmdc_ida);
> PMU_EVENT_ATTR_STRING(total-cycles, mmdc_pmu_total_cycles, "event=0x00")
> PMU_EVENT_ATTR_STRING(busy-cycles, mmdc_pmu_busy_cycles, "event=0x01")
> PMU_EVENT_ATTR_STRING(read-accesses, mmdc_pmu_read_accesses, "event=0x02")
> -PMU_EVENT_ATTR_STRING(write-accesses, mmdc_pmu_write_accesses, "config=0x03")
> +PMU_EVENT_ATTR_STRING(write-accesses, mmdc_pmu_write_accesses, "event=0x03")
> PMU_EVENT_ATTR_STRING(read-bytes, mmdc_pmu_read_bytes, "event=0x04")
> PMU_EVENT_ATTR_STRING(read-bytes.unit, mmdc_pmu_read_bytes_unit, "MB");
> PMU_EVENT_ATTR_STRING(read-bytes.scale, mmdc_pmu_read_bytes_scale, "0.000001");
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-02-14 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 9:01 [PATCH 0/2] Add AXI address filter support for MMDC profiling Tiberiu Breana
2017-02-14 9:01 ` [PATCH 1/2] Fix mmdc_pmu_write_accesses event definition Tiberiu Breana
2017-02-14 15:24 ` Zhi Li [this message]
2017-02-14 9:01 ` [PATCH 2/2] Add AXI address filter support for MMDC profiling Tiberiu Breana
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='CAHrpEqQh9vTmiLdrDHsOeuJ37Kq2PUGEdO=t6RZkjMMpMRhbJw@mail.gmail.com' \
--to=lznuaa@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrei-tiberiu.breana@nxp.com \
--cc=frank.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).