From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [Discuss][i386] Platform SMIs and their interferance with tsc based delay calibration
Date: Mon, 31 Jan 2005 18:25:23 +0100 [thread overview]
Message-ID: <41FE6A03.6010402@fujitsu-siemens.com> (raw)
In-Reply-To: <3rR0g-3aR-11@gated-at.bofh.it>
Venkatesh Pallipadi wrote:
> (0) Estimate a value for loops_per_jiffy
> (1) While (loops_per_jiffy estimate is accurate enough)
> (2) wait for jiffy transition (jiffy1)
> (3) Note down current tsc (tsc1)
> (4) loop until tsc becomes tsc1 + loops_per_jiffy
> (5) check whether jiffy changed since jiffy1 or not
> and refine loops_per_jiffy estimate
>
> Case 2: If SMIs happen between (3) and (4) above, then we can end up
> with a loops_per_jiffy value that is too high.
I don't think this can really happen (at least not on the bootstrap CPU)
because even if an SMI occurs, the CPU must first serve the timer
interrupt and increment jiffies before it continues looping.
However "LPJ too short" is what needs to be avoided at all cost.
Regards and thanks for working on this problem,
Martin
next parent reply other threads:[~2005-01-31 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3rR0g-3aR-11@gated-at.bofh.it>
2005-01-31 17:25 ` Martin Wilck [this message]
[not found] ` <3s4Tx-1gi-9@gated-at.bofh.it>
2005-01-31 17:29 ` [Discuss][i386] Platform SMIs and their interferance with tsc based delay calibration Martin Wilck
2005-01-29 14:37 Pallipadi, Venkatesh
-- strict thread matches above, loose matches on Subject: below --
2005-01-29 14:36 Pallipadi, Venkatesh
2005-01-29 2:51 Venkatesh Pallipadi
2005-01-29 5:17 ` Andrew Morton
2005-01-29 6:24 ` Andi Kleen
2005-01-29 17:44 ` Linus Torvalds
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=41FE6A03.6010402@fujitsu-siemens.com \
--to=martin.wilck@fujitsu-siemens.com \
--cc=linux-kernel@vger.kernel.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