public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] qemu-kvm: Fix test for I/O thread
Date: Sat, 19 Jul 2008 09:07:40 +0200	[thread overview]
Message-ID: <488192BC.7000807@web.de> (raw)
In-Reply-To: <48819143.1010702@qumranet.com>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

Avi Kivity wrote:
> Jan Kiszka wrote:
>> Looks to me like this was rather intended. But given that
>> 4e8b8a6d92c5ece048e65be3a3980d24f065b32b claims to actually fix a bug in
>> its original broken form, please have a careful look.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
>> index 431e26d..c36f60f 100644
>> --- a/qemu/qemu-kvm.c
>> +++ b/qemu/qemu-kvm.c
>> @@ -89,7 +89,7 @@ static void qemu_cond_wait(pthread_cond_t *cond)
>>      pthread_cond_timedwait(cond, &qemu_mutex, &ts);
>>      /* If we're the I/O thread, some other thread may be waiting for aio
>>       * completion */
>> -    if (!vcpu_info)
>> +    if (!env)
>>          qemu_aio_poll();
>>      cpu_single_env = env;
>>  }
>>   
> 
> Aren't the two lines equivalent?  vcpu_info is a thread-local-storage
> variable, and is unset for the iothread.
> 

Then you probably wanted to type 'vcpu', don't you? :)

However, I would stick with what the function already uses, ie. 'env'.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2008-07-19  7:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  8:10 [PATCH] qemu-kvm: Fix test for I/O thread Jan Kiszka
2008-07-19  7:01 ` Avi Kivity
2008-07-19  7:07   ` Jan Kiszka [this message]
2008-07-19  7:17     ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=488192BC.7000807@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox