committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r354589||kib||Nov. 10, 2019, 9:28 a.m.||amd64: move common_tss into pcpu.
This saves some memory, around 256K I think. It removes some code, e.g. KPTI does not need to specially map common_tss anymore. Also, common_tss become domain-local. Reviewed by: jhb Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D22231ViewVC
|r354588||kib||Nov. 10, 2019, 9:25 a.m.||Include cache zones into zone_foreach() where appropriate.|
|r354585||alc||Nov. 10, 2019, 5:22 a.m.||Eliminate a redundant pmap_load() from pmap_remove_pages().
There is no reason why the pmap_invalidate_all() in pmap_remove_pages() must be performed before the final PV list lock release. Move it past the lock release. Eliminate a stale comment from pmap_page_test_mappings(). We implemented a modified bit in r350004. MFC after: 1 weekViewVC
|r354584||jhibbits||Nov. 10, 2019, 4:24 a.m.||powerpc64/powernv: Use OPAL call for non-POWER8 PCI TCE reset
According to the OPAL documentation, only the POWER8 (PHB3) should use the register write TCE reset method. All others should use the OPAL call. On POWER9 the call is semantically identical to the register write, with a wait for completion.ViewVC
|r354581||mav||Nov. 10, 2019, 3:37 a.m.||Add compact scraptchpad protocol for ntb_transport(4).
Previously ntb_transport(4) required at least 6 scratchpad registers, plus 2 more for each additional memory window. That is too much for some configurations, where several drivers have to share resources of the same NTB hardware. This patch introduces new compact version of the protocol, requiring only 3 scratchpad registers, plus one more for each additional memory window. The optimization is based on fact that neither of version, number of windows or number of queue pairs really need more then one byte each, and window sizes of 4GB are not very useful now. The new protocol is activated automatically when the configuration is low on scratchpad registers, or it can be activated explicitly with loader tunable. MFC after: 2 weeks Sponsored by: iXsystems, Inc.ViewVC
|r354580||mav||Nov. 10, 2019, 3:24 a.m.||Allow splitting PLX NTB BAR2 into several memory windows.
Address Lookup Table (A-LUT) being enabled allows to specify separate translation for each 1/128th or 1/256th of the BAR2. Previously it was used only to limit effective window size by blocking access through some of A-LUT elements. This change allows A-LUT elements to also point different memory locations, providing to upper layers several (up to 128) independent memory windows. A-LUT hardware allows even more flexible configurations than this, but NTB KPI have no way to manage that now. MFC after: 2 weeks Sponsored by: iXsystems, Inc.ViewVC
|r354579||kevans||Nov. 10, 2019, 3:06 a.m.||bcm2835_sdhci: don't panic in DMA interrupt if curcmd went away
This is an exceptional case; generally found during controller errors. A panic when we attempt to acess slot->curcmd->data is less ideal than warning, and other verbiage will be emitted to indicate the exact error.ViewVC
|r354578||kevans||Nov. 10, 2019, 2:31 a.m.||Revert premature part of r354577
bcm2835_vcbus.c will be the future home to some I/O address mapping routines, but it has neither been committed nor reviewed.ViewVC
|r354577||kevans||Nov. 10, 2019, 1:43 a.m.||arm64: add SOC_BRCM_BCM2838, build it in GENERIC
BCM2838/BCM2711 is the Raspberry Pi 4, which we will soon be able to boot on once some ports bits are worked out.ViewVC
|r354576||rmacklem||Nov. 10, 2019, 1:21 a.m.||Update the VOP_COPY_FILE_RANGE man page to reflect the semantic change
made by r354574. This is a content change.ViewVC
|r354575||rmacklem||Nov. 10, 2019, 1:13 a.m.||Update the copy_file_range man page to reflect the semantic change
done by r354574. This is a content change.ViewVC
|r354574||rmacklem||Nov. 10, 2019, 1:08 a.m.||Update copy_file_range(2) to be Linux5 compatible.
The current linux man page and testing done on a fairly recent linux5.n kernel have identified two changes to the semantics of the linux copy_file_range system call. Since the copy_file_range(2) system call is intended to be linux compatible and is only currently in head/current and not used by any commands, it seems appropriate to update the system call to be compatible with the current linux one. The first of these semantic changes was changed to be compatible with linux5.n by r354564. For the second semantic change, the old linux man page stated that, if infd and outfd referred to the same file, EBADF should be returned. Now, the semantics is to allow infd and outfd to refer to the same file so long as the byte ranges defined by the input file offset, output file offset and len does not overlap. If the byte ranges do overlap, EINVAL should be returned. This patch modifies copy_file_range(2) to be linux5.n compatible for this semantic change.ViewVC
|r354573||manu||Nov. 9, 2019, 10:25 p.m.||generic_ehci_fdt: Fix compile when EXT_RESOURCES isn't present|
|r354572||bz||Nov. 9, 2019, 9:59 p.m.||libipsec: correct a typo
Correct a typo in the ipsec_errlist and replicated in a comment. No functional changes. MFC after: 3 weeksViewVC
|r354571||trasz||Nov. 9, 2019, 5:30 p.m.||Add GEOM attribute to report physical device name, and report it
via 'diskinfo -v'. This avoids the need to track it down via CAM, and should also work for disks that don't use CAM. And since it's inherited thru the GEOM hierarchy, in most cases one doesn't need to walk the GEOM graph either, eg you can use it on a partition instead of disk itself. Reviewed by: allanjude, imp Sponsored by: Klara Inc Differential Revision: https://reviews.freebsd.org/D22249ViewVC