From: sjhill@realitydiluted.com
To: john cooper <john.cooper@timesys.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Greg Weeks <greg.weeks@timesys.com>,
linux-mips@linux-mips.org
Subject: Re: PREEMPT
Date: Thu, 6 Oct 2005 13:45:55 -0500 (CDT) [thread overview]
Message-ID: <E1ENakd-0005up-Pl@real.realitydiluted.com> (raw)
In-Reply-To: <43457563.60505@timesys.com>
> The code base I'm dealing with is a 2.6.13 derivative
> with PREEMPT_RT support. Looks like the problem was
> due to PREEMPT_RT confusing fpu_emulator_cop1Handler()
> resulting in a SIGBUS nailing the associated task.
>
> I have it sort of working for soft FPU but expect it
> requires some attention to safely access a HW FPU where
> emulation assistance is needed.
>
Um, did no one have a look at Atsushi Nemoto's patch earlier today
that addressed pre-emption and CPU1, or am I missing something?
-Steve
next prev parent reply other threads:[~2005-10-06 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 18:36 PREEMPT Greg Weeks
2005-10-06 18:46 ` PREEMPT Ralf Baechle
2005-10-06 18:52 ` PREEMPT Greg Weeks
2005-10-06 18:55 ` PREEMPT Ralf Baechle
2005-10-06 19:05 ` PREEMPT john cooper
2005-10-06 18:45 ` sjhill [this message]
2005-10-07 13:55 ` PREEMPT Atsushi Nemoto
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=E1ENakd-0005up-Pl@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=greg.weeks@timesys.com \
--cc=john.cooper@timesys.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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