* William Lee Irwin III ([EMAIL PROTECTED]) wrote:
> On Sat, 10 Mar 2007 00:26:46 -0800, William Lee Irwin III <[EMAIL PROTECTED]>
> wrote:
> >> Oh dear. Could we bit a bit more idiomatic here? For instance,
> >> something like:
>
> On Sat, Mar 10, 2007 at 12:29:44AM -0800, David Miller wrote:
>
On Sat, 10 Mar 2007 00:26:46 -0800, William Lee Irwin III <[EMAIL PROTECTED]>
wrote:
>> Oh dear. Could we bit a bit more idiomatic here? For instance,
>> something like:
On Sat, Mar 10, 2007 at 12:29:44AM -0800, David Miller wrote:
> Ok I pulled the sparc32 patch back out until there is some
>
From: William Lee Irwin III <[EMAIL PROTECTED]>
Date: Sat, 10 Mar 2007 00:26:46 -0800
> On Sat, Mar 10, 2007 at 03:17:43AM -0500, Mathieu Desnoyers wrote:
> > @@ -348,7 +348,7 @@ void exit_thread(void)
> > #ifndef CONFIG_SMP
> > if(last_task_used_math == current) {
> > #else
> > -
On Sat, Mar 10, 2007 at 03:17:43AM -0500, Mathieu Desnoyers wrote:
> @@ -348,7 +348,7 @@ void exit_thread(void)
> #ifndef CONFIG_SMP
> if(last_task_used_math == current) {
> #else
> - if(current_thread_info()->flags & _TIF_USEDFPU) {
> +
From: Mathieu Desnoyers <[EMAIL PROTECTED]>
Date: Sat, 10 Mar 2007 03:17:43 -0500
> Fix sparc TIF_USEDFPU flag atomicity
Also applied, thanks again.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
This fix addresses the issue with *_ti_thread_flag().
Applies on 2.6.20.
Signed-off-by: Mathieu Desnoyers
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
This fix addresses the issue with *_ti_thread_flag().
Applies on 2.6.20.
Signed-off-by: Mathieu Desnoyers
On Sat, Mar 10, 2007 at 03:17:43AM -0500, Mathieu Desnoyers wrote:
@@ -348,7 +348,7 @@ void exit_thread(void)
#ifndef CONFIG_SMP
if(last_task_used_math == current) {
#else
- if(current_thread_info()-flags _TIF_USEDFPU) {
+ if(test_ti_thread_flag(current_thread_info(),
From: Mathieu Desnoyers [EMAIL PROTECTED]
Date: Sat, 10 Mar 2007 03:17:43 -0500
Fix sparc TIF_USEDFPU flag atomicity
Also applied, thanks again.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
From: William Lee Irwin III [EMAIL PROTECTED]
Date: Sat, 10 Mar 2007 00:26:46 -0800
On Sat, Mar 10, 2007 at 03:17:43AM -0500, Mathieu Desnoyers wrote:
@@ -348,7 +348,7 @@ void exit_thread(void)
#ifndef CONFIG_SMP
if(last_task_used_math == current) {
#else
-
On Sat, 10 Mar 2007 00:26:46 -0800, William Lee Irwin III [EMAIL PROTECTED]
wrote:
Oh dear. Could we bit a bit more idiomatic here? For instance,
something like:
On Sat, Mar 10, 2007 at 12:29:44AM -0800, David Miller wrote:
Ok I pulled the sparc32 patch back out until there is some
consensus
* William Lee Irwin III ([EMAIL PROTECTED]) wrote:
On Sat, 10 Mar 2007 00:26:46 -0800, William Lee Irwin III [EMAIL PROTECTED]
wrote:
Oh dear. Could we bit a bit more idiomatic here? For instance,
something like:
On Sat, Mar 10, 2007 at 12:29:44AM -0800, David Miller wrote:
Ok I pulled
On Thu, 8 Mar 2007 22:12:27 -0500 Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>> Fix sparc TIF_USEDFPU flag atomicity
>> Non atomic update of TIF can be very dangerous, except at thread structure
>> creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
>> Applies on 2.6.20.
On Thu, 8 Mar 2007 22:12:27 -0500 Mathieu Desnoyers [EMAIL PROTECTED] wrote:
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
Applies on 2.6.20.
From: Mathieu Desnoyers <[EMAIL PROTECTED]>
Date: Thu, 8 Mar 2007 22:12:27 -0500
> Fix sparc TIF_USEDFPU flag atomicity
>
> Non atomic update of TIF can be very dangerous, except at thread structure
> creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
>
> Applies on
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
Applies on 2.6.20.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/sparc/kernel/process.c
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
Applies on 2.6.20.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
--- a/arch/sparc/kernel/process.c
+++
From: Mathieu Desnoyers [EMAIL PROTECTED]
Date: Thu, 8 Mar 2007 22:12:27 -0500
Fix sparc TIF_USEDFPU flag atomicity
Non atomic update of TIF can be very dangerous, except at thread structure
creation time. Here I standardize the TIF_USEDFPU usage of the sparc arch.
Applies on 2.6.20.
18 matches
Mail list logo
