summaryrefslogtreecommitdiffstats
path: root/lib/libpcap/optimize.c
diff options
context:
space:
mode:
authorkettenis <kettenis@openbsd.org>2014-06-25 18:56:22 +0000
committerkettenis <kettenis@openbsd.org>2014-06-25 18:56:22 +0000
commit71843e79c5d112344ecc513c9ddc6fcb14ce3162 (patch)
treeaadf5bb73e34a5bab3e4632dbde312ae4a8ef27f /lib/libpcap/optimize.c
parentApply/fix OpenBSD tag. (diff)
downloadwireguard-openbsd-71843e79c5d112344ecc513c9ddc6fcb14ce3162.tar.xz
wireguard-openbsd-71843e79c5d112344ecc513c9ddc6fcb14ce3162.zip
So it turns out that there is AML out there that asks for an access
width that isn't compatible with the alignment of the region: OperationRegion (SATC, SystemMemory, 0xE008800A, 0x04) Field (SATC, DWordAcc, NoLock, Preserve) { STCL, 16 } DWordAcc means 4-byte access, but 0xE008800A is only 2-byte aligned. Moreover, the region itself is 4 bytes long. From this I conclude that 4-byte wide access to a 2-byte aligned address is really wanted in cases like this. ok deraadt@
Diffstat (limited to 'lib/libpcap/optimize.c')
0 files changed, 0 insertions, 0 deletions