Maybe it is not as simple.
I asked for a technical question for a real problem (Vtune is yet written, and obviously, not for me ;) ) and I just would like to help if I can. This is a way to acquire knowledge I think.
I know that this can be used for malicious software (viruses, trojans...) but it is not the case. I know for example, that the use of _syscall* is not recommended.... well but what if I want to use it to learn more about that? And it is widely known that the use of "goto" is not a good programming practice and the linux kernel uses it (for performance reasons, I think).
I only want to play with that profilers and try to make my own one in the same way (although maybe this is not the best approach).
Best regards
---------- Forwarded message ----------
From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Date: Jun 4, 2006 7:31 PM
Subject: Re: syscall nesting
To: Fernando Apesteguía <
fernando.apesteguia@xxxxxxxxx>
Cc: kernelnewbies@xxxxxxxxxxxx
On Sun, 2006-06-04 at 18:41 +0200, Fernando Apesteguía wrote:
> Hi,
> Any ideas?
yes.
Just don't add rogue system calls from modules.
It's as simple as that.
