similar to: [PATCH] MAINTAINERS: nouveau mailing list is moderated

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

From: Karol Herbst <kherbst at 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

From: Karol Herbst <kherbst at 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

From: Karol Herbst <kherbst at 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

From: Karol Herbst <kherbst at 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

4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at 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

3.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at 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

4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at 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

4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at 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

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

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

Hi, I think I got mmiotracing back to work on my machine. Would you please test this patch on your machines too? I still got some UNKNOWN entries in the mmiotrace file, but besides that it seems to work. I have no idea if that's the right way though, and it needs a big cleanup, but I just wanted to see if the basic idea works the patch should apply just fine on any 4.4 kernel happy

Hi Linus, The following changes since commit 540ad6b62b3a188a53b51cac81d8a60d40e29fbd: Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb (2010-07-28 20:01:26 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-mm-for-linus Andres Salomon (1): x86, mm: Create

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wayland-bugs at lists.freedesk |nouveau at lists.freedesktop.o |top.org |rg QA Contact|

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NOTOURBUG |--- --- Comment #11 from Pekka Paalanen

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #12 from Pekka Paalanen <ppaalanen at gmail.com> --- Setting status to NEW, since this

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #23 from Pekka Paalanen

The quilt patch titled Subject: x86/mm: add testmmiotrace MODULE_DESCRIPTION() has been removed from the -mm tree. Its filename was x86-mm-add-testmmiotrace-module_description.patch This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Jeff

The patch titled Subject: x86/mm: add testmmiotrace MODULE_DESCRIPTION() has been added to the -mm mm-nonmm-unstable branch. Its filename is x86-mm-add-testmmiotrace-module_description.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/x86-mm-add-testmmiotrace-module_description.patch This patch will later appear

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