committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|93940996||cem||Oct. 22, 2018, 5:42 p.m.||Conditionalize kern.tty_info_kstacks feature on STACKS option|
|2801dd08||markj||Oct. 22, 2018, 5:19 p.m.||Fix the build after r339601.|
|2a843ae7||markj||Oct. 22, 2018, 5:17 p.m.||Avoid a redundancy in a comment updated by r339601.|
|b0058196||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 <email@example.com> Reviewed by: alc, kib Discussed with: jeff MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17304cgit ViewVC
|127a9d73||hselasky||Oct. 22, 2018, 4:21 p.m.||Make sure returned value is checked and assert a valid refcount.|
|21744c82||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 <firstname.lastname@example.org> Reviewed by: alc MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D17483cgit ViewVC
|d3a4b0da||markj||Oct. 22, 2018, 4:09 p.m.||Fix style bugs in in6_pcblookup_lbgroup().|
|81c0d72c||glebius||Oct. 22, 2018, 3:48 p.m.||If we lost race or were migrated during bucket allocation for the per-CPU|
|ca8f3d1c||avg||Oct. 22, 2018, 3:33 p.m.||nfsrvd_readdirplus: for some errors, do not fail the entire request
Instead, a failing entry is skipped. This change consist of two logical changes. A failure to vget or lookup an entry is considered to be a result of a concurrent removal, which is the only reasonable explanation given that the filesystem is busied. So, the entry would be silently skipped. In the case of a failure to get attributes of an entry for an NFSv3 request, the entry would be silently skipped. There can be legitimate reasons for the failure, but NFSv3 does not provide any means to report the error, so we have two options: either fail the whole request or ignore the failed entry. Traditionally, the old NFS server used the latter option, so the code is reverted to it. Making the whole directory unreadable because of a single entry seems to be unpractical. Additionally, some bits of code are slightly re-arranged to account for the new control flow and to honor style(9). Reviewed by: rmacklem Sponsored by: Panzura Differential Revision: https://reviews.freebsd.org/D15424cgit ViewVC
|43e08d07||andrew||Oct. 22, 2018, 3:18 p.m.||Stop advertising ARMv8.3 Pointer Authentication|
|5bb9cd61||andrew||Oct. 22, 2018, 3:06 p.m.||Fix the ID_AA64ISAR0_EL1 dot product field shift.|
|71374d5d||andrew||Oct. 22, 2018, 2:58 p.m.||Correctly set the DAIF bits in new threads|
|da4e7cad||avg||Oct. 22, 2018, 2:44 p.m.||ichwd: add support for TCO watchdog timer in Lewisburg PCH (C620)
The change is based on public documents listed below as well as Linux changes and the code developed by Kostik. The documents: - Intel® C620 Series Chipset Platform Controller Hub Datasheet - Intel® 100 Series and Intel® C230 Series Chipset Family Platform Controller Hub (PCH) Datasheet - Volume 2 of 2 Interesting Linux commits: - https://github.com/torvalds/linux/commit/9424693035a57961a8eb09e96aab315a7096535d - https://github.com/torvalds/linux/commit/2a7a0e9bf7b32e838d873226808ab8a6c00148f7 The peculiarity of the new chipsets is that the watchdog resources are configured in PCI registers of SMBus controller and Power Management function as opposed to the LPC bridge. I took a simplistic approach of querying the resources from the respective PCI devices. ichwd is still a device on isa bus. The PCI devices are found by their slot and function defined in the datasheets as siblings of the upstream LPC bridge. There are some shortcuts and missing features. First of all, I have not implemented the functionality required to clear the no-reboot bit. That would require writing to a special PCI configuration register of a hidden / invisible PCI device after which the device would start responding to accesses to other registers. The no-reboot bit was not set on my test hardware, so I decided to leave its handling for the later time. Also, I did not try to handle the case where the watchdog resources are not configured by the hardware as well as the case where ACPI defined operational region conflicts with the watchdog resources. My test system did not have either of those problem, so, again, I decided to leave those cases until later. See this Linux commit for some details of the ACPI problem: https://github.com/torvalds/linux/commit/a7ae81952cdab56a1277bd2f9ed7284c0f575120 Finally, I have added only the PCI ID found on my test system. I think that more IDs can be added as the change gets tested. Tested on Dell PowerEdge R740. PR: 222079 Reviewed by: mav, kib MFC after: 3 weeks Relnotes: maybe Sponsored by: Panzura Differential Revision: https://reviews.freebsd.org/D17585cgit ViewVC
|a464523e||skozlov||Oct. 22, 2018, 2:01 p.m.||Add myself to mentees with sbruno as mentor|
|d93e635a||luporl||Oct. 22, 2018, 1:40 p.m.||ppc64: limited 32-bit DMA address range
Further investigation of issues with 32-bit DMA on PowerNV revealed that its window is hardcoded by OPAL (at least in skiboot version 5.4.9) and cannot be changed by the OS. Thus, now jhb suggestion of limiting the range in PCI DMA tag seems the best way to deal with it. Reviewed by: jhibbits, nwhitehorn, sbruno Approved by: jhibbits(mentor) Differential Revision: https://reviews.freebsd.org/D17601cgit ViewVC