From: William Cohen <wcohen@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Vincent Guittot <vincent.guittot@linaro.org>,
anmar.oueja@linaro.org, Arnd Bergmann <arnd@arndb.de>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dcookies: Make dcookies depend on CONFIG_OPROFILE
Date: Wed, 28 Oct 2020 12:34:26 -0400 [thread overview]
Message-ID: <b3a8e2e8-350f-65af-9707-a6d847352f8e@redhat.com> (raw)
In-Reply-To: <CAHk-=whw9t3ZtV8iA2SJWYQS1VOJuS14P_qhj3v5-9PCBmGQww@mail.gmail.com>
On 10/27/20 12:54 PM, Linus Torvalds wrote:
> On Tue, Oct 27, 2020 at 1:52 AM Christoph Hellwig <hch@infradead.org> wrote:
>>
>> Is it time to deprecate and eventually remove oprofile while we're at
>> it?
>
> I think it's well past time.
>
> I think the user-space "oprofile" program doesn't actually use the
> legacy kernel code any more, and hasn't for a long time.
>
> But I might be wrong. Adding William Cohen to the cc, since he seems
> to still maintain it to make sure it builds etc.
>
> Linus
>
Hi,
Yes, current OProfile code uses the existing linux perf infrastructure and doesn't use the old oprofile kernel code. I have thought about removing that old oprofile driver code from kernel, but have not submitted patches for it. I would be fine with eliminating that code from the kernel.
-Will
next prev parent reply other threads:[~2020-10-29 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 11:01 [PATCH] dcookies: Make dcookies depend on CONFIG_OPROFILE Viresh Kumar
2020-10-27 8:51 ` Christoph Hellwig
2020-10-27 16:54 ` Linus Torvalds
2020-10-28 16:34 ` William Cohen [this message]
2020-10-28 18:01 ` Arnd Bergmann
2020-12-17 21:15 ` Linus Torvalds
2020-11-24 6:33 ` Viresh Kumar
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=b3a8e2e8-350f-65af-9707-a6d847352f8e@redhat.com \
--to=wcohen@redhat.com \
--cc=anmar.oueja@linaro.org \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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).