<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/alpha/include/param.h, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/alpha/include/param.h?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/alpha/include/param.h?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2019-03-24T06:19:26Z</updated>
<entry>
<title>Add intr_{disable,restore}() for alpha.</title>
<updated>2019-03-24T06:19:26Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2019-03-24T06:19:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a7f4c0eaa5a9c1b02cf8b788f1a2165abcf9ece2'/>
<id>urn:sha1:a7f4c0eaa5a9c1b02cf8b788f1a2165abcf9ece2</id>
<content type='text'>
Reminded by deraadt@
</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>Split early startup code out of locore.S into locore0.S.  Adjust link</title>
<updated>2017-06-05T17:49:05Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2017-06-05T17:49:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=599a5352d9cf80c1cd045c515cf0ac6464b69dad'/>
<id>urn:sha1:599a5352d9cf80c1cd045c515cf0ac6464b69dad</id>
<content type='text'>
run so that this locore0.o is always at the start of the executable.
But randomize the link order of all other .o files in the kernel, so
that their exec/rodata/data/bss segments land all over the place.

Late during kernel boot, smash the startup code with traps so that
it does not point to the other randomly placed code.  It has be smashed,
because alpha (insecurely in my view) runs in the KSEG0 space.

As a result, the internal layout of every newly build bsd kernel is
different from past kernels.  Internal relative offsets are not known
to an outside attacker.  The only known offsets are in the startup code,
which is gone.

Ramdisk kernels cannot be compiled like this, because they are gzip'd.
When the internal pointer references change, the compression dictionary
bloats and results in poorer compression.
</content>
</entry>
<entry>
<title>Increase the number of mbufs on most architectures.  This is based</title>
<updated>2016-09-03T14:25:27Z</updated>
<author>
<name>bluhm</name>
<email>bluhm@openbsd.org</email>
</author>
<published>2016-09-03T14:25:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=29ae43e03c22032641bd3695f0b2a4c78063ba5d'/>
<id>urn:sha1:29ae43e03c22032641bd3695f0b2a4c78063ba5d</id>
<content type='text'>
on a guess how much memory a typical machine has.  If the value is
too high, users may run out of kernel memory.  Then we will have
to adjust this again.
OK claudio@ deraadt@
</content>
</entry>
<entry>
<title>PGSHIFT and PGOFSET are now contained inside the kernel namespace.</title>
<updated>2013-03-26T05:04:08Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2013-03-26T05:04:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=12595cf0735ae1d6bf93e51af1e7681889b30fc4'/>
<id>urn:sha1:12595cf0735ae1d6bf93e51af1e7681889b30fc4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ALIGNBYTES/ALIGN/ALIGNED_POINTER can move to the MI file.</title>
<updated>2013-03-25T17:46:22Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2013-03-25T17:46:22Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c875ba1b10349764901915212dce1355eced2088'/>
<id>urn:sha1:c875ba1b10349764901915212dce1355eced2088</id>
<content type='text'>
</content>
</entry>
<entry>
<title>refactor sys/param.h and machine/param.h.  A lot of #ifdef _KERNEL is added</title>
<updated>2013-03-23T16:12:18Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2013-03-23T16:12:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=184e2458f7c67437a49d9b4a6fb8f1b69c45f54b'/>
<id>urn:sha1:184e2458f7c67437a49d9b4a6fb8f1b69c45f54b</id>
<content type='text'>
to keep definitions our of user space.  The MD files now follow a consistant
order -- all namespace intrusion is at the tail can be cleaned up
independently.  locore, bootblocks, and libkvm still see enough visibility to
build.  Checked on 90% of platforms...
</content>
</entry>
<entry>
<title>Stop the song and dance where alpha param.h tries to include the world.</title>
<updated>2012-06-26T01:59:47Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2012-06-26T01:59:47Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6a6a52e026ea9eee4438599f5606005afa38bf0d'/>
<id>urn:sha1:6a6a52e026ea9eee4438599f5606005afa38bf0d</id>
<content type='text'>
"Why is this not commited yet?" says miod
</content>
</entry>
<entry>
<title>Provide namespace-safe alignment macros in &lt;machine/_types.h&gt;, with</title>
<updated>2011-09-08T03:40:32Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2011-09-08T03:40:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=28644381e51472c2bf95d1f309edd17b4cb3334d'/>
<id>urn:sha1:28644381e51472c2bf95d1f309edd17b4cb3334d</id>
<content type='text'>
compat names kept in &lt;machine/param.h&gt;.  In &lt;sys/socket.h&gt;, pull
in &lt;sys/_types.h&gt; instead of the namespace polluting &lt;machine/param.h&gt;
and completely eliminate __CMSG_ALIGN, replaced by _ALIGN

ok deraadt@
</content>
</entry>
<entry>
<title>Link the kernel at a higher physical address, in order to accomodate SRM</title>
<updated>2009-10-02T17:57:20Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2009-10-02T17:57:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=0e0c4f51b685ae875a22970a537e3ba66410d40b'/>
<id>urn:sha1:0e0c4f51b685ae875a22970a537e3ba66410d40b</id>
<content type='text'>
with larger footprint than the usual 2MB, as encountered on some of the
most recent alpha systems.
Tested on many models (DEC 3000, PC164, AS500, ES40, and more)
</content>
</entry>
</feed>
