Sponsored Content
Top Forums Programming Signal Handling and Context Switches Post 302261859 by XComp on Tuesday 25th of November 2008 07:50:22 PM
Old 11-25-2008
Reduced code

Ok...I've tried to reduce the code. Maybe it is easier to understand and nobody is scared by the big number of lines. I removed most of the if conditions. So let's take a second try! Smilie

Code:
// ...

#define UPPER_BOUND 500000000
#define QUANTUM_SEC 0
#define QUANTUM_MICRO_SEC 500000

// stores the context of the thread_function context
static ucontext_t thread_context;
// stores the context of the scheduler_function context
static ucontext_t scheduler_context;

int thread_finished;
int i;

static void signal_handler_function(int sig_nr, siginfo_t* info, void *context) {
    // saves the thread context
    thread_context = *((ucontext_t*)context);

    // swaps back to scheduler context
    setcontext(&scheduler_context);
}

// This function simulates a thread function. It consists of two simple for-loops and prints, whether every loop finished successfully.
void thread_function(void) {

    // 1st count
    for (i = 0; i < UPPER_BOUND; ++i);

    if (i == UPPER_BOUND) {
        printf("\n[Thread Function]\t1st counting worked fine...");
    } else {
        printf("\n[Thread Function]\tError: 1st counting didn't finished (%d)...", i);
    }

    // 2nd count
    for (i = 0; i < UPPER_BOUND; ++i);

    if (i == UPPER_BOUND) {
        printf("\n[Thread Function]\t2nd counting worked fine...");
    } else {
        printf("\n[Thread Function]\tError: 2nd counting didn't finished (%d)...", i);
    }

    thread_finished = 1;
}

// The context will swap into this function after a signal was raised. The while-loop ends, when thread_finished == 1.
// thread_finished is set to 1 at the end of the thread_function.
void scheduler_function() {
    // thread_finished is a global variable, which is set to 1, if the thread function is finished
    while(thread_finished != 1) {
        swapcontext(&scheduler_context, &thread_context);
        printf("\n[Scheduler Function]\tSwap back is done...");
    }
}

// main initializes all needed stuff (timer, signal handler) and starts the scheduler_function.
int main(int argc, char **argv) {
    thread_finished = 0;

    char thread_stack[65536];

    // initializing scheduler context
    getcontext(&scheduler_context);

    // initializing thread context
    getcontext(&thread_context);
    thread_context.uc_stack.ss_sp = thread_stack;
    thread_context.uc_stack.ss_size = sizeof(thread_stack);
    thread_context.uc_link = &scheduler_context;

    // initialize alternate stack for signal handling
    char * alternate_stack = (char*)malloc(65536);

    stack_t new_signal_stack;
    new_signal_stack.ss_sp = alternate_stack;
    new_signal_stack.ss_size = 65536;
    new_signal_stack.ss_flags = 0;
    sigaltstack(&new_signal_stack, NULL);

    // sets the signal handler for swapping to the scheduler context
    struct sigaction scheduling_interuption_handler;
    scheduling_interuption_handler.sa_sigaction = signal_handler_function;
    scheduling_interuption_handler.sa_flags = SA_RESTART | SA_SIGINFO | SA_ONSTACK;
    sigemptyset(&scheduling_interuption_handler.sa_mask);
    sigaction(SIGPROF, &scheduling_interuption_handler, NULL)

    // sets the timer which sends SIGPROF periodically
    struct itimerval timeslice;
    timeslice.it_value.tv_sec = QUANTUM_SEC;
    timeslice.it_value.tv_usec = QUANTUM_MICRO_SEC;
    timeslice.it_interval = timeslice.it_value;

    setitimer(ITIMER_PROF, &timeslice, NULL);

    // sets the thread function
    makecontext(&thread_context, thread_function, 0);

    // this function handles the swapping part
    scheduler_function();
}

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Handling SIGUSR2 signal

