From: Manfred Spraul <manfred@colorfullife.com>
To: bergsoft@home.com, linux-kernel@vger.kernel.org
Subject: Re: Followup to previous post: Atlon/VIA Instabilities
Date: Wed, 02 May 2001 00:10:53 +0200 [thread overview]
Message-ID: <3AEF346D.FB01EAE9@colorfullife.com> (raw)
> So it seems that CONFIG_X86_USE_3DNOW is simply used to
> enable access to the routines in mmx.c (the athlon-optimized
> routines on CONFIG_K7 kernels), so then it appears that somehow
> this is corrupting memory / not behaving as it should (very
> technical, right?) :)...
Do you use any unusual (binary only/with source) kernel modules?
mmx.c stores the current contents on the fpu registers into
current->thread.i387.f{,x}save.
If another module modifes the fpu registers and calls memmove it will
cause fpu corruptions.
I checked that a few months ago, and no module in the main kernel tree
does that.
--
Manfred
next reply other threads:[~2001-05-01 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 22:10 Manfred Spraul [this message]
2001-05-02 2:26 ` Followup to previous post: Atlon/VIA Instabilities Seth Goldberg
2001-05-02 9:22 ` Linux Kernel Developer
-- strict thread matches above, loose matches on Subject: below --
2001-05-01 11:31 Seth Goldberg
2001-05-01 13:02 ` Alan Cox
2001-05-02 11:10 ` Tom Leete
2001-05-03 10:36 ` Seth Goldberg
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=3AEF346D.FB01EAE9@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=bergsoft@home.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox