committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r339618||tijl||Oct. 22, 2018, 8:55 p.m.||Define linuxkpi readq for 64-bit architectures. It is used by drm-kmod.
Currently the compiler picks up the definition in machine/cpufunc.h. Add compiler memory barriers to read* and write*. The Linux x86 implementation of these functions uses inline asm with "memory" clobber. The Linux x86 implementation of read_relaxed* and write_relaxed* uses the same inline asm without "memory" clobber. Implement ioread* and iowrite* in terms of read* and write* so they also have memory barriers. Qualify the addr parameter in write* as volatile. Like Linux, define macros with the same name as the inline functions. Only define 64-bit versions on 64-bit architectures because generally 32-bit architectures can't do atomic 64-bit loads and stores. Regroup the functions a bit and add brief comments explaining what they do: - __raw_read*, __raw_write*: atomic, no barriers, no byte swapping - read_relaxed*, write_relaxed*: atomic, no barriers, little-endian - read*, write*: atomic, with barriers, little-endian Add a comment that says our implementation of ioread* and iowrite* only handles MMIO and does not support port IO. Reviewed by: hselasky MFC after: 3 daysViewVC
|r339617||cem||Oct. 22, 2018, 8:22 p.m.||Retroactively vendor 1.3.3, 1.3.4, and 1.3.7 imports|
|r339616||markj||Oct. 22, 2018, 8:13 p.m.||Make it possible to disable NUMA support with a tunable.
This provides a chicken switch for anyone negatively impacted by enabling NUMA in the amd64 GENERIC kernel configuration. With NUMA disabled at boot-time, information about the NUMA topology is not exposed to the rest of the kernel, and all of physical memory is viewed as coming from a single domain. This method still has some performance overhead relative to disabling NUMA support at compile time. PR: 231460 Reviewed by: alc, gallatin, kib MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17439ViewVC
|r339609||emaste||Oct. 22, 2018, 7:39 p.m.||release: set -e to exit on error in iso image scripts|
|r339608||emaste||Oct. 22, 2018, 6:41 p.m.||arch.7: first appeared in FreeBSD 11.1|
|r339607||emaste||Oct. 22, 2018, 6:40 p.m.||Makefile.inc1: clean up stale dependency hacks
Our dependency tracking cannot directly cope with certain source tree changes, particularly with respect to removing or moving source files or replacing generated files. We have a collection of ad-hoc workarounds to handle these cases. As there is a (small) build-time cost inherent in these workarounds, we do not want to keep them indefinitely. Thus, remove workarounds from 2017. Sponsored by: The FreeBSD FoundationViewVC
|r339606||cem||Oct. 22, 2018, 6:29 p.m.||Update to Zstandard 1.3.7
Relnotes: yes Sponsored by: Dell EMC IsilonViewVC
|r339605||cem||Oct. 22, 2018, 5:42 p.m.||Conditionalize kern.tty_info_kstacks feature on STACKS option
Fix tinderbox (mips XLPN32) after r339471. Reported by: tinderbox X-MFC-With: r339471 Sponsored by: Dell EMC IsilonViewVC
|r339603||markj||Oct. 22, 2018, 5:19 p.m.||Fix the build after r339601.|
|r339602||markj||Oct. 22, 2018, 5:17 p.m.||Avoid a redundancy in a comment updated by r339601.
Reported by: alc X-MFC with: r339601ViewVC
|r339601||markj||Oct. 22, 2018, 5:04 p.m.||Swap in processes unless there's a global memory shortage.
On NUMA systems, we would not swap in processes unless all domains had some free pages. This is too conservative in general. Instead, permit swapins so long as at least one domain has free pages, and add a kernel stack NUMA policy which ensures that we will try to allocate kernel stack pages from any domain. Reported and tested by: pho, Jan Bramkamp <firstname.lastname@example.org> Reviewed by: alc, kib Discussed with: jeff MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17304ViewVC
|r339600||hselasky||Oct. 22, 2018, 4:21 p.m.||Make sure returned value is checked and assert a valid refcount.|
|r339599||markj||Oct. 22, 2018, 4:16 p.m.||Don't import 0 into vmem quantum caches.
vmem uses UMA cache zones to implement the quantum cache. Since uma_zalloc() returns 0 (NULL) to signal an allocation failure, UMA should not be used to cache resource 0. Fix this by ensuring that 0 is never cached in UMA in the first place, and by modifying vmem_alloc() to fall back to a search of the free lists if the cache is depleted, rather than blocking in qc_import(). Reported by and discussed with: Brett Gutstein <email@example.com> Reviewed by: alc MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D17483ViewVC
|r339598||markj||Oct. 22, 2018, 4:09 p.m.||Fix style bugs in in6_pcblookup_lbgroup().|
|r339596||glebius||Oct. 22, 2018, 3:48 p.m.||If we lost race or were migrated during bucket allocation for the per-CPU
cache, then we put new bucket on generic bucket cache. However, code didn't honor UMA_ZONE_NOBUCKETCACHE flag, so potentially we could start a cache on a zone that clearly forbids that. Fix this. Reviewed by: markjViewVC