From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
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 3)
Date: Thu, 12 Mar 2009 14:38:46 +0100 [thread overview]
Message-ID: <49B91066.3010000@fujitsu-siemens.com> (raw)
In-Reply-To: <200903121041.34746.jdelvare@suse.de>
Hi Jean,
same answer as on Bugzilla...
> Sorry for replying to such an old thread, but did this patch go
> anywhere? I can't seem to find it in git. Was it somehow obsoleted
> by a different fix for the same issue (SMI flood during APIC
> calibration)? Or is the upstream kernel still affected?
We were asked for a solution for all affected architectures (in
particular, also i386) which was more than we were able to do
at the time, given that the pressure had been reduced by finding a BIOS
fix for the particular situation on system in question.
The APIC clock calibration code on i386 is more complex than x86_64, we
saw no way to provide a high-quality, regression-safe, tested patch for
that to upstream with a reasonable amount of effort.
That aside, I still think the x86_64 patch is fine and won't cause
regressions. It just doesn't help on 32bit systems.
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 525 2796
Fax: ++49 5251 525 2820
Email: mailto:martin.wilck@fujitsu-siemens.com
Internet: http://www.fujitsu-siemens.com
Company Details: http://www.fujitsu-siemens.com/imprint.html
next prev parent reply other threads:[~2009-03-12 13:48 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 [this message]
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=49B91066.3010000@fujitsu-siemens.com \
--to=martin.wilck@fujitsu-siemens.com \
--cc=Gerhard.Wichert@fujitsu-siemens.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--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.