From: Ralf Baechle <ralf@linux-mips.org>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>,
Matt Fleming <matt@console-pimps.org>
Cc: linux-mips@linux-mips.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@elte.hu, acme@redhat.com,
jamie.iles@picochip.com
Subject: Re: [PATCH v7 2/6] MIPS/Oprofile: extract PMU defines for sharing
Date: Tue, 5 Oct 2010 09:08:22 +0100 [thread overview]
Message-ID: <20101005080822.GA13217@linux-mips.org> (raw)
In-Reply-To: <1285837760-10362-3-git-send-email-dengcheng.zhu@gmail.com>
On Thu, Sep 30, 2010 at 05:09:16PM +0800, Deng-Cheng Zhu wrote:
> Moving performance counter/control defines into a single header file, so
> that software using the MIPS PMU can share the code.
Matt Fleming has patches pending that reimplement oprofile as a layer
based on top of perf. All things considered I'd be happier if you just
copied whatever perf needs from oprofile rather than sharing it.
Ralf
next prev parent reply other threads:[~2010-10-05 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 9:09 [PATCH v7 0/6] MIPS performance event support v7 Deng-Cheng Zhu
2010-09-30 9:09 ` [PATCH v7 1/6] MIPS: define local_xchg from xchg_local to atomic_long_xchg Deng-Cheng Zhu
2010-09-30 9:09 ` [PATCH v7 2/6] MIPS/Oprofile: extract PMU defines for sharing Deng-Cheng Zhu
2010-10-05 8:08 ` Ralf Baechle [this message]
2010-09-30 9:09 ` [PATCH v7 3/6] MIPS: add support for software performance events Deng-Cheng Zhu
2010-09-30 9:09 ` [PATCH v7 4/6] MIPS: add support for hardware performance events (skeleton) Deng-Cheng Zhu
2010-09-30 9:09 ` [PATCH v7 5/6] MIPS/Perf-events: add callchain support Deng-Cheng Zhu
2010-09-30 9:09 ` [PATCH v7 6/6] MIPS: add support for hardware performance events (mipsxx) Deng-Cheng Zhu
2010-09-30 9:26 ` Ingo Molnar
2010-09-30 13:39 ` Deng-Cheng Zhu
2010-10-04 19:33 ` [PATCH v7 0/6] MIPS performance event support v7 Matt Fleming
2010-10-05 0:06 ` Deng-Cheng Zhu
2010-10-05 7:52 ` Matt Fleming
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=20101005080822.GA13217@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dengcheng.zhu@gmail.com \
--cc=jamie.iles@picochip.com \
--cc=linux-mips@linux-mips.org \
--cc=matt@console-pimps.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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