Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Cleanup FPU ownership management
Date: Sat, 10 Mar 2007 12:37:29 +0000	[thread overview]
Message-ID: <20070310123729.GB500@linux-mips.org> (raw)
In-Reply-To: <20070310.012319.52129805.anemo@mba.ocn.ne.jp>

On Sat, Mar 10, 2007 at 01:23:19AM +0900, Atsushi Nemoto wrote:

> Currently preempt_disable/preempt_enable are scattered in FPU
> ownership management code.  This patch makes own_fpu() and lost_fpu()
> can save/restore FPU context in itself and make these functions (and
> init_fpu() too) preempt-proof.  This makes the FPU management codes
> much readable.  Also this patch introduce raw_cpu_has_fpu macro which
> is to be used if the caller did not need atomic context.

And this one dropped also.

  Ralf

      reply	other threads:[~2007-03-10 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 16:23 [PATCH] Cleanup FPU ownership management Atsushi Nemoto
2007-03-10 12:37 ` Ralf Baechle [this message]

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=20070310123729.GB500@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.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