From: Yeh, J. <jas...@am...> - 2006-02-01 20:08:10
|
John,=20 Some questions arise after re-reading your comment on the prototype of the API library. This email is referring to John's email with the link below: http://marc.theaimsgroup.com/?l=3Doprofile-list&m=3D113858341228548&w=3D2= John's original comments are in quotes. 1. "We need a utility function to enumerate the available sessions". opreport uses user specified sessions if specified, and the current session if none is specified. Do you suggest that the API look for the session in addition to the current capability of opreport? 2. "How do I find out the events available, how do I restrict to just those I'm intereste in?" The API can generate a dummy spec file to sweep all the sample files when users of API ask for available events, and return iterators t o the event. Should we provide similar function for cpu, tgid, tid, image or should we keep it simple and limit this function to just event? On a separate but related issue, what would be a better way to set profile specifications? Pass one structure with version number and all specification, or have many set_profile_specification() functions. regards, Jason |