Date:Wed, 20 Jul 2016 21:39:46 -0700
From:Charles Cui
Message-ID:
| In conclusion, you think the signals are consumed
| at the time of context switch.
No, not just a context switch (that is when one process stops running - on a
cpu - and another replaces it) -
Thanks Robert for your understanding.
In conclusion, you think the signals are consumed
at the time of context switch. I will keep this information
in mind and see how all functions are connected.
Thanks Charles
2016-07-20 9:15 GMT-07:00 Robert Elz :
> Date:Wed, 20 Jul 2016 15:28:13
Date:Wed, 20 Jul 2016 15:28:13 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20160720132813.gr43...@trav.math.uni-bonn.de>
| > so before any user code can execute again
| ... on this CPU. What about the other CPUs? Do all a processes LWPs run
| on the s
> Next note, that if we're doing this, kernel code is obviously running
On one of the CPUs, yes.
> so before any user code can execute again
... on this CPU. What about the other CPUs? Do all a processes LWPs run
on the same CPU?
First, the basic (since forever) unix signal handling method, then some
NetBSD code pointers (and I'm sure you will find the rest).
Signal generation (causing a signal to be sent to a process) you have
largely found I believe - either a sys call (from the process to
receive the signal, or another)
Hi guys,
I spent some time investigating the sigqueue code path, which is used by
realtime signals,
but I am confused about some logics,
please provide comments if you have specific knowledge about this part.
I followed the call chain path of sigqueue, and pretty confident about how
a signal is
