From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control
Date: Thu, 5 Dec 2013 15:26:38 -0800 [thread overview]
Message-ID: <20131205232638.GC28396@kroah.com> (raw)
In-Reply-To: <52A101F8.3060104@codeaurora.org>
On Thu, Dec 05, 2013 at 05:45:12PM -0500, Christopher Covington wrote:
> On 12/05/2013 03:16 PM, Greg Kroah-Hartman wrote:
> > On Thu, Dec 05, 2013 at 03:12:50PM -0500, Christopher Covington wrote:
> [...]
> > And adding new features to code that is "dead" and should probably be
> > removed isn't a good idea, as I'm sure you can understand.
>
> I would consider feature additions to be a sign of life. Maybe the
> architecture or user interface isn't ideal, but would you suggest just as
> quickly for media codec or cryptography hardware support be removed?
No, but I would ask that they be moved to use the same userspace api
for the same functionality, and not create custom ones just because
"they can".
> > How much work is it to incorportate ETM into the perf framework? Don't
> > you think that this is a better thing to do overall, instead of having
> > duplicating interfaces for the same thing?
>
> I'm not familiar enough with the ETM hardware (and the ETB, the buffer where
> the data is stored) and driver to say. One factor may be whether the perf
> events framework would need to be extended for complete functionality or could
> be used as-is.
How about moving this conversation to the proper mailing list for this
type of thing then?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: "Adrien Vergé" <adrienverge@gmail.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Will Deacon" <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
"Ben Dooks" <ben.dooks@codethink.co.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
linux-arm-kernel@lists.infradead.org,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
Subject: Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control
Date: Thu, 5 Dec 2013 15:26:38 -0800 [thread overview]
Message-ID: <20131205232638.GC28396@kroah.com> (raw)
In-Reply-To: <52A101F8.3060104@codeaurora.org>
On Thu, Dec 05, 2013 at 05:45:12PM -0500, Christopher Covington wrote:
> On 12/05/2013 03:16 PM, Greg Kroah-Hartman wrote:
> > On Thu, Dec 05, 2013 at 03:12:50PM -0500, Christopher Covington wrote:
> [...]
> > And adding new features to code that is "dead" and should probably be
> > removed isn't a good idea, as I'm sure you can understand.
>
> I would consider feature additions to be a sign of life. Maybe the
> architecture or user interface isn't ideal, but would you suggest just as
> quickly for media codec or cryptography hardware support be removed?
No, but I would ask that they be moved to use the same userspace api
for the same functionality, and not create custom ones just because
"they can".
> > How much work is it to incorportate ETM into the perf framework? Don't
> > you think that this is a better thing to do overall, instead of having
> > duplicating interfaces for the same thing?
>
> I'm not familiar enough with the ETM hardware (and the ETB, the buffer where
> the data is stored) and driver to say. One factor may be whether the perf
> events framework would need to be extended for complete functionality or could
> be used as-is.
How about moving this conversation to the proper mailing list for this
type of thing then?
thanks,
greg k-h
next prev parent reply other threads:[~2013-12-05 23:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 4:39 [PATCH 0/3] ARM Coresight: Enhance ETM tracing control Adrien Vergé
2013-12-04 4:39 ` Adrien Vergé
2013-12-04 7:04 ` Greg Kroah-Hartman
2013-12-04 7:04 ` Greg Kroah-Hartman
2013-12-04 16:52 ` Adrien Vergé
2013-12-04 16:52 ` Adrien Vergé
2013-12-04 17:07 ` Greg Kroah-Hartman
2013-12-04 17:07 ` Greg Kroah-Hartman
2013-12-04 21:12 ` Adrien Vergé
2013-12-04 21:12 ` Adrien Vergé
2013-12-04 23:02 ` Greg Kroah-Hartman
2013-12-04 23:02 ` Greg Kroah-Hartman
2013-12-05 3:49 ` Adrien Vergé
2013-12-05 3:49 ` Adrien Vergé
2013-12-05 4:01 ` Greg Kroah-Hartman
2013-12-05 4:01 ` Greg Kroah-Hartman
2013-12-05 20:12 ` Christopher Covington
2013-12-05 20:12 ` Christopher Covington
2013-12-05 20:16 ` Greg Kroah-Hartman
2013-12-05 20:16 ` Greg Kroah-Hartman
2013-12-05 22:45 ` Christopher Covington
2013-12-05 22:45 ` Christopher Covington
2013-12-05 23:26 ` Greg Kroah-Hartman [this message]
2013-12-05 23:26 ` Greg Kroah-Hartman
2013-12-05 23:54 ` Adrien Vergé
2013-12-05 23:54 ` Adrien Vergé
2013-12-06 0:06 ` Greg Kroah-Hartman
2013-12-06 0:06 ` Greg Kroah-Hartman
2013-12-06 0:23 ` Russell King - ARM Linux
2013-12-06 0:23 ` Russell King - ARM Linux
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=20131205232638.GC28396@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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.