<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/m88k, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/m88k?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/m88k?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-05-31T06:23:56Z</updated>
<entry>
<title>introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.</title>
<updated>2020-05-31T06:23:56Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2020-05-31T06:23:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=01802d2cc63d886227ab3b39e923ff13cf516166'/>
<id>urn:sha1:01802d2cc63d886227ab3b39e923ff13cf516166</id>
<content type='text'>
rnd.c uses nanotime to get access to some bits that change quickly
between events that it can mix into the entropy pool. it doesn't
use nanotime to get a monotonically increasing set or ordered and
accurate timestamps, it just wants something with bits that change.

there's been discussions for years about letting rnd use a clock
that's super fast to read, but not necessarily accurate, but it
wasn't until recently that i figured out it wasn't interested in
time at all, so things like keeping a fast clock coherent between
cpu cores or correct according to ntp is unecessary. this means we
can just let rnd read the cycle counters on cpus and things will
be fine.  cpus with cycle counters that vary in their speed and
arent kept consistent between cores may even be desirable in this
context.

so this is the first step in converting rnd.c to reading cycle
counter. it copies the nanotime backend to each arch, and they can
replace it with something MD as a second step later on.

djm@ suggested rnd_messybytes, but we landed on cpu_rnd_messybits.
thanks to visa for his eyes.
ok deraadt@ visa@
deraadt@ says he will help handle any MD fallout that occurs.
</content>
</entry>
<entry>
<title>Retire &lt;machine/varargs.h&gt;.</title>
<updated>2020-05-27T15:16:04Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2020-05-27T15:16:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=9df0f941a91e9f67cc4e63514cb174cb2a5783fd'/>
<id>urn:sha1:9df0f941a91e9f67cc4e63514cb174cb2a5783fd</id>
<content type='text'>
Nothing uses the header anymore.

OK deraadt@ mpi@
</content>
</entry>
<entry>
<title>Rewrite m88k mutex code as a slight variation of the MI mutex code.</title>
<updated>2020-05-26T11:55:10Z</updated>
<author>
<name>aoyama</name>
<email>aoyama@openbsd.org</email>
</author>
<published>2020-05-26T11:55:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=406e3054fc812f8b8a6e22f1c3dac8f6eb192cb0'/>
<id>urn:sha1:406e3054fc812f8b8a6e22f1c3dac8f6eb192cb0</id>
<content type='text'>
This will make mutex spinning time visible in top(1), and also might
improve stability.

The major change in this is that the old assembly code acquires
mutexes with an atomic exchange operation, but releases them with a
regular store, but the new code always uses atomic exchange
operations.

The mutex.h changes to the macros conform to &lt;sys/mutex.h&gt; to be able
to reset the system while in ddb.

Suggested from Miod Vallat, tested by me.  The stability in heavy load
is greatly improved in my case.
</content>
</entry>
<entry>
<title>%r26 hasn't been used by the threads implementation since 2016, so stop</title>
<updated>2019-12-11T07:21:40Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2019-12-11T07:21:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d74b3acf9e5d38e93ba0fbd936b150afff3002d5'/>
<id>urn:sha1:d74b3acf9e5d38e93ba0fbd936b150afff3002d5</id>
<content type='text'>
resetting it in child_return() and update the comment in tcb.h to reflect
reality

ok miod@ aoyama@
</content>
</entry>
<entry>
<title>TRUE/FALSE conversions missed in previous.</title>
<updated>2019-11-10T10:03:33Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-10T10:03:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b547fb050cbc08fba20d5ee728621a5aa26ba4ee'/>
<id>urn:sha1:b547fb050cbc08fba20d5ee728621a5aa26ba4ee</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Substitute boolean_t/TRUE/FALSE/db_addr_t by int/1/0/vaddr_t.</title>
<updated>2019-11-08T15:01:15Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-08T15:01:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=83877b198dc3df85fd0fee8f8e66e0f613b2046e'/>
<id>urn:sha1:83877b198dc3df85fd0fee8f8e66e0f613b2046e</id>
<content type='text'>
Tested by miod@, ok aoyama@
</content>
</entry>
<entry>
<title>Reduce the number of places where `p_priority' and `p_stat' are set.</title>
<updated>2019-10-15T10:05:43Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-10-15T10:05:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=76e7c40e8276d973d8030fe2aad05ecbf2cea0ad'/>
<id>urn:sha1:76e7c40e8276d973d8030fe2aad05ecbf2cea0ad</id>
<content type='text'>
This refactoring will help future scheduler locking, in particular to
shrink the SCHED_LOCK().

No intended behavior change.

ok visa@
</content>
</entry>
<entry>
<title>If uvm_map_inentry returns false then a signal has been delivered, and</title>
<updated>2019-09-06T12:22:01Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-09-06T12:22:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a0da50afa400c90214087c1ffef69c7f438478e9'/>
<id>urn:sha1:a0da50afa400c90214087c1ffef69c7f438478e9</id>
<content type='text'>
userret() must be called on trap() exit to deliver it, rather than
repeating the same cause infinitely.  discovered by George Koehler
ok kettenis bluhm visa
</content>
</entry>
<entry>
<title>sys/arch/luna88k/luna88k/locore0.S:dummy_cpu assumes that</title>
<updated>2019-08-28T13:48:40Z</updated>
<author>
<name>aoyama</name>
<email>aoyama@openbsd.org</email>
</author>
<published>2019-08-28T13:48:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8db9df62777b1c1bb6e93e6a1287c8982debb860'/>
<id>urn:sha1:8db9df62777b1c1bb6e93e6a1287c8982debb860</id>
<content type='text'>
ci_mp_atomic_{begin,end} are 6th and 7th elements of cpu_info
structure.  Actually that is dummy structure used in early boot stage,
but for consistency, move ci_srp_hazards position in cpu_info.

ok mpi@
</content>
</entry>
<entry>
<title>Increment `db_active' before entering db_trap() like other archs do.</title>
<updated>2019-07-20T23:03:55Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-07-20T23:03:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ddb88ac25d4f894c9e5cf0750f4ddf70a69a0b9b'/>
<id>urn:sha1:ddb88ac25d4f894c9e5cf0750f4ddf70a69a0b9b</id>
<content type='text'>
ok visa@
</content>
</entry>
</feed>
