All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Wilck <martin.wilck@fujitsu-siemens.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Wichert, Gerhard" <Gerhard.Wichert@fujitsu-siemens.com>
Subject: Re: [PATCH] x86 (64): make calibrate_APIC_clock() smp-safe
Date: Thu, 24 Jul 2008 09:31:48 -0400	[thread overview]
Message-ID: <48888444.1020305@zytor.com> (raw)
In-Reply-To: <48885DDC.9010003@fujitsu-siemens.com>

Martin Wilck wrote:
> Hi Thomas and Peter, hi everyone,
> 
> Asynchrounous events (e.g.SMIs) which occur during the APIC timer 
> calibration can cause timer miscalibrations, sometimes by large amounts.
> 
> This patch fixes this by two separate measures:
>   a) make sure that no significant interruption occurs between APIC and
>      TSC reads
>   b) make sure that the measurement loop isn't significantly longer
>      than originally intended.
> 
> I am sorry, due to a misconfiguration of our SMTP server I need to send 
> the patch as attachment.
> 

The other thing we may want to consider is doing multiple runs of the 
calibration loop.  I suspect we'd get a more accurate result running, 
say, 9 loops of the 1/9 the current duration and looking either for the 
best result or the median (NOT the mean.)

	-hpa


  parent reply	other threads:[~2008-07-24 13:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 10:47 [PATCH] x86 (64): make calibrate_APIC_clock() smp-safe Martin Wilck
2008-07-24 11:16 ` Cyrill Gorcunov
2008-07-24 11:58   ` Martin Wilck
2008-07-24 12:05     ` Cyrill Gorcunov
2008-07-24 13:55       ` [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe Martin Wilck
2008-07-24 14:31         ` Cyrill Gorcunov
2008-07-24 15:01           ` Cyrill Gorcunov
2008-07-24 15:13             ` Martin Wilck
2008-07-25  9:02               ` [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe (take 2) Martin Wilck
2008-07-25 10:08                 ` Cyrill Gorcunov
2008-07-25 12:29                   ` Martin Wilck
2008-07-25 12:59                     ` Cyrill Gorcunov
2008-07-25 13:38                       ` Martin Wilck
2008-07-25 13:48                         ` Cyrill Gorcunov
2008-07-25 14:01                           ` [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe (take 3) Martin Wilck
2008-07-25 14:15                             ` Cyrill Gorcunov
2008-07-25 15:01                             ` Cyrill Gorcunov
2008-07-25 15:13                               ` Martin Wilck
2008-07-25 15:39                                 ` Cyrill Gorcunov
2008-07-26 15:40                                 ` Ingo Molnar
2009-03-12  9:41                                 ` Jean Delvare
2009-03-12 13:38                                   ` Martin Wilck
2008-07-25 16:51                 ` [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe (take 2) Olaf Dabrunz
2008-07-24 13:31 ` H. Peter Anvin [this message]
2008-07-24 13:42   ` [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe Martin Wilck

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=48888444.1020305@zytor.com \
    --to=hpa@zytor.com \
    --cc=Gerhard.Wichert@fujitsu-siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.wilck@fujitsu-siemens.com \
    --cc=tglx@linutronix.de \
    /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.