| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | sys: Remove $FreeBSD$: one-line .c pattern | Warner Losh | 2023-08-23 | 1 | -2/+0 |
| | | | | | | | | Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ Similar commit in current: (cherry picked from commit 685dc743dc3b) | ||||
| * | spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD | Warner Losh | 2023-07-25 | 1 | -1/+1 |
| | | | | | | | | | | | | The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix (cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b) | ||||
| * | kvmclock: Fix initialization when EARLY_AP_STARTUP is not defined | Mark Johnston | 2023-01-29 | 1 | -5/+41 |
| | | | | | | | | | | | | | | | | | | | | | | To attach to the hypervisor, kvmclock needs to write a per-CPU MSR. When EARLY_AP_STARTUP is not defined, device attach happens too early: APs are not yet spun up, so smp_rendezvous only runs the callback on the local CPU. As a result, the timecounter only gets initialized on the BSP, and then timekeeping is broken on SMP systems. Implement handling for !EARLY_AP_STARTUP kernels: keep track of the CPU on which device attach ran, and then use a SI_SUB_SMP SYSINIT to register the rest of the CPUs with the hypervisor. Reported by: Shrikanth R Kamath <kshrikanth@juniper.net> Reviewed by: kib, jhb (earlier versions) Sponsored by: Klara, Inc. Sponsored by: Juniper Networks, Inc. MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D37705 (cherry picked from commit 568f552b0410f4f72db9ce710f7803acca23f79f) | ||||
| * | kvm_clock: KVM paravirtual clock support | Adam Fenn | 2021-10-10 | 1 | -0/+240 |
| (cherry picked from commit 6c69c6bb4c7ffde48b130df707799d4eca21ca9f) | |||||
 |
index : src | |
| FreeBSD source tree |
| aboutsummaryrefslogtreecommitdiff |