wireguard-openbsd/sys/arch/amd64, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64?h=master2021-03-29T12:39:02ZFix IA32_EPT_VPID_CAP_XO_TRANSLATIONS specification2021-03-29T12:39:02Zdvdv@openbsd.org2021-03-29T12:39:02Zurn:sha1:b134fa217db201f6e402bd40b585b1dd8064d634
Per Intel SDM (Vol 3D, App. A.10) bit 0 should be read as a 1 if enabled.
From Adam Steen. ok mlarkin@
The logic in mmrw() to check whether an address is within direct2021-03-24T14:26:39Zbluhmbluhm@openbsd.org2021-03-24T14:26:39Zurn:sha1:fc24682d162d1168f8409889883aa738fd923555
map was the wrong way around. The && prevented an EFAULT error and
could pass userland addresses as kernel source to copyout(9). The
kernel could crash with protection fault due to an invalid offset
when reading /dev/kmem.
Also make the range checks stricter. Not only the start address
must be valid, but also the end address must be within the region
to be copied.
Note that sysctl kern.allowkmem=0 makes the bug unreachable by
default.
OK deraadt@
another unfortunate action to cope with relentless kernel growth2021-03-19T04:30:56Zderaadtderaadt@openbsd.org2021-03-19T04:30:56Zurn:sha1:38c12d68c127995c7ac992225b26048cabbdbb91Always use an allocated buffer for {Read,Write}Blocks() to make2021-03-17T05:41:34Zyasuokayasuoka@openbsd.org2021-03-17T05:41:34Zurn:sha1:6202161edfd7c245b686aa7e49ac4d4ecfad7dda
efid_io() simpler. Also fixes the problem on some machines when boot
from CD-ROM. It happened because the previous version passed
unaligned pointers to the functions even if it is restricted by the
IoAlign property of the media. idea from kettenis, work with asou
ok kettenis
Add acpi_iommu_device_map(), which replaces the DMA tag with one that2021-03-15T22:44:57Zpatrickpatrick@openbsd.org2021-03-15T22:44:57Zurn:sha1:c375c363d9025b334c6cea967bb0cee9d9a41169
is blessed with IOMMU magic, if available. This is mainly for arm64,
since on amd64 and i386 the IOMMU only captures PCIe devices, as far
as I know, which uses the pci_probe_device_hook(). This though is for
non-PCI devices attached through ACPI.
ok kettenis@
spelling2021-03-11T11:16:54Zjsgjsg@openbsd.org2021-03-11T11:16:54Zurn:sha1:36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2Explicitly align kernel text.2021-03-07T23:10:54Zmortimermortimer@openbsd.org2021-03-07T23:10:54Zurn:sha1:3a759fb4b59efc98bb650e48d2acd4988fceee0e
lld11 no longer quietly aligns this when given an address, so we do the
alignment explicitly.
ok kettenis@
timecounting: use C99-style initialization for all timecounter structs2021-02-23T04:44:30Zchelohacheloha@openbsd.org2021-02-23T04:44:30Zurn:sha1:8611d3cdb295683ad47c33036b86b471b2d09741
The timecounter struct is large and I think it may change in the
future. Changing it later will be easier if we use C99-style
initialization for all timecounter structs. It also makes reading the
code a bit easier.
For reasons I cannot explain, switching to C99-style initialization
sometimes changes the hash of the resulting object file, even though
the resulting struct should be the same. So there is a binary change
here, but only sometimes. No behavior should change in either case.
I can't compile-test this everywhere but I have been staring at the
diff for days now and I'm relatively confident this will not break
compilation. Fingers crossed.
ok gnezdo@
Fix a comment2021-02-13T07:55:38Zmlarkinmlarkin@openbsd.org2021-02-13T07:55:38Zurn:sha1:f58493bac91e05fd7fda6c3bbf99d9b31f57e44aRemove trailing whitespace2021-02-13T07:47:37Zmlarkinmlarkin@openbsd.org2021-02-13T07:47:37Zurn:sha1:7df4ff5832b0c9c04f1584e52cdaacd75171dcda
No code/functional change