From: Marcelo Tosatti <mtosatti@redhat.com>
To: qemu-devel@nongnu.org
Cc: Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [patch 1/7] qemu: mutex/thread/cond wrappers
Date: Mon, 23 Mar 2009 20:17:56 -0300 [thread overview]
Message-ID: <20090323231756.GA4626@amt.cnet> (raw)
In-Reply-To: <49C26BE9.4030905@redhat.com>
On Thu, Mar 19, 2009 at 05:59:37PM +0200, Avi Kivity wrote:
>> +static void add_to_timespec(struct timespec *ts, unsigned int msecs)
>> +{
>> + ts->tv_sec = ts->tv_sec + (long)(msecs / 1000);
>> + ts->tv_nsec = (ts->tv_nsec + ((long)msecs % 1000) * 1000000);
>> + if (ts->tv_nsec >= 1000000000) {
>> + ts->tv_nsec -= 1000000000;
>> + ts->tv_sec++;
>> + }
>> +}
>>
>
> timespec_add_msec()?
> and why milliseconds?
Well, its suitable for the current purposes. Any other suggestion?
> Also, maybe uint64_t is a better type.
>> +
>> +int qemu_mutex_timedlock(QemuMutex *mutex, unsigned int msecs)
>> +{
>> + struct timespec ts;
>> +
>> + clock_gettime(CLOCK_REALTIME, &ts);
>> + add_to_timespec(&ts, msecs);
>> +
>> + return pthread_mutex_timedlock(&mutex->lock, &ts);
>> +}
>>
>
> I would have preferred a deadline instead of a timeout, but we'll see on
> the next patches.
Please expand?
Fixed the other comments, thanks.
next prev parent reply other threads:[~2009-03-23 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 14:57 [Qemu-devel] [patch 0/7] separate thread for io v2 mtosatti
2009-03-19 14:57 ` [Qemu-devel] [patch 1/7] qemu: mutex/thread/cond wrappers mtosatti
2009-03-19 15:59 ` Avi Kivity
2009-03-19 18:49 ` Jamie Lokier
2009-03-23 23:17 ` Marcelo Tosatti [this message]
2009-03-24 7:43 ` Avi Kivity
2009-03-19 14:57 ` [Qemu-devel] [patch 2/7] qemu: separate thread for io mtosatti
2009-03-20 17:43 ` [Qemu-devel] " Anthony Liguori
2009-03-21 0:06 ` Marcelo Tosatti
2009-03-21 1:04 ` Anthony Liguori
2009-03-21 1:44 ` Marcelo Tosatti
2009-03-21 1:50 ` Anthony Liguori
2009-03-22 8:48 ` Avi Kivity
2009-03-22 11:17 ` Anthony Liguori
2009-03-19 14:57 ` [Qemu-devel] [patch 3/7] qemu: main thread does io and cpu thread is spawned mtosatti
2009-03-19 14:57 ` [Qemu-devel] [patch 4/7] qemu: handle reset/poweroff/shutdown in iothread mtosatti
2009-03-19 14:57 ` [Qemu-devel] [patch 5/7] qemu: pause and resume cpu thread(s) mtosatti
2009-03-19 14:57 ` [Qemu-devel] [patch 6/7] qemu: handle vmstop from cpu context mtosatti
2009-03-19 14:57 ` [Qemu-devel] [patch 7/7] qemu: use pipe to wakeup io thread mtosatti
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=20090323231756.GA4626@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).