History log of /dragonfly/sys/platform/vkernel64/platform/kqueue.c (Results 1 – 10 of 10)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3
# e2164e29 18-Oct-2019 zrj <rimvydas.jasinskas@gmail.com>

<sys/slaballoc.h>: Switch to lighter <sys/_malloc.h> header.

The <sys/globaldata.h> embeds SLGlobalData that in turn embeds the
"struct malloc_type". Adjust several kernel sources for missing
in

<sys/slaballoc.h>: Switch to lighter <sys/_malloc.h> header.

The <sys/globaldata.h> embeds SLGlobalData that in turn embeds the
"struct malloc_type". Adjust several kernel sources for missing
includes where memory allocation is performed. Try to use alphabetical
include order.

Now (in most cases) <sys/malloc.h> is included after <sys/objcache.h>.
Once it gets cleaned up, the <sys/malloc.h> inclusion could be moved
out of <sys/idr.h> to drm Linux compat layer linux/slab.h without side
effects.

show more ...


Revision tags: v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2
# fcf6efef 02-Mar-2019 Sascha Wildner <saw@online.de>

kernel: Remove numerous #include <sys/thread2.h>.

Most of them were added when we converted spl*() calls to
crit_enter()/crit_exit(), almost 14 years ago. We can now
remove a good chunk of them agai

kernel: Remove numerous #include <sys/thread2.h>.

Most of them were added when we converted spl*() calls to
crit_enter()/crit_exit(), almost 14 years ago. We can now
remove a good chunk of them again for where crit_*() are
no longer used.

I had to adjust some files that were relying on thread2.h
or headers that it includes coming in via other headers
that it was removed from.

show more ...


Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc
# c91894e0 22-Jan-2017 Matthew Dillon <dillon@apollo.backplane.com>

vkernel - Restabilize pmap code, redo kqueue, systimer, and console code

* Remove vm_token and add necessary vm_page spin locks to the vkernel's
pmap code, improving its stability.

* Separate the

vkernel - Restabilize pmap code, redo kqueue, systimer, and console code

* Remove vm_token and add necessary vm_page spin locks to the vkernel's
pmap code, improving its stability.

* Separate the systimer interrupt and console tty support from the
kqueue subsystem.

Uses SIGURG for systimer
Uses SIGIO for kqueue
Uses SIGALRM for cothread signalling

* The vkernel systimer code now uses a dedicated cothread for timing. The
cothread is a bit of a hack at the moment but is a more direct way of
handling systimers.

* Attempt to fix user%/sys%/intr%/idle% in the systat -vm and
systat -pv output. Still isn't perfect, but it is now more
accurate.

show more ...


Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3
# 591325ea 02-Jul-2013 Sascha Wildner <saw@online.de>

kernel/platform: Remove some #include duplicates.


Revision tags: v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1
# 988854f9 02-Feb-2012 Matthew Dillon <dillon@apollo.backplane.com>

vkernel - Fix semi-random SIGILL crashes under heavy network loads

* SIGIO was being installed with SA_NODEFER, resulting in situations
under heavy network loads where multiple SIGIOs could stack

vkernel - Fix semi-random SIGILL crashes under heavy network loads

* SIGIO was being installed with SA_NODEFER, resulting in situations
under heavy network loads where multiple SIGIOs could stack and cause
a stack overflow. This often resulted in the sendsig code in the kernel
generating a SIGILL to the process after being unable to push a new
signal context.

* Removing SA_NODEFER appears to solve the problem.

Reported-by: tuxillo

show more ...


Revision tags: v3.1.0, v3.0.0
# bae88a6f 31-Dec-2011 Sepherosa Ziehau <sephe@dragonflybsd.org>

vkernel/intr: Pin vkernel "hardware interrupts" to CPU0

Due to the nondeterminsm of CPU to which SIGIO will be delivered,
we can't depend on "hardware interrupts" of vkernel always happen
on the reg

vkernel/intr: Pin vkernel "hardware interrupts" to CPU0

Due to the nondeterminsm of CPU to which SIGIO will be delivered,
we can't depend on "hardware interrupts" of vkernel always happen
on the registered CPU. We now pin the vkernel "hardware interrupts"
to CPU0, so the interrupt scheduling code could always know the
correct ithread to be scheduled.

Reported-by: tuxillo vsrinivas

show more ...


# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


# 6355d931 28-Oct-2011 Sepherosa Ziehau <sephe@dragonflybsd.org>

intr: Pass cpuid to register_int and unregister_int


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0
# 56f4b223 05-Apr-2011 Matthew Dillon <dillon@apollo.backplane.com>

vkernel - Fix problem where cpu-bound user process cannot be interrupted

* Fix an issue where a cpu-bound user process running in a vkernel cannot
be interrupted from within the vkernel.

The pr

vkernel - Fix problem where cpu-bound user process cannot be interrupted

* Fix an issue where a cpu-bound user process running in a vkernel cannot
be interrupted from within the vkernel.

The problem occurs because the timer interrupt was not marked MPSAFE,
causing the interrupt thread to hold the MP token which then prevented
the thread preemption code from letting the timer interrupt thread
preempt the currently running user process.

* Fixed by marking the timer interrupt and other vkernel interrupt
handlers as being MPSAFE.

* This is a problem for the vkernel and not for normal kernel. Normal
kernels have a doreti function which 'catches' pending flags on
any attempt to return to userland.

The vkernel does not, instead relying on the preemption mechanic to
catch pending flags.

Reported-by: Antonio Huete Jimenez <ahuete.devel@gmail.com>

show more ...


Revision tags: v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0
# da673940 17-Aug-2009 Jordan Gordeev <jgordeev@dir.bg>

Add platform vkernel64.