All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Emil Tantilov <emocom-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: lost ticks in linux
Date: Thu, 21 Dec 2006 17:43:33 +0200	[thread overview]
Message-ID: <458AABA5.1040007@qumranet.com> (raw)
In-Reply-To: <767986.54825.qm-v0vK/1KhsBWA/QwVtaZbd3CJp6faPEW9@public.gmane.org>

Emil Tantilov wrote:
> Yep - that is corect. init 0 works OK, but init 6
> panics.
>
> EIP points to delay_tsc, so I think it might be
> related to the issue with the clock (TSC running
> slow).
>
>   

Well, the EIP points at a sub instruction, which has no business 
generating divide exceptions.

  b:   8d b6 00 00 00 00       lea    0x0(%esi),%esi
  11:   8d bf 00 00 00 00       lea    0x0(%edi),%edi
  17:   53                      push   %ebx
  18:   8b 5c 24 08             mov    0x8(%esp),%ebx
  1c:   0f 31                   rdtsc
  1e:   89 c1                   mov    %eax,%ecx
  20:   8d b4 26 00 00 00 00    lea    0x0(%esi),%esi
  27:   f3 90                   pause
  29:   0f 31                   rdtsc
exception here -->
  2b:   29 c8                   sub    %ecx,%eax
  2d:   39 d8                   cmp    %ebx,%eax
  2f:   72 f6                   jb     0x27
  31:   5b                      pop    %ebx
  32:   c3                      ret

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2006-12-21 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 14:30 lost ticks in linux Emil Tantilov
     [not found] ` <300726.43604.qm-GOr6M1UduhqA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2006-12-21 14:35   ` Avi Kivity
     [not found]     ` <458A9BC0.8070300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-21 15:33       ` Emil Tantilov
     [not found]         ` <767986.54825.qm-v0vK/1KhsBWA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2006-12-21 15:43           ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-21  2:47 Emil Tantilov
     [not found] ` <20061221024743.72244.qmail-Jum9+C5DOP6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2006-12-21  2:55   ` Lonnie Mendez

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=458AABA5.1040007@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=emocom-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.