On 02/17/2013 05:42 PM, Jann Horn wrote:
> On Thu, Feb 14, 2013 at 08:19:45PM +0400, Pavel Emelyanov wrote:
>> +struct sigevent event;
> [...]
>> +event.sigev_notify = timer->it_sigev_notify;
>> +event.sigev_signo = timer->sigq->info.si_signo;
>> +event.sigev_value =
On Thu, Feb 14, 2013 at 08:19:45PM +0400, Pavel Emelyanov wrote:
> + struct sigevent event;
[...]
> + event.sigev_notify = timer->it_sigev_notify;
> + event.sigev_signo = timer->sigq->info.si_signo;
> + event.sigev_value = timer->sigq->info.si_value;
> +
On Thu, Feb 14, 2013 at 08:19:45PM +0400, Pavel Emelyanov wrote:
+ struct sigevent event;
[...]
+ event.sigev_notify = timer-it_sigev_notify;
+ event.sigev_signo = timer-sigq-info.si_signo;
+ event.sigev_value = timer-sigq-info.si_value;
+ event.sigev_notify_thread_id =
On 02/17/2013 05:42 PM, Jann Horn wrote:
On Thu, Feb 14, 2013 at 08:19:45PM +0400, Pavel Emelyanov wrote:
+struct sigevent event;
[...]
+event.sigev_notify = timer-it_sigev_notify;
+event.sigev_signo = timer-sigq-info.si_signo;
+event.sigev_value = timer-sigq-info.si_value;
The intention is to make a syscall, that works like sigaction
but on a posix timer. I.e. -- puts (if provided) new sigevent
on the timer and reports the previous value (if requested).
That said, the syscall accepts timer id to work on, a pointer
to the new sigevent (may be NULL, meaning that the
The intention is to make a syscall, that works like sigaction
but on a posix timer. I.e. -- puts (if provided) new sigevent
on the timer and reports the previous value (if requested).
That said, the syscall accepts timer id to work on, a pointer
to the new sigevent (may be NULL, meaning that the
6 matches
Mail list logo