From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Re: Very large value from get_nsec_offset() in timer_interrupt
Date: Fri, 21 Apr 2006 11:16:42 -0500 [thread overview]
Message-ID: <20060421161642.GA16776@us.ibm.com> (raw)
In-Reply-To: <20060420224735.GY16776@us.ibm.com>
* Ryan Harper <ryanh@us.ibm.com> [2006-04-20 17:47]:
>
> ns_offset is calculated from get_nsec_offset(). I'm going to dig
> a little further, but I wanted to get what I'm seeing out there.
static u64 get_nsec_offset(struct shadow_time_info *shadow)
{
u64 now, delta;
rdtscll(now);
delta = now - shadow->tsc_timestamp;
return scale_delta(delta, shadow->tsc_to_nsec_mul, shadow->tsc_shift);
}
For some currently unknown reason, now is < shadow->tsc_timestamp; This
results in a very large delta value, which is scaled up even larger.
The output from the multi-cpu clock info dump doesn't show anything
bogus:
(XEN) Min = 68672793737292 ; Max = 68672793747633 ; Diff = 10341 (10 microseconds)
(XEN) Min = 68899728719792 ; Max = 68899728727283 ; Diff = 7491 (7 microseconds)
Any thoughts on why the shadow copy of the tsc_timestamp would be > than
the value returned from reading the tsc would be helpful.
Very likely this is related to the hardware, this is a 4-node x460
32-way. I've not reproduced this on anything but multi-node setups.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2006-04-21 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 22:47 Very large value from get_nsec_offset() in timer_interrupt Ryan Harper
2006-04-21 16:16 ` Ryan Harper [this message]
2006-04-21 19:53 ` [PATCH] update_vcpu_system_time work-around Ryan Harper
2006-04-22 9:30 ` Keir Fraser
2006-04-24 15:06 ` Ryan Harper
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=20060421161642.GA16776@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.