<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/amd64/include/pmap.h, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64/include/pmap.h?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64/include/pmap.h?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-01-24T05:27:31Z</updated>
<entry>
<title>Machines have started to appear that have the framebuffer at an address &gt; 4GB.</title>
<updated>2020-01-24T05:27:31Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-01-24T05:27:31Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4034e82e838fba757df621c4556dc2f3ec20ad8a'/>
<id>urn:sha1:4034e82e838fba757df621c4556dc2f3ec20ad8a</id>
<content type='text'>
On these machines we can't use the direct map since early on during boot
the direct map only covers the first 4GB of memory.  Instead, use a
special (and temporary) mapping until we remap the framebuffer near the
start of autoconf.  With lots of help from mlarkin@

tested by yasuoka@
ok mlarkin@
</content>
</entry>
<entry>
<title>Convert boolean_t/TRUE/FALSE to int/1/0 for coherency with the rest of</title>
<updated>2019-12-19T17:42:17Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-12-19T17:42:17Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=46ad639f8a81d6d74469923b6ae79d06102cfe8d'/>
<id>urn:sha1:46ad639f8a81d6d74469923b6ae79d06102cfe8d</id>
<content type='text'>
the kernel.

ok mlarkin@, visa@
</content>
</entry>
<entry>
<title>vmm(4): flush EPT when uvm removes mappings from a nested page table</title>
<updated>2019-04-01T12:45:49Z</updated>
<author>
<name>mlarkin</name>
<email>mlarkin@openbsd.org</email>
</author>
<published>2019-04-01T12:45:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a4cc50f2fbc5778f7e2355255b9855813e689090'/>
<id>urn:sha1:a4cc50f2fbc5778f7e2355255b9855813e689090</id>
<content type='text'>
Ensure TLB is flushed to avoid stale entries when uvm removes
entries from a guest VM's EPT. This is done on VM teardown and when uvm
pages out pages in low memory situations. Prompted by a conversation with
Maxime from NetBSD a few months back.

ok deraadt
</content>
</entry>
<entry>
<title>Remove PTPpaddr and use proc0.p_addr-&gt;u_pcb.pcb_cr3 instead.  This also</title>
<updated>2019-02-18T08:26:19Z</updated>
<author>
<name>yasuoka</name>
<email>yasuoka@openbsd.org</email>
</author>
<published>2019-02-18T08:26:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cec5b69eefeefb57cbfc7447c70420c978290594'/>
<id>urn:sha1:cec5b69eefeefb57cbfc7447c70420c978290594</id>
<content type='text'>
fixes kernel core dump to be readable by savecore.  From fukaumi at
soum.co.jp

ok mlarkin
</content>
</entry>
<entry>
<title>Support 2TB phys mem</title>
<updated>2019-01-21T06:18:37Z</updated>
<author>
<name>mlarkin</name>
<email>mlarkin@openbsd.org</email>
</author>
<published>2019-01-21T06:18:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d2fed53307d3e5c422efbfbe0dfa3c7c28017b4f'/>
<id>urn:sha1:d2fed53307d3e5c422efbfbe0dfa3c7c28017b4f</id>
<content type='text'>
This change expands the direct map to 4 slots (512GB each), to support
machines with up to 2TB physical memory. Should further expansion be
required, this change provides the means to do that with a single #define
change.

with help from and ok guenther
</content>
</entry>
<entry>
<title>Finish randominzing remaining layers of pmap_kernel</title>
<updated>2019-01-19T04:07:12Z</updated>
<author>
<name>mlarkin</name>
<email>mlarkin@openbsd.org</email>
</author>
<published>2019-01-19T04:07:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a821d2d923695ae92270fff2f115f92c395ac2e0'/>
<id>urn:sha1:a821d2d923695ae92270fff2f115f92c395ac2e0</id>
<content type='text'>
An earlier diff moved the top level page, this diff finishes the lower
layers. New pages are allocated for the existing hiererchy (which thus
benefit from random placement from pmemrange/etc). Existing managed
pages are returned to uvm (a small number of bootstrap pages are not
returned as they are allocated in locore0 and thus aren't managed).

ok deraadt
</content>
</entry>
<entry>
<title>Move the placement of pmap_kernel's toplevel PML4 page</title>
<updated>2019-01-11T06:25:06Z</updated>
<author>
<name>mlarkin</name>
<email>mlarkin@openbsd.org</email>
</author>
<published>2019-01-11T06:25:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=163e3b0334749ff7e4680e34ca331817ffdc4098'/>
<id>urn:sha1:163e3b0334749ff7e4680e34ca331817ffdc4098</id>
<content type='text'>
This change moves the PML4 for pmap_kernel elsewhere during early boot.
Lower levels of pmap_kernel will be moved in subsequent changes, but there
are other pmap changes coming that need to be integrated first.

In snaps for 3 days, no fallout seen.

ok deraadt and substantial input and help from guenther@

cvs: ----------------------------------------------------------------------
</content>
</entry>
<entry>
<title>Increase L2 PTE reservation for the kernel</title>
<updated>2019-01-06T21:43:19Z</updated>
<author>
<name>mlarkin</name>
<email>mlarkin@openbsd.org</email>
</author>
<published>2019-01-06T21:43:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bfaa8ac6909948835231b0d403817ee2410ae5be'/>
<id>urn:sha1:bfaa8ac6909948835231b0d403817ee2410ae5be</id>
<content type='text'>
Bump the number of L2 page table entries reserved for the kernel from 16
to 64, to allow for larger kernels. This diff was in snaps for 21 days
without any reported fallout.

ok deraadt
</content>
</entry>
<entry>
<title>Use PCIDs where they and the INVPCID instruction are available.</title>
<updated>2018-10-04T05:00:40Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2018-10-04T05:00:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f95e373fb5dc99ea1b42391f80bd0d1296af1362'/>
<id>urn:sha1:f95e373fb5dc99ea1b42391f80bd0d1296af1362</id>
<content type='text'>
This uses one PCID for kernel threads, one for the U+K tables of
normal processes, one for the matching U-K tables (when meltdown
in effect), and one for temporary mappings when poking other
processes.  Some further tweaks are envisioned but this is good
enough to provide more separation and has (finally) been stable
under ports testing.

lots of ports testing and valid complaints from naddy@ and sthen@
feedback from mlarkin@ and sf@
</content>
</entry>
<entry>
<title>Delete the reserve_dumppages() declaration, missed in its 2010 removal</title>
<updated>2018-09-30T18:46:09Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2018-09-30T18:46:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=247dae0587f80739edcb610b80f36a62051e5c13'/>
<id>urn:sha1:247dae0587f80739edcb610b80f36a62051e5c13</id>
<content type='text'>
ok deraadt@
</content>
</entry>
</feed>
