mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@fenrus.demon.nl>,
	Doug Ledford <dledford@redhat.com>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC] framework for fpu usage in kernel
Date: Sun, 11 Feb 2001 21:30:53 +0100	[thread overview]
Message-ID: <3A86F67D.53C1BD9B@colorfullife.com> (raw)
In-Reply-To: <E14S359-0004vi-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > memcopy is a really generic function, and calling it saves the current
> > fpu state into thread.i387.f{,x}save. IMHO that's wrong, memcopy must
> > save into a local buffer like raid5 checksumming.
> 
> The mmx copy is only done in task context. There are a whole variety
> of _horrible_ problems doing it in interrupt space so based on the
> considerable number of problems with prior attempts to get it right on
> IRQ and copyuser cases I didnt bother
>
Even task context is dangerous:

What if a drm module wants to use the fpu and then uses memcpy() after
modifying the ftp registers?

--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-11 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11 19:03 Manfred Spraul
2001-02-11 20:26 ` Alan Cox
2001-02-11 20:30   ` Manfred Spraul [this message]
2001-02-11 20:37     ` 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=3A86F67D.53C1BD9B@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@fenrus.demon.nl \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®