summaryrefslogtreecommitdiffstats
path: root/share
Commit message (Collapse)AuthorAgeFilesLines
* MFC r318109:gjb2017-05-125-10/+10
| | | | | | | Correct "first appeared in" entries for various drivers that exist in stable/11. Sponsored by: The FreeBSD Foundation
* MFC r317584:hselasky2017-05-111-1/+1
| | | | Correct manual page link to usbdi(9).
* MFC 314894: Fix a couple of typos and reword some sentences in bsd.README.jhb2017-05-101-5/+5
|
* MFC r317775:ken2017-05-101-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix error recovery behavior in the pass(4) driver. After FreeBSD SVN revision 236814, the pass(4) driver changed from only doing error recovery when the CAM_PASS_ERR_RECOVER flag was set on a CCB to sometimes doing error recovery if the passed in retry count was non-zero. Error recovery would happen if two conditions were met: 1. The error recovery action was simply a retry. (Which is most cases.) 2. The retry_count is non-zero. (Which happened a lot because of cut-and-pasted code.) This explains a bug I noticed in with camcontrol: # camcontrol tur da34 -v Unit is ready # camcontrol reset da34 Reset of 1:172:0 was successful At this point, there should be a Unit Attention: # camcontrol tur da34 -v Unit is ready No Unit Attention. Try it again: # camcontrol reset da34 Reset of 1:172:0 was successful Now set the retry_count to 0 for the TUR: # camcontrol tur da34 -v -C 0 Unit is not ready (pass42:mps1:0:172:0): TEST UNIT READY. CDB: 00 00 00 00 00 00 (pass42:mps1:0:172:0): CAM status: SCSI Status Error (pass42:mps1:0:172:0): SCSI status: Check Condition (pass42:mps1:0:172:0): SCSI sense: UNIT ATTENTION asc:29,2 (SCSI bus reset occurred) (pass42:mps1:0:172:0): Field Replaceable Unit: 2 There is the unit attention. camcontrol(8) has a default retry_count of 1, in case someone sets the -E flag without setting -C. The CAM_PASS_ERR_RECOVER behavior was only broken with the CAMIOCOMMAND ioctl, which is the synchronous pass(4) API. It has worked as intended (error recovery is only done when the flag is set) in the asynchronous API (CAMIOQUEUE ioctl). sys/cam/scsi/scsi_pass.c: In passsendccb(), when calling cam_periph_runccb(), only specify the error routine when CAM_PASS_ERR_RECOVER is set. share/man/man4/pass.4: Document that CAM_PASS_ERR_RECOVER is needed to enable error recovery. Reported by: Terry Kennedy <TERRY@glaver.org> PR: kern/218572 Sponsored by: Spectra Logic
* MFC r306773:bdrewery2017-05-091-1/+2
| | | | Add link for vrefl(9).
* MFC r317848:ken2017-05-081-2/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add basic programmable early warning error injection to the sa(4) driver. This will help application developers simulate end of tape conditions. To inject an error in sa0: sysctl kern.cam.sa.0.inject_eom=1 This will return the next read or write request queued with 0 bytes written. Any subsequent writes or reads will go along as usual. This will also cause the early warning position flag to get set for the next position query. So, 'mt status' will show the BPEW (Beyond Programmable Early Warning) flag on the first query after an error injection. After that, the position flags will be as they are in the underlying tape drive. Also, update the sa(4) man page to describe tape parameters, which can be set via 'mt param'. sys/cam/scsi/scsi_sa.c: In saregister(), create the inject_eom sysctl variable. In sastart(), check to see whether inject_eom is set. If so, return the read or write with 0 bytes written to indicate EOM. Set the set_pews_status flag so that we fake PEWS status in the next position call for reads, and the next 3 calls for writes. This allows the user to see the BPEW flag one time via 'mt status'. In sagetpos(), check the set_pews_status flag and fake PEWS status and decrement the counter if it is set. share/man/man4/sa.4: Document the inject_eom sysctl variable. Document all of the parameters currently supported via 'mt param'. usr.bin/mt/mt.1: Point the user to the sa(4) man page for more details on supported parameters. Sponsored by: Spectra Logic
* MFC r316945-r316946asomers2017-05-051-0/+9
| | | | | | | | | | | | | | | | | r316945: Add 410.status-mfi, a periodic script for mfi(4) arrays PR: 176049 Submitted by: doconnor@gsoft.com.au Reviewed by: scottl, Larry Rosenman <ler@lerctr.org> Relnotes: yes r316946: Reorder Makefile entries from r316945 PR: 176049 Reported by: Oliver Pinter X-MFC-With: 316945
* MFC r315526vangyzen2017-05-011-1/+2
| | | | | | | | | | | | | | | | | | | | | | Add clock_nanosleep() Add a clock_nanosleep() syscall, as specified by POSIX. Make nanosleep() a wrapper around it. Attach the clock_nanosleep test from NetBSD. Adjust it for the FreeBSD behavior of updating rmtp only when interrupted by a signal. I believe this to be POSIX-compliant, since POSIX mentions the rmtp parameter only in the paragraph about EINTR. This is also what Linux does. (NetBSD updates rmtp unconditionally.) Copy the whole nanosleep.2 man page from NetBSD because it is complete and closely resembles the POSIX description. Edit, polish, and reword it a bit, being sure to keep any relevant text from the FreeBSD page. Regenerate syscall files. Relnotes: yes Sponsored by: Dell EMC
* Merge r317444, r317445:glebius2017-04-292-16/+1
| | | | | | | UMA_ZONE_REFCNT was removed. PR: 209715 PR: 218887
* MFC r316586:bdrewery2017-04-281-1/+1
| | | | META_MODE: Fix build-tools still sometimes rebuilding during target build.
* MFC r316342, r316358asomers2017-04-241-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | r316342: Consolidate random sleeps in periodic scripts Multiple periodic scripts sleep for a random amount of time in order to mitigate the thundering herd problem. This is bad, because the sum of multiple uniformly distributed random variables approaches a normal distribution, so the problem isn't mitigated as effectively as it would be with a single sleep. This change creates a single configurable anticongestion sleep. periodic will only sleep if at least one script requires it, and it will never sleep more than once per invocation. It also won't sleep if periodic was run interactively, fixing an unrelated longstanding bug. PR: 217055 PR: 210188 Reviewed by: cy MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D10211 r316358: Fix man page typo from r316342 Reported by: rgrimes MFC after: 20 days X-MFC-With: 316342
* MFC r316589:trasz2017-04-231-14/+12
| | | | Unify capitalization.
* MFC r316587:trasz2017-04-231-34/+17
| | | | | Update hier(7) by removing files and directories that no longer exist and doing a few random tweaks.
* MFC r316467:trasz2017-04-231-1/+62
| | | | Add basic description of kernel source layout.
* MFC r316466:trasz2017-04-231-23/+23
| | | | | | | | Remove excessive horizontal whitespace from hier(7) by correctly using "-width". The http://mdocml.bsd.lv/mdoc/details/width.html says: "Do not use macros in the argument specifying the width, that's not portable. While GNU troff can handle it, mandoc cannot." The same problem seems to exist in many other man pages.
* MFC r316057:trasz2017-04-232-14/+32
| | | | | | Document EVENTHANDLER_DEFINE(9). Sponsored by: DARPA, AFRL
* MFC r316056:trasz2017-04-231-2/+1
| | | | | | The cn_consume was removed in r296716. Sponsored by: DARPA, AFRL
* MFC: r314694rgrimes2017-04-221-1/+9
| | | | | | | | Make vmrun.sh passthrough -u and -w to bhybe PR: 214273 Submitted by: Martin Birgmeier <la5lb...@aon.at> Approved by: grehan (mentor)
* MFC r314691:rgrimes2017-04-221-0/+8
| | | | | | Document 3 more src/ directories Approved by: grehan (mentor)
* MFC r310181 (matthew) (originally r309314):gjb2017-04-211-0/+5
| | | | | | | Allow a user-overridable setting 'PKG_CMD' to control the command used to create a repo during 'make packages'. Sponsored by: The FreeBSD Foundation
* Fix the arm64 userland building with lld:andrew2017-04-191-1/+1
| | | | | | | | | | | | | | | MFC 308124: On arm64 build the efi loader with -fPIC. Without this clang 3.9 will generate relocation in the self relocation code. MFC 316608: Add -fPIC to the standalone build flags on arm64. This is needed as loader.efi is position independend, however we were not building it as such causing a build failure when building with lld. MFC 315452: Mark the EFI PE header as allocated. While ld.bfd doesn't seem to care about not having this flag ld.lld fails to link without it.
* MFC r316485davidcs2017-04-192-0/+93
| | | | | Add 25/40/100Gigabit Ethernet Driver version v1.3.0 for Cavium Inc's. Qlogic 45000 Series Adapters
* MFC r316310davidcs2017-04-191-1/+2
| | | | | | Update man page for commit r316309 "Add support for optional Soft LRO". The driver provides the ability to select either HW or Software LRO, when LRO is enabled (default HW LRO).
* MFC r316956:bapt2017-04-171-7/+13
| | | | Update pci_vendors to 2017.04.03
* MFC r315461:bdrewery2017-04-131-0/+7
| | | | META_MODE: Fix not using .depend files when no OBJDIR is present.
* MFC r315211:bdrewery2017-04-131-6/+6
| | | | hier(7): Fix entry location for /usr/share/vt.
* MFC r316036:markj2017-04-111-1/+1
| | | | Typo.
* MFC r313959:trasz2017-04-096-0/+142
| | | | | | | | | | | | | | | | | | Add USB Mass Storage CTL frontend. This makes it possible for USB OTG-capable hardware to implement device side of USB Mass Storage, ie pretend it's a flash drive. It's configured in the same way as other CTL frontends, using ctladm(8) or ctld(8). Differently from usfs(4), all the configuration can be done without rebuilding the kernel. Testing and review is welcome. Right now I'm still moving, and I don't have access to my test environment, so I'm somewhat reluctant to making larger changes to this code; on the other hand I don't want to let it sit on Phab until my testing setup is back, because I want to get it into 11.1-RELEASE. Relnotes: yes Sponsored by: The FreeBSD Foundation
* MFC r315619: pet manlintdelphij2017-04-031-5/+5
|
* Regenerate src.conf.5 after the addition of WITH/WITHOUT_LLD_IS_LD.dim2017-04-021-7/+52
|
* Update clang, llvm, lld, lldb, compiler-rt and libc++ to 4.0.0 release:dim2017-04-022-8/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MFC r309142 (by emaste): Add WITH_LLD_AS_LD build knob If set it installs LLD as /usr/bin/ld. LLD (as of version 3.9) is not capable of linking the world and kernel, but can self-host and link many substantial applications. GNU ld continues to be used for the world and kernel build, regardless of how this knob is set. It is on by default for arm64, and off for all other CPU architectures. Sponsored by: The FreeBSD Foundation MFC r310840: Reapply 310775, now it also builds correctly if lldb is disabled: Move llvm-objdump from CLANG_EXTRAS to installed by default We currently install three tools from binutils 2.17.50: as, ld, and objdump. Work is underway to migrate to a permissively-licensed tool-chain, with one goal being the retirement of binutils 2.17.50. LLVM's llvm-objdump is intended to be compatible with GNU objdump although it is currently missing some options and may have formatting differences. Enable it by default for testing and further investigation. It may later be changed to install as /usr/bin/objdump, it becomes a fully viable replacement. Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D8879 MFC r312855 (by emaste): Rename LLD_AS_LD to LLD_IS_LD, for consistency with CLANG_IS_CC Reported by: Dan McGregor <dan.mcgregor usask.ca> MFC r313559 | glebius | 2017-02-10 18:34:48 +0100 (Fri, 10 Feb 2017) | 5 lines Don't check struct rtentry on FreeBSD, it is an internal kernel structure. On other systems it may be API structure for SIOCADDRT/SIOCDELRT. Reviewed by: emaste, dim MFC r314152 (by jkim): Remove an assembler flag, which is redundant since r309124. The upstream took care of it by introducing a macro NO_EXEC_STACK_DIRECTIVE. http://llvm.org/viewvc/llvm-project?rev=273500&view=rev Reviewed by: dim MFC r314564: Upgrade our copies of clang, llvm, lld, lldb, compiler-rt and libc++ to 4.0.0 (branches/release_40 296509). The release will follow soon. Please note that from 3.5.0 onwards, clang, llvm and lldb require C++11 support to build; see UPDATING for more information. Also note that as of 4.0.0, lld should be able to link the base system on amd64 and aarch64. See the WITH_LLD_IS_LLD setting in src.conf(5). Though please be aware that this is work in progress. Release notes for llvm, clang and lld will be available here: <http://releases.llvm.org/4.0.0/docs/ReleaseNotes.html> <http://releases.llvm.org/4.0.0/tools/clang/docs/ReleaseNotes.html> <http://releases.llvm.org/4.0.0/tools/lld/docs/ReleaseNotes.html> Thanks to Ed Maste, Jan Beich, Antoine Brodin and Eric Fiselier for their help. Relnotes: yes Exp-run: antoine PR: 215969, 216008 MFC r314708: For now, revert r287232 from upstream llvm trunk (by Daniil Fukalov): [SCEV] limit recursion depth of CompareSCEVComplexity Summary: CompareSCEVComplexity goes too deep (50+ on a quite a big unrolled loop) and runs almost infinite time. Added cache of "equal" SCEV pairs to earlier cutoff of further estimation. Recursion depth limit was also introduced as a parameter. Reviewers: sanjoy Subscribers: mzolotukhin, tstellarAMD, llvm-commits Differential Revision: https://reviews.llvm.org/D26389 This commit is the cause of excessive compile times on skein_block.c (and possibly other files) during kernel builds on amd64. We never saw the problematic behavior described in this upstream commit, so for now it is better to revert it. An upstream bug has been filed here: https://bugs.llvm.org/show_bug.cgi?id=32142 Reported by: mjg MFC r314795: Reapply r287232 from upstream llvm trunk (by Daniil Fukalov): [SCEV] limit recursion depth of CompareSCEVComplexity Summary: CompareSCEVComplexity goes too deep (50+ on a quite a big unrolled loop) and runs almost infinite time. Added cache of "equal" SCEV pairs to earlier cutoff of further estimation. Recursion depth limit was also introduced as a parameter. Reviewers: sanjoy Subscribers: mzolotukhin, tstellarAMD, llvm-commits Differential Revision: https://reviews.llvm.org/D26389 Pull in r296992 from upstream llvm trunk (by Sanjoy Das): [SCEV] Decrease the recursion threshold for CompareValueComplexity Fixes PR32142. r287232 accidentally increased the recursion threshold for CompareValueComplexity from 2 to 32. This change reverses that change by introducing a separate flag for CompareValueComplexity's threshold. The latter revision fixes the excessive compile times for skein_block.c. MFC r314907 | mmel | 2017-03-08 12:40:27 +0100 (Wed, 08 Mar 2017) | 7 lines Unbreak ARMv6 world. The new compiler_rt library imported with clang 4.0.0 have several fatal issues (non-functional __udivsi3 for example) with ARM specific instrict functions. As temporary workaround, until upstream solve these problems, disable all thumb[1][2] related feature. MFC r315016: Update clang, llvm, lld, lldb, compiler-rt and libc++ to 4.0.0 release. We were already very close to the last release candidate, so this is a pretty minor update. Relnotes: yes MFC r316005: Revert r314907, and pull in r298713 from upstream compiler-rt trunk (by Weiming Zhao): builtins: Select correct code fragments when compiling for Thumb1/Thum2/ARM ISA. Summary: Value of __ARM_ARCH_ISA_THUMB isn't based on the actual compilation mode (-mthumb, -marm), it reflect's capability of given CPU. Due to this: - use __tbumb__ and __thumb2__ insteand of __ARM_ARCH_ISA_THUMB - use '.thumb' directive consistently in all affected files - decorate all thumb functions using DEFINE_COMPILERRT_THUMB_FUNCTION() --------- Note: This patch doesn't fix broken Thumb1 variant of __udivsi3 ! Reviewers: weimingz, rengolin, compnerd Subscribers: aemerson, dim Differential Revision: https://reviews.llvm.org/D30938 Discussed with: mmel
* MFC r314056:asomers2017-04-021-12/+15
| | | | | | | | | | | | | Improve pjdfstest run instructions In the Kyua era, it's no longer necessary to set PJDFSTEST_TEST_PATH. Just use TMPDIR instead. Reviewed by: ngie MFC after: 3 weeks Relnotes: yes Sponsored by: Spectra Logic Corp Differential Revision: https://reviews.freebsd.org/D9340
* MFC r314947:asomers2017-04-011-1/+1
| | | | | | | | Slight rewording in nvme(4) Reviewed by: jimharris, imp MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D9927
* MFC r316061:bapt2017-04-011-8/+59
| | | | Update pci_vendors to 2017-03-16
* MFC r315798:ngie2017-03-301-1/+3
| | | | | | DB_COMMAND(9): fix mandoc markup Start new sentences on new lines.
* Regenerate src.conf(5)ngie2017-03-301-1/+10
| | | | Differential Revision: Dell EMC Isilon
* MFC r315762:ngie2017-03-301-1/+1
| | | | | | rc.conf(5): fix a .Xr call for chroot(8) Add the missing section number to the .Xr call.
* MFC r315795:ngie2017-03-301-2/+2
| | | | | | alq(9): fix mandoc markup Start new sentence on a new line.
* MFC r315803:ngie2017-03-301-3/+3
| | | | | | | memguard(9): fix igor/manlint warnings - Expand a contraction [1]. - Add a missing section number when referring to uma(9) with .Xr .
* MFC r315790:ngie2017-03-301-2/+2
| | | | | | tuning(7): fix SEE ALSO section sorting dummynet(4) should come before eventtimers(4)
* MFC r315788:ngie2017-03-301-3/+3
| | | | | | build(7): sort SEE ALSO section tests(7) should be grouped in the man section 7 group, not the section 8 group.
* MFC r315802:ngie2017-03-301-4/+4
| | | | | | | ifnet(9): fix some igor/manlint warnings - Fix typos (queueing -> queuing) [1]. - Add missing section number for polling .Xr reference [2].
* MFC r315804:ngie2017-03-302-4/+4
| | | | | | | PCI_IOV_*INIT(9): fix make manlint warnings Add missing section number when referring to PCI_IOV_*INIT(9) with .Xr from the other corresponding manpage.
* MFC r315772:ngie2017-03-301-3/+3
| | | | | | | tmpfs(5): fix mdoc warnings - Delete trailing whitespace - Sort SEE ALSO order: mmap(2)'s Xr should come before nmount(2)'s Xr.
* MFC r315789:ngie2017-03-301-3/+4
| | | | | | tests(7): fix mdoc warning Continue sentence in "Configuring the tests" on a new line.
* Backport mlx4{en,ib}(4) from ^/headngie2017-03-303-0/+195
| | | | | | | | | | | MFCing other pieces would be very structurally disruptive. This just brings back the manpages so they can be used by end-users and to ease future backports. svn:mergeinfo omitted, in part because this is a direct commit to ^/stable/11. Sponsored by: Dell EMC Isilon
* Revert r316226 (I used the wrong commit message)ngie2017-03-303-195/+0
| | | | Pointyhat to: ngie
* MFC r315797:ngie2017-03-301-1/+1
| | | | | | | buf_ring(9): fix mandoc markup Remove spurious trailing comma after `buf_ring_peek` in the NAME section.
* MFC r315759,r315761:ngie2017-03-303-0/+195
| | | | | | | | | | | r315759 (by gjb): Add mlx5en(4) to the hardware page. [1] Belatedly bump copyright years after several changes. r315761: Add cxgbe(4), ixl(4), and mlx4en(4) to the hardware release notes
* MFC r316053:ngie2017-03-301-3/+3
| | | | pthread_mutex_consistent: sort SEE ALSO by reference name
OpenPOWER on IntegriCloud