MFC r324312: fix the misleading log facility used in devd/zfs.conf

MFC 321762
hyperv: Add VF bringup scripts and devd rules.

How network VF works with hn(4) on Hyper-V in non-transparent mode:

- Each network VF has a cooresponding hn(4).
- The network VF and the it's cooresponding hn(4) have the same hardware
address.
- Once the network VF is up, e.g. ifconfig VF up:
o All of the transmission should go through the network VF.
o Most of the reception goes through the network VF.
o Small amount of reception may go through the cooresponding hn(4).
This reception will happen, even if the the cooresponding hn(4) is
down. The cooresponding hn(4) will change the reception interface
to the network VF, so that network layer and application layer will
be tricked into thinking that these packets were received by the
network VF.
o The cooresponding hn(4) pretends the physical link is down.
- Once the network VF is down or detached:
o All of the transmission should go through the cooresponding hn(4).
o All of the reception goes through the cooresponding hn(4).
o The cooresponding hn(4) fallbacks to the original physical link
detection logic.

All these features are mainly used to help live migration, during which
the network VF will be detached, while the network communication to the
VM must not be cut off. In order to reach this level of live migration
transparency, we use failover mode lagg(4) with the network VF and the
cooresponding hn(4) attached to it.

To ease user configuration for both network VF and non-network VF, the
lagg(4) will be created by the following rules, and the configuration
of the cooresponding hn(4) will be applied to the lagg(4) automatically.

Sponsored by: Microsoft
Differential Revision: https://reviews.freebsd.org/D11635

MFC 308664,308742,308743

308664
hyperv/vss: Add driver and tools for VSS

VSS stands for "Volume Shadow Copy Service". Unlike virtual machine
snapshot, it only takes snapshot for the virtual disks, so both
filesystem and applications have to aware of it, and cooperate the
whole 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 disabled
by editting /etc/devd/hyperv.conf.

Submitted by: Hongjiang Zhang <honzhan microsoft com>
Reviewed by: kib, mckusick
Sponsored by: Microsoft
Differential Revision: https://reviews.freebsd.org/D8224

308742
hyperv/vss: Nuke unused variables.

Submitted by: markj
Reported by: markj
Sponsored by: Microsoft

308743
hyperv/vss: Install the userland daemon to /usr/sbin instead of /

Submitted by: markj
Reported by: markj
Sponsored by: Microsoft

MFC r298783:
Regenerate usb.conf .

MFC r291703:
Regenerate usb.conf .

MFC r277730:

r277730:

Honor MK_ACPI in etc/devd and etc/rc.d

Sponsored by: EMC / Isilon Storage Division

MFC r270028:

r270028:

Make the USB and ZFS devd configuration files optional depending on the
values of MK_USB/MK_ZFS

Making zfs.conf optional resolves PR # 186971

PR: 186971
Phabric: D606
Approved by: jmmv (mentor)
Sponsored by: EMC / Isilon Storage Division

MFC r275790 and r275791:
Resolve USB driver identification conflict.
Regenerate etc/devd/usb.conf.

MFC r261894: move devd rules for zfs events into a separate file

... and fix stale event types

MFC r272253:

Regenerate usb.conf

Approved by: re, gjb

MFC r271493,271688-271689,271696,271854,272139-272143:

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 to
disable building and installing of the HyperV utilities when necessary.

The HyperV utilities are only built for i386 and amd64 targets.

Approved by: re (gjb)

Properly revert r272128.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Revert r272149, which introduces obscure vestiges from the
r272128 reversal.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Revert r272128:
Though this passes the buildworld test, this fails during
installworld with:

make[3]: "/releng/scripts-release/chroots/10/i386/release/etc/devd/Makefile"
line 13: Malformed conditional (${MK_HYPERV} != "no")

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

MFC r271493,271688,271689,271696,271854:

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 to
disable building and installing of the HyperV utilities when necessary.

The HyperV utilities are only built for i386 and amd64 targets.

Approved by: re (gjb)

MFC
Sync usb.conf file to head branch.

