#
310fc6c5 |
| 02-Feb-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r357389 through r357407.
|
#
bb9c7e26 |
| 02-Feb-2020 |
Warner Losh <imp@FreeBSD.org> |
Move font.h generation to conf/files from conf/files.*
Use ${SRCTOP} instead of /usr/share. Prefer to depend on option sc_dflt_fnt instead of sc. gc the 4 otherwise identical instances in the tree.
Move font.h generation to conf/files from conf/files.*
Use ${SRCTOP} instead of /usr/share. Prefer to depend on option sc_dflt_fnt instead of sc. gc the 4 otherwise identical instances in the tree. Platforms that don't need this won't included it.
show more ...
|
#
e17b7f1a |
| 02-Feb-2020 |
Warner Losh <imp@FreeBSD.org> |
Fix old-style build
Fix the old-style build by using ${SRCTOP} instead of a weird construct that only works for new-style build. Simplify the building of keymap files by using macros Move atkbdmap.h
Fix old-style build
Fix the old-style build by using ${SRCTOP} instead of a weird construct that only works for new-style build. Simplify the building of keymap files by using macros Move atkbdmap.h in files.x86 This has been broken since r296899 which removed the implicit dependency on /usr/share.
show more ...
|
#
a78eada5 |
| 01-Feb-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r357350 through r357367.
|
#
f6d5b31f |
| 01-Feb-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Revert r357349, since the clang 10.0.0 warning was actually correct, and the ! operator should have been a ~ instead:
Merge r357348 from the clang 10.0.0 import branch:
Disable new clang 10.0.0
Revert r357349, since the clang 10.0.0 warning was actually correct, and the ! operator should have been a ~ instead:
Merge r357348 from the clang 10.0.0 import branch:
Disable new clang 10.0.0 warnings about converting the result of shift operations to a boolean in tpm(4):
sys/dev/tpm/tpm_crb.c:301:32: error: converting the result of '<<' to a boolean; did you mean '(1 << (0)) != 0'? [-Werror,-Wint-in-bool-context] WR4(sc, TPM_CRB_CTRL_CANCEL, !TPM_CRB_CTRL_CANCEL_CMD); ^ sys/dev/tpm/tpm_crb.c:73:34: note: expanded from macro 'TPM_CRB_CTRL_CANCEL_CMD' #define TPM_CRB_CTRL_CANCEL_CMD BIT(0) ^ sys/dev/tpm/tpm20.h:60:19: note: expanded from macro 'BIT' #define BIT(x) (1 << (x)) ^
Such warnings can be useful in C++ contexts, but not so much in kernel drivers, where this type of bit twiddling is commonplace. So disable it for this case.
Noticed by: cem MFC after: 3 days
show more ...
|
#
19e5e202 |
| 31-Jan-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Merge r357348 from the clang 10.0.0 import branch:
Disable new clang 10.0.0 warnings about converting the result of shift operations to a boolean in tpm(4):
sys/dev/tpm/tpm_crb.c:301:32: error: con
Merge r357348 from the clang 10.0.0 import branch:
Disable new clang 10.0.0 warnings about converting the result of shift operations to a boolean in tpm(4):
sys/dev/tpm/tpm_crb.c:301:32: error: converting the result of '<<' to a boolean; did you mean '(1 << (0)) != 0'? [-Werror,-Wint-in-bool-context] WR4(sc, TPM_CRB_CTRL_CANCEL, !TPM_CRB_CTRL_CANCEL_CMD); ^ sys/dev/tpm/tpm_crb.c:73:34: note: expanded from macro 'TPM_CRB_CTRL_CANCEL_CMD' #define TPM_CRB_CTRL_CANCEL_CMD BIT(0) ^ sys/dev/tpm/tpm20.h:60:19: note: expanded from macro 'BIT' #define BIT(x) (1 << (x)) ^
Such warnings can be useful in C++ contexts, but not so much in kernel drivers, where this type of bit twiddling is commonplace. So disable it for this case.
MFC after: 3 days
show more ...
|
#
0a51af91 |
| 31-Jan-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Disable new clang 10.0.0 warnings about converting the result of shift operations to a boolean in tpm(4):
sys/dev/tpm/tpm_crb.c:301:32: error: converting the result of '<<' to a boolean; did you mea
Disable new clang 10.0.0 warnings about converting the result of shift operations to a boolean in tpm(4):
sys/dev/tpm/tpm_crb.c:301:32: error: converting the result of '<<' to a boolean; did you mean '(1 << (0)) != 0'? [-Werror,-Wint-in-bool-context] WR4(sc, TPM_CRB_CTRL_CANCEL, !TPM_CRB_CTRL_CANCEL_CMD); ^ sys/dev/tpm/tpm_crb.c:73:34: note: expanded from macro 'TPM_CRB_CTRL_CANCEL_CMD' #define TPM_CRB_CTRL_CANCEL_CMD BIT(0) ^ sys/dev/tpm/tpm20.h:60:19: note: expanded from macro 'BIT' #define BIT(x) (1 << (x)) ^
Such warnings can be useful in C++ contexts, but not so much in kernel drivers, where this type of bit twiddling is commonplace. So disable it for this case.
MFC after: 3 days
show more ...
|
#
71f00776 |
| 21-Nov-2019 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Remove sio(4). It had been disconnected from build in r181233 in 2008.
Reviewed by: imp
|
#
052e12a5 |
| 15-Nov-2019 |
Josh Paetzel <jpaetzel@FreeBSD.org> |
Add the pvscsi driver to the tree.
This driver allows to usage of the paravirt SCSI controller in VMware products like ESXi. The pvscsi driver provides a substantial performance improvement in bloc
Add the pvscsi driver to the tree.
This driver allows to usage of the paravirt SCSI controller in VMware products like ESXi. The pvscsi driver provides a substantial performance improvement in block devices versus the emulated mpt and mps SCSI/SAS controllers.
Error handling in this driver has not been extensively tested yet.
Submitted by: vbhakta@vmware.com Relnotes: yes Sponsored by: VMware, Panzura Differential Revision: D18613
show more ...
|
Revision tags: release/12.1.0 |
|
#
2a4300e9 |
| 30-Oct-2019 |
Warner Losh <imp@FreeBSD.org> |
Move all the sys/dev/[a-j]* that are common to files.x86
All these device entries are common between the two files. Move them to files.x86. Also sort entries from this range into proper order in fil
Move all the sys/dev/[a-j]* that are common to files.x86
All these device entries are common between the two files. Move them to files.x86. Also sort entries from this range into proper order in files.amd64.
show more ...
|
#
d0c0856f |
| 10-Oct-2019 |
Andriy Gapon <avg@FreeBSD.org> |
emulate illumos membar_producer with atomic_thread_fence_rel
membar_producer is supposed to be a store-store barrier. Also, in the code that FreeBSD has ported from illumos membar_producer is used o
emulate illumos membar_producer with atomic_thread_fence_rel
membar_producer is supposed to be a store-store barrier. Also, in the code that FreeBSD has ported from illumos membar_producer is used only with regular stores to regular memory (with respect to caching).
We do not have an MI primitive for the store-store barrier, so atomic_thread_fence_rel is the closest we have as it provides (load | store) -> store barrier.
Previously, membar_producer was an empty function call on all 32-bit arm-s, 32-bit powerpc, riscv and all mips variants. I think that it was inadequate. On other platforms, such as amd64, arm64, i386, powerpc64, sparc64, membar_producer was implemented using stronger primitives than required for a store-store barrier with respect to regular memory access. For example, it used sfence on amd64 and lock-ed nop in i386 (despite TSO). On powerpc64 we now use recommended lwsync instead of eieio. On sparc64 FreeBSD uses TSO mode. On arm64/aarch64 we now use dmb sy instead of dmb ish. Not sure if this is an improvement, actually.
After this change we can drop opensolaris_atomic.S for aarch64, amd64, powerpc64 and sparc64 as all required atomic operations have either direct or light-weight mapping to FreeBSD native atomic operations.
Discussed with: kib MFC after: 4 weeks
show more ...
|
#
f2521a76 |
| 10-Oct-2019 |
Doug Ambrisko <ambrisko@FreeBSD.org> |
This driver attaches to the Intel VMD drive and connects a new PCI domain starting at the max. domain, and then work down. Then existing FreeBSD drivers will attach. Interrupt routing from the VMD
This driver attaches to the Intel VMD drive and connects a new PCI domain starting at the max. domain, and then work down. Then existing FreeBSD drivers will attach. Interrupt routing from the VMD MSI-X to the NVME drive is not well known, so any interrupt is sent to all children that register.
VROC used Intel meta data so graid(8) works with it. However, graid(8) supports RAID 0,1,10 for read and write. I have some early code to support writes with RAID 5. Note that RAID 5 can have life issues with SSDs since it can cause write amplification from updating the parity data.
Hot plug support needs a change to skip the following check to work: if (pcib_request_feature(dev, PCI_FEATURE_HP) != 0) { in sys/dev/pci/pci_pci.c.
Looked at by: imp, rpokala, bcr Differential Revision: https://reviews.freebsd.org/D21383
show more ...
|
#
c5c3ba6b |
| 03-Sep-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r351317 through r351731.
|
#
7d65d420 |
| 25-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Fix bogusly declared WERRORs in kernel build
Many arm kernel configs bogusly specified WERROR=-Werror. There's no reason for this because the default is that and there's no reason to override. These
Fix bogusly declared WERRORs in kernel build
Many arm kernel configs bogusly specified WERROR=-Werror. There's no reason for this because the default is that and there's no reason to override. These date from a time when we needed to add additional warning->error suppression. They are obsolete and were cut and paste propagated from file to file.
Comment out all the WERROR=.... lines in powerpc. They aren't bogus, but were appropriate for the old defaults for gcc4.2.1. Now that we've made the policy decision to suppress -Werror by default on these platforms, it is appropriate to comment these out. People wishing to fix these errors can still un-comment them out, or say WERROR=-Werror on the command line.
Fix two instances (cut and paste propagation) of hard-coded -Werror in x86 code. Replace with ${WERROR} instead. This is a no-op change except for people who build WERROR=-Wno-error :).
This should fix tinderbox / CI breakage.
show more ...
|
#
96f556f5 |
| 16-Aug-2019 |
Alexander Motin <mav@FreeBSD.org> |
NTB Tool: Test driver for NTB hardware drivers.
NTB Tool driver is meant for testing NTB hardware driver functionalities, such as doorbell interrupts, link events, scratchpad registers and memory wi
NTB Tool: Test driver for NTB hardware drivers.
NTB Tool driver is meant for testing NTB hardware driver functionalities, such as doorbell interrupts, link events, scratchpad registers and memory windows. This is a port of ntb_tool driver from Linux. It has been verified on top of AMD and PLX NTB HW drivers.
Submitted by: Arpan Palit <arpan.palit@amd.com> Cleaned up by: mav MFC after: 2 weeks Relnotes: yes Differential Revision: https://reviews.freebsd.org/D18819
show more ...
|
#
041f5b36 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Move the common x86 ipmi files to files.x86. The powerpc file list is different enough that unification will have to wait for the next pass.
Reviewed by: jhb (verbal OK on irc) Differential Revision
Move the common x86 ipmi files to files.x86. The powerpc file list is different enough that unification will have to wait for the next pass.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
show more ...
|
#
b38e67c9 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
The x86 part of hwpmc is shared, so move it to files.x86.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
|
#
ff45348b |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Windows ndis support is x86 only. Move the MI parts there.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
|
#
cfb592fa |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Intel's isci is part of the chipset, so it is x86 specific.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
|
#
43602a9c |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Move hyperv to files.x86
Move the comomon part of hyperv to files.x86.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
|
#
ca46f711 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
The bxe driver, QLogic NetXtreme II Ethernet 10Gb PCIe adapter driver, is x86 specific, and only builds there. Likewise the module is built there. Move it to the x86-only files.x86.
Reviewed by: jhb
The bxe driver, QLogic NetXtreme II Ethernet 10Gb PCIe adapter driver, is x86 specific, and only builds there. Likewise the module is built there. Move it to the x86-only files.x86.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
show more ...
|
#
5f82f736 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
The ACPI parts are identical between i386 and amd64
Apart from one MD file, ACPI is a x86 implementation, not specific to either i386 or amd64, so put it into files.x86. Other architectures include
The ACPI parts are identical between i386 and amd64
Apart from one MD file, ACPI is a x86 implementation, not specific to either i386 or amd64, so put it into files.x86. Other architectures include fewer files for the same options, so it can't move into the MI files file.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
show more ...
|
#
439fd246 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Move via padlock files to files.x86.
VIA Padlock support is for VIA C3, C7 and Eden processors, which are 64bit x86 processors.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://re
Move via padlock files to files.x86.
VIA Padlock support is for VIA C3, C7 and Eden processors, which are 64bit x86 processors.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
show more ...
|
#
807e7867 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Apart from one MD file, aesni is common to x86. Move it into files.x86.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
|
#
e80d8265 |
| 14-Aug-2019 |
Warner Losh <imp@FreeBSD.org> |
Move all the hp* drivers too files.x86
The HPT drivers are all x86 only. Move them to files.x86. Because of the way we run uudecode, we can use $M instead of needing entries for them in separate fil
Move all the hp* drivers too files.x86
The HPT drivers are all x86 only. Move them to files.x86. Because of the way we run uudecode, we can use $M instead of needing entries for them in separate files.
Reviewed by: jhb (verbal OK on irc) Differential Revision: https://reviews.freebsd.org/D21248
show more ...
|