* PREEMPT
@ 2005-10-06 18:36 Greg Weeks
2005-10-06 18:46 ` PREEMPT Ralf Baechle
0 siblings, 1 reply; 7+ messages in thread
From: Greg Weeks @ 2005-10-06 18:36 UTC (permalink / raw)
To: linux-mips; +Cc: Cooper, John
Does anyone know of any current problems with CONFIG_PREEMPT on a 4kc
malta board? We're seeing some oddness in the floating point emulator
with PREEMPT_RT and wondered if it was in our RT code, or if it's from
the base kernel code.
Greg W
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 19:05 ` PREEMPT john cooper
@ 2005-10-06 18:45 ` sjhill
2005-10-07 13:55 ` PREEMPT Atsushi Nemoto
0 siblings, 1 reply; 7+ messages in thread
From: sjhill @ 2005-10-06 18:45 UTC (permalink / raw)
To: john cooper; +Cc: Ralf Baechle, Greg Weeks, linux-mips
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 18:36 PREEMPT Greg Weeks
@ 2005-10-06 18:46 ` Ralf Baechle
2005-10-06 18:52 ` PREEMPT Greg Weeks
0 siblings, 1 reply; 7+ messages in thread
From: Ralf Baechle @ 2005-10-06 18:46 UTC (permalink / raw)
To: Greg Weeks; +Cc: linux-mips, Cooper, John
On Thu, Oct 06, 2005 at 02:36:25PM -0400, Greg Weeks wrote:
> Does anyone know of any current problems with CONFIG_PREEMPT on a 4kc
> malta board? We're seeing some oddness in the floating point emulator
> with PREEMPT_RT and wondered if it was in our RT code, or if it's from
> the base kernel code.
No known problem in current problems in that area.
Ralf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 18:46 ` PREEMPT Ralf Baechle
@ 2005-10-06 18:52 ` Greg Weeks
2005-10-06 18:55 ` PREEMPT Ralf Baechle
0 siblings, 1 reply; 7+ messages in thread
From: Greg Weeks @ 2005-10-06 18:52 UTC (permalink / raw)
To: Ralf Baechle; +Cc: linux-mips, Cooper, John
Ralf Baechle wrote:
>On Thu, Oct 06, 2005 at 02:36:25PM -0400, Greg Weeks wrote:
>
>
>
>>Does anyone know of any current problems with CONFIG_PREEMPT on a 4kc
>>malta board? We're seeing some oddness in the floating point emulator
>>with PREEMPT_RT and wondered if it was in our RT code, or if it's from
>>the base kernel code.
>>
>>
>
>No known problem in current problems in that area.
>
>
>
I'd remembered some problems ages ago, but had thought they'd been
fixed. John was just picking my brain about it so I thought I'd ask to
be sure.
Greg W
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 18:52 ` PREEMPT Greg Weeks
@ 2005-10-06 18:55 ` Ralf Baechle
2005-10-06 19:05 ` PREEMPT john cooper
0 siblings, 1 reply; 7+ messages in thread
From: Ralf Baechle @ 2005-10-06 18:55 UTC (permalink / raw)
To: Greg Weeks; +Cc: linux-mips, Cooper, John
On Thu, Oct 06, 2005 at 02:52:22PM -0400, Greg Weeks wrote:
> I'd remembered some problems ages ago, but had thought they'd been
> fixed. John was just picking my brain about it so I thought I'd ask to
> be sure.
The problems I recall were all related to being preempted just while
fiddling with the hardware FPU - can't happen on the fpu-less 4Kc.
Another issue fixesd recently even though more cosmetic were a bunch
of global variables.
Ralf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 18:55 ` PREEMPT Ralf Baechle
@ 2005-10-06 19:05 ` john cooper
2005-10-06 18:45 ` PREEMPT sjhill
0 siblings, 1 reply; 7+ messages in thread
From: john cooper @ 2005-10-06 19:05 UTC (permalink / raw)
To: Ralf Baechle; +Cc: Greg Weeks, linux-mips, john cooper
Ralf Baechle wrote:
> On Thu, Oct 06, 2005 at 02:52:22PM -0400, Greg Weeks wrote:
>
>
>>I'd remembered some problems ages ago, but had thought they'd been
>>fixed. John was just picking my brain about it so I thought I'd ask to
>>be sure.
>
>
> The problems I recall were all related to being preempted just while
> fiddling with the hardware FPU - can't happen on the fpu-less 4Kc.
> Another issue fixesd recently even though more cosmetic were a bunch
> of global variables.
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.
-john
--
john.cooper@timesys.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PREEMPT
2005-10-06 18:45 ` PREEMPT sjhill
@ 2005-10-07 13:55 ` Atsushi Nemoto
0 siblings, 0 replies; 7+ messages in thread
From: Atsushi Nemoto @ 2005-10-07 13:55 UTC (permalink / raw)
To: sjhill; +Cc: john.cooper, ralf, greg.weeks, linux-mips
>>>>> On Thu, 6 Oct 2005 13:45:55 -0500 (CDT), sjhill@realitydiluted.com said:
sjhill> Um, did no one have a look at Atsushi Nemoto's patch earlier
sjhill> today that addressed pre-emption and CPU1, or am I missing
sjhill> something?
The patch I posted yesterday affects just for ptrace. I suppose this
is not irrelevant.
Also, though it might irrelevant too, I think there are still possible
bug related signal and fpu_context. I'll post a patch again.
---
Atsushi Nemoto
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-10-07 13:57 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` PREEMPT sjhill
2005-10-07 13:55 ` PREEMPT Atsushi Nemoto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox