From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Weil <weil@mail.berlios.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH] qemu-timer: Run timers in alarm timer handler
Date: Thu, 23 Aug 2012 20:09:44 +0200 [thread overview]
Message-ID: <503671E8.1090205@siemens.com> (raw)
In-Reply-To: <50362C09.60508@redhat.com>
On 2012-08-23 15:11, Paolo Bonzini wrote:
>>> So, in order to remove the qemu_notify_event completely, what about not
>>> using signals anymore for timers? You could just tweak the select
>>> timeout and drop all the -clock madness. Zero syscalls, practically no
>>> overhead. If this is not precise enough, use timerfd on Linux only
>>
>> Need to think about it. At least, real-time tasks will get proper
>> precision on Linux. Not sure if it will be sufficient on other hosts.
>
> Do we care (I put non-Linux POSIX just a little above Windows but not much)?
Well, at least we should not regress.
For Windows I just found out that we support millisecond resolution in
os_host_main_loop_wait at best due to g_poll. That would be fine, but
what is g_poll really using? Likely not mm-timers...
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-08-23 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 11:23 [Qemu-devel] [RFC][PATCH] qemu-timer: Run timers in alarm timer handler Jan Kiszka
2012-08-23 11:39 ` Paolo Bonzini
2012-08-23 12:10 ` Jan Kiszka
2012-08-23 12:24 ` Paolo Bonzini
2012-08-23 13:01 ` Jan Kiszka
2012-08-23 13:11 ` Paolo Bonzini
2012-08-23 18:09 ` Jan Kiszka [this message]
2012-08-24 7:45 ` Paolo Bonzini
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=503671E8.1090205@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).