arm: fix a typo in nvidia/drm2/tegra_bo.cUnbreaks building TEGRA124Sponsored by: Rubicon Communications, LLC ("Netgate")(cherry picked from commit e2493f4912cabd1d04be88fd17139a64bf2a2622)
Convert consumers to vm_page_alloc_noobj_contig()Remove now-unneeded page zeroing. No functional change intended.Reviewed by: alc, hselasky, kibSponsored by: The FreeBSD Foundation(cherry pic
Convert consumers to vm_page_alloc_noobj_contig()Remove now-unneeded page zeroing. No functional change intended.Reviewed by: alc, hselasky, kibSponsored by: The FreeBSD Foundation(cherry picked from commit 84c3922243a7b7fd510dcfb100aec59c878c57d0)
show more ...
arm: arm64: Directly use #include <dt-binding/...>We have it in the includes path and this will help the transition to thenew device-tree import in sys/contrib
arm: clean up empty lines in .c and .h files
remove extraneous double ;s in sys/
Fix a few places that free a page from an object without busy held. This istightening constraints on busy as a precursor to lockless page lookup andshould largely be a NOP for these cases.Review
Fix a few places that free a page from an object without busy held. This istightening constraints on busy as a precursor to lockless page lookup andshould largely be a NOP for these cases.Reviewed by: alc, kib, markjDifferential Revision: https://reviews.freebsd.org/D22611
Change synchonization rules for vm_page reference counting.There are several mechanisms by which a vm_page reference is held,preventing the page from being freed back to the page allocator. Inpa
Change synchonization rules for vm_page reference counting.There are several mechanisms by which a vm_page reference is held,preventing the page from being freed back to the page allocator. Inparticular, holding the page's object lock is sufficient to prevent thepage from being freed; holding the busy lock or a wiring is sufficent aswell. These references are protected by the page lock, which musttherefore be acquired for many per-page operations. This results infalse sharing since the page locks are external to the vm_pagestructures themselves and each lock protects multiple structures.Transition to using an atomically updated per-page reference counter.The object's reference is counted using a flag bit in the counter. Asecond flag bit is used to atomically block new references viapmap_extract_and_hold() while removing managed mappings of a page.Thus, the reference count of a page is guaranteed not to increase if thepage is unbusied, unmapped, and the object's write lock is held. Asa consequence of this, the page lock no longer protects a page'sidentity; operations which move pages between objects are nowsynchronized solely by the objects' locks.The vm_page_wire() and vm_page_unwire() KPIs are changed. The formerrequires that either the object lock or the busy lock is held. Thelatter no longer has a return value and may free the page if it releasesthe last reference to that page. vm_page_unwire_noq() behaves the sameas before; the caller is responsible for checking its return value andfreeing or enqueuing the page as appropriate. vm_page_wire_mapped() isintroduced for use in pmap_extract_and_hold(). It fails if the page isconcurrently being unmapped, typically triggering a fallback to thefault handler. vm_page_wire() no longer requires the page lock andvm_page_unwire() now internally acquires the page lock when releasingthe last wiring of a page (since the page lock still protects a page'squeue state). In particular, synchronization details are no longerleaked into the caller.The change excises the page lock from several frequently executed codepaths. In particular, vm_object_terminate() no longer bounces betweenpage locks as it releases an object's pages, and direct I/O andsendfile(SF_NOCACHE) completions no longer require the page lock. Inthese latter cases we now get linear scalability in the common scenariowhere different threads are operating on different files.__FreeBSD_version is bumped. The DRM ports have been updated toaccomodate the KPI changes.Reviewed by: jeff (earlier version)Tested by: gallatin (earlier version), phoSponsored by: NetflixDifferential Revision: https://reviews.freebsd.org/D20486
Replace uses of vm_page_unwire(m, PQ_NONE) with vm_page_unwire_noq(m).These calls are not the same in general: the former will dequeue thepage if it is enqueued, while the latter will just leave i
Replace uses of vm_page_unwire(m, PQ_NONE) with vm_page_unwire_noq(m).These calls are not the same in general: the former will dequeue thepage if it is enqueued, while the latter will just leave it alone. But,all existing uses of the former apply to unmanaged pages, which arenever enqueued in the first place. No functional change intended.Reviewed by: kibMFC after: 1 weekSponsored by: NetflixDifferential Revision: https://reviews.freebsd.org/D20470
Eliminate kmem_alloc_contig()'s unused arena parameter.Reviewed by: hselasky, kib, markjDiscussed with: jeffDifferential Revision: https://reviews.freebsd.org/D16799
Align OF_getencprop_alloc API with OF_getencprop and OF_getprop_allocChange OF_getencprop_alloc semantics to be combination of malloc andOF_getencprop and return size of the property, not number o
Align OF_getencprop_alloc API with OF_getencprop and OF_getprop_allocChange OF_getencprop_alloc semantics to be combination of malloc andOF_getencprop and return size of the property, not number of elementsallocated.For the use cases where number of elements is preferred introduceOF_getencprop_alloc_multi helper function that copies semanticsof OF_getencprop_alloc prior to this change.This is to make OF_getencprop_alloc and OF_getencprop_alloc_multifunction signatures consistent with OF_getencprop_alloc andOF_getencprop_alloc_multi.Functionality-wise this patch is mostly rename of OF_getencprop_allocto OF_getencprop_alloc_multi except two calls in ofw_bus_setup_iinfowhere 1 was used as a block size.
vm_wait() rework.Make vm_wait() take the vm_object argument which specifies the domainset to wait for the min condition pass. If there is no objectassociated with the wait, use curthread' policy
vm_wait() rework.Make vm_wait() take the vm_object argument which specifies the domainset to wait for the min condition pass. If there is no objectassociated with the wait, use curthread' policy domainset. Themechanics of the wait in vm_wait() and vm_wait_domain() is supplied bythe new helper vm_wait_doms(), which directly takes the bitmask of thedomains to wait for passing min condition.Eliminate pagedaemon_wait(). vm_domain_clear() handles the sameoperations.Eliminate VM_WAIT and VM_WAITPFAULT macros, the direct functions callsare enough.Eliminate several control state variables from vm_domain, unneededafter the vm_wait() conversion.Scetched and reviewed by: jeffTested by: phoSponsored by: The FreeBSD Foundation, Mellanox TechnologiesDifferential revision: https://reviews.freebsd.org/D14384
Implement drivers for NVIDIA tegra124 display controller, HDMI sourceand host1x module. Unfortunately, tegra124 SoC doesn't have 2D accelerationengine and 3D requires not yet started nouveau driver
Implement drivers for NVIDIA tegra124 display controller, HDMI sourceand host1x module. Unfortunately, tegra124 SoC doesn't have 2D accelerationengine and 3D requires not yet started nouveau driver.These drivers forms a first non-x86 DRM2 enabled graphic stack.Note, there are 2 outstanding issues: - The code uses gross hack in order to be comply with OBJT_MGTDEVICE pager. (See tegra_bo_init_pager() in tegra_bo.c) - Due to improper(probably) refcounting in drm_gem_mmap_single() (in drm_gem.c), the gem objects are never released.I hope that I will be able to address both issues in finite time,but I don't want to touch x86 world now.MFC after: 1 month