Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MICA counters for specific code block #7

Open
rjfnobre opened this issue Nov 16, 2016 · 2 comments
Open

MICA counters for specific code block #7

rjfnobre opened this issue Nov 16, 2016 · 2 comments

Comments

@rjfnobre
Copy link

Is it possible to make MICA/PIN to measure between A and B?

In the following example what would I have to do (in terms of code instrumentation or parameters passed to MICA) so that the MICA counters would only be incremented for CODE BLOCK 2?

int main() {

// CODE BLOCK 1
// start measuring
// CODE BLOCK 2
// end measurement
// CODE BLOCK 3

}

@boegel
Copy link
Owner

boegel commented Nov 16, 2016

Last time I used PIN was ages ago, but I think you can selectively enable instrumentation by injecting some PIN methods... @amirjamez?

@amirjamez
Copy link
Collaborator

Hi,

Sorry for the sluggish reply.

I haven't done this myself, but i believe you can use PIN's instrumentation
features.

How about this?
http://reverseengineering.stackexchange.com/questions/8884/how-can-i-remove-a-bbl-instrumentation-call-at-a-specific-address-in-pin#

Nevertheless, you should track the number of times the instrumentation is
done, depending on the number of invocation of the block (calls) it has and
I believe it might be a little noisy. As another workaround, you can make
each of those blocks an independent executable object and use the native
MICA feature to instrument the binary at run-time.

Hope either of them work.

-Amir

On Wed, Nov 16, 2016 at 7:15 PM, Kenneth Hoste [email protected]
wrote:

Last time I used PIN was ages ago, but I think you can selectively
enable instrumentation by injecting some PIN methods... @amirjamez
https://github.com/amirjamez?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIglHsRGpx-9OJ2T4aPXTKnJG8XrX4QRks5q-yUNgaJpZM4K0AZl
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants