From: Robert Richter <rric@kernel.org>
To: Matt Redfearn <matt.redfearn@mips.com>
Cc: James Hogan <jhogan@kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Huacai Chen <chenhc@lemote.com>,
linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
oprofile-list@lists.sf.net
Subject: Re: [RFC PATCH] MIPS: Oprofile: Drop support
Date: Fri, 4 May 2018 12:26:01 +0200 [thread overview]
Message-ID: <20180504102600.GD4493@rric.localdomain> (raw)
In-Reply-To: <dd951d1e-206d-78dd-49ae-3a16cad9ebcc@mips.com>
On 04.05.18 10:54:32, Matt Redfearn wrote:
> perf is available for MIPS and supports many more CPU types than oprofile.
> oprofile userspace seemingly has been broken since 1.0.0 - removing oprofile
> support from the MIPS kernel would not break it more thatn it already is,
What do you mean with "oprofile is broken"? It looks like you modified
Kconfig to enable oprofile and perf in parallel, which is not intended
to work. Have you tried a kernel with oprofile disabled and perf
enabled?
As said, oprofile version 0.9.x is still available for cpus that do
not support perf. What is the breakage?
Thanks,
-Robert
next prev parent reply other threads:[~2018-05-04 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 12:55 Matt Redfearn
2018-04-24 13:05 ` James Hogan
2018-04-24 13:15 ` Matt Redfearn
2018-05-04 9:30 ` Robert Richter
2018-05-04 9:54 ` Matt Redfearn
2018-05-04 10:26 ` Robert Richter [this message]
2018-05-04 11:03 ` Matt Redfearn
2018-05-04 12:27 ` Robert Richter
2018-05-04 12:56 ` Ralf Baechle
2018-05-04 12:59 ` Matt Redfearn
2018-04-24 13:59 ` Christoph Hellwig
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=20180504102600.GD4493@rric.localdomain \
--to=rric@kernel.org \
--cc=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=matt.redfearn@mips.com \
--cc=oprofile-list@lists.sf.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®