From: Robert Richter <rric@kernel.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Tejun Heo <tj@kernel.org>,
oprofile-list@lists.sf.net, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
Andreas Arnez <arnez@linux.vnet.ibm.com>,
William Cohen <wcohen@redhat.com>
Subject: Re: [PATCH] s390/oprofile: Remove deprecated create_workqueue
Date: Mon, 13 Jun 2016 18:29:14 +0200 [thread overview]
Message-ID: <20160613162914.GK25086@rric.localdomain> (raw)
In-Reply-To: <20160609090056.GC3250@osiris>
Heiko,
On 09.06.16 11:00:56, Heiko Carstens wrote:
> However I'm wondering if we shouldn't simply remove at least the s390
> specific hwswampler code from the oprofile module. This would still leave
> the common code timer based sampling mode for oprofile working on s390.
>
> It looks like the oprofile user space utility nowadays (since 2012) uses
> the kernel perf interface instead of the oprofile interface anyway, if
> present. So the oprofile module itself doesn't seem to have too many users
> left.
>
> Any opinions?
yes, the kernel driver is not necessary for oprofile userland for a
while now. There is no ongoing development any longer, most patches
are due to changes in the kernel apis.
So if there is code that needs a larger rework due to other kernel
changes and there is no user anymore, I am fine with removing the code
instead of reworking it. I still would just keep existing code as long
as we can keep it unchanged (some like the lightwight of oprofile,
esp. in the embedded space). If there is a user of the code, a
Tested-by would be good for new code changes.
If there are users of the hwswampler, speak up now. Else, let's just
remove it.
-Robert
next prev parent reply other threads:[~2016-06-13 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 21:59 [PATCH] s390/oprofile: Remove deprecated create_workqueue Bhaktipriya Shridhar
2016-06-07 23:29 ` kbuild test robot
2016-06-09 9:00 ` Heiko Carstens
2016-06-13 16:29 ` Robert Richter [this message]
2016-06-13 20:44 ` William Cohen
2016-06-14 5:36 ` Heiko Carstens
2016-06-14 13:28 ` Robert Richter
2016-06-14 15:56 ` Heiko Carstens
2016-06-17 9:08 ` Hendrik Brueckner
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=20160613162914.GK25086@rric.localdomain \
--to=rric@kernel.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=bhaktipriya96@gmail.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=krebbel@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=schwidefsky@de.ibm.com \
--cc=tj@kernel.org \
--cc=wcohen@redhat.com \
/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