Perf Monitoring for rdtsc dynamically












0














Is there a way to monitor for assembly instructions in "real-time" dynamically using perf?
I have seen that if I use perf record /perf top and then click on the recorded functions, I see the assembly instructions, but can I directly monitor specific assembly instructions e.g., rdtsc or clflush e.g., how often they are called by a process within certain period using perf?



I am using Debian 9 on Skylake and also on Haswell.



sudo uname -a Linux bla 4.9.0-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux



sudo /proc/config.gz returns command not found Any help/ideas are appreciated.






assembly profiling monitoring perf rdtsc







share|improve this question






















  • If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
    – Margaret Bloom
    Nov 20 at 10:04






  • 1




    sounds very much like this question
    – Zulan
    Nov 20 at 11:25










  • Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
    – assembly_question
    Nov 20 at 11:47










  • There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
    – Peter Cordes
    Nov 20 at 17:26










  • No, you can't do that using perf.
    – Hadi Brais
    Nov 20 at 19:34
















0














Is there a way to monitor for assembly instructions in "real-time" dynamically using perf?
I have seen that if I use perf record /perf top and then click on the recorded functions, I see the assembly instructions, but can I directly monitor specific assembly instructions e.g., rdtsc or clflush e.g., how often they are called by a process within certain period using perf?



I am using Debian 9 on Skylake and also on Haswell.



sudo uname -a Linux bla 4.9.0-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux



sudo /proc/config.gz returns command not found Any help/ideas are appreciated.






assembly profiling monitoring perf rdtsc







share|improve this question






















  • If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
    – Margaret Bloom
    Nov 20 at 10:04






  • 1




    sounds very much like this question
    – Zulan
    Nov 20 at 11:25










  • Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
    – assembly_question
    Nov 20 at 11:47










  • There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
    – Peter Cordes
    Nov 20 at 17:26










  • No, you can't do that using perf.
    – Hadi Brais
    Nov 20 at 19:34














0












0








0







Is there a way to monitor for assembly instructions in "real-time" dynamically using perf?
I have seen that if I use perf record /perf top and then click on the recorded functions, I see the assembly instructions, but can I directly monitor specific assembly instructions e.g., rdtsc or clflush e.g., how often they are called by a process within certain period using perf?



I am using Debian 9 on Skylake and also on Haswell.



sudo uname -a Linux bla 4.9.0-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux



sudo /proc/config.gz returns command not found Any help/ideas are appreciated.






assembly profiling monitoring perf rdtsc







share|improve this question













Is there a way to monitor for assembly instructions in "real-time" dynamically using perf?
I have seen that if I use perf record /perf top and then click on the recorded functions, I see the assembly instructions, but can I directly monitor specific assembly instructions e.g., rdtsc or clflush e.g., how often they are called by a process within certain period using perf?



I am using Debian 9 on Skylake and also on Haswell.



sudo uname -a Linux bla 4.9.0-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux



sudo /proc/config.gz returns command not found Any help/ideas are appreciated.






assembly profiling monitoring perf rdtsc




assembly profiling monitoring perf rdtsc






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 9:56









assembly_question

92




92












  • If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
    – Margaret Bloom
    Nov 20 at 10:04






  • 1




    sounds very much like this question
    – Zulan
    Nov 20 at 11:25










  • Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
    – assembly_question
    Nov 20 at 11:47










  • There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
    – Peter Cordes
    Nov 20 at 17:26










  • No, you can't do that using perf.
    – Hadi Brais
    Nov 20 at 19:34


















  • If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
    – Margaret Bloom
    Nov 20 at 10:04






  • 1




    sounds very much like this question
    – Zulan
    Nov 20 at 11:25










  • Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
    – assembly_question
    Nov 20 at 11:47










  • There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
    – Peter Cordes
    Nov 20 at 17:26










  • No, you can't do that using perf.
    – Hadi Brais
    Nov 20 at 19:34
















If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
– Margaret Bloom
Nov 20 at 10:04




If you want to limit your self to a process, use a BDI tool (like frida, dynamoRio or even rr). System-wide I don't think it's possible with reasonable performance.
– Margaret Bloom
Nov 20 at 10:04




1




1




sounds very much like this question
– Zulan
Nov 20 at 11:25




sounds very much like this question
– Zulan
Nov 20 at 11:25












Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
– assembly_question
Nov 20 at 11:47




Thanks for the answers. However, I do not have a specific process and do not want to do binary instrumentation. If I use performance counters monitoring e.g., with perf I can see the rdtsc during runtime, but only if I manually click on the function that calls it. That is why I was thinking that there might be a way.. setting some registers or whatever
– assembly_question
Nov 20 at 11:47












There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
– Peter Cordes
Nov 20 at 17:26




There aren't perf events for most specific instructions. For division, there's arith.divider_active. You might find microcoded instructions with idq.ms_cycles, but that isn't specific to rdtsc or clflush. (I'm not sure clflush is more than 4 uops, though.)
– Peter Cordes
Nov 20 at 17:26












