Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@junsun.net>
To: zhan rongkai <zhanrk@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: About task->used_math and TIF_USEDFPU
Date: Thu, 16 Dec 2004 09:33:06 -0800	[thread overview]
Message-ID: <20041216173306.GA3230@gw.junsun.net> (raw)
In-Reply-To: <73e6204504121600066a2ce0b1@mail.gmail.com>

On Thu, Dec 16, 2004 at 04:06:12PM +0800, zhan rongkai wrote:
> hi all,
> 
> I am a little confused about the task_struct member 'used_math', and
> thread_info flag TIF_USEDFPU.
> 
> What are their meaning, and what is the difference between them?
> 

used_math is used to indicate whether a process has ever used FPU since
it is created (which typically is true due to the glibc using FPU at the
beginning of each program).

TIF_USEDFPU indicates whether a _running_ process has used FPU since
it is context-switched on.

Jun

      reply	other threads:[~2004-12-16 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16  8:06 About task->used_math and TIF_USEDFPU zhan rongkai
2004-12-16 17:33 ` Jun Sun [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=20041216173306.GA3230@gw.junsun.net \
    --to=jsun@junsun.net \
    --cc=linux-mips@linux-mips.org \
    --cc=zhanrk@gmail.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