From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: anyone including <linux/perf_counter.h>?
Date: Wed, 16 Dec 2009 10:01:39 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912161000130.7970@localhost> (raw)
In-Reply-To: <20091216145851.GM28962@bombadil.infradead.org>
On Wed, 16 Dec 2009, Kyle McMartin wrote:
> On Wed, Dec 16, 2009 at 09:56:47AM -0500, Robert P. J. Day wrote:
> > > See the comment at the top, it's being provided to provide the
> > > old names to userspace for a short time, now that the
> > > functionality has been renamed to perf_events.
> >
> > but if it's supposed to be providing info to user-space,
> > shouldn't it be *exported* to user space? it's not listed in
> > include/linux/Kbuild. or am i misunderstanding?
>
> No, you're quite correct, my guess would be that the original
> perf_counter.h header-y line was renamed to perf_event.h, and
> someone forgot to add a new one for the old header.
so i can submit a patch to do one of two things:
1) add it into Kbuild, since user-space needs it, or
2) delete it entirely since it's never been in user-space all
this time but no one seems to have missed it. :-)
thoughts? i'm fine either way.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-12-16 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 14:42 anyone including <linux/perf_counter.h>? Robert P. J. Day
2009-12-16 14:51 ` Kyle McMartin
2009-12-16 14:56 ` Robert P. J. Day
2009-12-16 14:58 ` Kyle McMartin
2009-12-16 15:01 ` Robert P. J. Day [this message]
2009-12-16 15:04 ` Kyle McMartin
2009-12-16 15:06 ` Robert P. J. Day
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=alpine.LFD.2.00.0912161000130.7970@localhost \
--to=rpjday@crashcourse.ca \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.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