| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ok kettenis@
|
|
|
|
|
|
being 0; after multiply there is no perturbance to the from-disk entropy
buffer. Further investigation showed perturbance was biased towards
the lower bytes of a word. Compensate for this with a hocus pocus
bit-spreading operation which applies a result byte by byte.
discussion with kettenis, tb, mlarkin, naddy
ok naddy
|
|
on the Samsung ATIV Book 9 laptop. This initial version only
supports ACPI config/attachment.
Add ihidev, a HID-over-i2c driver largely based on uhidev. dwiic
handles attaching ihidev devices found in ACPI.
Add ims, a HID-over-i2c mouse/trackpad driver to get basic cursor
and button functionality from HID-compliant i2c trackpads.
ok kettenis deraadt
|
|
|
|
displays. This makes sure the keyboard mux gets picked up by the primary
(console) display and that USB keyboards get paired with the console even
if they are not marked as the console keyboard. This is what most people
expect to happen. If you really want to associate your USB keyboard with
a secondary display, you can detach it from the mux using
wsconscfg -f /dev/ttyCcfg -k -d
and attach it to another display using
wsconscfg -f /dev/ttyDcfg -k
|
|
|
|
- compute fault reason for uvm_fault() (e.g. page not present,
protection violation) instead of passing a protection code
- a page does not need to be zero'd after faulting it in. uvm_fault() does
that for fresh anon pages already, and we also do not want a page that
is swapped back in have its contents wiped.
ok mlarkin@
|
|
"platform" devices that attach to acpi(4).
ok mlarkin@, deraadt@
|
|
These files aren't USB-specific and were used by the previous
Bluetooth implementation, and will be used by the upcoming
HID-over-i2C implementation
ok deraadt
previous version ok kettenis and mpi
|
|
This will allow to pledge vmd(8)'s vmm and vm processes, so that VMs
themselves run "sandboxed", including their host-side virtio layer.
It will remain disabled for now (in userland) to not get into the way
of ongoing development and upcoming changes in vmd and the ioctl
interface.
OK mlarkin@ deraadt@ "kernel side in, but not the callers in userland"
|
|
|
|
and check that is valid. Ensures that NVRAM is accessed at
sensible offsets.
Convert i386/nvram.c to uiomove() while there.
Diff from Martin Natano, thanks!
ok kettenis@, deraadt@
|
|
Encouragement from deraadt@, ok reyk
|
|
|
|
the same error messages on GPT processing failures.
Add a message about failed GPT entry checksum error to both. This
was inadvertantly deleted in the switch to one entry at a time
processing.
tweaks & ok yasuoka@ jsing@
|
|
for findopenbsd_gpt().
|
|
This should fix some of the odd termination errors people have been seeing
(vmctl status showing running VMs after they have exited/crashed, and
invalid instruction panics on vmptrld during certain races)
This diff also implements dropping the biglock when running a VCPU, and
reacquiring the lock as needed based on the type of exit (normal vs.
external interrupt)
diff supplied by Stefan Kempf <sn.kempf at t-online.de>, many thanks!
|
|
|
|
OpenBSD partition. Just one 128-byte stack copy of a single entry.
Problems with EFI installs involving many disks reported by and fix
tested by Thomas Bohl.
Stefan Kempf pointed finger of suspicion at the addition of the 2nd
16K static buffer for softraid GPT and suggested/reviewed several
versions of the diff.
Tweaked and ok jsing@
|
|
|
|
to the kernel rng. If the rdseed source is empty fallback to rdrand
as suggested by naddy. rdrand output comes from a prng that is
periodically reseeded. rdseed should give us more bits of entropy.
ok naddy@ djm@ deraadt@
|
|
starts at sector 1. Instead return -1, as for all other failures during
the header check.
|
|
non-static) by passing disk size as 2nd parameter instead of the
different structures holding the disk size info. The fifth copy of
gpt_chk_mbr() in fdisk is a little specialer. No functional change.
|
|
declarations of gpt_chk_mbr() to match prototypes in efidev.c and
softraid.c.
|
|
Another diff from Stefan Kempf <sn.kempf at t-online.de>.
|
|
Noticed over a month ago by Stefan Kempf <sn.kempf at t-online.de>, and I
shamefully just got around to committing it. Thanks Stefan.
|
|
Use the size info in struct sr_boot_volume, and not the uninitialized
info in the disklabel, when checking the GPT protective MBR. Now
both GPT and MBR formatted softraid volumes actually boot.
As a bonus add prototype for gpt_chk_mbr().
|
|
MBR/GPT.
Problem found the hard way by Glenn Faustino on tech@
|
|
boot from such volumes to match being able to install to them.
Problem spotted by jcs@, fix tested by rpe@, ok jsing@
|
|
This patch adds a new driver for use of virtio-console devices as
ttys. It's still in an early state and not compiled by default, yet.
Currently it is only wired into amd64. i386 is still missing.
Discussed with uebayasi@, deraadt@
|
|
|
|
decision as to how the vcpu should be set up for initial start and
reset. Also removes some hardcoded register constants from vmm(4).
ok jsing@, mpi@
|
|
|
|
later).
discussed with deraadt@ and reyk@ at length.
|
|
|
|
ok reyk@, beck@, mpi@
|
|
(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@
|
|
|
|
ok mlarkin
|
|
|
|
This is a simple driver for the virtual PCI device with only one
purpose: to allocate the interrupt vector and communicate that
to the Hypervisor in case the IDT callback method was not available.
With input from and OK deraadt, mlarkin, reyk, mpi
|
|
This adds support for delivering the combined Xen interrupt
that later fans out into event port specific (device specific)
interrupts via an IDT of a guest system.
The Xen IDT vector is set to be the first of the IPL_NET group
and is implemented the same way LAPIC timer and IPIs are done.
The additional machinery is there to be able to mask it via
standard mechanisms (e.g. splnet).
Discussed with kettenis@, OK mlarkin, reyk
|
|
Its location will be communicated with the Xen hypervisor
that will fill it in with instructions resulting in VMEXIT
events.
Discussed with kettenis@ and deraadt@, with input from and
OK mpi, mlarkin, reyk
|
|
With input from and OK mpi, mlarkin, reyk
|
|
"Intel Architecture Instruction Set Extensions Programming Reference"
|
|
|
|
|
