From: "Jan Beulich" <JBeulich@suse.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Joao Martins <joao.m.martins@oracle.com>,
Tim Deegan <tim@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: BUG: NOW() seems to (sometimes) go backwards!
Date: Wed, 08 Jun 2016 08:01:18 -0600 [thread overview]
Message-ID: <5758414E02000078000F3245@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1465393417.15816.206.camel@citrix.com>
>>> On 08.06.16 at 15:43, <dario.faggioli@citrix.com> wrote:
> On Wed, 2016-06-08 at 04:42 -0600, Jan Beulich wrote:
>> How big of system are we talking about? I'm asking to assess the
>> overhead of adding some cross-CPU checks to get_s_time_fixed()
>> (in a debugging patch), logging relevant values if non-monotonic
>> output gets detected. (On too big a system, the overhead here
>> might end up masking the problem.)
>>
> Yeah, I sort of tried doing something like that already, but was
> logging the wrong thing (I was not yet suspecting a problem with
> scaling).
Yeah, I did also realize that with you observing the problem even
within a core, the cross-CPU checking could be limited to just the
other SMT sibling, which should bring the overhead down quite a
bit. Otoh, with it - as you say - often just being a couple of nano-
seconds, even that may then already be too much.
Speaking of overhead: The tracing itself that you use does not
influence the picture in any way, does it?
Considering how easily you say you see the problem, it ought to
be more widespread. I'm considering to try to do some such
instrumentation to see whether I can see the issue anywhere.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-08 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 15:54 BUG: NOW() seems to (sometimes) go backwards! Dario Faggioli
2016-06-08 10:42 ` Jan Beulich
2016-06-08 13:43 ` Dario Faggioli
2016-06-08 14:01 ` Jan Beulich [this message]
2016-06-08 20:36 ` Joao Martins
2016-06-09 8:05 ` Jan Beulich
2016-06-09 10:24 ` Joao Martins
2016-06-09 10:43 ` Joao Martins
2016-06-09 11:25 ` Jan Beulich
2016-06-09 11:31 ` Jan Beulich
2016-06-09 10:19 ` George Dunlap
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=5758414E02000078000F3245@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=joao.m.martins@oracle.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).