Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=683e3ab2b54a7190ec8517705880171cc8ac1d92
Commit:     683e3ab2b54a7190ec8517705880171cc8ac1d92
Parent:     430404ed9c2f202ca9d3c8072699b2b0279e4dfe
Author:     Andre Detsch <[EMAIL PROTECTED]>
AuthorDate: Tue Jul 31 09:48:11 2007 +1000
Committer:  Paul Mackerras <[EMAIL PROTECTED]>
CommitDate: Fri Aug 3 19:18:10 2007 +1000

    [POWERPC] spufs: Fix affinity after introduction of node_allowed() calls
    
    This patch fixes affinity reference point placement, which was not being
    done in some situations, after the introduction of node_allowed() calls.
    
    The previously used parameter, 'ctx', is just the iterator of the
    previous list_for_each_entry_reverse loop, and its value might be
    invalid at the end of the loop. Also, the right context to seek
    for information when defining the reference ctx location
    _is_ the reference ctx.
    
    Signed-off-by: Andre Detsch <[EMAIL PROTECTED]>
    Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
    Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
    Signed-off-by: Paul Mackerras <[EMAIL PROTECTED]>
---
 arch/powerpc/platforms/cell/spufs/sched.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/arch/powerpc/platforms/cell/spufs/sched.c 
b/arch/powerpc/platforms/cell/spufs/sched.c
index 758a80a..c784edd 100644
--- a/arch/powerpc/platforms/cell/spufs/sched.c
+++ b/arch/powerpc/platforms/cell/spufs/sched.c
@@ -351,7 +351,8 @@ static void aff_set_ref_point_location(struct spu_gang 
*gang)
                lowest_offset = ctx->aff_offset;
        }
 
-       gang->aff_ref_spu = aff_ref_location(ctx, mem_aff, gs, lowest_offset);
+       gang->aff_ref_spu = aff_ref_location(gang->aff_ref_ctx, mem_aff, gs,
+                                                       lowest_offset);
 }
 
 static struct spu *ctx_location(struct spu *ref, int offset, int node)
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to