<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/arm/include, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/arm/include?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/arm/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>Add machdep.compatible.</title>
<updated>2020-05-17T15:36:50Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-05-17T15:36:50Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c5c0009c6b631723b5fb95feae57638eaf156035'/>
<id>urn:sha1:c5c0009c6b631723b5fb95feae57638eaf156035</id>
<content type='text'>
ok jsg@
</content>
</entry>
<entry>
<title>Let the armv7 bus_dma layer and simplebus(4) implementation deal with</title>
<updated>2020-04-29T15:25:07Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-04-29T15:25:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=37084e1e34e6eafe959b14d27c905d6c5ddf0888'/>
<id>urn:sha1:37084e1e34e6eafe959b14d27c905d6c5ddf0888</id>
<content type='text'>
DMA remapping in the same way as arm64.  This relies on the dma-ranges
property in the device tree and allows us to get rid of the hack for
the Raspberry Pi in the dwctwo(4) driver.

Note that this does not include the hack in simplebus(4) that we have on
arm64 since firmware that has the dma-ranges is in widespread use now.

ok patrick@
</content>
</entry>
<entry>
<title>Implement cpu_kick() and cpu_unidle().</title>
<updated>2020-01-12T16:55:00Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-01-12T16:55:00Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=056a2ca64e92b2e792c6ef8deb8255cee5ff099b'/>
<id>urn:sha1:056a2ca64e92b2e792c6ef8deb8255cee5ff099b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Convert boolean_t/TRUE/FALSE to int/1/0 for coherency with the rest of</title>
<updated>2019-12-19T17:53:27Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-12-19T17:53:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=20b8e21a6ed450b3757a6f438fd47483feb5bfe0'/>
<id>urn:sha1:20b8e21a6ed450b3757a6f438fd47483feb5bfe0</id>
<content type='text'>
the kernel.

ok patrick@
</content>
</entry>
<entry>
<title>Remove get_pc_str_offset(), which has been unused since we switched</title>
<updated>2019-11-07T21:54:49Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2019-11-07T21:54:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=fdf77656d36f9b7b81b91b3200ebf153cd1a0460'/>
<id>urn:sha1:fdf77656d36f9b7b81b91b3200ebf153cd1a0460</id>
<content type='text'>
to clang, where the stack frame format changed significantly.

Prompted by guenther@ noticing deprecated ASM warnings
ok drahn@
</content>
</entry>
<entry>
<title>Convert db_addr_t -&gt; vaddr_t but leave the typedef for now.</title>
<updated>2019-11-07T14:44:52Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-07T14:44:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6d6b8a876ccc0691e0769b505db074d6e7d968ef'/>
<id>urn:sha1:6d6b8a876ccc0691e0769b505db074d6e7d968ef</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add code to spin up secondary CPUs.</title>
<updated>2019-10-27T10:26:12Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2019-10-27T10:26:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4e7e04ca925b10f704b4398d5900b06e3f194bba'/>
<id>urn:sha1:4e7e04ca925b10f704b4398d5900b06e3f194bba</id>
<content type='text'>
ok jsg@
</content>
</entry>
<entry>
<title>Synch the cpu match/attach/identify code with arm64.  This drops some</title>
<updated>2019-09-30T21:48:32Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2019-09-30T21:48:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6a1ae6a6f2650c25cd442f350f6dc0fc16c4e5be'/>
<id>urn:sha1:6a1ae6a6f2650c25cd442f350f6dc0fc16c4e5be</id>
<content type='text'>
information from dmesg that is no longer relevant to ARMv7 CPUs in favour
of printing the full architected cache hierarchy in the same way as we
do on arm64.  It also is another small step towards SMP support on armv7.

ok patrick@
</content>
</entry>
<entry>
<title>Implement DVFS support.</title>
<updated>2019-09-23T18:10:43Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2019-09-23T18:10:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3d29854d4b138f482ccdf6aa653e7f3f8371b152'/>
<id>urn:sha1:3d29854d4b138f482ccdf6aa653e7f3f8371b152</id>
<content type='text'>
ok patrick@
</content>
</entry>
</feed>
