search for: mmiotracing

Is this expected result for Chipset: G98 (NV98)? $ modinfo nvidia -F version 304.123 $ stat -c %s mmiotrace.log 134659197 $ file mmiotrace.log mmiotrace.log: ASCII text $ grep -i lost mmiotrace.log ; echo $? 1 $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d"); open($fh41ac, ">fuc41ac");

On Mon, 14 Oct 2013 22:45:09 +0400 Eugene Shatokhin <euspectre at gmail.com> wrote: > Hi, > > There is an interesting TODO item on MmioTraceDeveloper page: > "kprobes has a generic instruction decoding facility, use that instead of > homebrewn (or KVM), and use emulation instead of page faulting" > > Actually, I have done something similar in one of my

After every iounmap mmiotrace has to free kmmio_fault_pages, but it can't do it directly, so it defers freeing by RCU. It usually works, but when mmiotraced code calls ioremap-iounmap multiple times without sleeping between (so RCU won't kick in and start freeing) it can be given the same virtual address, so at every iounmap mmiotrace will schedule the same pages for release. Obviously it

On Fri, 25 Oct 2013 17:19:56 +0400 Eugene Shatokhin <euspectre at gmail.com> wrote: > Hi, > > 2013/10/25 Pekka Paalanen <pq at iki.fi> > ... > > We could use some comments from the real reverse-engineers. I used > > to be mostly a tool writer. > > > > Yes, if some experts could share their knowledge of this matter, this would > be most

After every iounmap mmiotrace has to free kmmio_fault_pages, but it can't do it directly, so it defers freeing by RCU. It usually works, but when mmiotraced code calls ioremap-iounmap multiple times without sleeping between (so RCU won't kick in and start freeing) it can be given the same virtual address, so at every iounmap mmiotrace will schedule the same pages for release. Obviously it

On Wed, 16 Apr 2008 13:46:09 +0200 Ingo Molnar <mingo at elte.hu> wrote: > > * Pekka Paalanen <pq at iki.fi> wrote: > > > > we should fix this restriction ASAP. Forcibly dropping to UP will > > > cause mmiotrace to be much less useful for diagnostic purposes of > > > Linux > > > > Ok, how do you propose we solve this? > >

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 buffer (where they will be read from from the user space) and that ensures the order of events is kept. May be less than ideal but

...inux I was using for a long time only Intel GPU. I generated mmio tracing with this kernel (from kernel.org, I disabled Symmetric multiprocessing) compiled on my own. I have used NVIDIA-Linux-x86_64-340.24 driver on 64 bit system with UEFI enabled. I followed this manual: https://wiki.ubuntu.com/X/MMIOTracing. Others used commands are contained in archive (I have run for first mmiotrace: xserver + openbox for second: xserver + openbox + glxgears). ubuntu at random:~$ uname -a Linux random 3.12.24 #1 Wed Jul 9 13:42:50 CEST 2014 x86_64 x86_64 x86_64 GNU/Linux Kernel is a clean, recent code from kernel.or...

Hi all, some nouveau users and developers have an issue with mmiotracing the nvidia driver. After some digging I think it might has something todo with hugepages and/or the tracing infrastructure in general, but generally I am still clueless what is causing this. Generally it can be triggered by starting a X server on the nvidia gpu with the nvidia kernel module loaded...

...ime only Intel GPU. > > > > I generated mmio tracing with this kernel (from kernel.org, I disabled Symmetric multiprocessing) compiled on my own. I have used NVIDIA-Linux-x86_64-340.24 driver on 64 bit system with UEFI enabled. > > I followed this manual: https://wiki.ubuntu.com/X/MMIOTracing. Others used commands are contained in archive (I have run for first mmiotrace: xserver + openbox for second: xserver + openbox + glxgears). > > ubuntu at random:~$ uname -a > > Linux random 3.12.24 #1 Wed Jul 9 13:42:50 CEST 2014 x86_64 x86_64 x86_64 GNU/Linux > > Kernel is a cle...

...s to why.] > "You basically never need to do the mmiotrace, unless you're a nouveau developer."? I did everything by the book[1]. Though I don't need this, I still wanted to see how it works with 'nouveau.config=NvGrUseFW=1'. Bummer. [1] https://wiki.ubuntu.com/X/MMIOTracing >> >> $ modinfo nvidia -F version >> 304.123 >> >> $ stat -c %s mmiotrace.log >> 134659197 >> >> $ file mmiotrace.log >> mmiotrace.log: ASCII text >> >> $ grep -i lost mmiotrace.log ; echo $? >> 1 >> >> $ ./envyto...

If something calls ioremap with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap the address passed to unregister_kmmio_probe was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep track o...

Jialong Yang <jialong.yang at shingroup.cn> writes: > mmiotrace is a useful tool to trace MMIO accesses. Nowadays, it only > supported on x86 and x86_64 platforms. I've never used mmiotrace, and don't know it well. I'm not necessarily opposed to merging it, but AFAIK it was mostly used for reverse engineering proprietary drivers, where the driver itself couldn't be

...redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...

...redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...

...redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...

...redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...

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

...t redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...

...t redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to unregister_kmmio_probe() was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page align addresses while (un)registerung mappings, because the mmiotracer works on top of pages, not mappings. We still keep tra...