HI, I need to handle SIGUSR2 signal in my application to change the state of the application dynamically. I have implemented the signal handler. However the application is able to catch only one SIGUSR2 signal. The second SIGUSR2 signal causes the application to crash. This is happning only with... (3 Replies)
Discussion started by: diganta
3 Replies

2. UNIX for Advanced & Expert Users

signal handling in shell script

Hi can any please tell me is it possible to catch the signal in a shell script like we do in C. if yes please give me some idea or a link. (4 Replies)
Discussion started by: Raom
4 Replies

3. Programming

Signal Handling

Hi folks I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file. The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
Discussion started by: themezzaman
3 Replies

4. Shell Programming and Scripting

Signal handling in Perl

Guys, I'm doing signal handling in Perl. I'm trying to catch ^C signal inside the script. There two scripts : one shell script and one perl script. The shell script calls the perl script. For e.g. shell script a.sh and perl scipt sig.pl. Shell script a.sh looks something like this :... (6 Replies)
Discussion started by: obelix
6 Replies

5. UNIX for Advanced & Expert Users

thread context switches: detection, prevention

#1: does anyone know how to detect how many times (and/or the time length) a given thread has been context switched out of the CPU? #2: are there any tchniques that minimize/eliminate your thread getting context switched? I would be happy to know the answers to these questions for ANY... (2 Replies)
Discussion started by: fabulous2
2 Replies

6. Programming

signal handling question

Hello all, I am starting to learn signal handling in Linux and have been trying out some simple codes to deal with SIGALRM. The code shown below sets a timer to count down. When the timer is finished a SIGALRM is produced. The handler for the signal just increments a variable called count. This... (7 Replies)
Discussion started by: fox_hound_33
7 Replies

7. Programming

Signal handling

I am trying to write a small program where I can send signals and then ask for an action to be triggered if that signal is received. For example, here is an example where I am trying to write a programme that will say you pressed ctrl*c when someone presses ctrl+c. My questions are what you would... (1 Reply)
Discussion started by: #moveon
1 Replies

8. Programming

problem in SIGSEGV signal handling

i wrote handler for sigsegv such that i can allocate memory for a variable to which sigsegv generated for illlegal acces of memory. my code is #include <signal.h> #include<stdio.h> #include<stdlib.h> #include<string.h> char *j; void segv_handler(int dummy) { j=(char *)malloc(10); ... (4 Replies)
Discussion started by: pavan6754
4 Replies

9. UNIX and Linux Applications

SIGSEGV Signal handling

Hello, Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies

10. Programming

problem in reforking and signal handling

hi friends i have a problem in signal handling ... let me explain my problem clearly.. i have four process .. main process forks two child process and each child process again forks another new process respectively... the problem is whenever i kill the child process it is reforking and the... (2 Replies)
Discussion started by: senvenugopal
2 Replies
pause(2)							System Calls Manual							  pause(2)

NAME
pause - suspend process until signal SYNOPSIS
DESCRIPTION
suspends the calling process until it receives a signal. The signal must be one that is not currently set to be ignored or blocked (masked) by the calling process. If the signal causes termination of the calling process, does not return. If the signal is by the calling process and control is returned from the signal-catching function (see signal(5)), the calling process resumes execution from the point of suspension; with a return value of -1 from and set to APPLICATION USAGE
Threads Considerations Signal dispositions (such as catch/default/ignore) are shared by all threads in the process and blocked signal masks are maintained by each thread. Therefore, the signals being waited for should not be ignored by the process or blocked by the calling thread. will suspend only the calling thread until it receives a signal. If other threads in the process do not block the signal, the signal may be delivered to another thread in the process and the thread in may continue waiting. For this reason, the use of is recommended instead of for multi-threaded applications. For more information regarding signals and threads, refer to signal(5). SEE ALSO
alarm(2), kill(2), sigwait(2), wait(2), signal(5). STANDARDS CONFORMANCE
pause(2)
All times are GMT -4. The time now is 10:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy