search for: mmiotrac

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"); open($fh41ad, &q...

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 systems, KernelStrider > (http://code.google.com/p/kernel-...

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...

...t; > ... > > 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 welcome! Hi, I got one comment in IRC, saying that a faster mmiotrace would be nice, but probably not something he would invest time in. Looking at it from that point of view, I guess mmiotrace works well enough, and is "only" a reverse-engineering tool, not something used daily. That, and the lack of replies here indicate that rewriting mmiotrace with yo...

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...

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? > > > > I have asked the question before, and then I had two ideas. Well, the > > first one was actually your idea (so I hear) to solve the same pro...

...is manageable, the system already handles string functions, for example, and reports appropriate events. The handlers for other functions could be added as well. So this just requires a bit more maintenance work. > Unfortunately, my job exhausts my coding energy, and I haven't even touched mmiotrace in years. I understand. I have many other responsibilities too. Code to write, bugs to fix, etc. ;-) Well, then, when time permits, I'll try to prepare a prototype so that its performance and reliability could be evaluated. Hard to tell what the numbers will be before that. Suggestions, com...

...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...

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 loa...

Od: "Ilia Mirkin" <imirkin at alum.mit.edu> Do: "Lampshade" <lampshade at poczta.fm>; Wys?ane: 19:07 Czwartek 2014-07-10 Temat: Re: [Nouveau] Warnings in dmesg and results of mmiotrace 10de:1140 Geforce620m Optimus Laptop Acer E1-531G > On Thu, Jul 10, 2014 at 11:01 AM, Lampshade wrote: > > Hello > > in dmesg I always have these informations (I tested several kernels between 3.7 and 3.16-rc3): > > > > [ 13.742006] nouveau E[ DRM] Pointer to TMD...

...ec 2, 2014 at 8:38 AM, poma <pomidorabelisima at gmail.com> wrote: >> Is this expected result for Chipset: G98 (NV98)? > > Yep, 100% expected. [Perhaps you might glance at the wiki page you got > that from for clues as 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 >>...

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 trac...

...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...

...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...

...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...

...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...

...uffer (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 it currently works quite well with network drivers, the performance > overhead is acceptable there. Ah, you are not using the ftrace framework nor relayfs? Mmiotrace used to be relayfs at one point and then converted to ftrace. > A subtle drawback may be that the system sees the memory reads and writes > made by the code of the driver directly but if the driver uses some other > kernel functions, it needs to intercept these calls and determine how th...

...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...

...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...

...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...