[pypy-dev] Where should I look then !

[Shubha Ramani]

Armin I don't blame you for being upset with me. I'm sorry...I will lay low and dive deep into the pointers you've just nowmentioned in this email. I'm sorry, I didn't know about the August Vtune thread.Please accept my apologies.
Shubha 

    On Monday, December 12, 2016 11:11 AM, Armin Rigo <armin.rigo at gmail.com> wrote:
 

 Hi Shubha,

Sorry, you are asking many questions and I think you are not carefully
reading the answers.  Similarly, you are insisting that you've read
*all* the docs---which would be good, except that at the same time
some of yours questions have clear answers in the docs.

About your precise question: you should re-read some past answers,
e.g. Richard's December 9th, and then look in the source code how the
vmprof integration is done through RPython.  You might also be
interested in the pypy-dev thread from August about VTune, which
contains the answers to similar questions asked by other Intel people
at the time.

In the source code, all relevant places can be found from the
high-level pypy.module._vmprof, to the RPython-level
rpython.rlib.rvmprof; and x86.assembler._call_header_vmprof() which
generates in the assembler frames some structure with
VMPROF_JITTED_TAG, which is read by logic in rpython.rlib.rvmprof.  In
general, grepping for "vmprof" or "rvmprof" throughout the source code
of RPython is a good start.

I will now assume that you have read the answer above and actually
seriously dig into the various parts I mention, before asking more
questions.  Of course, you can keep asking anyway, but you need to
accept that we may not have the time and energy to keep answering you.
Asking a deluge of questions and then pressuring to get prompt
answers, that is the perfect way to get ignored in the open source
world---nobody *has* to answer you.

Also, I have nothing against helping someone building VTune support
inside PyPy, but if you read the August thread I mentioned above you'd
understand that I see VTune in a negative light right now: it pretends
to be more open-source-friendly that it is.  As far as I am concerned,
I am helping you build support specifically for an Intel commercial
product, and I am doing that without getting paid.  I am fine with
doing that to some extend, but it is an unstable situation.


A bientôt,

Armin.

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20161212/b28cd224/attachment.html>