ƒ¹O233675 142 440 949 482 119 462 142 142 121 394 836 279 279 279 351 686 222 119 269 184 651 258 203 263 125 269 137 308 487 99 167 240 240 126 1877 917 723 2098 274 653 1056 774 774 221 221 180 180 1073 1073 429 429 728 728 728 661 119 333 174 121 164 124 184 184 155 155 1073 205 237 237 400 400 134 453 216 178 324 206 206 155 159 111 184 155 199 128 204 848 1581 1636 236 121 316 236 205 209 614 293 188 143 752 207 483 281 301 158 189 202 669 2188 517 326 326 326 351 263 264 263 1029 173 745 151 151 151 163 170 170 170 231 231 570 206 301 352 262 227 310 289 304 304 304 367 367 146 K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-29T18:58:02.411218Z K 7 svn:log V 347 Restore proper use of bounce buffers for ISA DMA. When locking was added, the call to pmap_kextract() was moved up, and as a result the code never updated the physical address to use for DMA if a bounce buffer was used. Restore the earlier location of pmap_kextract() so it takes bounce buffers into account. Tested by: kargl MFC after: 1 week END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-29T19:03:22.358658Z K 7 svn:log V 856 Use a more proper fix for enabling HT MSI mapping windows on Host-PCI bridges. Rather than blindly enabling the windows on all of them, only enable the window when an MSI interrupt is enabled for a device behind the bridge, similar to what already happens for HT PCI-PCI bridges. To implement this, each x86 Host-PCI bridge driver has to be able to locate it's actual backing device on bus 0. For ACPI, use the _ADR method to find the slot and function of the device. For the non-ACPI case, the legacy(4) driver already scans bus 0 looking for Host-PCI bridge devices. Now it saves the slot and function of each bridge that it finds as ivars that the Host-PCI bridge driver can then use in its pcib_map_msi() method. This fixes machines where non-MSI interrupts were broken by the previous round of HT MSI changes. Tested by: bapt MFC after: 1 week END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-03-29T19:26:39.796125Z K 7 svn:log V 388 Revert r233662 and generalize the hack. Writing zero to BAR actually does not disable it and it is even harmful as hselasky found out. Historically, this code was originated from (OLDCARD) CardBus driver and later leaked into PCI driver when CardBus was newbus'ified and refactored with PCI driver. However, it is not really necessary even for CardBus. Reviewed by: hselasky, imp, jhb END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-03-29T19:29:24.547344Z K 7 svn:log V 26 Fix couple of style nits. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-03-29T20:11:16.512886Z K 7 svn:log V 365 If hastd is invoked with "-P pidfile" option always create pidfile regardless of whether -F (foreground) option is set or not. Also, if -P option is specified, ignore pidfile setting from configuration not only on start but on reload too. This fixes the issue when for hastd run with -P option reload caused the pidfile change. Reviewed by: pjd MFC after: 1 week END K 10 svn:author V 4 joel K 8 svn:date V 27 2012-03-29T20:23:35.657418Z K 7 svn:log V 49 Remove unnecessary Xo/Xc. Reviewed by: brueffer END K 10 svn:author V 4 joel K 8 svn:date V 27 2012-03-29T20:55:45.487439Z K 7 svn:log V 49 Fix typo from last commit. Noticed by: brueffer END K 10 svn:author V 6 adrian K 8 svn:date V 27 2012-03-29T21:54:19.867884Z K 7 svn:log V 26 oops, add a missing lock. END K 10 svn:author V 3 dim K 8 svn:date V 27 2012-03-29T23:30:17.285092Z K 7 svn:log V 301 Revert sys/x86/include/endian.h to what it was before r233419, as that revision has two problems: - It can produce worse code with both clang and gcc. - It doesn't fix the actual issue introduced in r232721, which will be fixed in the next commit. Submitted by: bde, tijl and jh Pointy hat to: dim END K 10 svn:author V 3 dim K 8 svn:date V 27 2012-03-29T23:31:48.607871Z K 7 svn:log V 743 Fix an issue introduced in sys/x86/include/endian.h with r232721. In that revision, the bswapXX_const() macros were renamed to bswapXX_gen(). Also, bswap64_gen() was implemented as two calls to bswap32(), and similarly, bswap32_gen() as two calls to bswap16(). This mainly helps our base gcc to produce more efficient assembly. However, the arguments are not properly masked, which results in the wrong value being calculated in some instances. For example, bswap32(0x12345678) returns 0x7c563412, and bswap64(0x123456789abcdef0) returns 0xfcdefc9a7c563412. Fix this by appropriately masking the arguments to bswap16() in bswap32_gen(), and to bswap32() in bswap64_gen(). This should also silence warnings from clang. Submitted by: jh END K 10 svn:author V 6 eadler K 8 svn:date V 27 2012-03-29T23:57:54.078552Z K 7 svn:log V 183 MFC r231300, r231328: Permit the use of relative paths for the prefix argument. Remove an unnecessary cwd from created plists when -p is specified Approved by: cperciva (implicit) END K 10 svn:author V 6 eadler K 8 svn:date V 27 2012-03-29T23:58:16.421355Z K 7 svn:log V 183 MFC r231300, r231328: Permit the use of relative paths for the prefix argument. Remove an unnecessary cwd from created plists when -p is specified Approved by: cperciva (implicit) END K 10 svn:author V 6 eadler K 8 svn:date V 27 2012-03-29T23:59:02.554873Z K 7 svn:log V 183 MFC r231300, r231328: Permit the use of relative paths for the prefix argument. Remove an unnecessary cwd from created plists when -p is specified Approved by: cperciva (implicit) END K 10 svn:author V 7 yongari K 8 svn:date V 27 2012-03-30T04:46:39.302968Z K 7 svn:log V 254 Remove task queue based link state change handler. Driver no longer needs to defer link state handling. While I'm here, mark IFF_DRV_RUNNING before changing media. If link is established without any delay, that link state change handling could be lost. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2012-03-30T05:27:05.904201Z K 7 svn:log V 589 Do not report current link status if driver is not running. This change also workarounds dhclient's link state handling bug by not giving current link status. Unlike other controllers, ale(4)'s PHY hibernation perfectly works such that driver does not see a valid link if the controller is not brought up. If dhclient(8) runs on ale(4) it will blindly waits until link UP and then gives up after 10 seconds. Because dhclient(8) still thinks interface got a valid link when IFM_AVALID is not set for selected media, this change makes dhclient initiate DHCP without waiting for link UP. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2012-03-30T05:40:26.458126Z K 7 svn:log V 125 Merge umtxq_sleep and umtxq_nanosleep into a single function by using an abs_timeout structure which describes timeout info. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2012-03-30T05:49:32.521619Z K 7 svn:log V 23 Remove trailing space. END K 10 svn:author V 3 mav K 8 svn:date V 27 2012-03-30T08:33:08.166256Z K 7 svn:log V 176 Reenable unsolicited responses on CODEC if hdaa_sense_init() called again. This fixes jack connection events handling after suspend/resume. PR: kern/166382 MFC after: 1 week END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2012-03-30T09:03:53.596750Z K 7 svn:log V 88 Fix COMPAT_FREEBSD32 build. Submitted by: Andreas Tobler < andreast at fgznet dot ch > END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-30T09:34:19.756647Z K 7 svn:log V 558 MFC r232831: Add support for preinit, init and fini arrays to rtld. Only binaries marked with proper ABI note gets array ctr/dtrs called. MFC r232856: When iterating over the dso program headers, the object is not initialized yet, and object segments are not yet mapped. Only parse the notes that appear in the first page of the dso (as it should be anyway), and use the preloaded page content. MFC r232857 (by dim): Fix a warning/error with clang. MFC r232859 (by dim): Amend r232857, now dropping the casts entirely, as they were not necessary at all. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-30T09:36:12.358828Z K 7 svn:log V 165 MFC r232861: Provide rtld-private implementations of __stack_chk_guard, __stack_chk_fail() and __chk_fail() symbols, to be used by functions linked from libc_pic.a. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-30T09:37:25.415039Z K 7 svn:log V 110 MFC r232862: Do not use stdio for libmap.conf read. Directly map the file and parse lines from the mappings. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-30T09:38:35.287472Z K 7 svn:log V 170 MFC r232974: Stop using strerror(3) in rtld, which brings in msgcat and stdio. Directly access sys_errlist array of errno messages with private rtld_strerror() function. END K 10 svn:author V 4 joel K 8 svn:date V 27 2012-03-30T12:34:34.917758Z K 7 svn:log V 32 mdoc: terminate quoted strings. END K 10 svn:author V 8 theraven K 8 svn:date V 27 2012-03-30T12:48:36.763975Z K 7 svn:log V 171 Undo the earlier revert of the ABI change in libsupc++. On further discussion, posting an errata notice with 9.1 is the less painful solution. Approved by: dim (mentor) END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2012-03-30T12:57:14.456982Z K 7 svn:log V 41 Remove trailing semicolon, it is a typo. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T15:08:09.111356Z K 7 svn:log V 212 - Remove erroneous trailing semicolon. [1] - Correctly determine the maximum payload size for setting the TX link frequent NACK latency and replay timer thresholds. Submitted by: stefanf [1] MFC after: 3 days END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-03-30T16:32:41.389821Z K 7 svn:log V 393 Work around Erratum 721 for AMD Family 10h and 12h processors. "Under a highly specific and detailed set of internal timing conditions, the processor may incorrectly update the stack pointer after a long series of push and/or near-call instructions, or a long series of pop and/or near-return instructions. The processor must be in 64-bit mode for this erratum to occur." MFC after: 3 days END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-03-30T16:54:21.970549Z K 7 svn:log V 4 MFC END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-03-30T17:03:06.457400Z K 7 svn:log V 74 Re-initialize model-specific MSRs when we resume CPUs. MFC after: 1 week END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-30T17:38:28.279500Z K 7 svn:log V 147 MFC 232669: Use bus_get_dma_tag() to inherit the 4G boundary restriction from the parent PCI bus and remove the home-grown version in this driver. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-30T17:38:57.441775Z K 7 svn:log V 147 MFC 232669: Use bus_get_dma_tag() to inherit the 4G boundary restriction from the parent PCI bus and remove the home-grown version in this driver. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-30T19:10:14.178403Z K 7 svn:log V 34 Move the legacy(4) driver to x86. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-30T19:54:48.128155Z K 7 svn:log V 1783 Fix a few issues with transmit handling in em(4) and igb(4): - Do not define the foo_start() methods or set if_start in the ifnet if multiq transmit is enabled. Also, set if_transmit and if_qflush before ether_ifattach rather than after when multiq transmit is enabled. This helps to ensure that the drivers never try to mix different transmit methods. - Properly restart transmit during resume. igb(4) was not restarting it at all, and em(4) was restarting even if the link was down and was calling the wrong method if multiq transmit was enabled. - Remove all the 'more' handling for transmit completions. Transmit completion processing does not have a processing limit, so it always runs to completion and never has more work to do when it returns. Instead, the previous code was returning 'true' anytime there were packets in the queue that weren't still in the process of being transmitted. The effect was that the driver would continuously reschedule a task to process TX completions in effect running at 100% CPU polling the hardware until it finished transmitting all of the packets in the ring. Now it will just wait for the next TX completion interrupt. - Restart packet transmission when the link becomes active. - Fix the MSI-X queue interrupt handlers to restart packet transmission if there are pending packets in the relevant software queue (IFQ or buf_ring) after processing TX completions. This is the root cause for the OACTIVE hangs as if the MSI-X queue handler drained all the pending packets from the TX ring, nothing would ever restart it. As such, remove some previously-added workarounds to reschedule a task to poll the TX ring anytime OACTIVE was set. Tested by: sbruno Reviewed by: jfv MFC after: 1 week END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-03-30T20:17:39.462504Z K 7 svn:log V 824 Attempt to make machine check handling a bit more robust: - Don't malloc() new MCA records for machine checks logged due to a CMCI or MC# exception. Instead, use a pre-allocated pool of records. When a CMCI or MC# exception fires, schedule a swi to refill the pool. The pool is sized to hold at least one record per available machine bank, and one record per CPU. This should handle the case of all CPUs triggering a single bank at once as well as the case a single CPU triggering all of its banks. The periodic scans still use malloc() since they are run from a safe context. - Since we have to create an swi to handle refills, make the periodic scan a second swi for the same thread instead of having a separate taskqueue thread for the scans. Suggested by: mdf (avoiding malloc()) MFC after: 2 weeks END K 10 svn:author V 3 dim K 8 svn:date V 27 2012-03-30T22:52:08.922258Z K 7 svn:log V 630 Fix the following compilation warning with clang trunk in isci(4): sys/dev/isci/isci_task_request.c:198:7: error: case value not in enumerated type 'SCI_TASK_STATUS' (aka 'enum _SCI_TASK_STATUS') [-Werror,-Wswitch] case SCI_FAILURE_TIMEOUT: ^ This is because the switch is done on a SCI_TASK_STATUS enum type, but the SCI_FAILURE_TIMEOUT value belongs to SCI_STATUS instead. Because the list of SCI_TASK_STATUS values cannot be modified at this time, use the simplest way to get rid of this warning, which is to cast the switch argument to int. No functional change. Reviewed by: jimharris MFC after: 3 days END K 10 svn:author V 8 ambrisko K 8 svn:date V 27 2012-03-30T23:05:48.821369Z K 7 svn:log V 1999 MFhead_mfi r227068 First cut of new HW support from LSI and merge into FreeBSD. Supports Drake Skinny and ThunderBolt cards. MFhead_mfi r227574 Style MFhead_mfi r227579 Use bus_addr_t instead of uintXX_t. MFhead_mfi r227580 MSI support MFhead_mfi r227612 More bus_addr_t and remove "#ifdef __amd64__". MFhead_mfi r227905 Improved timeout support from Scott. MFhead_mfi r228108 Make file. MFhead_mfi r228208 Fixed botched merge of Skinny support and enhanced handling in call back routine. MFhead_mfi r228279 Remove superfluous !TAILQ_EMPTY() checks before TAILQ_FOREACH(). MFhead_mfi r228310 Move mfi_decode_evt() to taskqueue. MFhead_mfi r228320 Implement MFI_DEBUG for 64bit S/G lists. MFhead_mfi r231988 Restore structure layout by reverting the array header to use [0] instead of [1]. MFhead_mfi r232412 Put wildcard pattern later in the match table. MFhead_mfi r232413 Use lower case for hexadecimal numbers to match surrounding style. MFhead_mfi r232414 Add more Thunderbolt variants. MFhead_mfi r232888 Don't act on events prior to boot or when shutting down. Add hw.mfi.detect_jbod_change to enable or disable acting on JBOD type of disks being added on insert and removed on removing. Switch hw.mfi.msi to 1 by default since it works better on newer cards. MFhead_mfi r233016 Release driver lock before taking Giant when deleting children. Use TAILQ_FOREACH_SAFE when items can be deleted. Make code a little simplier to follow. Fix a couple more style issues. MFhead_mfi r233620 Update mfi_spare/mfi_array with the actual number of elements for array_ref and pd. Change these max. #define names to avoid name space collisions. This will require an update to mfiutil It avoids mfiutil having to do a magic calculation. Add a note and #define to state that a "SYSTEM" disk is really what the firmware calls a "JBOD" drive. Thanks to the many that helped, LSI for the initial code drop, mav, delphij, jhb, sbruno that all helped with code and testing. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:24:44.970755Z K 7 svn:log V 178 MFC: r233273 Exclude devices which are mutually exclusive with ATA_CAM. For better or worse, the former are still built as modules as part of the LINT builds. Reviewed by: mav END K 10 svn:author V 8 ambrisko K 8 svn:date V 27 2012-03-30T23:39:39.416820Z K 7 svn:log V 555 MFhead_mfi r233621 Remove the magic mfi_array is 288 bytes and just use the sizeof the array since it is not 288 bytes. Change reporting of a "SYSTEM" disk to "JBOD" to match LSI MegaCli and firmware reporting. This means that fiutil command to "create jbod" is now a little confusing since a RAID per drive is not really what LSI defines JBOD to be. This should be fixed in the future and support added to really create LSI JBOD and enable that feature on cards that support it. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:48:15.631061Z K 7 svn:log V 960 MFC: r226179 Add a "kern.features.ata_cam" sysctl in the kernel when the ATA_CAM kernel option is defined. This sysctl can be queried by feature_present(3). Query for this feature in /sbin/atacontrol and /usr/sbin/burncd. If these utilities detect that ATA_CAM is enabled, then these utilities will error out. These utilities are compatible with the old ATA driver, but are incomptible with the new ATA_CAM driver. By erroring out, we give end-users an idea as to what remedies to use, and reduce the need for them to file PR's. For atacontrol, camcontrol must be used instead, and for burncd, alternative utilties from the ports collection must be used such as sysutils/cdrtools. In future, maybe someone can re-write burncd to work with ATA_CAM, but at least for now, we give a somewhat useful error message to end users. PR: 160979 Reviewed by: jh, Arnaud Lacombe Reported by: Joe Barbish END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:50:16.214134Z K 7 svn:log V 678 MFC: r233274 Remove remnants of ATA_LOCKING uses in the ATA_CAM case and wrap it along with functions, SYSCTLs and tunables that are not used with ATA_CAM in #ifndef ATA_CAM, similar to the existing #ifdef'ed ATA_CAM code for the other way around. This makes it easier to understand which parts of ata(4) actually are used in the new world order and to later on remove the !ATA_CAM bits. It also makes it obvious that there is something fishy with the C-bus front-end as well as in the ATP850 support, as these used ATA_LOCKING which is defunct in the ATA_CAM case. When fixing the former, ATA_LOCKING probably needs to be brought back in some form or other. Reviewed by: mav END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:50:26.239165Z K 7 svn:log V 678 MFC: r233274 Remove remnants of ATA_LOCKING uses in the ATA_CAM case and wrap it along with functions, SYSCTLs and tunables that are not used with ATA_CAM in #ifndef ATA_CAM, similar to the existing #ifdef'ed ATA_CAM code for the other way around. This makes it easier to understand which parts of ata(4) actually are used in the new world order and to later on remove the !ATA_CAM bits. It also makes it obvious that there is something fishy with the C-bus front-end as well as in the ATP850 support, as these used ATA_LOCKING which is defunct in the ATA_CAM case. When fixing the former, ATA_LOCKING probably needs to be brought back in some form or other. Reviewed by: mav END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:56:16.652392Z K 7 svn:log V 125 MFC: r233282 - First pass at const'ifying ata(4) as appropriate. - Use DEVMETHOD_END. - Use NULL instead of 0 for pointers. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-30T23:56:19.931331Z K 7 svn:log V 125 MFC: r233282 - First pass at const'ifying ata(4) as appropriate. - Use DEVMETHOD_END. - Use NULL instead of 0 for pointers. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:07:53.987281Z K 7 svn:log V 85 MFC: r233287 Use the common/shared CRC-32 implementation instead of duplicating it. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:07:54.633172Z K 7 svn:log V 85 MFC: r233287 Use the common/shared CRC-32 implementation instead of duplicating it. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:10:16.997754Z K 7 svn:log V 977 MFC: r233403, r233404 - Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So rename the macros not present in mpi_cnfg.h to match the naming scheme in the latter and but suffix them with a _FB in order to not cause conflicts. - Like mpt_set_config_regs(), comment out mpt_read_config_regs() as the content of the registers read isn't actually used and both functions aren't exactly up to date regarding the possible layouts of the BARs (these function might be helpful for debugging though, so don't remove them completely). - Use DEVMETHOD_END. - Use NULL rather than 0 for pointers. - Remove an unusual check for the softc being NULL. - Remove redundant zeroing of the softc. - Remove an overly banal and actually partly incorrect as well as partly outdated comment regarding the allocation of the memory resource. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:10:17.766161Z K 7 svn:log V 977 MFC: r233403, r233404 - Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So rename the macros not present in mpi_cnfg.h to match the naming scheme in the latter and but suffix them with a _FB in order to not cause conflicts. - Like mpt_set_config_regs(), comment out mpt_read_config_regs() as the content of the registers read isn't actually used and both functions aren't exactly up to date regarding the possible layouts of the BARs (these function might be helpful for debugging though, so don't remove them completely). - Use DEVMETHOD_END. - Use NULL rather than 0 for pointers. - Remove an unusual check for the softc being NULL. - Remove redundant zeroing of the softc. - Remove an overly banal and actually partly incorrect as well as partly outdated comment regarding the allocation of the memory resource. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:13:41.122860Z K 7 svn:log V 333 MFC: r233421 Given that this is a host-PCI-Express bridge driver, create the parent DMA tag with a 4 GB boundary as required by PCI-Express. With r232403 (MFC'ed to stable/9 in r233393) in place this actually is redundant. However, the host-PCI-Express bridge driver is the more appropriate place for implementing this restriction. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T00:13:46.343989Z K 7 svn:log V 333 MFC: r233421 Given that this is a host-PCI-Express bridge driver, create the parent DMA tag with a 4 GB boundary as required by PCI-Express. With r232403 (MFC'ed to stable/8 in r233394) in place this actually is redundant. However, the host-PCI-Express bridge driver is the more appropriate place for implementing this restriction. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T01:21:46.727139Z K 7 svn:log V 632 MFC: r233423 Initialize the mutexes used for the NVM and the swflag as MTX_DUPOK in order to avoid otherwise harmless witness warnings when these are acquired at the same time and due to both using MTX_NETWORK_LOCK as their type. The right fix actually would be to use different, descriptive types for these. However, the latter would require undesirable changes to the shared code base. Another approach would be to just supply NULL as the type, which was deemed as less desirable though as it would cause the unique but cryptic name also to be used for the type and to diverge from the type used by other network device drivers. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T01:21:53.647663Z K 7 svn:log V 632 MFC: r233423 Initialize the mutexes used for the NVM and the swflag as MTX_DUPOK in order to avoid otherwise harmless witness warnings when these are acquired at the same time and due to both using MTX_NETWORK_LOCK as their type. The right fix actually would be to use different, descriptive types for these. However, the latter would require undesirable changes to the shared code base. Another approach would be to just supply NULL as the type, which was deemed as less desirable though as it would cause the unique but cryptic name also to be used for the type and to diverge from the type used by other network device drivers. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T01:21:54.947387Z K 7 svn:log V 632 MFC: r233423 Initialize the mutexes used for the NVM and the swflag as MTX_DUPOK in order to avoid otherwise harmless witness warnings when these are acquired at the same time and due to both using MTX_NETWORK_LOCK as their type. The right fix actually would be to use different, descriptive types for these. However, the latter would require undesirable changes to the shared code base. Another approach would be to just supply NULL as the type, which was deemed as less desirable though as it would cause the unique but cryptic name also to be used for the type and to diverge from the type used by other network device drivers. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-31T06:44:48.069762Z K 7 svn:log V 568 MFC r233100: In vm_object_page_clean(), do not clean OBJ_MIGHTBEDIRTY object flag if the filesystem performed short write and we are skipping the page due to this. Propogate write error from the pager back to the callers of vm_pageout_flush(). Report the failure to write a page from the requested range as the FALSE return value from vm_object_page_clean(), and propagate it back to msync(2) to return EIO to usermode. While there, convert the clearobjflags variable in the vm_object_page_clean() and arguments of the helper functions to boolean. PR: kern/165927 END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2012-03-31T06:48:41.317654Z K 7 svn:log V 23 Remove stale comments. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-31T06:50:27.849106Z K 7 svn:log V 240 MFC r233101: Add sysctl vfs.nfs.nfs_keep_dirty_on_error to switch the nfs client behaviour on error from write RPC back to behaviour of old nfs client. When set to not zero, the pages for which write failed are kept dirty. PR: kern/165927 END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-31T06:53:52.273837Z K 7 svn:log V 82 MFC r233102: Do not claim that msync(2) is obsoleted. Document EIO from msync(2). END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-03-31T06:58:16.572409Z K 7 svn:log V 29 MFC r233607: Update comment. END K 10 svn:author V 4 joel K 8 svn:date V 27 2012-03-31T07:08:35.960595Z K 7 svn:log V 71 mdoc: use It for each item in the list and separate each cell with Ta. END K 10 svn:author V 4 joel K 8 svn:date V 27 2012-03-31T07:10:16.939338Z K 7 svn:log V 31 Remove end of line whitespace. END K 10 svn:author V 8 bschmidt K 8 svn:date V 27 2012-03-31T08:44:27.151898Z K 7 svn:log V 87 MFC r233328,r233382: Fix incorrect parameter usage. Submitted by: Monthadar Al Jaberi END K 10 svn:author V 8 bschmidt K 8 svn:date V 27 2012-03-31T08:46:11.102866Z K 7 svn:log V 87 MFC r233328,r233382: Fix incorrect parameter usage. Submitted by: Monthadar Al Jaberi END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:20:48.306324Z K 7 svn:log V 60 MFC: r233426 Add QGE-X to the list of known-working cards. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:20:50.367807Z K 7 svn:log V 60 MFC: r233426 Add QGE-X to the list of known-working cards. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:25:16.822239Z K 7 svn:log V 977 MFC: r233403, r233404 - Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So rename the macros not present in mpi_cnfg.h to match the naming scheme in the latter and but suffix them with a _FB in order to not cause conflicts. - Like mpt_set_config_regs(), comment out mpt_read_config_regs() as the content of the registers read isn't actually used and both functions aren't exactly up to date regarding the possible layouts of the BARs (these function might be helpful for debugging though, so don't remove them completely). - Use DEVMETHOD_END. - Use NULL rather than 0 for pointers. - Remove an unusual check for the softc being NULL. - Remove redundant zeroing of the softc. - Remove an overly banal and actually partly incorrect as well as partly outdated comment regarding the allocation of the memory resource. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:26:58.237444Z K 7 svn:log V 109 MFC: r233425 Consistently update to the MPI header set version 01.05.20 after r224761. Requested by: mjacob END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:27:00.449916Z K 7 svn:log V 141 MFC: r233425 Consistently update to the MPI header set version 01.05.20 after r224761 (MFC'ed to stable/8 in r224820). Requested by: mjacob END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:29:20.704222Z K 7 svn:log V 141 MFC: r233425 Consistently update to the MPI header set version 01.05.20 after r224761 (MFC'ed to stable/2 in r224821). Requested by: mjacob END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:47:34.985468Z K 7 svn:log V 304 MFC: r233427 Add cas(4), gem(4) and hme(4) to x86 GENERICs as suggested by netchild@ in <20120222095239.Horde.0hpYHJjmRSRPRKzXsoFRbYk@webmail.leidinger.net>. According to some private emails received, it apparently is not unpopular to use at least Quad GigaSwift cards driven by cas(4) in x86 machines. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T10:47:40.776765Z K 7 svn:log V 304 MFC: r233427 Add cas(4), gem(4) and hme(4) to x86 GENERICs as suggested by netchild@ in <20120222095239.Horde.0hpYHJjmRSRPRKzXsoFRbYk@webmail.leidinger.net>. According to some private emails received, it apparently is not unpopular to use at least Quad GigaSwift cards driven by cas(4) in x86 machines. END K 10 svn:author V 7 glebius K 8 svn:date V 27 2012-03-31T11:20:48.475322Z K 7 svn:log V 38 Don't check malloc(M_WAITOK) results. END K 10 svn:author V 3 mav K 8 svn:date V 27 2012-03-31T11:23:09.896542Z K 7 svn:log V 360 Be more conservative in using READ CAPACITY(16) command. Previous code checked PROTECT bit in INQUIRY data for all SPC devices, while it is defined only since SPC-3. But there are some SPC-2 USB devices were reported, that have PROTECT bit set, return no error for READ CAPACITY(16) command, but return wrong sector count value in response. MFC after: 3 days END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T13:56:24.027974Z K 7 svn:log V 120 Fix panic on kernel traps having a mapping in trap_sig b0rked in r206086. Repored by: David E. Cross MFC after: 3 days END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-03-31T14:03:16.834398Z K 7 svn:log V 83 Remove checks that are redundant due to tf_type being unsigned. MFC after: 3 days END K 10 svn:author V 8 theraven K 8 svn:date V 27 2012-03-31T14:25:12.013810Z K 7 svn:log V 226 Make libsupc++ build as a shared library and make libstdc++ a filter library for it. This allows people to swap out libsupc++ for libcxxrt easily, so we can begin the libstdc++ -> libc++ migration. Approved by: dim (mentor) END K 10 svn:author V 3 alc K 8 svn:date V 27 2012-03-31T17:47:50.455512Z K 7 svn:log V 113 MFC r233256 Eliminate vm.pmap.shpgperproc and vm.pmap.pv_entry_max because they no longer serve any purpose. END K 10 svn:author V 3 alc K 8 svn:date V 27 2012-03-31T18:29:24.518506Z K 7 svn:log V 113 MFC r233256 Eliminate vm.pmap.shpgperproc and vm.pmap.pv_entry_max because they no longer serve any purpose. END K 10 svn:author V 6 andrew K 8 svn:date V 27 2012-04-01T01:14:05.001380Z K 7 svn:log V 60 Remove a file that should have been deleted in the last IFC END K 10 svn:author V 6 andrew K 8 svn:date V 27 2012-04-01T06:31:57.417240Z K 7 svn:log V 64 Revert to the libc softfloat. Other parts of libc depend on it. END K 10 svn:author V 8 andreast K 8 svn:date V 27 2012-04-01T08:14:50.959292Z K 7 svn:log V 14 IFC @ r233751 END K 10 svn:author V 2 jh K 8 svn:date V 27 2012-04-01T08:40:52.839774Z K 7 svn:log V 93 MFC r232450: Use snprintf(3) constantly when generating CAM error messages. PR: bin/57088 END K 10 svn:author V 6 andrew K 8 svn:date V 27 2012-04-01T08:58:21.096716Z K 7 svn:log V 60 Use the correct C++ exception and unwind support for AEABI. END K 10 svn:author V 8 theraven K 8 svn:date V 27 2012-04-01T09:35:23.337330Z K 7 svn:log V 101 Bump __FreeBSD_version for xlocale cleanup, as requested by ports people. Approved by: dim (mentor) END K 10 svn:author V 6 andrew K 8 svn:date V 27 2012-04-01T09:38:22.120215Z K 7 svn:log V 33 Add files missed in the last IFC END K 10 svn:author V 5 kevlo K 8 svn:date V 27 2012-04-01T15:05:15.505857Z K 7 svn:log V 109 MFC r233121: Repair function when used with large scales Submitted by: AIDA Shinra END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-01T18:22:48.913576Z K 7 svn:log V 755 Export some more useful info about shared memory objects to userland via procstat(1) and fstat(1): - Change shm file descriptors to track the pathname they are associated with and add a shm_path() method to copy the path out to a caller-supplied buffer. - Use the fo_stat() method of shared memory objects and shm_path() to export the path, mode, and size of a shared memory object via struct kinfo_file. - Add a struct shmstat to the libprocstat(3) interface along with a procstat_get_shm_info() to export the mode and size of a shared memory object. - Change procstat to always print out the path for a given object if it is valid. - Teach fstat about shared memory objects and to display their path, mode, and size. MFC after: 2 weeks END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-01T20:53:35.579094Z K 7 svn:log V 1483 MFC r229667, r230541, r230869, r231909, r231910, r231911, r231912: r229667, r230541, r230869 (ghelmer): Change the notes about the pidfile to include Doug's preference for pre-creating the pidfile with appropriate owner and permissions. Requested by dougb r231909: The pidfile_open(3) is going to be fixed to set close-on-exec in order not to leak the descriptor after exec(3). This raises the issue for daemon(3) of the pidfile lock to be lost when the child process executes. To solve this and also to have the pidfile cleaned up when the program exits, if a pidfile is specified, spawn a child to exec the command and wait in the parent keeping the pidfile locked until the child process exits and remove the file. Reported by: Andrey Zonov Suggested by: pjd Reviewed by: pjd r231910: If the supervising process receives SIGTERM, forward it to the spawned process. Normally it will cause the child to exit followed by the termination of the supervisor after removing the pidfile. This looks like desirable behavior, because termination of a supervisor usually supposes termination of its charge. Also it will fix the issue with stale pid files after reboot due to init kills a supervisor before its child exits. r231911: Add -r option to restart the program if it has been terminated. Suggested by: Andrey Zonov r231912: If permitted protect the supervisor against pageout kill. Suggested by: Andrey Zonov END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-01T20:56:07.800086Z K 7 svn:log V 1538 MFC r208190, r229667, r230541, r230869, r231909, r231910, r231911, r231912: r208190 (ivoras): Slightly improve wording. r229667, r230541, r230869 (ghelmer): Change the notes about the pidfile to include Doug's preference for pre-creating the pidfile with appropriate owner and permissions. Requested by dougb r231909: The pidfile_open(3) is going to be fixed to set close-on-exec in order not to leak the descriptor after exec(3). This raises the issue for daemon(3) of the pidfile lock to be lost when the child process executes. To solve this and also to have the pidfile cleaned up when the program exits, if a pidfile is specified, spawn a child to exec the command and wait in the parent keeping the pidfile locked until the child process exits and remove the file. Reported by: Andrey Zonov Suggested by: pjd Reviewed by: pjd r231910: If the supervising process receives SIGTERM, forward it to the spawned process. Normally it will cause the child to exit followed by the termination of the supervisor after removing the pidfile. This looks like desirable behavior, because termination of a supervisor usually supposes termination of its charge. Also it will fix the issue with stale pid files after reboot due to init kills a supervisor before its child exits. r231911: Add -r option to restart the program if it has been terminated. Suggested by: Andrey Zonov r231912: If permitted protect the supervisor against pageout kill. Suggested by: Andrey Zonov END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-01T20:57:04.021188Z K 7 svn:log V 143 MFC r232828: ELF image can have several PT_NOTE program headers. Look for the ELF brand note in each header, instead of using only first one. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-01T21:08:56.040063Z K 7 svn:log V 29 MFC r233607: Update comment. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-01T21:13:13.334625Z K 7 svn:log V 223 MFC r233101: Add sysctl vfs.nfs.nfs_keep_dirty_on_error to switch the nfs client behaviour on error from write RPC back to behaviour of old nfs client. When set to not zero, the pages for which write failed are kept dirty. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-01T21:35:34.500257Z K 7 svn:log V 143 MFC r232828: ELF image can have several PT_NOTE program headers. Look for the ELF brand note in each header, instead of using only first one. END K 10 svn:author V 5 gonzo K 8 svn:date V 27 2012-04-02T00:11:26.204521Z K 7 svn:log V 110 Remove extra semicolon which rendered condition useless Submitted by: Stefan Farfelder END K 10 svn:author V 8 ambrisko K 8 svn:date V 27 2012-04-02T02:22:22.128908Z K 7 svn:log V 111 Change typedef atomic_t to struct mfi_atomic to avoid name space collision and some couple more style changes. END K 10 svn:author V 7 delphij K 8 svn:date V 27 2012-04-02T07:18:31.301724Z K 7 svn:log V 517 MFC r227802: Improve the way to calculate available pages in tmpfs: - Don't deduct wired pages from total usable counts because it does not make any sense. To make things worse, on systems where swap size is smaller than physical memory and use a lot of wired pages (e.g. ZFS), tmpfs can suddenly have free space of 0 because of this; - Count cached pages as available; [1] - Don't count inactive pages as available, technically we could but that might be too aggressive; [1] [1] Suggested by kib@ END K 10 svn:author V 7 delphij K 8 svn:date V 27 2012-04-02T07:42:17.777182Z K 7 svn:log V 196 Eliminate two cases of unwanted strncpy(). The name is not required by the current code, and the results would get overwritten anyway by subsequent memset(). Reviewed by: ume MFC after: 1 month END K 10 svn:author V 8 hselasky K 8 svn:date V 27 2012-04-02T07:51:30.971580Z K 7 svn:log V 91 Add definitions and structures for USB 2.0 Link Power Management, LPM. MFC after: 2 weeks END K 10 svn:author V 6 ivoras K 8 svn:date V 27 2012-04-02T10:24:50.625644Z K 7 svn:log V 48 Merge r233506: MySQL port 3306 in /etc/services END K 10 svn:author V 7 glebius K 8 svn:date V 27 2012-04-02T10:44:25.009769Z K 7 svn:log V 655 Historically arp(8) did a route lookup for the entry it is about to add, and failed if it exist and had invalid data link type. Later on, in r201282, this check morphed to other code, but message "proxy entry exists for non 802 device" still left, and now it is printed in a case if route prefix found is equal to current address being added. In other words, when we are trying to add ARP entry for a network address. The message is absolutely unrelated and disappointing in this case. I don't see anything bad with setting ARP entries for network addresses. While useless in usual network, in a /31 RFC3021 it may be necessary. This, remove this code. END K 10 svn:author V 8 hselasky K 8 svn:date V 27 2012-04-02T10:50:42.602539Z K 7 svn:log V 109 Fix compiler warnings, mostly signed issues, when USB modules are compiled with WARNS=9. MFC after: 1 weeks END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-02T11:27:20.929841Z K 7 svn:log V 390 MFC r233168: If we ever allow for managed fictitious pages, the pages shall be excluded from superpage promotions. At least one of the reason is that pv_table is sized for non-fictitious pages only. Consistently check for the page to be non-fictitious before accesing superpage pv list. MFC note: erronous chunks from r233168 which were fixed in r233185 are not included into the merge. END K 10 svn:author V 8 jchandra K 8 svn:date V 27 2012-04-02T11:41:33.241878Z K 7 svn:log V 183 Reinstate the XTLB handler for CPU_NLM and CPU_RMI These platforms set the KX bit even when booted in 32 bit mode. So the XLTB handler is needed even when __mips_n64 is not defined. END K 10 svn:author V 3 kan K 8 svn:date V 27 2012-04-02T11:50:14.471204Z K 7 svn:log V 208 Do not try to adjust stacks if dlopen_object is called too early. This is a follow-up to r233231, which fixed similar issue with object initialization code. Reviewed by: kib MFC after: 1 week (with 233231) END K 10 svn:author V 3 kan K 8 svn:date V 27 2012-04-02T11:59:13.323766Z K 7 svn:log V 66 Remove extra blank line from revious commit. Submitted by: trema END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2012-04-02T12:00:35.424042Z K 7 svn:log V 89 Turn off WITNESS, etc. for GENERIC64. This was missed in the stable/9 branch in r226405. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T14:52:28.435514Z K 7 svn:log V 109 MFC 233256: Eliminate vm.pmap.shpgperproc and vm.pmap.pv_entry_max because they no longer serve any purpose. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T15:07:22.082556Z K 7 svn:log V 576 Make machine check exception logging more readable. On newer Intel systems, an uncorrected ECC error tends to fire on all CPUs in a package simultaneously and the current printf hacks are not sufficient to make the messages legible. Instead, use the existing mca_lock spinlock to serialize calls to mca_log() and change the machine check code to panic directly when an unrecoverable error is encoutered rather than falling back to a trap_fatal() call in trap() (which adds nearly a screen-full of logging messages that aren't useful for machine checks). MFC after: 2 weeks END K 10 svn:author V 7 glebius K 8 svn:date V 27 2012-04-02T16:13:54.856063Z K 7 svn:log V 2090 Major step in making pf more SMP friendly. Lots of changes, that depend on each other, thus this commit couldn't be effectively split. - The RB-tree for states dropped, a hash introduced instead. Locking is per hash slot. Hash function is cheap here, it is (id % hashsize), thus slot mutex is also used to lock all states inside the slot. - The RB-tree for state keys dropped, a hash introduced instead. Locking is per hash slot. Lock order is "key hash lock", then "id hash lock". - The global list of states dropped. Traversing ID hash slots used instead. - Introduce state referencing. ID hash, pfsync, keys, each give state a reference. - pf_find_state(), pf_find_state_byid() return locked on success. - pf_unlink_state() actually frees the state, if we got the last reference. - pf_purge_expired_states() processes fraction of ID hash each second. Black magic with sx(9) lock removed. - pfsync_state_in_use() axed, generic referencing used. - The key-to-key pointer sk->reverse is temporarily disabled. Enabling it introduces LORs difficult to deal with. Also disabling it removes the m_addr_changed() hack from the TCP/IP stack. Re-introducing of this optimization should be reconsidered later. - Start on better locking in pfioctl(): acquire PF_LOCK() separately for each command, so that we can unlock them one by one, as well as work on using M_WAITOK and don't interlock for copyout(). For now the only polished command is DIOCGETSTATES. - Move some pf(4) initialization from pf_ioctl.c to pf.c, making them static. I believe only the ioctl stuff should belong to pf_ioctl.c. And probably lots of smaller changes not directly related to the above idea. I'm sorry. This code hasn't been properly tested. I just feed my test box via pfsync(4) with some live data, while the port on switch is in monitor mode, and monitors live pfsync vlan. The test box isn't forwarding anything, except its own traffic. The entire pf is still running under "pf Giant lock", since there are a lot of other things that should be locked before we can remove it. END K 10 svn:author V 8 andreast K 8 svn:date V 27 2012-04-02T16:26:32.587028Z K 7 svn:log V 419 - Write the ISO9660 descriptor after the apm partition entries. - Fill the needed pmPartStatus flags. At least the OpenBIOS implementation relies on these flags. This commit fixes the panic seen on OS-X when inserting a FreeBSD/ppc disc. Additionally OpenBIOS recognizes the partition where the boot code is located. This lets us load a FreeBSD/ppc PowerMac kernel inside qemu. PR: powerpc/162091 MFC after: 1 week END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:30:13.483161Z K 7 svn:log V 227 MFC r233622: Ensure consistent target IDs for direct-attached devices. Sponsored by: Intel Reported by: sbruno, Ravi Pokala Tested by: Ravi Pokala Approved by: sbruno END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:31:53.890184Z K 7 svn:log V 227 MFC r233622: Ensure consistent target IDs for direct-attached devices. Sponsored by: Intel Reported by: sbruno, Ravi Pokala Tested by: Ravi Pokala Approved by: sbruno END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:33:07.606534Z K 7 svn:log V 227 MFC r233622: Ensure consistent target IDs for direct-attached devices. Sponsored by: Intel Reported by: sbruno, Ravi Pokala Tested by: Ravi Pokala Approved by: sbruno END K 10 svn:author V 2 jh K 8 svn:date V 27 2012-04-02T16:33:21.658643Z K 7 svn:log V 259 - Use more natural ip->i_flags instead of vap->va_flags in the final flags check. - Add a comment for the immutable/append check done after handling of the flags. - Style improvements. No functional change intended. Submitted by: bde MFC after: 2 weeks END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:35:42.902840Z K 7 svn:log V 164 MFC r233663: Fix bug where isci(4) would report only 15 bytes of returned data on a READ_CAP_16 command to a SATA target. Sponsored by: Intel Approved by: sbruno END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:36:44.541657Z K 7 svn:log V 165 MFC r233663: Fix bug where isci(4) would report only 15 bytes of returned data on a READ_CAP_16 comnmand to a SATA target. Sponsored by: Intel Approved by: sbruno END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-04-02T16:37:46.440742Z K 7 svn:log V 164 MFC r233663: Fix bug where isci(4) would report only 15 bytes of returned data on a READ_CAP_16 command to a SATA target. Sponsored by: Intel Approved by: sbruno END K 10 svn:author V 5 gibbs K 8 svn:date V 27 2012-04-02T16:50:48.921930Z K 7 svn:log V 934 MFC Revision 233465 Correct failure to attach the PV block front device on Citrix XenServer configurations that advertise the multi-page ring extension, but only allow a single page of ring space. sys/dev/xen/blkfront/blkfront.c: If only one page of ring space is being used, do not publish in the XenStore the number of pages in use (1), via either of the supported multi-page ring extension schemes. Single page operation is the same with or without the ring-page extension being negotiated. Relying on the legacy behavior avoids an incompatible difference in how the two ring-page extension schemes that are out in the wild deal with the base case of a single page. The Amazon/Red Hat drivers use the same XenStore variable as if the extension was not negotiated. The Citrix drivers assume the new ring reference XenStore variables will be available. Reported by: Oliver Schonefeld END K 10 svn:author V 6 jilles K 8 svn:date V 27 2012-04-02T17:16:24.825317Z K 7 svn:log V 78 sh: Fix build with -DDEBUG=2. Reported by: Kristof Provost MFC after: 1 week END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T17:26:21.067492Z K 7 svn:log V 652 Further tweak the changes made in r233709. The kernel doesn't permit sleeping from a swi handler (even though in this case it would be ok), so switch the refill and scanning SWI handlers to being tasks on a fast taskqueue. Also, only schedule the refill task for a CMCI as an MC# can fire at any time, so it should do the minimal amount of work needed and avoid opportunities to deadlock before it panics (such as scheduling a task it won't ever need in practice). To handle the case of an MC# only finding recoverable errors (which should never happen), always try to refill the event free list when the periodic scan executes. MFC after: 2 weeks END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T17:33:46.657785Z K 7 svn:log V 58 MFC: r233619 Add a PNP ID for Japanese 106-key keyboard. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T17:34:50.547709Z K 7 svn:log V 58 MFC: r233619 Add a PNP ID for Japanese 106-key keyboard. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T17:35:26.216126Z K 7 svn:log V 58 MFC: r233619 Add a PNP ID for Japanese 106-key keyboard. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T18:13:29.257970Z K 7 svn:log V 70 MFC: r232416, r232561 Add VESA option to GENERIC for amd64 and i386. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T18:17:51.824898Z K 7 svn:log V 77 MFC: r233702 Work around Erratum 721 for AMD Family 10h and 12h processors. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T18:27:06.492621Z K 7 svn:log V 77 MFC: r233702 Work around Erratum 721 for AMD Family 10h and 12h processors. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-04-02T18:31:01.362607Z K 7 svn:log V 77 MFC: r233702 Work around Erratum 721 for AMD Family 10h and 12h processors. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T18:52:52.127034Z K 7 svn:log V 134 MFC r231976: unp_connect() may use a shared lock on the vnode to fetch the socket. Suggested by: jhb Reviewed by: jhb, kib, rwatson END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T18:54:10.515138Z K 7 svn:log V 134 MFC r231976: unp_connect() may use a shared lock on the vnode to fetch the socket. Suggested by: jhb Reviewed by: jhb, kib, rwatson END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T19:01:32.785145Z K 7 svn:log V 473 MFC r232152: When detaching a unix domain socket, uipc_detach() checks unp->unp_vnode pointer to detect if there is a vnode associated with (binded to) this socket and does necessary cleanup if there is. The issue is that after forced unmount this check may be too late as the unp_vnode is reclaimed and the reference is stale. To fix this provide a helper function that is called on a socket vnode reclamation to do necessary cleanup. Pointed by: kib Reviewed by: kib END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T19:06:28.379103Z K 7 svn:log V 109 MFC r231975: Make vnode_if.awk parse vnode operations with underscores, like VOP_FOO_BAR. Reviewed by: kib END K 10 svn:author V 8 ambrisko K 8 svn:date V 27 2012-04-02T19:13:02.538712Z K 7 svn:log V 203 Move struct megasas_sge from mfi_ioctl.h to mfivar.h so we can remove including machine/bus.h. Add some more mfi_ prefixes to avoid name space pollution. This should address the last tinderbox issues. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T19:15:32.121904Z K 7 svn:log V 255 MFC r232181, r232455: r232181: Add sysctl to retrieve or set umask of another process. Submitted by: Dmitry Banschikov Discussed with: kib, rwatson Reviewed by: kib r232455: Make kern.proc.umask sysctl readonly. Requested by: src END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-04-02T19:17:01.855966Z K 7 svn:log V 165 MFC r232182: When displaying security credential information show also process umask. Submitted by: Dmitry Banschikov Discussed with: rwatson END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-02T19:34:56.653043Z K 7 svn:log V 134 Add helper function to remove the process from the orphans list and use it instead of inlined code. Tested by: pho MFC after: 3 days END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-04-02T19:35:36.486983Z K 7 svn:log V 217 When process exists, not only the children shall be reparented to init, but also the orphans shall be removed from the orphan list, because the list header is destroyed. Reported and tested by: pho MFC after: 3 days END K 10 svn:author V 3 gnn K 8 svn:date V 27 2012-04-02T20:10:50.820481Z K 7 svn:log V 196 MFC: 232612 Properly mask off bits that are not supported in the IAP counters. This fixes a bug where users would see massively large counts, near to 2**64 -1, due to the bits not being cleared. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-04-02T20:14:32.801919Z K 7 svn:log V 208 MFC: r233701 - Remove erroneous trailing semicolon. [1] - Correctly determine the maximum payload size for setting the TX link frequent NACK latency and replay timer thresholds. Submitted by: stefanf [1] END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-04-02T20:14:40.633841Z K 7 svn:log V 208 MFC: r233701 - Remove erroneous trailing semicolon. [1] - Correctly determine the maximum payload size for setting the TX link frequent NACK latency and replay timer thresholds. Submitted by: stefanf [1] END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-04-02T20:14:51.763529Z K 7 svn:log V 208 MFC: r233701 - Remove erroneous trailing semicolon. [1] - Correctly determine the maximum payload size for setting the TX link frequent NACK latency and replay timer thresholds. Submitted by: stefanf [1] END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T20:34:15.711559Z K 7 svn:log V 274 MFC 232700: Add a new sched_clear_name() method to the scheduler interface to clear the cached name used for KTR_SCHED traces when a thread's name changes. This way KTR_SCHED traces (and thus schedgraph) will notice when a thread's name changes, most commonly via execve(). END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T20:34:41.497159Z K 7 svn:log V 274 MFC 232700: Add a new sched_clear_name() method to the scheduler interface to clear the cached name used for KTR_SCHED traces when a thread's name changes. This way KTR_SCHED traces (and thus schedgraph) will notice when a thread's name changes, most commonly via execve(). END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-04-02T20:36:35.211082Z K 7 svn:log V 54 MFC 233236: Add sys/ofed to the 'make cscope' target. END