Hi Eliot, Thanks again for your help. Am 21.04.2014 um 22:56 schrieb Eliot Miranda <[hidden email]>: No, when I trigger SIGALRM from the outside the image works (albeit very slow). First I emitted SIGALRM by means of kill -SIGALRM <pid> from the shell; later I wrote a simple C program to do that for me :) Yeah, I don’t know how I could miss this. I will debug a little bit in order to find out why this doesn’t work as expected on OpenSolaris. After the initial step through heartbeat, there won’t be any heartbeat_handler calls triggered from within the vm… I already did that yesterday. Alas it’s only working with superuser rights, otherwise I’ll get "pthread_setschedparam failed; consider using ITIMER_HEARTBEAT: Not owner“. I will also investigate further here so maybe I will get this working.
Regards, Andreas
|
In reply to this post by Eliot Miranda-2
Hi again, Am 21.04.2014 um 22:56 schrieb Eliot Miranda <[hidden email]>:
Now I have a clue why I didn’t see it before. If ITIMER_HEARTBEAT is set then all functionality is in sqUnixITimerHeartbeat.c and there is no nanosleep call there… Regards, Andreas |
In reply to this post by Andreas Wacknitz
On Tue, Apr 22, 2014 at 8:09 AM, Andreas Wacknitz <[hidden email]> wrote:
Ah, ok. That was the situation on linux before the 2.6.16 kernel (IIRC). I guess you're stuck with the getitimer heartbeat. So the issue is how to rearm the signal handler. If necessary put a call to signal/sigaction in heartbeat_handler.
best, Eliot
|
Free forum by Nabble | Edit this page |