qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [PATCH 01/22] Prevent abortion on multiple VCPU kicks


From: Avi Kivity
Subject: [Qemu-devel] Re: [PATCH 01/22] Prevent abortion on multiple VCPU kicks
Date: Mon, 31 Jan 2011 15:16:27 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7

On 01/31/2011 01:19 PM, Jan Kiszka wrote:
On 2011-01-31 10:44, Avi Kivity wrote:
>  On 01/27/2011 03:09 PM, Jan Kiszka wrote:
>>  If we call qemu_cpu_kick more than once before the target was able to
>>  process the signal, pthread_kill will fail, and qemu will abort. Prevent
>>  this by avoiding the redundant signal.
>>
>
>  Doesn't fit with the manual page (or with the idea that signals are
>  asynchronous):
>
>  NAME
>          pthread_kill - send a signal to a thread
>
>
>  ...
>
>  ERRORS
>          ESRCH  No thread with the ID thread could be found.
>
>          EINVAL An invalid signal was specified.
>

Valid remark, but I was receiving EAGAIN for blocked RT signals. Don't
know if this is Linux-specific. A quick glance at the man pages did not
reveal if this is allowed or at least gray area.


    } else if (!is_si_special(info)) {
        if (sig >= SIGRTMIN && info->si_code != SI_USER) {
            /*
             * Queue overflow, abort.  We may abort if the
             * signal was rt and sent by user using something
             * other than kill().
             */
            trace_signal_overflow_fail(sig, group, info);
            return -EAGAIN;
        }

However, even when selectively ignoring this, it's more efficient to
catch the redundant signaling in user space.

Yes.

--
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]