No, you can't do that using perf.
– Hadi Brais
Nov 20 at 19:34




No, you can't do that using perf.
– Hadi Brais
Nov 20 at 19:34












1 Answer
1






active

oldest

votes


















1














Yes, you could certainly build something that dynamically samples instructions running on the host.



The basic idea is to periodically sample the processes you are interested in (which could be "all of them"), and examine the area around the sampled instruction pointer to determine the instructions that must have been executed for such a sample to have existed: for example, by disassembling until the next conditional branch, or perhaps just until the end of the basic block.



Doing this repeatedly you'll get a histogram of executed instructions, and you can then estimate how often rdtsc or any other instruction of interest is operating.



This isn't even actually all that difficult: most of the logic already exists in perf top, perf record and perf report: just combine the sampling code from perf top with the annotation code from perf top and/or perf report as described above. Perhaps you can even do it after the fact: use perf record --all-cpus to gather the samples and then run perf script or otherwise parse the file to monitor the instructions.



Each sample will only give you a small window of executed instructions, so if you need to catch the occasional rdtsc accurately, this won't work at all.



You could extend the "window" for each sample by exploiting the "last branch record" feature to essentially go back in time based on the most recent branches, and disassemble all those basic blocks, which would extend your coverage per sample by a lot.






share|improve this answer





















  • Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
    – assembly_question
    Nov 30 at 13:41













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390392%2fperf-monitoring-for-rdtsc-dynamically%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Yes, you could certainly build something that dynamically samples instructions running on the host.



The basic idea is to periodically sample the processes you are interested in (which could be "all of them"), and examine the area around the sampled instruction pointer to determine the instructions that must have been executed for such a sample to have existed: for example, by disassembling until the next conditional branch, or perhaps just until the end of the basic block.



Doing this repeatedly you'll get a histogram of executed instructions, and you can then estimate how often rdtsc or any other instruction of interest is operating.



This isn't even actually all that difficult: most of the logic already exists in perf top, perf record and perf report: just combine the sampling code from perf top with the annotation code from perf top and/or perf report as described above. Perhaps you can even do it after the fact: use perf record --all-cpus to gather the samples and then run perf script or otherwise parse the file to monitor the instructions.



Each sample will only give you a small window of executed instructions, so if you need to catch the occasional rdtsc accurately, this won't work at all.



You could extend the "window" for each sample by exploiting the "last branch record" feature to essentially go back in time based on the most recent branches, and disassemble all those basic blocks, which would extend your coverage per sample by a lot.






share|improve this answer





















  • Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
    – assembly_question
    Nov 30 at 13:41


















1














Yes, you could certainly build something that dynamically samples instructions running on the host.



The basic idea is to periodically sample the processes you are interested in (which could be "all of them"), and examine the area around the sampled instruction pointer to determine the instructions that must have been executed for such a sample to have existed: for example, by disassembling until the next conditional branch, or perhaps just until the end of the basic block.



Doing this repeatedly you'll get a histogram of executed instructions, and you can then estimate how often rdtsc or any other instruction of interest is operating.



This isn't even actually all that difficult: most of the logic already exists in perf top, perf record and perf report: just combine the sampling code from perf top with the annotation code from perf top and/or perf report as described above. Perhaps you can even do it after the fact: use perf record --all-cpus to gather the samples and then run perf script or otherwise parse the file to monitor the instructions.



Each sample will only give you a small window of executed instructions, so if you need to catch the occasional rdtsc accurately, this won't work at all.



You could extend the "window" for each sample by exploiting the "last branch record" feature to essentially go back in time based on the most recent branches, and disassemble all those basic blocks, which would extend your coverage per sample by a lot.






share|improve this answer





















  • Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
    – assembly_question
    Nov 30 at 13:41
















1












1








1






Yes, you could certainly build something that dynamically samples instructions running on the host.



The basic idea is to periodically sample the processes you are interested in (which could be "all of them"), and examine the area around the sampled instruction pointer to determine the instructions that must have been executed for such a sample to have existed: for example, by disassembling until the next conditional branch, or perhaps just until the end of the basic block.



Doing this repeatedly you'll get a histogram of executed instructions, and you can then estimate how often rdtsc or any other instruction of interest is operating.



This isn't even actually all that difficult: most of the logic already exists in perf top, perf record and perf report: just combine the sampling code from perf top with the annotation code from perf top and/or perf report as described above. Perhaps you can even do it after the fact: use perf record --all-cpus to gather the samples and then run perf script or otherwise parse the file to monitor the instructions.



Each sample will only give you a small window of executed instructions, so if you need to catch the occasional rdtsc accurately, this won't work at all.



You could extend the "window" for each sample by exploiting the "last branch record" feature to essentially go back in time based on the most recent branches, and disassemble all those basic blocks, which would extend your coverage per sample by a lot.






