<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/m88k/include, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/m88k/include?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/m88k/include?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>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>Include srp.h where struct cpu_info uses srp to avoid erroring out when</title>
<updated>2018-12-05T10:28:21Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2018-12-05T10:28:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1a1181a966226532433438cb3741ae7cdc0727d4'/>
<id>urn:sha1:1a1181a966226532433438cb3741ae7cdc0727d4</id>
<content type='text'>
including cpu.h machine/intr.h etc without first including param.h when
MULTIPROCESSOR is defined.

ok visa@
</content>
</entry>
<entry>
<title>Unify and bump some of the NMBCLUSTERS defines. Some archs had it set to</title>
<updated>2018-09-14T13:58:20Z</updated>
<author>
<name>claudio</name>
<email>claudio@openbsd.org</email>
</author>
<published>2018-09-14T13:58:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=965127f80578c0400be53e4188190c636e97095a'/>
<id>urn:sha1:965127f80578c0400be53e4188190c636e97095a</id>
<content type='text'>
4MB which is far too low especially when the platform is able to run MP.
New limits are, amd64 = 256M; arm64, mips64, sparc64 = 64M; alpha, arm,
hppa, i386, powerpc = 32M; m88k, sh = 8M
Still rather conservative numbers but much better than before. At least
some hangs of arm64 build boxes was caused by this.
OK kettenis@, visa@
</content>
</entry>
<entry>
<title>Adding membar_xxx defines to userland.</title>
<updated>2018-08-22T11:25:58Z</updated>
<author>
<name>aoyama</name>
<email>aoyama@openbsd.org</email>
</author>
<published>2018-08-22T11:25:58Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=fc343cf934d04b41f9abaa99e672a3beee955880'/>
<id>urn:sha1:fc343cf934d04b41f9abaa99e672a3beee955880</id>
<content type='text'>
The src/lib/libc/thread/rthread.c 1.8 change adds #include
&lt;sys/atomic.h&gt; in userland code.

Current m88k atomic.h contents are inside of #if defined(_KERNEL)
guard, then, nothing is defined for userland program.
So we need adding some defines to compile it on m88k.

The original diff is suggested from Miod Vallat, modified by the
advice from mpi@ and kettenis@.

ok kettenis@
</content>
</entry>
<entry>
<title>Remove unused spllock().</title>
<updated>2018-08-20T15:02:07Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2018-08-20T15:02:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=864f2f83ec4c08eb41848f403ee4e5dadd8f3951'/>
<id>urn:sha1:864f2f83ec4c08eb41848f403ee4e5dadd8f3951</id>
<content type='text'>
OK deraadt@ mpi@
</content>
</entry>
<entry>
<title>Make luna88k use the MI mplock implementation.</title>
<updated>2018-03-12T11:17:06Z</updated>
<author>
<name>aoyama</name>
<email>aoyama@openbsd.org</email>
</author>
<published>2018-03-12T11:17:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d17918f32781f7a1ace999fc004e52c3d45248a8'/>
<id>urn:sha1:d17918f32781f7a1ace999fc004e52c3d45248a8</id>
<content type='text'>
ok visa@
</content>
</entry>
</feed>
