| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
CID 1501713
ok jmatthew@
|
|
|
|
|
|
| |
here 10 years ago, xdr isn't scary at all.
ok dlg@
|
|
|
|
|
|
|
| |
allocated as part of the softc, though it's always been the same buffer
so far.
ok dlg@
|
|
|
|
| |
ok dlg@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
time_second(9) and time_uptime(9) are widely used in the kernel to
quickly get the system UTC or system uptime as a time_t. However,
time_t is 64-bit everywhere, so it is not generally safe to use them
on 32-bit platforms: you have a split-read problem if your hardware
cannot perform atomic 64-bit reads.
This patch replaces time_second(9) with gettime(9), a safer successor
interface, throughout the kernel. Similarly, time_uptime(9) is replaced
with getuptime(9).
There is a performance cost on 32-bit platforms in exchange for
eliminating the split-read problem: instead of two register reads you
now have a lockless read loop to pull the values from the timehands.
This is really not *too* bad in the grand scheme of things, but
compared to what we were doing before it is several times slower.
There is no performance cost on 64-bit (__LP64__) platforms.
With input from visa@, dlg@, and tedu@.
Several bugs squashed by visa@.
ok kettenis@
|
|
|
|
|
|
| |
conversion steps). it only contains kernel prototypes for 4 interfaces,
all of which legitimately belong in sys/systm.h, which are already included
by all enqueue_randomness() users.
|
|
|
|
|
|
|
|
| |
ESXi doesn't carry the guest info over when a guest gets moved to a
different host, and this appears to be the only hint the guest gets
that this has happened.
ok dlg@
|
| |
|
|
|
|
|
|
|
|
|
| |
this gets rid of the source annotation which doesn't really add
anything other than adding complexitiy. randomess is generally
good enough that the few extra bits that the source type would
add are not worth it.
ok mikeb@ deraadt@
|
|
|
|
|
|
|
| |
clone running guests and take disk-only snapshots, most of the time ending
up with a clean filesystem.
ok dlg@ deraadt@
|
|
|
|
| |
from Seth Jackson
|
|
|
|
|
|
|
| |
of a shutdown. Correct a mistake in rev 1.11 to make this trigger a
shutdown again.
ok reyk@
|
|
|
|
|
|
|
|
| |
tasks from the PV drivers into a central place. While here, we
figured out that it is not needed to check for allowpowerdown on the
hypervisor-initiated shutdown requests.
OK mikeb@
|
|
|
|
|
|
| |
string literal" warning from clang.
ok jca@
|
|
|
|
|
|
|
|
|
|
|
| |
mechanism is used to configure VMs in the VMware vSphere world:
instead of using individual key-value guestinfo.* properties, it uses
the guestinfo.ovfEnv value to pass an enterprise-compliant XML file
that includes key-value properties. This file can be rather large,
especially with comments, but 4k ought to be enough for anybody.
Also change a stack buffer to malloc'ed memory in the ioctl path.
OK mikeb@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the underlying information store of the host from the OpenBSD-VM's
userspace. OpenBSD did not provide access to these stores before,
mostly because we did not want to add a custom tool and interface for
each hypervisor. The pvbus(4) interface provides backends for
xen(4)'s XenStore and vmt(4)'s VMware Tools "guestinfo". These
information stores are fairly different, XenStore is a "filesystem"
while vmt is a RPC, and the key-value abstraction limits them a bit
but provides the most wanted functionality.
Discussed with many
OK mikeb@
|
|
|
|
| |
Fix a regression reported by Ian Mcwilliam on tech@
|
|
|
|
|
|
| |
similar to config_defer(9).
ok mikeb@, deraadt@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
information and for some generic CPUID/MSR-level initialization. This
changes the attach/match path a bit.
Hypervisor informatiom may include a version number, for example:
pvbus0 at mainbus0: Hyper-V 6.3.9600
OK mlarkin@
|
|
|
|
|
|
| |
listed in pvbus.c anymore and are defined by the config only.
OK mlarkin@ sf@
|
|
in the Attic of sys/dev/vmt.c.
OK to do it deraadt@
|