wireguard-openbsd/sys/arch/alpha/dev/shared_intr.c, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/alpha/dev/shared_intr.c?h=jd%2Fqueueboosts 2015-09-02T14:07:41Z sizes for free() 2015-09-02T14:07:41Z deraadt deraadt@openbsd.org 2015-09-02T14:07:41Z urn:sha1:fdb343009bdcf51b4ce9b144c6435b4dac0d402c Move acquisition of the kernel lock deeper in the interrupt path, and make 2015-05-19T20:28:14Z miod miod@openbsd.org 2015-05-19T20:28:14Z urn:sha1:ebfa05375088d510da702ab7f48d794fb544562f sure clock interrupts do not attempt to acquire it. This will also eventually allow for IPL_MPSAFE interrupts on alpha. Tested by dlg@ and I. Replace some malloc(n*size,...) calls with mallocarray(). 2014-12-09T06:58:28Z doug doug@openbsd.org 2014-12-09T06:58:28Z urn:sha1:5714159a8ce4224ba1272c14d2303d9f9e962179 ok tedu@ deraadt@ add a size argument to free. will be used soon, but for now default to 0. 2014-07-12T18:44:40Z tedu tedu@openbsd.org 2014-07-12T18:44:40Z urn:sha1:f8e6c4256e251ce0386dacd7e411f1d0894ef80e after discussions with beck deraadt kettenis. More than a decade ago, interrupt handlers on sparc started returning 0 2011-04-15T20:40:03Z deraadt deraadt@openbsd.org 2011-04-15T20:40:03Z urn:sha1:323a282b167e48fa7781fa54f895cb1e1e7b1191 (interrupt was not for me), 1 (positive interrupt was for me), or -1 (i am not sure...). We have continued with this practice in as many drivers as possible, throughout the tree. This makes some of the architectures use that information in their interrupt handler calling code -- if 1 is returned (and we know this specific machine does not have edge-shared interrupts), we finish servicing other possible handlers on the same pin. If the interrupt pin remains asserted (from a different device), we will end up back in the interrupt servicing code of course... but this is cheaper than calling all the chained interrupts on a pin. This does of course count on shared level interrupts being properly sorted by IPL. There have been some concerns about starvation of drivers which incorrectly return 1. Those drivers should be hunted down so that they return -1. (other architectures will follow) ok kettenis drahn dlg miod Get rid of evcount's support for arranging counters in a tree 2010-09-20T06:33:46Z matthew matthew@openbsd.org 2010-09-20T06:33:46Z urn:sha1:4667bebbb63d1a17d5f01b2cbe4d386208702e10 hierarchy. Everything attached to a single root node anyway, so at best we had a bush. "i think it is good" deraadt@ Remove unused last argument of alpha_shared_intr_disestablish(). 2009-09-30T20:16:22Z miod miod@openbsd.org 2009-09-30T20:16:22Z urn:sha1:962a9e5422d5ad0c2b451c058e4ba4dbbff89845 Rework the interrupt code, shaving some cycles off in the process. 2006-06-15T20:08:29Z brad brad@openbsd.org 2006-06-15T20:08:29Z urn:sha1:c62181b11cb87b8bc9827b5000bf73416171cb3f Rather than an "iointr" routine that decomposes a vector into an IRQ, we maintain a vector table directly, hooking up each "iointr" routine at the correct vector. This also allows us to hook device interrupts up to specific vectors. From thorpej NetBSD Tested by myself and a number of end-users. Add a alpha_shared_intr_reset_strays() function that resets the stray 2006-01-29T10:47:35Z martin martin@openbsd.org 2006-01-29T10:47:35Z urn:sha1:17a294c74c811105a8ba91b1904c00cee05ca64e interrupt counter for a given shared interrupt descriptor. When an interrupt is successfully handled, reset the strays counter, thus preventing a "slow leak" from eventually shutting off the interrupt vector. from NetBSD via KUDO Takashi Use list and queue macros where applicable to make the code easier to read; 2004-12-25T23:02:21Z miod miod@openbsd.org 2004-12-25T23:02:21Z urn:sha1:5cf5f4a3979fccea390e66955458358208fbdaa8 no functional change.