<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/dev/pci/ppb.c, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/pci/ppb.c?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/pci/ppb.c?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2019-04-23T19:37:35Z</updated>
<entry>
<title>Since ppb(4) properly allocates bus ranges for attached devices,</title>
<updated>2019-04-23T19:37:35Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2019-04-23T19:37:35Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4c9de485a3341c3ad6c7595f8b8929956025baa3'/>
<id>urn:sha1:4c9de485a3341c3ad6c7595f8b8929956025baa3</id>
<content type='text'>
the hotplug code doesn't need to do the same.  Also the hotplug
code only configured a single bus and did that before the proper
allocation ran, so there was no chance for hotplugged ppb(4)s to
have children busses.

ok kettenis@
</content>
</entry>
<entry>
<title>When we encounter ppb(4)s that are not configured we allocate a range</title>
<updated>2019-04-16T18:03:07Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2019-04-16T18:03:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=449408a90202e178acd7af3d254f64b67eeb7376'/>
<id>urn:sha1:449408a90202e178acd7af3d254f64b67eeb7376</id>
<content type='text'>
of bus numbers from the parent's bus extent.  On detach, which can
happen with hotplug-able devices, we should free those busses.

ok kettenis@
</content>
</entry>
<entry>
<title>If port io is disabled, disable the associated windows as well.</title>
<updated>2018-04-06T13:59:30Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2018-04-06T13:59:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cfde75116272715436811dfb26d1a3a0c1cb555f'/>
<id>urn:sha1:cfde75116272715436811dfb26d1a3a0c1cb555f</id>
<content type='text'>
ok patrick@, deraadt@
</content>
</entry>
<entry>
<title>Teach ppb(4) how to allocate PCI bus numbers such that it can properly</title>
<updated>2015-12-01T21:02:04Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2015-12-01T21:02:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=68218d1b97682f4ece924ee3a69ac730829a6eff'/>
<id>urn:sha1:68218d1b97682f4ece924ee3a69ac730829a6eff</id>
<content type='text'>
condigure bridges left unconfigured by the system firmware.  Not perfect yet,
but good enough to make the Apple Thunderbolt Giabit Ethernet adapter work
when inserted at boot time.

ok deraadt@
</content>
</entry>
<entry>
<title>Properly restore the prefetchable memory window upon resume.</title>
<updated>2015-10-19T19:24:54Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2015-10-19T19:24:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=49b0da6a2bae971f7b03702adeb708d9e3433c09'/>
<id>urn:sha1:49b0da6a2bae971f7b03702adeb708d9e3433c09</id>
<content type='text'>
ok deraadt@
</content>
</entry>
<entry>
<title>PPB_EXNAMLEN for the extent name; now easier to pass as a size for free()</title>
<updated>2015-09-10T10:36:04Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2015-09-10T10:36:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e9476d63e0a88a99a52f66035751849f9176659f'/>
<id>urn:sha1:e9476d63e0a88a99a52f66035751849f9176659f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove some includes include-what-you-use claims don't</title>
<updated>2015-03-14T03:38:46Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2015-03-14T03:38:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=21dab745d772244ad59a415114e48be2888cfbc8'/>
<id>urn:sha1:21dab745d772244ad59a415114e48be2888cfbc8</id>
<content type='text'>
have any direct symbols used.  Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@
</content>
</entry>
<entry>
<title>remove the second void * argument on tasks.</title>
<updated>2015-01-27T03:17:35Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2015-01-27T03:17:35Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e419548092f59c20a140404818050eb2ab331a19'/>
<id>urn:sha1:e419548092f59c20a140404818050eb2ab331a19</id>
<content type='text'>
when workqs were introduced, we provided a second argument so you
could pass a thing and some context to work on it in. there were
very few things that took advantage of the second argument, so when
i introduced pools i suggested removing it. since tasks were meant
to replace workqs, it was requested that we keep the second argument
to make porting from workqs to tasks easier.

now that workqs are gone, i had a look at the use of the second
argument again and found only one good use of it (vdsp(4) on sparc64
if you're interested) and a tiny handful of questionable uses. the
vast majority of tasks only used a single argument. i have since
modified all tasks that used two args to only use one, so now we
can remove the second argument.

so this is a mechanical change. all tasks only passed NULL as their
second argument, so we can just remove it.

ok krw@
</content>
</entry>
<entry>
<title>Fix some issues with 64-bit BARs behind PCI-PCI bridges.</title>
<updated>2014-11-24T13:48:49Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2014-11-24T13:48:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=30394c8022327547fdf88e8a7b2653538b7a3607'/>
<id>urn:sha1:30394c8022327547fdf88e8a7b2653538b7a3607</id>
<content type='text'>
Actual BARs that have the upper 32-bits set seen in the wild now on a
SPARC T5-2 system.

Tested by many.
</content>
</entry>
<entry>
<title>Add generic support for bridges that support subtractive decoding.</title>
<updated>2014-09-15T14:22:07Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2014-09-15T14:22:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ea85fdece28cf3b07273edb8f7e89b236c28ad24'/>
<id>urn:sha1:ea85fdece28cf3b07273edb8f7e89b236c28ad24</id>
<content type='text'>
Fixes issues with pcmcia behind a ATI SB400 PCI bridge reported by Thierry
Deval.

ok mpi@
</content>
</entry>
</feed>
