Displaying 3 results from an estimated 3 matches for "bwql".
Did you mean:
bwl
2013 Oct 19
0
MmioTrace: Using the Instruction Decoder, etc.
...n that (KernelStrider has to deal with
register allocation, relocations and other things) but the principle is as
I described.
The function calls are processed too so that we can set our own handlers to
execute at the beginning of a function and right before its exit.
Yes, the functions like read[bwql]() and write[bwlq]() are usually inline
but they pose no problem: on x86 they compile to ordinary MOV instructions
and the like which are handled as I described above.
The instrumented code will access the ioremapped area the same way as the
original code would, no need for single-stepping or emul...
2013 Oct 19
3
MmioTrace: Using the Instruction Decoder, etc.
On Fri, 18 Oct 2013 00:11:15 +0400
Eugene Shatokhin <euspectre at gmail.com> wrote:
> Hi,
>
> Good to know that!
>
> Yes, it should be faster than page faulting, although I haven't done the
> benchmarking yet. And yes, it is not needed to disable all but one CPU. In
> my current implementation, I use an ordered workqueue to send the data to
> the mmapped output
2013 Oct 25
2
MmioTrace: Using the Instruction Decoder, etc.
...ith
> register allocation, relocations and other things) but the principle is as
> I described.
>
> The function calls are processed too so that we can set our own handlers to
> execute at the beginning of a function and right before its exit.
>
> Yes, the functions like read[bwql]() and write[bwlq]() are usually inline
> but they pose no problem: on x86 they compile to ordinary MOV instructions
> and the like which are handled as I described above.
>
> The instrumented code will access the ioremapped area the same way as the
> original code would, no need fo...