From: "Yinghai Lu" <yinghai@kernel.org>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Krzysztof Helt" <krzysztof.h1@poczta.fm>,
linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: do not allow to optimize flag_is_changeable_p()
Date: Mon, 29 Sep 2008 23:34:51 -0700 [thread overview]
Message-ID: <86802c440809292334o557d2158ob2c52aebd3caf0b3@mail.gmail.com> (raw)
In-Reply-To: <48E1C3BD.5020705@goop.org>
On Mon, Sep 29, 2008 at 11:14 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Krzysztof Helt wrote:
>> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>>
>> The flag_is_changeable_p() is used by
>> has_cpuid_p() which can return different results
>> in the code sequence below:
>>
>> if (!have_cpuid_p())
>> identify_cpu_without_cpuid(c);
>>
>> /* cyrix could have cpuid enabled via c_identify()*/
>> if (!have_cpuid_p())
>> return;
>>
>> Otherwise, the gcc 3.4.6 optimizes these two calls
>> into one which make the code not working correctly.
>> Cyrix cpus have the CPUID instruction enabled but
>> it is not detected due to the gcc optimization.
>> Thus the ARR registers (mtrr like) are not detected
>> on such a cpu.
>>
>
> If "asm volatile" changes the code and fixes the bug, it seems like
> you're making use of an undocumented - or at least non-portable - behaviour.
>
> Does adding a "memory" clobber also fix the problem? That would have
> better defined characteristics.
>
how about
if (!have_cpuid_p()) {
identify_cpu_without_cpuid(c);
/* cyrix could have cpuid enabled via c_identify()*/
if (!have_cpuid_p())
return;
}
YH
next prev parent reply other threads:[~2008-09-30 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:06 Krzysztof Helt
2008-09-29 18:17 ` H. Peter Anvin
2008-09-30 6:14 ` Jeremy Fitzhardinge
2008-09-30 6:34 ` Yinghai Lu [this message]
2008-09-30 6:54 ` Jeremy Fitzhardinge
2008-09-30 8:27 krzysztof.h1
2008-09-30 15:23 ` Jeremy Fitzhardinge
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=86802c440809292334o557d2158ob2c52aebd3caf0b3@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®