summaryrefslogtreecommitdiffstats
path: root/share
Commit message (Collapse)AuthorAgeFilesLines
* Make libldns and libssh private.des2013-09-081-2/+2
| | | | Approved by: re (blanket)
* Create a private library directory (LIBPRIVATEDIR) for libraries whichdes2013-09-083-20/+39
| | | | | | | | | | | | | | we don't want to expose but which can't or shouldn't be static. To mark a library as private, define PRIVATELIB in its Makefile. It will be installed in LIBPRIVATEDIR, which is normally /usr/lib/private (or /usr/lib32/private for 32-bit libraries on 64-bit platforms). To indicate that a program or library depends on a private library, define USEPRIVATELIB in its Makefile. The correct version of LIBPRIVATEDIR will be added to its run-time library search path. Approved by: re (blanket)
* MFCmarkm2013-09-072-8/+56
|\
| * Regenerate after unhooking gcc/g++ from the default build for some arches.zeising2013-09-061-7/+26
| |
| * Only set -Wno-c++11-extensions if we're building with clang, so bootstrappingtheraven2013-09-061-0/+3
| | | | | | | | clang with gcc doesn't fail.
| * Fix use of MACHINE_ARCH where MACHINE was intended for pc98 detection.theraven2013-09-061-1/+1
| | | | | | | | Reported by: nwhitehorn
| * On platforms where clang is the default compiler, don't build gcc or libstdc++.theraven2013-09-061-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To enable them, set WITH_GCC and WITH_GNUCXX in src.conf. Make clang default to using libc++ on FreeBSD 10. Bumped __FreeBSD_version for the change. GCC is still enabled on PC98, because the PC98 bootloader requires GCC to build (or, at least, hard-codes the use of gcc into its build). Thanks to everyone who helped make the ports tree ready for this (and bapt for coordinating them all). Also to imp for reviewing this and working on the forward-porting of the changes in our gcc so that we're getting to a much better place with regard to external toolchains. Sorry to all of the people who helped who I forgot to mention by name. Reviewed by: bapt, imp, dim, ...
* | MFCmarkm2013-09-069-212/+259
|\ \ | |/
| * Fix a typo.carl2013-09-051-1/+1
| | | | | | | | | | Approved by: jimharris Sponsored by: Intel
| * Add more references.mav2013-09-051-1/+5
| | | | | | | | | | Submitted by: Dmitry Luhtionov <dmitryluhtionov@gmail.com> MFC after: 1 week
| * Add missing '2'.pjd2013-09-051-1/+1
| |
| * Remove trailing comma.pjd2013-09-051-1/+1
| |
| * Add myself as a new committer and cognet as my mentor.zbb2013-09-041-0/+2
| | | | | | | | Approved by: cognet (mentor)
| * Add myself to the list of ports committers.gnn2013-09-041-0/+3
| | | | | | | | Approved by: skreuzer (mentor)
| * add links for the various vmem functions...jmg2013-09-041-0/+7
| |
| * - Add myself as a src committerbr2013-09-041-0/+2
| | | | | | | | | | | | - Note cognet is my mentor Approved by: cognet (mentor)
| * Connect libexecinfo to the buildemaste2013-09-031-0/+1
| | | | | | | | Sponsored by: DARPA, AFRL
| * Since r254974, periodic scripts' period can be configuredjlh2013-09-031-208/+236
| | | | | | | | | | independently. There is no reason to leave their options with the daily ones, so move them to their own section.
* | MFCmarkm2013-09-012-4/+20
|\ \ | |/
| * Bring legacy CAM target implementation back into API/KPI-coherent and evenmav2013-09-011-4/+4
| | | | | | | | | | | | | | | | | | functional state. While CTL is much more superior target from all points, there is no reason why this code should not work. Tested with ahc(4) as target side HBA. MFC after: 2 weeks
| * Import multiqueue VirtIO net driver from my user/bryanv/vtnetmq branchbryanv2013-09-011-0/+16
| | | | | | | | | | | | This is a significant rewrite of much of the previous driver; lots of misc. cleanup was also performed, and support for a few other minor features was also added.
* | MFCmarkm2013-08-311-0/+1
|\ \ | |/
| * mdoc: add missing El.joel2013-08-301-0/+1
| |
* | Remove short-lived idea; thread to harvest (eg) RDRAND enropy into the usual ↵markm2013-08-301-19/+1
| | | | | | | | | | | | harvest queues. It was a nifty idea, but too heavyweight. Submitted by: Arthur Mesh <arthurmesh@gmail.com>
* | MFCmarkm2013-08-3010-121/+298
|\ \ | |/
| * Few more minor if_vmx tweaksbryanv2013-08-301-1/+20
| | | | | | | | | | | | | | - Allow the Rx/Tx queue sizes to be configured by tunables - Bail out earlier if the Tx queue unlikely has enough free descriptors to hold the frame - Cleanup some of the offloading capabilities handling
| * Fix after r255014antoine2013-08-291-4/+1
| |
| * Drop build option switch for the older GNU patch.pfg2013-08-291-1/+0
| | | | | | | | | | | | | | | | As promised, drop the option to make the older GNU patch the default. GNU patch is still being built but something drastic may happen to it to it before Release.
| * Add a simple procdesc(4) man page describing "options PROCDESC" and therwatson2013-08-283-5/+103
| | | | | | | | | | | | | | | | high-level facility, supplementing pdfork(2) and friends. Update capsicum.4 to xref. Suggested by: sbruno MFC after: 3 days
| * mdoc fixjoel2013-08-281-1/+1
| |
| * Really regen after r254962.zeising2013-08-271-7/+4
| | | | | | | | | | | | | | This removes the WITH_BSDCONFIG description alltogether, since this option is removed. At the same time, fix the WITHOUT_LIBCPLUSPLUS option that had gotten inverted.
| * Use .SHELL to tell bmake to use 'set -e' when running scriptssjg2013-08-271-6/+20
| | | | | | | | | | | | | | | | since most FreeBSD makefiles it is in effect. Move the other bmake compatability knobs out of the POSIX block. Reviewed by: obrien
| * Make the period of each periodic security script configurable.jlh2013-08-271-18/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are now six additional variables weekly_status_security_enable weekly_status_security_inline weekly_status_security_output monthly_status_security_enable monthly_status_security_inline monthly_status_security_output alongside their existing daily counterparts. They all have the same default values. All other "daily_status_security_${scriptname}_${whatever}" variables have been renamed to "security_status_${name}_${whatever}". A compatibility shim has been introduced for the old variable names, which we will be able to remove in 11.0-RELEASE. "security_status_${name}_enable" is still a boolean but a new "security_status_${name}_period" allows to define the period of each script. The value is one of "daily" (the default for backward compatibility), "weekly", "monthly" and "NO". Note that when the security periodic scripts are run directly from crontab(5) (as opposed to being called by daily or weekly periodic scripts), they will run unless the test is explicitely disabled with a "NO", either for in the "_enable" or the "_period" variable. When the security output is not inlined, the mail subject has been changed from "$host $arg run output" to "$host $arg $period run output". For instance: myfbsd security run output -> myfbsd security daily run output I don't think this is considered as a stable API, but feel free to correct me if I'm wrong. Finally, I will rearrange periodic.conf(5) and default/periodic.conf to put the security options in their own section. I left them in place for this commit to make reviewing easier. Reviewed by: hackers@
| * Formally remove WITH_BSDCONFIG build option and re-generate src.conf.5dteske2013-08-271-4/+4
| | | | | | | | NOTE: Should have been inline with revisions 252862 and 254958.
| * It was brought to my attention that SVN r252862 was incomplete. It neededdteske2013-08-271-1/+0
| | | | | | | | to also make this change, to completely deprecate WITH_BSDCONFIG.
| * fix up my copyright..jmg2013-08-261-2/+1
| |
| * none of the drivers in the tree support CDIOCCAPABILITY or CDIOCPITCH..jmg2013-08-261-81/+0
| | | | | | | | | | remove the documentation so people won't get confused and think they are supported...
* | MFCmarkm2013-08-263-7/+22
|\ \ | |/
| * Joerg was my mentor way back when...jmg2013-08-261-0/+2
| |
| * Regenerate src.conf.5antoine2013-08-261-7/+19
| |
| * Hook vm_page_busy.9 to the buildantoine2013-08-261-0/+1
| |
* | MFCmarkm2013-08-253-3/+5
|\ \ | |/
| * Remove EOL whitespace.joel2013-08-251-1/+1
| |
| * mdoc fixes.joel2013-08-251-1/+2
| |
| * Fix BUGS section after botched modify in r254772.andre2013-08-241-2/+1
| | | | | | | | Reported by: bjk
| * Rename the kld_unload event handler to kld_unload_try, and add a newmarkj2013-08-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | kld_unload event handler which gets invoked after a linker file has been successfully unloaded. The kld_unload and kld_load event handlers are now invoked with the shared linker lock held, while kld_unload_try is invoked with the lock exclusively held. Convert hwpmc(4) to use these event handlers instead of having kern_kldload() and kern_kldunload() invoke hwpmc(4) hooks whenever files are loaded or unloaded. This has no functional effect, but simplifes the linker code somewhat. Reviewed by: jhb
* | 1) example (partially humorous random_adaptor, that I call "EXAMPLE")markm2013-08-243-1/+119
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * It's not meant to be used in a real system, it's there to show how the basics of how to create interfaces for random_adaptors. Perhaps it should belong in a manual page 2) Move probe.c's functionality in to random_adaptors.c * rename random_ident_hardware() to random_adaptor_choose() 3) Introduce a new way to choose (or select) random_adaptors via tunable "rngs_want" It's a list of comma separated names of adaptors, ordered by preferences. I.e.: rngs_want="yarrow,rdrand" Such setting would cause yarrow to be preferred to rdrand. If neither of them are available (or registered), then system will default to something reasonable (currently yarrow). If yarrow is not present, then we fall back to the adaptor that's first on the list of registered adaptors. 4) Introduce a way where RNGs can play a role of entropy source. This is mostly useful for HW rngs. The way I envision this is that every HW RNG will use this functionality by default. Functionality to disable this is also present. I have an example of how to use this in random_adaptor_example.c (see modload event, and init function) 5) fix kern.random.adaptors from kern.random.adaptors: yarrowpanicblock to kern.random.adaptors: yarrow,panic,block 6) add kern.random.active_adaptor to indicate currently selected adaptor: root@freebsd04:~ # sysctl kern.random.active_adaptor kern.random.active_adaptor: yarrow Submitted by: Arthur Mesh <arthurmesh@gmail.com>
* Adjust for the pfil_func_t typedef added in r254769.andre2013-08-241-4/+4
|
* pfil_hook_get() has been internalized in r254771 and is no longerandre2013-08-241-9/+2
| | | | part of the API. It wasn't safe for external use in any case.
* Add support to physio(9) for devices that don't want I/O split andken2013-08-241-1/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configure sa(4) to request no I/O splitting by default. For tape devices, the user needs to be able to clearly understand what blocksize is actually being used when writing to a tape device. The previous behavior of physio(9) was that it would split up any I/O that was too large for the device, or too large to fit into MAXPHYS. This means that if, for instance, the user wrote a 1MB block to a tape device, and MAXPHYS was 128KB, the 1MB write would be split into 8 128K chunks. This would be done without informing the user. This has suboptimal effects, especially when trying to communicate status to the user. In the event of an error writing to a tape (e.g. physical end of tape) in the middle of a 1MB block that has been split into 8 pieces, the user could have the first two 128K pieces written successfully, the third returned with an error, and the last 5 returned with 0 bytes written. If the user is using a standard write(2) system call, all he will see is the ENOSPC error. He won't have a clue how much actually got written. (With a writev(2) system call, he should be able to determine how much got written in addition to the error.) The solution is to prevent physio(9) from splitting the I/O. The new cdev flag, SI_NOSPLIT, tells physio that the driver does not want I/O to be split beforehand. Although the sa(4) driver now enables SI_NOSPLIT by default, that can be disabled by two loader tunables for now. It will not be configurable starting in FreeBSD 11.0. kern.cam.sa.allow_io_split allows the user to configure I/O splitting for all sa(4) driver instances. kern.cam.sa.%d.allow_io_split allows the user to configure I/O splitting for a specific sa(4) instance. There are also now three sa(4) driver sysctl variables that let the users see some sa(4) driver values. kern.cam.sa.%d.allow_io_split shows whether I/O splitting is turned on. kern.cam.sa.%d.maxio shows the maximum I/O size allowed by kernel configuration parameters (e.g. MAXPHYS, DFLTPHYS) and the capabilities of the controller. kern.cam.sa.%d.cpi_maxio shows the maximum I/O size supported by the controller. Note that a better long term solution would be to implement support for chaining buffers, so that that MAXPHYS is no longer a limiting factor for I/O size to tape and disk devices. At that point, the controller and the tape drive would become the limiting factors. sys/conf.h: Add a new cdev flag, SI_NOSPLIT, that allows a driver to tell physio not to split up I/O. sys/param.h: Bump __FreeBSD_version to 1000049 for the addition of the SI_NOSPLIT cdev flag. kern_physio.c: If the SI_NOSPLIT flag is set on the cdev, return any I/O that is larger than si_iosize_max or MAXPHYS, has more than one segment, or would have to be split because of misalignment with EFBIG. (File too large). In the event of an error, print a console message to give the user a clue about what happened. scsi_sa.c: Set the SI_NOSPLIT cdev flag on the devices created for the sa(4) driver by default. Add tunables to control whether we allow I/O splitting in physio(9). Explain in the comments that allowing I/O splitting will be deprecated for the sa(4) driver in FreeBSD 11.0. Add sysctl variables to display the maximum I/O size we can do (which could be further limited by read block limits) and the maximum I/O size that the controller can do. Limit our maximum I/O size (recorded in the cdev's si_iosize_max) by MAXPHYS. This isn't strictly necessary, because physio(9) will limit it to MAXPHYS, but it will provide some clarity for the application. Record the controller's maximum I/O size reported in the Path Inquiry CCB. sa.4: Document the block size behavior, and explain that the option of allowing physio(9) to split the I/O will disappear in FreeBSD 11.0. Sponsored by: Spectra Logic
OpenPOWER on IntegriCloud