sys: Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
arm64: Hyper-V: enablement for ARM64 in Hyper-V (Part 3, final)This is the last part for ARM64 Hyper-V enablement. This includescommone files and make file changes to enable the ARM64 FreeBSDgues
arm64: Hyper-V: enablement for ARM64 in Hyper-V (Part 3, final)This is the last part for ARM64 Hyper-V enablement. This includescommone files and make file changes to enable the ARM64 FreeBSDguest on Hyper-V. With this patch, it should be able to buildthe ARM64 image and install it on Hyper-V.Reviewed by: emaste, andrew, whuTested by: Souradeep Chakrabarti <[email protected]>Sponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D36744
show more ...
sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon
hyperv/ic: Rename cleaned up files.MFC after: 1 weekSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8850
hyperv/ic: Rname cleaned up file.MFC after: 1 weekSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8848
hyperv/vss: Add driver and tools for VSSVSS stands for "Volume Shadow Copy Service". Unlike virtual machinesnapshot, it only takes snapshot for the virtual disks, so bothfilesystem and applicati
hyperv/vss: Add driver and tools for VSSVSS stands for "Volume Shadow Copy Service". Unlike virtual machinesnapshot, it only takes snapshot for the virtual disks, so bothfilesystem and applications have to aware of it, and cooperate thewhole VSS process.This driver exposes two device files to the userland: /dev/hv_fsvss_dev Normally userland programs should _not_ mess with this device file. It is currently used by the hv_vss_daemon(8), which freezes and thaws the filesystem. NOTE: currently only UFS is supported, if the system mounts _any_ other filesystems, the hv_vss_daemon(8) will veto the VSS process. If hv_vss_daemon(8) was disabled, then this device file must be opened, and proper ioctls must be issued to keep the VSS working. /dev/hv_appvss_dev Userland application can opened this device file to receive the VSS freeze notification, hold the VSS for a while (mainly to flush application data to filesystem), release the VSS process, and receive the VSS thaw notification i.e. applications can run again. The VSS will still work, even if this device file is not opened. However, only filesystem consistency is promised, if this device file is not opened or is not operated properly.hv_vss_daemon(8) is started by devd(8) by default. It can be disabledby editting /etc/devd/hyperv.conf.Submitted by: Hongjiang Zhang <honzhan microsoft com>Reviewed by: kib, mckusickMFC after: 3 weeksSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8224
hyperv/vmbus: Add vmbus method for GUID base device probing.Reduce the exposure of hv_device.MFC after: 1 weekSponsored by: Microsoft OSTCDifferential Revision: https://reviews.freebsd.org/D7024
hyperv/utils: Code rearrange and cleanupSplit heartbeat, shutdown and timesync out of utils codeand name them properly.Submitted by: Jun Su <junsu microsoft com>Reviewed by: adrian, sephe, Hong
hyperv/utils: Code rearrange and cleanupSplit heartbeat, shutdown and timesync out of utils codeand name them properly.Submitted by: Jun Su <junsu microsoft com>Reviewed by: adrian, sephe, Hongjiang Zhang <honzhan microsoft com>MFC after: 1 weekSponsored by: Microsoft OSTCDifferential Revision: https://reviews.freebsd.org/D5216
Import HyperV Key-Value Pair (KVP) driver and daemon code by Microsoft,many thanks for their continued support of FreeBSD.While I'm there, also implement a new build knob, WITHOUT_HYPERV todisabl
Import HyperV Key-Value Pair (KVP) driver and daemon code by Microsoft,many thanks for their continued support of FreeBSD.While I'm there, also implement a new build knob, WITHOUT_HYPERV todisable building and installing of the HyperV utilities when necessary.The HyperV utilities are only built for i386 and amd64 targets.This is a stable/10 candidate for inclusion with 10.1-RELEASE.Submitted by: Wei Hu <weh microsoft com>MFC after: 1 week
Fix make depend, apply a bit of style.Approved by: re (marius)Reviewed by: grehan
Revert the kvp code - there's still some work thatneeds to be done for that.Discussed with: Microsoft hyper-v devs
Latest update from Microsoft.Obtained from: Microsoft Hyper-v dev team
Microsoft have changed their policy on how the hyper-v code willbe pulled into FreeBSD. From now, FreeBSD will be considered theupstream repo.First step: move the drivers away from the contrib ar
Microsoft have changed their policy on how the hyper-v code willbe pulled into FreeBSD. From now, FreeBSD will be considered theupstream repo.First step: move the drivers away from the contrib area and intothe base system.A follow-on commit will include the drivers in the amd64 GENERIC kernel.
make glue to hook up the hyperv kmods to the build.Modified from the original Microsoft versions to pullcode/headers in from the sys/contrib/dev directory.