From: David Gibson <david@gibson.dropbear.id.au>
To: eranian@gmail.com
Cc: linux-kernel@vger.kernel.org,
perfmon2-devel <perfmon2-devel@lists.sourceforge.net>
Subject: Re: perfmon3 interface overview
Date: Sat, 4 Oct 2008 16:05:06 +1000 [thread overview]
Message-ID: <20081004060506.GO30184@yookeroo.seuss> (raw)
In-Reply-To: <7c86c4470810030412l34d3dc13mef10c9320884d635@mail.gmail.com>
On Fri, Oct 03, 2008 at 01:12:09PM +0200, stephane eranian wrote:
> David,
> >> [snip]
> >> > III) attaching and detaching
> >> >
> >> > With v2.81:
> >> > int pfm_load_context(int fd, pfarg_load_t *load);
> >> > int pfm_unload_context(int fd);
> >> >
> >> > With v3.0:
> >> > int pfm_attach_session(int fd, int flags, int target);
> >> > int pfm_detach_session(int fd, int flags);
> >>
> >> Couldn't you get rid of one more syscall here by making detach a
> >> special case of attach with a special "null" value for target, or a
> >> special flag?
> >
> >
> > We could combine the two and use the flag field to indicate attach/detach.
> > The target is not a pointer but an int. Some people suggested I use an
> > unsigned long instead. In anycase, we could not use 0 to indicate "detach"
> > because CPU0 is a valid choice for system-wide. Thus we would have to
> > pick another value to mean "nothing", e.g, -1.
> >
> > > IV) starting and stopping
> > >
> > > With v2.81:
> > > int pfm_start(int fd, pfarg_start_t *st);
> > > int pfm_stop(int fd);
> > > int pfm_restart(int fd);
> > >
> > > With v3.0:
> > > int pfm_start_session(int fd, int flags);
> > > int pfm_stop_session(int fd, int flags);
> >
> >> Likewise, couldn't you cut this down by one more syscall by making it
> >> int pfm_set_session_state(int fd, int flags);
> >> and having a 'RUNNING' flag, which selects start or stop behaviour?
> >
> > That one we can certainly do. That's a good idea.
>
> Some more thoughts on this.
>
> If we wanted to go even further, we could combine start/stop, attach/detach
> into a single syscall:
Well, you could. But the attach/detach take a parameter which
start/stop don't, making it a less obvious merge to make.
> int pfm_control_session(int fd, int flags, int target);
> With flags:
> PFM_CTFL_START : start monitoring
> PFM_CTFL_STOP : stop monitoring
> PFM_CTFL_RESTART: resume after overflow notification
>
> PFM_CTFL_ATTACH: attach to thread or cpu designated by 'target'
> PFM_CTFL_DETACH: detach session
>
> But then, this is a form of ioctl() which people don't like....
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-10-04 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c86c4470809231432j4231cfa4g7dd158a7fe9c9277@mail.gmail.com>
2008-09-25 21:48 ` stephane eranian
2008-10-03 6:17 ` David Gibson
[not found] ` <7c86c4470810030354x6984372akfe18761da7504a0c@mail.gmail.com>
2008-10-03 10:58 ` stephane eranian
2008-10-03 11:12 ` stephane eranian
2008-10-04 6:05 ` David Gibson [this message]
2008-10-04 7:20 ` stephane eranian
2008-10-05 5:44 ` David Gibson
2008-10-05 5:53 ` David Gibson
2008-10-05 21:23 ` stephane eranian
2008-10-07 3:56 ` David Gibson
2008-10-07 9:46 ` stephane eranian
2008-10-08 0:53 ` David Gibson
2008-10-08 10:09 ` stephane eranian
2008-10-07 9:24 ` [perfmon2] " Arnd Bergmann
2008-10-03 14:44 ` stephane eranian
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=20081004060506.GO30184@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perfmon2-devel@lists.sourceforge.net \
/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®