summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Update vendor/illumos/dist and vendor-sys/illumos/distdelphij2013-01-162-1/+44
| | | | | | | | | | | | | | | to illumos-gate 13921:9d721847e469 (illumos zfs issue #3035 LZ4 compression support in ZFS and GRUB)
| * | Push vendor/illumos/dist to illumos-gate 13894:f4af77f6bbd2mm2012-12-151-9/+17
| | | | | | | | | | | | (illumos zfs issues #3397 #3398)
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2012-11-221-5/+13
| | | | | | | | | | | | | | | to illumos-gate 13889:a67716f16746 (illumos zfs issue #3254)
| * | Update vendor/illumos/dist and vendor/illumos-sys/distmm2012-11-141-5/+42
| | | | | | | | | | | | | | | to illumos-gate 13887:196932ec9e6a (illumos zfs issue #3236)
| * | Update vendor/illumos/dist and vendor/illumos-sys/distmm2012-11-141-21/+119
| | | | | | | | | | | | | | | to illumos-gate 13886:e3261d03efbf (illumos zfs issue #3349)
| * | Update vendor/illumos/dist and vendor/illumos-sys/distmm2012-11-086-45/+212
| | | | | | | | | | | | | | | to illumos-gate 13871:a9c12c2c1647 (zfs changes, illumos issues #3306, #3321)
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2012-11-084-9/+92
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13869:921a99998bb4 (illumos ZFS issue #3246 ZFS I/O deadman thread) Note: illumos disables deadman logic by default on vmware and sparc
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2012-11-081-33/+66
| | | | | | | | | | | | | | | to illumos-gate 13849:3468a95b27cd (illumos ZFS issues #3145, #3212, #3258)
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2012-09-262-17/+5
| | | | | | | | | | | | | | | to illumos-gate 13836:37bf491c434c (illumos ZFS issues #2678, #2811, #3139, #3189, #3208)
| * | Update vendor/illumos/dist to illumos-gate 13811:4dadf1a8e003mm2012-09-111-1/+1
| | | | | | | | | | | | (zfs, illumos issue #3064)
| * | Update vendor/illumos/dist to illumos-gate 13810:4b38a0c01186mm2012-09-102-22/+26
| | | | | | | | | | | | (zfs changes, illumos issue #3098)
| * | Update vendor/illumos/dist and vendor/illumos-sys/distmm2012-09-094-490/+417
| | | | | | | | | | | | | | | to illumos-gate 13805:e3a9ae14a119 (zfs changes, illumos issues #1884, #3006)
| * | Update vendor/illumos/dist to illumos-gate 13804:9f4f28db61d2mm2012-09-091-0/+1
| | | | | | | | | | | | (dtrace changes only, illumos issue #3021)
| * | Update vendor/illumos/dist and vendor/illumos-gate/distmm2012-09-042-0/+3
| | | | | | | | | | | | | | | | | | to illumos-gate revision 13794:7c5e0e746b2c Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos to illumos-gate 13788:0cb9e2232ae0mm2012-09-0410-194/+451
| | | | | | | | | | | | (dtrace changes, illumos issue #3123)
| * | Update vendor/illumos/dist and vendor/illumos-gate/distmm2012-08-273-8/+34
| | | | | | | | | | | | | | | | | | to illumos-gate revision 13782:8f78aae28a63 Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Add zpool-features.5 vendor manual page, revision 13753:2aba784c276bmm2012-08-271-0/+173
| | | | | | | | | | | | Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos and vendor-sys/illumos to revision 13777:b1e53580146dmm2012-08-232-48/+63
| | | | | | | | | | | | Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos to illumos-gate 13773:00c2a08cf1bbmm2012-08-191-6/+95
| | | | | | | | | | | | | | | | | | | | | References: https://www.illumos.org/issues/2399 (zfs manual page) Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos to illumos-gate 13758:23432da34147 (dtrace changes)mm2012-08-1971-819/+2262
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | References: https://www.illumos.org/issues/3021 https://www.illumos.org/issues/3022 https://www.illumos.org/issues/3023 https://www.illumos.org/issues/3024 https://www.illumos.org/issues/3025 https://www.illumos.org/issues/3026 Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos to illumos-gate 13754:7231b684c18bmm2012-08-191-6/+38
| | | | | | | | | | | | | | | | | | | | | References: https://www.illumos.org/issues/2978 Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor/illumos to illumos-gate 13753:2aba784c276bmm2012-07-235-106/+366
| | | | | | | | | | | | Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
| * | Update vendor-sys/illumos/dist to illumos-gate 13752:9f5f6c52ba19mm2012-07-181-3/+83
| | | | | | | | | | | | | | | | | | (non-zfs part) Obtained from: ssh://anonhg@hg.illumos.org/illumos-gate
* | | Set the backlink in mmc commands to the mmc request that contains them.ian2013-03-242-0/+4
| | |
* | | No need to erase all 64 bytes of CFIS area if we never use more then 16.mav2013-03-241-4/+4
| | |
* | | Micro-optimize the control flow in a few places. Eliminate a panic callalc2013-03-241-8/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | that could never be reached in vm_radix_insert(). (If the pointer being checked by the panic call were ever NULL, the immmediately preceding loop would have already crashed on a NULL pointer dereference.) Reviewed by: attilio (an earlier version) Sponsored by: EMC / Isilon Storage Division
* | | Add 2 more obsolete files and a missing date.antoine2013-03-241-0/+4
| | |
* | | Resolve clang compile errors on amd64/i386 for certain by casting.sbruno2013-03-241-4/+4
| | | | | | | | | | | | | | | | | | | | | compile tested with clang on i386, amd64 compile tested with gcc on i386, amd64, sparc64 Submitted by: delphij
* | | Fix long known deadlock between geom dev destruction and d_close() call.mav2013-03-241-71/+129
| | | | | | | | | | | | | | | | | | | | | | | | Use destroy_dev_sched_cb() to not wait for device destruction while holding GEOM topology lock (that actually caused deadlock). Use request counting protected by mutex to properly wait for outstanding requests completion in cases of device closing and geom destruction. Unlike r227009, this code does not block taskqueue thread for indefinite time, waiting for completion.
* | | Add new regulatory domain.adrian2013-03-242-0/+26
| | | | | | | | | | | | Obtained from: Qualcomm Atheros
* | | Move the TXQ lock earlier in this routine - so to correctly protect theadrian2013-03-241-1/+2
| | | | | | | | | | | | link pointer check.
* | | Fix the locking changes due to the TXQ change drive-by.adrian2013-03-241-1/+4
| | | | | | | | | | | | | | | | | | Tested: * AR9580, STA mode
* | | Make g_wither_washer() to not loop by itself, but only when there was somemav2013-03-243-29/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | more topology change done that may require its attention. Add few missing g_do_wither() calls in respective places to signal it. This fixes potential infinite loop here when some provider is withered, but still opened or connected for some reason and so can not be destroyed. For example, see r227009 and r227510.
* | | Minor formatting fix for printf() to fix clang builds.sbruno2013-03-241-2/+2
| | | | | | | | | | | | | | | Submitted by: db Reviewed by: gjb
* | | Compile contrib/tzcode/stdtime/localtime.c with -fwrapv, since it reliesdim2013-03-241-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on signed integer overflow wrapping. Otherwise mktime(3) and timegm(3) can hang, in case the timestamp passed in struct tm is not representable in a time_t. Specifically, any timestamp after 2038-01-19 03:14:07, in combination with a 32-bit time_t. Note that it would be better to change the code to not rely on undefined behaviour, but it is contributed code, and it is not entirely trivial to fix the issue properly. MFC after: 3 days
* | | Overhaul the TXQ locking (again!) as part of some beacon/cabq timingadrian2013-03-249-44/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | related issues. Moving the TX locking under one lock made things easier to progress on but it had one important side-effect - it increased the latency when handling CABQ setup when sending beacons. This commit introduces a bunch of new changes and a few unrelated changs that are just easier to lump in here. The aim is to have the CABQ locking separate from other locking. The CABQ transmit path in the beacon process thus doesn't have to grab the general TX lock, reducing lock contention/latency and making it more likely that we'll make the beacon TX timing. The second half of this commit is the CABQ related setup changes needed for sane looking EDMA CABQ support. Right now the EDMA TX code naively assumes that only one frame (MPDU or A-MPDU) is being pushed into each FIFO slot. For the CABQ this isn't true - a whole list of frames is being pushed in - and thus CABQ handling breaks very quickly. The aim here is to setup the CABQ list and then push _that list_ to the hardware for transmission. I can then extend the EDMA TX code to stamp that list as being "one" FIFO entry (likely by tagging the last buffer in that list as "FIFO END") so the EDMA TX completion code correctly tracks things. Major: * Migrate the per-TXQ add/removal locking back to per-TXQ, rather than a single lock. * Leave the software queue side of things under the ATH_TX_LOCK lock, (continuing) to serialise things as they are. * Add a new function which is called whenever there's a beacon miss, to print out some debugging. This is primarily designed to help me figure out if the beacon miss events are due to a noisy environment, issues with the PHY/MAC, or other. * Move the CABQ setup/enable to occur _after_ all the VAPs have been looked at. This means that for multiple VAPS in bursted mode, the CABQ gets primed once all VAPs are checked, rather than being primed on the first VAP and then having frames appended after this. Minor: * Add a (disabled) twiddle to let me enable/disable cabq traffic. It's primarily there to let me easily debug what's going on with beacon and CABQ setup/traffic; there's some DMA engine hangs which I'm finally trying to trace down. * Clear bf_next when flushing frames; it should quieten some warnings that show up when a node goes away. Tested: * AR9280, STA/hostap, up to 4 vaps (staggered) * AR5416, STA/hostap, up to 4 vaps (staggered) TODO: * (Lots) more AR9380 and later testing, as I may have missed something here. * Leverage this to fix CABQ hanling for AR9380 and later chips. * Force bursted beaconing on the chips that default to staggered beacons and ensure the CABQ stuff is all sane (eg, the MORE bits that aren't being correctly set when chaining descriptors.)
* | | CABQ calculation changes to try and fix some weird corner cases leadingadrian2013-03-231-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to stuck beacons. * Set the cabq readytime (ie, how long to burst for) to 50% of the total beacon interval time * fix the cabq adjustment calculation based on how the beacon offset is calculated (the SWBA/DBA time offset.) This is all still a bit magic voodoo but it does seem to have further quietened issues with missed/stuck beacons under my local testing. In any case, it better matches what the reference HAL implements. Obtained from: Qualcomm Atheros
* | | More indentation fixes.adrian2013-03-231-6/+6
| | |
* | | Expose the beacon miss counter.adrian2013-03-231-1/+5
| | |
* | | Do not call malloc(M_WAITOK) while bodev->fence_lock mutex iskib2013-03-231-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | held. The ttm_buffer_object_transfer() does not need the mutex locked at all, except for the call to the driver sync_obj_ref() method. Reported and tested by: dumbbell MFC after: 2 weeks
* | | Merge bugfix from vendor master branch:mm2013-03-231-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Limit write requests to at most INT_MAX. This prevents a certain common programming error (passing -1 to write) from leading to other problems deeper in the library. References: https://github.com/libarchive/libarchive/commit/22531545514043e0 Reported by: Xin Li <delphij@FreeBSD.org> Obtained from: libarchive (master branch)
* | | drm/ttm: Fix a typo: s/pTTM]/[TTM]/dumbbell2013-03-231-1/+1
| | |
* | | drm/ttm: Explain why we don't need to acquire a ref in ttm_bo_vm_ctor()dumbbell2013-03-231-0/+5
| | |
* | | Fix kernel build with options ZFS after r24571 (libzfs_core).mm2013-03-231-0/+2
| | | | | | | | | | | | Submitted by: Bjoern A. Zeeb <bz@FreeBSD.org>
* | | Revert 248634 and 248643 (e.g., restoring 248625 and 248639).mckusick2013-03-238-59/+158
| | | | | | | | | | | | Build verified by: Glen Barber (gjb@)
* | | drm/ttm: Fix TTM buffer object refcountdumbbell2013-03-231-5/+1
| | | | | | | | | | | | | | | | | | | | | This fixes memory leaks in the radeonkms driver. Reviewed by: Konstantin Belousov (kib@) Tested by: J.R. Oldroyd <jr@opal.com>
* | | Fix compiling ed w/ WITHOUT_ED_CRYPTO... These variables aren'tjmg2013-03-231-3/+1
| | | | | | | | | | | | | | | | | | used.. Submitted by: deeptech71 at gmail dot com
* | | Don't check and warn about pmap mismatch on every call to busdma sync.ian2013-03-231-17/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With some recent busdma refactoring, sometimes it happens that a sync op gets called when bus_dmamap_load() never got called, which results in a spurious warning about a map mismatch when no sync operations will actually happen anyway. Now the check is done only if a sync operation is actually performed, and the result of the check is a panic, not just a printf. Reviewed by: cognet (who prevented me from donning a point hat)
* | | Be more explicit about what each bio_cmd & bio_flags value means.will2013-03-231-8/+12
| | | | | | | | | | | | Reviewed by: ken (mentor)
* | | ZFS: Fix a panic while unmounting a busy filesystem.will2013-03-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This particular scenario was easily reproduced using a NFS export. When the first 'zfs unmount' occurred, it returned EBUSY via this path, while vflush() had flushed references on the filesystem's root vnode, which in turn caused its v_interlock to be destroyed. The next time 'zfs unmount' was called, vflush() tried to obtain this lock, which caused this panic. Since vflush() on FreeBSD is a definitive call, there is no need to check vfsp->vfs_count after it completes. Simply #ifdef sun this check. Submitted by: avg Reviewed by: avg Approved by: ken (mentor) MFC after: 1 month
OpenPOWER on IntegriCloud