summaryrefslogtreecommitdiff
path: root/debian/cscope.install
diff options
context:
space:
mode:
Diffstat (limited to 'debian/cscope.install')
-rw-r--r--debian/cscope.install13
1 files changed, 12 insertions, 1 deletions
diff --git a/debian/cscope.install b/debian/cscope.install
index 2ff4aa3..c60d27e 100644
--- a/debian/cscope.install
+++ b/debian/cscope.install
@@ -1 +1,12 @@
-contrib/xcscope/xcscope.el usr/share/emacs/site-lisp
+
+src/cscope usr/bin
+contrib/ocs usr/bin
+contrib/xcscope/cscope-indexer usr/bin
+contrib/README usr/share/doc/cscope/contrib
+
+contrib/webcscope/cgi-lib.pl usr/share/doc/cscope/contrib/webcscope
+contrib/webcscope/cscope usr/share/doc/cscope/contrib/webcscope
+contrib/webcscope/hilite.c usr/share/doc/cscope/contrib/webcscope
+contrib/webcscope/icons usr/share/doc/cscope/contrib/webcscope
+contrib/webcscope/INSTALL usr/share/doc/cscope/contrib/webcscope
+contrib/webcscope/TODO usr/share/doc/cscope/contrib/webcscope
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-04-26 15:52:54 +0000
when the user of mmu_notifiers has to manage a hardware TLB it can still wipe out TLB entries in invalidate_range_start, but it can't make sure that no new TLB entries in the given range are established between invalidate_range_start and invalidate_range_end. To avoid silent data corruption the entries in the non-CPU TLB need to be flushed when the pages are unmapped (at this point in time no _new_ TLB entries can be established in the non-CPU TLB) but not yet freed (as the non-CPU TLB may still have _existing_ entries pointing to the pages about to be freed). To fix this problem we need to catch the moment when the Linux VMM flushes remote TLBs (as a non-CPU TLB is not very CPU TLB), as this is the point in time when the pages are unmapped but _not_ yet freed. The mmu_notifier_invalidate_range() function aims to catch that moment. IOMMU code will be one user of the notifier-callback. Currently this is only the AMD IOMMUv2 driver, but its code is about to be more generalized and converted to a generic IOMMU-API extension to fit the needs of similar functionality in other IOMMUs as well. The current attempt in the AMD IOMMUv2 driver to work around the invalidate_range_start/end() shortcoming is to assign an empty page table to the non-CPU TLB between any invalidata_range_start/end calls. With the empty page-table assigned, every page-table walk to re-fill the non-CPU TLB will cause a page-fault reported to the IOMMU driver via an interrupt, possibly causing interrupt storms. The page-fault handler in the AMD IOMMUv2 driver doesn't handle the fault if an invalidate_range_start/end pair is active, it just reports back SUCCESS to the device and let it refault the page. But existing hardware (newer Radeon GPUs) that makes use of this feature don't re-fault indefinitly, after a certain number of faults for the same address the device enters a failure state and needs to be resetted. To avoid the GPUs entering a failure state we need to get rid of the empty-page-table workaround and use the mmu_notifier_invalidate_range() function introduced with this patch. Signed-off-by: Joerg Roedel <jroedel@suse.de> Reviewed-by: Andrea Arcangeli <aarcange@redhat.com> Reviewed-by: Jérôme Glisse <jglisse@redhat.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Rik van Riel <riel@redhat.com> Cc: Hugh Dickins <hughd@google.com> Cc: Mel Gorman <mgorman@suse.de> Cc: Johannes Weiner <jweiner@redhat.com> Cc: Jay Cornwall <Jay.Cornwall@amd.com> Cc: Oded Gabbay <Oded.Gabbay@amd.com> Cc: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com> Cc: Jesse Barnes <jbarnes@virtuousgeek.org> Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Oded Gabbay <oded.gabbay@amd.com>
Diffstat (limited to 'include/linux/mmu_notifier.h')