Regenerate after
r255238, r257044, r259453 (if_run)
r255128 (ng_ubt)
r259592 (u3g)

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Regenerate after recent addition of FTDI and bluetooth device IDs.

Regen for if_rsu.

Regenerate usb.conf

MFC after: 1 week

Regenerate usb.conf after r252196.

Spotted by: rpaulo

Regen.

Regenerate usb.conf

MFC after: 1 week

Regenerate usb.conf

MFC after: 1 week

Regenerate usb.conf

MFC after: 1 week

Regenerate usb.conf

MFC after: 1 week

Regenerate usb.conf

MFC after: 2 weeks

Regenerate usb.conf

MFC after: 3 days

Regenerate usb.conf to use new -n option when doing kldload.

MFC after: 1 week

Add backlight control to ATI-graphics PowerBooks and iBooks.

Approved by: nwhitehorn (mentor)
MFC after: 1 week

Re-generate /etc/devd/usb.conf

MFC after: 1 day

Remove the notify match from a couple devd apple events, the events don't
include notify tags.

Approved by: nwhitehorn (mentor)
MFC after: 3 days

Fix style(9) issues from r228270.

Approved by: nwhitehorn (mentor)

Add a devd notification for closing/opening the lid on PowerBooks and iBooks.

Approved by: nwhitehorn (mentor)

Add new USB IDs to RUN driver. Update usb.conf.

PR: usb/161798
MFC after: 3 days

Add support for special keys (volume/brightness/eject) on Apple laptops with
ADB keyboards.

Submitted by: Justin Hibbits <jrh29 at alumni dot cwru dot edu>
MFC after: 9.0-RELEASE

Regenerate usb.conf after r223566.

The SMCWUSBG is a zyd(4) device, not an uath(4) device. Remove from the
latter.

It appears that the addition to uath(4) came in through PR kern/135009,
which had tested another device, the SMCWUSBTG2, successfully with uath(4)
and included the SMCWUSBG as it "has the same chipset". I can find no
other evidence that these two do actually share the same chipset. Moreover,
Linux treats the SMCWUSBG as a zyd(4) device also.

This reverts r223537.

Discussed with: hselasky, kevlo
MFC after: 1 week

- Move bus_auto.conf back into /etc/devd/
- Rename bus_auto.conf into usb.conf

Requested by: imp @
MFC after: 14 days

- Move auto-load devd config file into etc/defaults folder.
- Regenerate file after bugfix in the generator.

Suggested by: Jeremy Messenger
MFC after: 14 days

- Export more USB device ID's.
- Update bus_auto.conf accordingly.

MFC after: 3 days

- Add auto-load devd config file for USB kernel modules.

MFC after: 14 days

Change usb devd events from fake attach to a notify. The ugen device is not a
proper device_t so it faked the devctl event to appear like one, this is now a
notify which allows more information to be passed.

We notify for both the device attach/detach and for each usb interface. A devd
rule can now match on the interface properties, including composite devices
which may have a uvideo interface and also usound and possibly uhid too.

An example to match a umass device with a scsi subclass and BBB protocol would be

notify 100 {
match "system" "USB";
match "subsystem" "INTERFACE";
match "type" "ATTACH";
match "intclass" "0x08";
match "intsubclass" "0x06";
match "intprotocol" "0x50";
action ...
};

The old attach devctl event has been retained for the moment to make merging to
8.1 easier. This was never compatible with 7.x or earlier due to the ugen regex
change needed.

Reviewed by: warner
MFC after: 1 week

adds a hardware specific configuration file for uath(4).

Pointed by: sam
Reviewed by: imp, thompsa

revert r187343

add FCC4 SKU to expose Public Safety Band (PSB) frequencies; this is
modeled after the Atheros SKU of the same name

Move another block of ASUS events to devd/asus.conf that were missed in r186249

Add /etc/devd/ and move hardware specific configuration there. This makes it
easier to maintain custom rules for non-system things like ACPI hotkeys.

/etc/devd.conf is already set up to check this directory, no change needed there.