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.
|r303803||stevek||Aug. 6, 2016, 6:48 p.m.||Add hw.fdt sysctl node.|
|r303802||bcr||Aug. 6, 2016, 5:53 p.m.||Update with the members of the 9th core team.|
|r303801||bjk||Aug. 6, 2016, 5:27 p.m.||Correct the documentation of the 'type' parameter for the _SWAP|
|r303800||pfg||Aug. 6, 2016, 5:24 p.m.||ext2fs: Add defines for some missing ext4 feature flags.
These are currently unused in our implementation and some even appear to have not been implemented yet on linux but it is good to keep them for reference. Obtained from: NetBSD (CVS Rev. 1.41) MFC after: 1 monthViewVC
|r303799||pfg||Aug. 6, 2016, 4:48 p.m.||ext2fs: Add some more inode flags.
These are currently unused in out implementation but it is good to keep them for reference. Obtained from: NetBSD (CVS Rev. 1.35) MFC after: 1 monthViewVC
|r303798||tuexen||Aug. 6, 2016, 3:29 p.m.||Don't modify a structure without holding a reference count on it.
MFC after: 3 daysViewVC
|r303797||jhibbits||Aug. 6, 2016, 3:10 p.m.||Check the first byte of the array for NUL, instead of the array as a NULL pointer
The partition_name field is an array, so can never be NULL itself. Check only the first byte instead. This was found when test building with clang, but I'm not sure how it passes gcc's warnings either.ViewVC
|r303796||jhibbits||Aug. 6, 2016, 3:06 p.m.||Two fixups for dtrace
* Use the right incantation to get the next stack pointer. Since powerpc uses special frames for traps, dereferencing the stack pointer straight up won't get us the next stack pointer in every case. * Clear EE using the correct instruction sequence. The PowerISA states that 'andi.' ANDs the register with 0||<imm>, instead of sign extending or filling out the unavailable bits with 1. Even if it did sign extend, PSL_EE is 0x8000, so ~PSL_EE is 0x7fff, and the upper bits would be cleared. Use rlwinm in the 32-bit case, and a two-rotate sequence in the 64-bit case, the latter chosen to follow the output generated by gcc. MFC after: 1 weekViewVC
|r303795||kib||Aug. 6, 2016, 1:32 p.m.||Add __cxa_thread_atexit(3) API implementation.
This is the backing feature to implement C++11 thread storage duration specified by the thread_local keyword. A destructor for given thread-local object is registered to be executed at the thread termination time using __cxa_thread_atexit(). Libc calls the __cxa_thread_calls_dtors() during exit(3), before finalizers and atexit functions, and libthr calls the function at the thread termination time, after the stack unwinding and thread-specific key destruction. There are several uncertainties in the API which lacks a formal specification. Among them: - is it allowed to register destructors during destructing; we allow, but limiting the nesting level. If too many iterations detected, a diagnostic is issued to stderr and thread forcibly terminates for now. - how to handle destructors which belong to an unloading dso; for now, we ignore destructor calls for such entries, and issue a diagnostic. Linux does prevent dso unload until all threads with destructors from the dso terminated. It is supposed that the diagnostics allow to detect real-world applications relying on the above details and possibly adjust our implementation. Right now the choices were to provide the slim API (but that rarely stands the practice test). Tests are added to check generic functionality and to specify some of the above implementation choices. Submitted by: Mahdi Mokhtari <mokhi64_gmail.com> Reviewed by: theraven Discussed with: dim (detection of -std=c++11 supoort for tests) Sponsored by: The FreeBSD Foundation (my involvement) MFC after: 2 weeks Differential revisions: https://reviews.freebsd.org/D7224, https://reviews.freebsd.org/D7427ViewVC
|r303794||kib||Aug. 6, 2016, 1:28 p.m.||Create namespace for the symbols added during 12-CURRENT cycle.
Sponsored by: The FreeBSD Foundation MFC after: 2 weeksViewVC
|r303793||tuexen||Aug. 6, 2016, 12:51 p.m.||Mark an unused parameter as such.
MFC after: 3 daysViewVC
|r303792||tuexen||Aug. 6, 2016, 12:33 p.m.||Fix various bugs in relation to the I-DATA chunk support
This is joint work with rrs. MFC after: 3 daysViewVC
|r303791||avg||Aug. 6, 2016, 11:02 a.m.||fix .zfs-related cases in zfs_lookup that were broken by r303763
The problem is that the special .zfs nodes are not represented by znodes but by special gfs-based nodes. r303763 changed interface of zfs_dirlook such that started operating on znodes rather than on vnodes and, thus, the function became unsuitable for handling .zfs entities. The solution is to move the handling of the special cases to zfs_lookup, the only consumer of zfs_dirlook. I already had this solution applied in D7421, but for different reasons. Reported by: asomers MFC after: 3 days X-MFC with: r303763ViewVC
|r303788||vangyzen||Aug. 5, 2016, 11:23 p.m.||Fix some logic in PCIe HotPlug; display EI status
The interpretation of the Electromechanical Interlock Status was inverted, so we disengaged the EI if a card was inserted. Fix it to engage the EI if a card is inserted. When displaying the slot capabilites/status with pciconf: - We inverted the sense of the Power Controller Control bit, saying the power was off when it was really on (according to this bit). Fix that. - Display the status of the Electromechanical Interlock: EI(engaged) EI(disengaged) Reviewed by: jhb MFC after: 3 days Sponsored by: Dell Inc. Differential Revision: https://reviews.freebsd.org/D7426ViewVC
|r303786||markj||Aug. 5, 2016, 9:34 p.m.||mthca: Add a wrapper for the firmware's DIAG_RPRT command.
MFC after: 1 week Sponsored by: EMC / Isilon Storage DivisionViewVC