From: David Daney <david.s.daney@gmail.com>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>, ralf@linux-mips.org
Cc: David Daney <david.daney@cavium.com>,
linux-mips@linux-mips.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH v5 4/5] MIPS: perf: Add support for 64-bit perf counters.
Date: Sat, 24 Sep 2011 13:57:40 -0700 [thread overview]
Message-ID: <4E7E4444.4010706@gmail.com> (raw)
In-Reply-To: <CAOfQC98YwVoFWz+ZYv5JYCPG=NhzoeMKy70oE7aJbwAB+yZ6gA@mail.gmail.com>
On 09/23/2011 07:54 PM, Deng-Cheng Zhu wrote:
> 2011/9/23 David Daney<david.daney@cavium.com>:
>> The hard coded constants are moved to struct mips_pmu. All counter
>> register access move to the read_counter and write_counter function
>> pointers, which are set to either 32-bit or 64-bit access methods at
>> initialization time.
>>
>> Many of the function pointers in struct mips_pmu were not needed as
>> there was only a single implementation, these were removed.
>>
>> I couldn't figure out what made struct cpu_hw_events.msbs[] at all
>> useful, so I removed it too.
> The idea behind msbs is to simulate 32-bit counters based on the fact
> of MIPS using the MSB to trigger the overflow interrupt. By doing this, the
> average length of the overflow ISR can be shorter in the case of event
> period is bigger than 0x80000000.
It doesn't make the maximum overflow period any shorter. It just hides
it from the perf core, which is perfectly capable of handling the
shorter maximum overflow period.
> Also, it simplifies counter value related
> algorithms in the code
Have you looked at the code? It in no way simplifies things. The patch
removes 80 lines of code while maintaining 32-bit counter support *and*
adding 64-bit support.
> - most of other architectures have 32-bit counters
> instead of 31-bit. In addition, taking over those bugfixes can be easier as
> a concequence.
Not the Linux way. If there are bugs in the perf core we fix them, we
don't work around them in archecture specific code.
David Daney
next prev parent reply other threads:[~2011-09-24 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:26 [PATCH v5 0/5] MIPS: perf: Add support for 64-bit MIPS hardware counters David Daney
2011-09-22 17:26 ` [PATCH v5 1/5] MIPS: Add accessor macros for 64-bit performance counter registers David Daney
2011-09-24 0:19 ` Ralf Baechle
2011-09-22 17:26 ` [PATCH 2/2] MIPS: Add probes for more Octeon II CPUs David Daney
2011-09-22 17:30 ` David Daney
2011-09-22 17:26 ` [PATCH v5 3/5] MIPS: perf: Reorganize contents of perf support files David Daney
2011-09-24 0:19 ` Ralf Baechle
2011-09-24 2:50 ` Deng-Cheng Zhu
2011-09-24 20:44 ` David Daney
2011-09-26 9:12 ` Deng-Cheng Zhu
2011-09-22 17:26 ` [PATCH v5 4/5] MIPS: perf: Add support for 64-bit perf counters David Daney
2011-09-24 0:20 ` Ralf Baechle
2011-09-24 2:54 ` Deng-Cheng Zhu
2011-09-24 20:57 ` David Daney [this message]
2011-09-26 9:07 ` Deng-Cheng Zhu
2011-09-22 17:26 ` [PATCH v5 5/5] MIPS: perf: Add Octeon support for hardware perf David Daney
2011-09-24 0:20 ` Ralf Baechle
2011-09-22 17:32 ` [PATCH v5 2/5] MIPS: perf: Cleanup formatting in arch/mips/kernel/perf_event.c David Daney
2011-09-24 0:19 ` Ralf Baechle
2011-09-24 2:48 ` Deng-Cheng Zhu
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=4E7E4444.4010706@gmail.com \
--to=david.s.daney@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=david.daney@cavium.com \
--cc=dengcheng.zhu@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.