From: "Tommy Faasen" <tommy@vuurwerk.nl>
To: <linux-kernel@vger.kernel.org>
Subject: SMP processor rework help needed
Date: Sun, 14 Oct 2001 22:23:37 +0200 [thread overview]
Message-ID: <000b01c154ee$1d6a2610$6400a8c0@it0> (raw)
Hi,
I have this unique situation where cpu 1 has less features (like fxsr) then
cpu 0.
However the linux kernel only looks at the cpu 0 and assumes the all the
other cpu's have the same capabilities. Which can cause it to oops.
Several of you have been so kind to help me find this problem. Now I can
manually fit it in processor.h to change #define cpu_has_fxsr 0.
I would like to rewrite this bit so it tests all the cpu's if it has a
certain capability and only then activates this feature, I think this would
be a more clean way of handling things.
Anyway I have been looking through processor.h and bitops.h and figured it
does a some asm to extract this information.
So again I am stuck as my limited knowledge stops here, so I was hoping that
someone could give me a helping hand or point me in a direction.
Ps 2.4.12-ac2 works fine with my little modification on my aic78xxx lx smp
system in case you wanted to know.
next reply other threads:[~2001-10-14 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 20:23 Tommy Faasen [this message]
2001-10-14 20:33 ` SMP processor rework help needed Andi Kleen
2001-10-14 20:50 ` Gerhard Mack
2001-10-14 21:07 ` Andi Kleen
2001-10-15 15:20 ` Eric W. Biederman
2001-10-14 22:09 ` Tommy Faasen
2001-10-15 5:07 ` Pascal Schmidt
2001-10-15 21:25 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2001-10-15 17:16 Manfred Spraul
2001-10-15 21:39 ` Alan Cox
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='000b01c154ee$1d6a2610$6400a8c0@it0' \
--to=tommy@vuurwerk.nl \
--cc=linux-kernel@vger.kernel.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 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.