| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
OK deraadt@, mpi@
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
ok tedu@ krw@ deraadt@
|
|
|
|
|
|
|
|
|
| |
Emulate kvm pvclock in vmm(4). Compatible with pvclock(4) in OpenBSD. Linux
does not attach to this (yet).
Fixes by reyk@ and tested extensively by reyk@, tb@ and phessler@
ok mlarkin@ phessler@ reyk@
|
|
|
|
| |
From canacar@, thanks!
|
|
|
|
|
|
|
|
| |
cpu_hatch() on each cpu, allowing initialization of per-cpu features on each
cpu as it starts up.
input from reyk@ and mikeb@
ok mikeb@
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
OK mikeb@
|
|
|
|
| |
OK mikeb@ mlarkin@
|
|
|
|
|
|
|
| |
This sets hw.vendor to "OpenBSD" if running on vmm(4) because it
doesn't provide an SMBIOS.
OK mikeb@
|
|
|
|
| |
ok reyk (a while ago)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
|
|
|
| |
speedup interrupt handling on virtual machines. Unfortunately it is
broken on Xen 4.2 or older, so use the early pvbus detection to drop
the advertised x2APIC CPU feature. Xen has fixed this in late 2013,
but the problem still shows up in "the Cloud" (it doesn't seem to
affect others as they either use legacy APIC or Xen IPIs).
OK mlarkin@ mikeb@
Cvs: ----------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
| |
(bios, CPU, interrupt handlers, pvbus). This splits the pvbus attach
function into two parts: pvbus_identify() to scan the CPUID registers
for supported hypervisors and pvbus_attach() to attach the bus, print
information, and configure the children.
This will be needed for Xen and KVM, as discussed with mikeb@ and sf@
OK mlarkin@
|
|
|
|
|
|
|
| |
on amd64. make sure the signature is not null before using it in
pvbus_attach.
fixes a panic on i386 under vmware.
|
| |
|
|
|
|
| |
circulated on hackers@, no objections. Disabled by default.
|
|
|
|
| |
ok reyk, with deraadt@'s permission
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
OK mlarkin@
|
|
|
|
|
|
| |
listed in pvbus.c anymore and are defined by the config only.
OK mlarkin@ sf@
|
|
vmt(4) is moved from mainbus0 to pvbus0, more devices will follow.
OK sf@ deraadt@
|