FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=stable%2F13 2023-10-24T18:58:15Z 2023-10-24T18:58:15Z John Baldwin jhb@FreeBSD.org 2023-10-16T22:17:48Z urn:sha1:506890a652aaf19f59da0a84be26e991f99372d9 EPRINTLN handles newlines appropriately when stdout/stderr have been reused as the backend for a serial port. For bhyverun.c itself, the rule this attempts to follow is to use regular fprintf/perror/warn/err prior to init_pci() (which is when serial ports are configured) and to switch to EPRINTLN afterwards. Reviewed by: corvink, markj Differential Revision: https://reviews.freebsd.org/D42182 (cherry picked from commit b0936440b8fcee523c0b26fdbbef7c3b2b5098bf) 2023-08-23T17:43:26Z Warner Losh imp@FreeBSD.org 2023-08-22T01:31:41Z urn:sha1:3d497e17ebd33fe0f58d773e35ab994d750258d6 Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ Similar commit in main: (cherry picked from commit 1d386b48a555) 2023-08-23T17:43:21Z Warner Losh imp@FreeBSD.org 2023-08-22T01:31:07Z urn:sha1:17da660ad5b3b9cd90e164dd4dbb9beaa7203054 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ Similar commit in main: (cherry picked from commit b3e7694832e8) 2023-08-18T07:52:10Z Corvin Köhne corvink@FreeBSD.org 2021-08-16T07:50:15Z urn:sha1:b02e0f96402830405c0812dc26b7492d487f795b The bootindex option creates an entry in the "bootorder" fwcfg file. This file can be picked up by the guest firmware to determine the bootorder. Nevertheless, it's not guaranteed that the guest firmware uses the bootorder. At the moment, our OVMF ignores the bootorder. This will change in the future. If guest firmware supports the "bootorder" fwcfg file and no device uses the bootindex option, the boot order is determined by the firmware itself. If one or more devices specify a bootindex, the first bootable device with the lowest bootindex will be booted. It's not garanteed that devices without a bootindex will be recognized as bootable from the firmware in that case. Reviewed by: jhb MFC after: 1 week Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D39285 (cherry picked from commit 480bef9481f0c44b19ac4b2adb09f6c3191acd41) 2023-07-25T15:13:49Z Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58Z urn:sha1:caa41f641755c935b036e17440a3b49329c904ed 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) 2023-03-17T10:26:34Z Vitaliy Gusev gusev.vitaliy@gmail.com 2023-03-06T11:35:17Z urn:sha1:c8b5f347317d1d0dca53acf2f40682314ad0b64e Reviewed by: corvink, markj MFC after: 1 week Sponsored by: vStack Differential Revision: https://reviews.freebsd.org/D38855 (cherry picked from commit 5c0a03125988b89610f61a1bb2137b0e29d7cf31) 2023-01-26T19:43:04Z Mark Johnston markj@FreeBSD.org 2022-10-23T14:32:45Z urn:sha1:a48715b58c5adb009649fc64222c18328425b957 MFC after: 1 week (cherry picked from commit ed7216843133c9d6748251b5e180ee90410131f0) 2023-01-26T19:42:43Z Mark Johnston markj@FreeBSD.org 2022-10-25T13:16:23Z urn:sha1:c369cdd696568cc037958413ead78f7225193302 - Use unsigned types for all arithmetic. Use a new signed variable for holding the return value of pread() and pwrite(). - Handle short I/O from pwrite(). MFC after: 1 week (cherry picked from commit 46f5c828961e64646c46ff9e3bc8e55f46f3e7bb) 2023-01-26T19:30:45Z Mark Johnston markj@FreeBSD.org 2022-10-08T15:22:38Z urn:sha1:e696777efa6086d0c1a78aad3a9b8c967166acb3 MFC after: 1 week (cherry picked from commit 98d920d9cf0b439ea351c60353626946971684f6) 2023-01-26T19:29:17Z Vitaliy Gusev gusev.vitaliy@gmail.com 2022-06-23T18:46:06Z urn:sha1:b22b31b380e8810f59ada8e60fb87dcddc585054 When pausing a block I/O device model as part of suspending a VM, wait for all active block I/O requests to finish before saving snapshot data. This avoids having to save information about in-flight requests both in the block_if layer and in storage device models. For the AHCI device model, the queues are now guaranteed to be idle when taking a snapshot, so remove the code to save queue state and rely on the initial state in a resumed VM having all queues already idle. This will also simplify adding NVMe snapshot support in the future. Reviewed by: jhb Sponsored by: vStack Differential Revision: https://reviews.freebsd.org/D26267 (cherry picked from commit cd9618bdb274375139080ee4e33ccbdc980513f3)