From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sean Young <sean@mess.org>, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Regression: boot failure on AMD Elan TS-5500
Date: Tue, 01 Jul 2008 13:39:13 -0700 [thread overview]
Message-ID: <486A95F1.3080007@zytor.com> (raw)
In-Reply-To: <486A938D.3080009@goop.org>
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Not really. In particular, I really don't want to add something that
>> is even remotely likely to break on other platforms, and a fence
>> instruction is relatively recent.
>
> I wonder if a cpuid would do the trick? Do we still support cpuid-less
> processors?
Yes, we do. Worst case, we could bypass it, but I'd like to understand
what the real constraint is, here.
-hpa
next prev parent reply other threads:[~2008-07-01 20:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:11 Regression: boot failure on AMD Elan TS-5500 Sean Young
2008-06-16 13:27 ` Rusty Russell
2008-06-16 13:37 ` Jeremy Fitzhardinge
2008-06-16 16:19 ` Sean Young
2008-06-16 17:06 ` H. Peter Anvin
2008-06-16 17:58 ` Sean Young
2008-06-16 18:16 ` H. Peter Anvin
2008-06-16 17:06 ` H. Peter Anvin
2008-06-16 17:07 ` Jeremy Fitzhardinge
2008-06-30 21:43 ` Sean Young
2008-06-30 21:52 ` Jeremy Fitzhardinge
2008-06-30 22:04 ` H. Peter Anvin
2008-06-30 22:14 ` H. Peter Anvin
2008-06-30 22:36 ` Jeremy Fitzhardinge
2008-06-30 22:45 ` H. Peter Anvin
2008-06-30 22:31 ` Sean Young
2008-06-30 22:34 ` Jeremy Fitzhardinge
2008-06-30 22:42 ` H. Peter Anvin
2008-07-01 19:59 ` Sean Young
2008-07-01 20:20 ` Sean Young
2008-07-01 20:24 ` Jeremy Fitzhardinge
2008-07-01 20:25 ` H. Peter Anvin
2008-07-15 22:23 ` Sean Young
2008-07-15 22:30 ` H. Peter Anvin
2008-07-01 20:22 ` Jeremy Fitzhardinge
2008-07-01 20:23 ` H. Peter Anvin
2008-07-01 20:29 ` Jeremy Fitzhardinge
2008-07-01 20:39 ` H. Peter Anvin [this message]
2008-07-06 13:21 ` Pavel Machek
2008-06-30 22:09 ` Sean Young
2008-07-06 2:41 ` Eric W. Biederman
2008-07-06 3:07 ` H. Peter Anvin
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=486A95F1.3080007@zytor.com \
--to=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sean@mess.org \
/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