From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH v6] um: Add a high resolution timer subsystem
Date: Mon, 11 May 2015 18:20:40 +0100 [thread overview]
Message-ID: <5550E4E8.1090300@kot-begemot.co.uk> (raw)
In-Reply-To: <672e7d23-295e-42eb-a92a-d13faa966927@email.android.com>
On 11/05/15 18:00, Thomas Meyer wrote:
> Hi,
>
> maybe there is a bug in how the timers are created for all user space processes.
> In the latest patch I use os__timer_remain for the initial interval.
> The idea was to launch all timers at the same time. But I now think this can never work using relative times, especially when os__timer_remain returns 0, then the new timer is never launched.
That is not a bad idea, just requires a more complex check in setting up
interval so it is reset to default when a zero value or value > HZ is
passed.
>
> That may explain the hangs you see.
> You could try to replace os__timer_remain with the current HZ value in nanoseconds.
I am going to adjust time.c instead as above.
A.
>
> Kind regards
> Thomad
>
> A
[snip]
A.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2015-05-11 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 23:14 [uml-devel] [PATCH v6] um: Add a high resolution timer subsystem Thomas Meyer
2015-05-10 12:35 ` Richard Weinberger
2015-05-10 13:32 ` Anton Ivanov
2015-05-10 14:34 ` Thomas Meyer
2015-05-10 18:25 ` Anton Ivanov
2015-05-10 20:51 ` Richard Weinberger
2015-05-11 12:52 ` Anton Ivanov
2015-05-11 15:05 ` Anton Ivanov
2015-05-11 15:43 ` Anton Ivanov
2015-05-11 17:00 ` Thomas Meyer
2015-05-11 17:20 ` Anton Ivanov [this message]
2015-05-11 17:31 ` Anton Ivanov
2015-05-11 17:41 ` Thomas Meyer
2015-05-11 19:42 ` Anton Ivanov
2015-05-11 21:22 ` Thomas Meyer
2015-05-26 10:56 ` stian
2015-05-11 22:34 ` Richard Weinberger
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=5550E4E8.1090300@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--cc=thomas@m3y3r.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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