share|improve this answer












Yes, you could certainly build something that dynamically samples instructions running on the host.



The basic idea is to periodically sample the processes you are interested in (which could be "all of them"), and examine the area around the sampled instruction pointer to determine the instructions that must have been executed for such a sample to have existed: for example, by disassembling until the next conditional branch, or perhaps just until the end of the basic block.



Doing this repeatedly you'll get a histogram of executed instructions, and you can then estimate how often rdtsc or any other instruction of interest is operating.



This isn't even actually all that difficult: most of the logic already exists in perf top, perf record and perf report: just combine the sampling code from perf top with the annotation code from perf top and/or perf report as described above. Perhaps you can even do it after the fact: use perf record --all-cpus to gather the samples and then run perf script or otherwise parse the file to monitor the instructions.



Each sample will only give you a small window of executed instructions, so if you need to catch the occasional rdtsc accurately, this won't work at all.



You could extend the "window" for each sample by exploiting the "last branch record" feature to essentially go back in time based on the most recent branches, and disassemble all those basic blocks, which would extend your coverage per sample by a lot.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 at 3:33









BeeOnRope

24.8k875170




24.8k875170












  • Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
    – assembly_question
    Nov 30 at 13:41




















  • Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
    – assembly_question
    Nov 30 at 13:41


















Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
– assembly_question
Nov 30 at 13:41






Hi, thanks for the answer! The thing is that I do not know how to get to this instruction to count it. I see that rdtsc has been used if I use perf top and click on the process that has called her and see the corresponding assembly code and there I see the instruction, but if I want to derive statistics for that with the --all-cpus option, I do not know what should I parse. With the perf script it was not showing it directly. Could you give me a tip about that?
– assembly_question
Nov 30 at 13:41




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390392%2fperf-monitoring-for-rdtsc-dynamically%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Costa Masnaga

Image
.mw-parser-output .avviso .mbox-text-div>div,.mw-parser-output .avviso .mbox-text-full-div>div{font-size:90%}.mw-parser-output .avviso .mbox-image div{width:52px}.mw-parser-output .avviso .mbox-text-full-div .hide-when-compact{display:block} Questa voce o sezione sull'argomento Lombardia non cita le fonti necessarie o quelle presenti sono insufficienti . Puoi migliorare questa voce aggiungendo citazioni da fonti attendibili secondo le linee guida sull'uso delle fonti. Segui i suggerimenti del progetto di riferimento. Costa Masnaga comune Localizzazione Stato   Italia Regione Lombardia Provincia Lecco Amministrazione Sindaco Sabina Panzeri (Al centro il cittadino) dall'08/06/2009 Territorio Coordinate 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Coordinate: 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Altitudine 318 m s.l.m...
Read more

Fotorealismo

Image
Guerrino Boatto, Venice's St. Barnaba Church and canal Il fotorealismo è un genere di pittura basato sull'uso di una o più fotografie dalle quali l'artista prende le informazioni necessarie da utilizzare poi nel processo della creazione dell'opera, in genere ad olio o ad acrilico, al fine di avere un aspetto finale il più simile possibile alla fotografia. Indice 1 Storia 2 Lista dei fotorealisti 3 Note 4 Voci correlate 5 Altri progetti Storia | Il fotorealismo è un movimento che nasce negli Stati Uniti d'America alla fine degli anni sessanta [1] sulla scia della Pop Art [2] [3] [4] , e insieme condividono il carattere reazionario verso la travolgente ascesa dei media, che alla metà del ventesimo secolo si trasforma in un fenomeno di massa talmente imponente da minacciare il valore dell'immagine nell'arte. [5] [6] Ne consegue così che, colto il gesto d'inizio che fu della Pop Art, i fotorealisti aprono ad un ...
Read more

Sidney Franklin

Image
Questa voce sull'argomento registi statunitensi è solo un abbozzo . Contribuisci a migliorarla secondo le convenzioni di Wikipedia. Sidney Franklin, foto di Carl Van Vechten Oscar alla memoria Irving G. Thalberg 1943 Sidney Franklin , all'anagrafe Sidney Arnold Franklin , (San Francisco, 21 marzo 1893 – Santa Monica, 18 maggio 1972), è stato un regista, produttore cinematografico e attore statunitense. Il 20 giugno 1963, si sposò con l'attrice australiana Enid Bennett. Il matrimonio durò fino alla morte dell'attrice, il 14 maggio 1969 [1] Indice 1 Filmografia 1.1 Regista 1.2 Aiuto regia (parziale) 1.3 Produttore 1.4 Attore (parziale) 2 Note 3 Altri progetti 4 Collegamenti esterni Filmografia | Regista | The Baby , co-regia Chester M. Franklin (1915) The Rivals , co-regia Chester M. Franklin (1915) Little Dick's First Case , co-regia Chester M. Franklin (1915) Her Filmland Hero , co-...
Read more