All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: FPU context switching fix for SMP
Date: Tue, 15 Feb 2005 20:01:12 +0000	[thread overview]
Message-ID: <20050215200112.GZ13009@holomorphy.com> (raw)
In-Reply-To: <41f753cabb795@wp.pl>

On Tue, Feb 15, 2005 at 09:40:57AM -0800, David S. Miller wrote:
> I've modified your patch to only do this in the SMP case.
> Here is how the two mechanisms work:
[...]
> The SMP case works in that each thread, when scheduled(), has
> it's PSR_EF flag cleared.
> This fork() bug takes away that invariant, which is why the
> problems arose.
> Thanks a lot Krzysztof.

Looks like you got this one wrapped up before I figured out what was
going on.

Thanks.


-- wli

      parent reply	other threads:[~2005-02-15 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  8:24 FPU context switching fix for SMP Krzysztof Helt
2005-01-26  8:26 ` William Lee Irwin III
2005-01-26  8:57 ` Krzysztof Helt
2005-01-26 22:06 ` Baurjan Ismagulov
2005-01-26 23:09 ` David S. Miller
2005-01-29 18:22 ` Baurjan Ismagulov
2005-02-15 17:40 ` David S. Miller
2005-02-15 20:01 ` William Lee Irwin III [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=20050215200112.GZ13009@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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.