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() smp-safe
Date: Thu, 24 Jul 2008 16:05:12 +0400 [thread overview]
Message-ID: <20080724120512.GA21804@lenovo> (raw)
In-Reply-To: <48886E6D.1030005@fujitsu-siemens.com>
[Martin Wilck - Thu, Jul 24, 2008 at 01:58:37PM +0200]
> Cyrill Gorcunov wrote:
>
>> Hi, but what if SMI flood happens? We could stuck here forever, don't we?
>>
>> - Cyrill -
>
>
> Yes, if the SMI flood never ends. But you wouldn't want to work on such
> a system anyway (with the current kernel code, your APIC timer would
> most probably be miscalibrated, which can have the weirdest effects).
>
> Anyway, we can add a maximum iteration count to the patch so that there
> is no risk of getting stuck.
>
> Martin
>
> --
> Martin Wilck
> PRIMERGY System Software Engineer
> FSC IP ESP DEV 6
>
> Fujitsu Siemens Computers GmbH
> Heinz-Nixdorf-Ring 1
> 33106 Paderborn
> Germany
>
> Tel: ++49 5251 8 15113
> Fax: ++49 5251 8 20209
> Email: mailto:martin.wilck@fujitsu-siemens.com
> Internet: http://www.fujitsu-siemens.com
> Company Details: http://www.fujitsu-siemens.com/imprint.html
>
yes, it will issue some effects but it's better then stuck there.
More over in 'case of SMI flood with current patch you don't get
error message printed i think so you better add max iteration
counter so user will see on console (or whatever) that he is got
problems.
- Cyrill -
next prev parent reply other threads:[~2008-07-24 12:05 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 [this message]
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 ` [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=20080724120512.GA21804@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 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.