summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MFHgjb2016-04-11494-20849/+35709
|\ | | | | | | Sponsored by: The FreeBSD Foundation
| * Fix the problem, when gpart(8) can't write both bootcode and partcodeae2016-04-111-8/+12
| | | | | | | | | | | | | | | | | | in one command due to wrong file size limit. Do not use bootcode size to calculate partsize limit. Also add report message about successful partcode writing. Reported by: Trond Endrestøl MFC after: 2 weeks
| * Only include sysctl in kernel buildsmh2016-04-111-37/+47
| | | | | | | | | | | | | | | | | | | | Only include sysctl in kernel builds fixing warning about implicit declaration of function 'sysctl_handle_int'. PR: 204140 MFC after: 1 week X-MFC-With: r297813 Sponsored by: Multiplay
| * Update 25xx chips firmware from 7.03.00 to 8.03.00.mav2016-04-111-14487/+15003
| | | | | | | | | | | | | | | | While the same update is also available for 24xx chips, it seems have a problem with disabling virtual ports -- firmware handles the request, but does not respong on it, causing timeout in driver. MFC after: 1 month
| * Polish debugging IOCB dumping.mav2016-04-112-31/+42
| | | | | | | | | | | | Add few more missing cases, unify byte order. MFC after: 1 month
| * During if_vmove() we call if_detach_internal() which in turn calls the eventbz2016-04-113-0/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | handler notifying about interface departure and one of the consumers will detach if_bpf. There is no way for us to re-attach this easily as the DLT and hdrlen are only given on interface creation. Add a function to allow us to query the DLT and hdrlen from a current BPF attachment and after if_attach_internal() manually re-add the if_bpf attachment using these values. Found by panics triggered by nd6 packets running past BPF_MTAP() with no proper if_bpf pointer on the interface. Also add a basic DDB show function to investigate the if_bpf attachment of an interface. Reviewed by: gnn MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D5896
| * hyperv: Typosephe2016-04-111-1/+1
| | | | | | | | | | | | Noticed by: kib MFC after: 1 week Sponsored by: Microsoft OSTC
| * Only include sysctl in kernel buildsmh2016-04-111-2/+2
| | | | | | | | | | | | | | Only include sysctl in kernel builds fixing warning about implicit declaration of function 'sysctl_handle_int'. Sponsored by: Multiplay
| * zio: align use of "no dump" flag between use_uma and !use_uma casesavg2016-04-111-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | At the moment no ZFS buffers are included into a crash dump unless ZFS_DEBUG (or INVARIANTS) kernel option is enabled. That's not very helpful for debugging of ZFS problems, because important information often resides in metadata buffers. This change switches the dumping behavior when UMA is used from the illumos behavior to a more useful behavior that we have on FreeBSD when ZFS buffers are allocated via malloc. Reviewed by: smh, mav MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D5892
| * hyperv/hn: Remove unnecessary NULL checkssephe2016-04-112-10/+5
| | | | | | | | | | | | | | | | Submitted by: Jun Su <junsu microsoft com> Reviewed by: sephe MFC after: 1 week Sponsored by: Microsoft OSTC Differential Revision: https://reviews.freebsd.org/D5905
| * hyperv/hn: By default enable multiple TX/RX rings, aka vRSS.sephe2016-04-111-2/+2
| | | | | | | | | | | | | | Reviewed by: Dexuan Cui <decui microsoft com> MFC after: 1 week Sponsored by: Microsoft OSTC Differential Revision: https://reviews.freebsd.org/D5880
| * hyperv/hn: Cap default # of rings to 8.sephe2016-04-111-1/+9
| | | | | | | | | | | | | | | | | | | | 8 gives the best performance in both Azure and local Hyper-V on both 10Ge and 40Ge. More rings are still allowed by manual configuration. Reviewed by: Dexuan Cui <decui microsoft com> MFC after: 1 week Sponsored by: Microsoft OSTC Differential Revision: https://reviews.freebsd.org/D5879
| * hyperv: Define macro for Hyper-V interfacesephe2016-04-111-1/+2
| | | | | | | | | | | | Suggested by: rpokala MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv: Print more featuressephe2016-04-112-20/+57
| | | | | | | | | | | | | | And add comment about the MSR features. MFC after: 1 week Sponsored by: Microsoft OSTC
| * Allow guest writes to AMD microcode update[0xc0010020] MSR without updating ↵anish2016-04-111-0/+5
| | | | | | | | | | | | | | | | actual hardware MSR. This allows guest microcode update to go through which otherwise failing because wrmsr() was returning EINVAL. Submitted by:Yamagi Burmeister Approved by:grehan MFC after:2 weeks
| * hyperv: Break long linesephe2016-04-111-1/+2
| | | | | | | | | | MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv: Declare hyperv_{features,recommends} properlysephe2016-04-111-0/+3
| | | | | | | | | | MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv: Resurrect r297481sephe2016-04-111-2/+5
| | | | | | | | | | | | | | | | | | This time we make sure that the TIME_REF_COUNT MSR exists. Submitted by: Jun Su <junsu microsoft com> Reviewed by: sephe, Dexuan Cui <decui microsoft com> MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv: Identify Hyper-V features and recommends properlysephe2016-04-112-2/+98
| | | | | | | | | | | | | | | | | | | | | | Features bits will be used to detect devices, e.g. timers, which do not have corresponding event channels. Submitted by: Jun Su <junsu microsoft com> Reviewed by: sephe, Dexuan Cui <decui microsoft com> Rearranged by: sephe MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv/vmbus: Get rid of max_leaf detection; this is actually not used.sephe2016-04-111-32/+0
| | | | | | | | | | | | | | It will be replaced by a new one. MFC after: 1 week Sponsored by: Microsoft OSTC
| * hyperv/vmbus: Nuke unused functionsephe2016-04-112-13/+0
| | | | | | | | | | MFC after: 1 week Sponsored by: Microsoft OSTC
| * cxgbe(4): Provide an explicit value for nqpcq in the firmwarenp2016-04-111-1/+2
| | | | | | | | configuration file.
| * ext2fs: replace 0 with NULL for pointers.pfg2016-04-111-1/+2
| | | | | | | | | | | | | | | | | | While here do late initialization of ebap, similar as was done in UFS. Found with devel/coccinelle. MFC after: 2 weeks
| * lpr: replace 0 with NULL for pointers.pfg2016-04-108-23/+23
| | | | | | | | | | | | Found with devel/coccinelle. Reviewed by: gad
| * Fix IIC "how" argument dereferencing on big-endian platformsgonzo2016-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | "how" argument is passed as value of int* pointer to callback function but dereferenced as char* so only one byte taken into into account. On little-endian systems it happens to work because first byte is LSB that contains actual value, on big-endian it's MSB and in this case it's always equal zero PR: 207786 Submitted by: chadf@triularity.org
| * Cleanup unnecessary semicolons from the kernel.pfg2016-04-10117-293/+291
| | | | | | | | Found with devel/coccinelle.
| * Since r296250 it is no longer possible for devices to use bus spacemarius2016-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | addresses exceeding 32 bit, so bump BUS_SPACE_MAXADDR to 64 bit. The whole situation is sub par, though; prior to r296250 and despite what their names imply, BUS_SPACE_MAX* were primarily, even almost exclusively used for bus_dma(9). Now these macros also have a vital role for bus_space(9). However, it does not necessarily hold that both bus DMA and space addresses universally have the same limits per platform. As for sparc64, 64 bit clearly is beyond what can be addressed via the various IOMMUs. With this change in place, we now rely on the parent bus DMA tags of the host-to-foo drivers causing the child tags to be capped as necessary. PR: 207998
| * ufs: replace 0 with NULL for pointers.pfg2016-04-104-22/+29
| | | | | | | | | | | | | | | | | | | | While here also do late initialization of the variables we are changing. Found with devel/coccinelle. Reviewed by: mckusick MFC after: 2 weeks
| * libc: replace 0 with NULL for pointers.pfg2016-04-1022-52/+49
| | | | | | | | | | | | | | | | | | While here also cleanup some surrounding code; particularly drop some malloc() casts. Found with devel/coccinelle. Reviewed by: bde (previous version - all new bugs are mine)
| * Add bofh@ in calendar.freebsdbofh2016-04-101-0/+1
| |
| * VM_MAXUSER_ADDRESS is highest page start, not highest address.jhibbits2016-04-101-1/+1
| | | | | | | | | | In case a single page mapping is requested first, which might overlap the user address space, fix the device map block to the next page.
| * Restructure device mappings for Book-E.jhibbits2016-04-102-18/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: There is currently a 1GB hole between user and kernel address spaces into which direct (1:1 PA:VA) device mappings go. This appears to go largely unused, leaving all devices to contend with the 128MB block at the end of the 32-bit space (0xf8000000-0xffffffff). This easily fills up, and needs to be densely packed. However, dense packing wastes precious TLB1 space, of which there are only 16 (e500v2) or 64(e5500) entries available. Change this by using the 1GB space for all device mappings, and allow the kernel to use the entire upper 1GB for KVA. This also allows us to use sparse device mappings, freeing up TLB entries. Test Plan: Boot tested on p5020. Differential Revision: https://reviews.freebsd.org/D5832
| * More complete implementation of /proc/self/limits.dchagin2016-04-102-42/+76
| | | | | | | | | | | | | | | | Fix the way the code accesses process limits struct - pointed out by mjg@. PR: 207386 Reviewed by: no objection form des@ MFC after: 3 weeks
| * Add a 'show t4 devlog <nexus>' DDB command.jhb2016-04-101-0/+93
| | | | | | | | | | | | | | This command displays the adapter's firmware device log similar to the dev.<nexus>.misc.devlog sysctl. Sponsored by: Chelsio Communications
| * Allow the location of the kernel source tree to be overridden.grehan2016-04-101-1/+3
| | | | | | | | | | This makes it easier for the bhyve executable to be built out of the tree.
| * Add a 'show t4 tcb <nexus> <tid>' command to dump a TCB from DDB.jhb2016-04-103-25/+86
| | | | | | | | | | This allows the contents of a TCB to be extracted from a T4/T5 card in DDB after a panic.
| * Add a function to lookup a device_t object by name.jhb2016-04-102-6/+17
| | | | | | | | | | | | This just walks the global list of devices looking for one with the requested name. The one use case outside of devctl2's implementation is for DDB commands that wish to lookup devices by name.
| * [net80211] correctly (i hope, wow) do a ticks comparison to limit A-MPDU ↵adrian2016-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | attempts I was seeing the stack constantly attempt to renegotiate A-MPDU TX even after 3 failures. My hunch is that the direct ticks comparison is failing around the ticks wrap-around point. This failure shouldn't /really/ happen normally, but it turns out being the IBSS master node on FreeBSD doesn't quite setup 11n right, so negotiating A-MPDU TX fails.
| * [net80211] unconditionally do A-MPDU RX aging.adrian2016-04-101-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | It's 2016 and vendors (including us!) still have 802.11n TX/RX sequence handling bugs. It's suboptimal, but I'd rather see us default to handling things in a sensible way. So, just delete the #ifdef'ed code for now. I'll leave the option in so it doesn't break existing configurations. This all started because I've started getting reports about urtwn not working after I enabled 802.11n support, and it's because the ARM kernel configs don't include A-MPDU RX aging.
| * Implement support for boot-time DTrace.markj2016-04-102-65/+167
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows one to enable DTrace probes relatively early during boot, during SI_SUB_DTRACE_ANON, before dtrace(1) can invoked. The desired enabling is created using dtrace -A, which writes a /boot/dtrace.dof file and uses nextboot(8) to ensure that DTrace kernel modules are loaded and that the DOF file describing the enabling is loaded by loader(8) during the subsequent boot. The trace output can then be fetched with dtrace -a. With this commit, boot-time DTrace is only functional on i386 and amd64: on other architectures, the high-resolution timer frequency is initialized during SI_SUB_CLOCKS and is thus not available when the anonymous tracing state is initialized. On x86, the TSC is used and is thus available earlier. MFC after: 1 month Relnotes: yes
| * nextboot(8): add a -a option for appending to a configuration.markj2016-04-102-5/+30
| | | | | | | | | | | | | | | | By default, a nextboot invocation will clobber any existing nextboot configuration. MFC after: 2 weeks Relnotes: yes
| * Initialize SDT probes during SI_SUB_DTRACE_PROVIDER.markj2016-04-101-13/+5
| | | | | | | | | | | | | | This is consistent with all other DTrace providers and ensures that SDT probes are available for boot-time tracing. MFC after: 2 weeks
| * Initialize DTrace hrtimer frequency during SI_SUB_CPU on i386 and amd64.markj2016-04-102-36/+60
| | | | | | | | | | | | | | | | | | This allows the hrtimer to be used earlier during boot. This is required for boot-time DTrace: anonymous enablings are created during SI_SUB_DTRACE_ANON, which runs before APs are started. In particular, the DTrace deadman timer requires that the hrtimer be functional. MFC after: 2 weeks
| * [net80211] log the node pointer when calling ht node init/cleanupadrian2016-04-091-6/+7
| | | | | | | | | | | | | | | | This makes it easier to track which node is having what done do it during normal use. This is likely the eighth time I've done this since I started doing net80211 development, so I think it's about time I just committed it.
| * [net80211] add back in the ff/superg node init call that I accidentallyadrian2016-04-091-0/+8
| | | | | | | | | | | | deleted. It's mostly a no-op right now, so it shouldn't have changed behaviour.
| * USB: replace 0 with NULL for pointers.pfg2016-04-095-8/+8
| | | | | | | | | | | | Found with devel/coccinelle. Reviewed by: hselasky
| * MFV r297760: 6418 zpool should have a label clearing commandmav2016-04-096-86/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com> Reviewed by: Matthew Ahrens <mahrens@delphix.com> Reviewed by: George Wilson <george.wilson@delphix.com> Author: Will Andrews <will@firepipe.net> Closes #83 Closes #32 openzfs/openzfs@9663688425131744221ea99f9e66b9ed964492ae FreeBSD already had `zpool labelclear` functionality, so this is mostly just a diff reduction. MFC after: 1 month
| * Use DELAY() instead of sleeping during boot-time attach.jhb2016-04-091-1/+4
| | | | | | | | Tested by: Wolfgang Zenker <wolfgang@lyxys.ka.sub.org>
| * sh(1): replace 0 with NULL for pointers.pfg2016-04-092-2/+2
| | | | | | | | | | | | Found with devel/coccinelle. Reviewed by: jilles
| * Align the start of the text segment to an 8-byte boundary. This fixesian2016-04-091-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | alignment aborts in ubldr.bin for RPi that started happening with clang 3.8 (earlier clang apparently didn't generate strd instructions that trigger the alignment fault). The abort happened in ubldr.bin and not ubldr (elf version) because the elf headers are 0xf4 bytes long, and stripping them off left everything 4-byte aligned. While here, also stop aligning the data segment to a page boundary, align it to 8 bytes instead (aligning to a page just needlessly makes the file bigger); pointed out by andrew@.
OpenPOWER on IntegriCloud