From: Cyrill Gorcunov <gorcunov@gmail.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>,
"H. Peter Anvin" <hpa@zytor.com>,
"Wichert, Gerhard" <Gerhard.Wichert@fujitsu-siemens.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] x86 (64): make calibrate_APIC_clock() SMI-safe (take 2)
Date: Fri, 25 Jul 2008 16:59:50 +0400 [thread overview]
Message-ID: <20080725125950.GA28466@lenovo> (raw)
In-Reply-To: <4889C723.7050402@fujitsu-siemens.com>
[Martin Wilck - Fri, Jul 25, 2008 at 02:29:23PM +0200]
> Cyrill Gorcunov wrote:
>
>> Hi Martin, what about the patch below - I simplified it a bit.
>> Actually we have to handle 32bit mode as well I think.
>
> Yes.
>
>> Anyway,
>> take a look. I don't really mind against your patch but we better
>> should wait until Maciej could take a look (he will be able in
>> a week or maybe a bit later).
>>
>
>> + for (i = 0; i < MAX_ITER; i++) {
>> + rdtscll(tsc0);
>> + *apic = apic_read(APIC_TMCCT);
>> + rdtscll(tsc1);
>> + diff = tsc1 - tsc0;
>> + if (diff < MAX_DIFFERENCE) {
>> + *tsc = tsc0 + diff / 2;
>> + return 0;
>> + }
>> + }
> > +
> > + return -EIO ;
>
> This is wrong - you need to set *tsc also in the -EIO case, otherwise
> the function can return total bogus.
indeed, thanks! that is not the only problem - I also initialized 'i'
twice :)
>
> I have to say that my simplified patch failed to do the calibration
> correctly on our test system (the original patch worked well). Please
> stay tuned, we are investigating this currently.
>
> Martin
>
ok, Martin, I'm leaving for vacation soon - hope someone else could
take a look :)
- Cyrill -
next prev parent reply other threads:[~2008-07-25 13:00 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 [this message]
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 ` [PATCH] x86 (64): make calibrate_APIC_clock() smp-safe H. Peter Anvin
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=20080725125950.GA28466@lenovo \
--to=gorcunov@gmail.com \
--cc=Gerhard.Wichert@fujitsu-siemens.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox