lkml.org 
[lkml]   [2010]   [Jul]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[Patch 05/25] GRU - cbe cache flush
    From: Jack Steiner <steiner@sgi.com>

    In some cases, for performance reasons flushing the SGI GRU cbe
    needs to dirty the cacheline before doing the cacheline flush. This ensures
    that the dirty cacheline actually goes back to the caching home agent.
    Update a reserved field in the CBE instead of a field that might be used. This
    _should_ not be required (dirtying any field should be ok) but early
    silicon has an issue here.

    Note that flushing the CL is not a requirement - only a performance enhancement.

    Signed-off-by: Jack Steiner <steiner@sgi.com>


    ---
    drivers/misc/sgi-gru/grufault.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    Index: linux/drivers/misc/sgi-gru/grufault.c
    ===================================================================
    --- linux.orig/drivers/misc/sgi-gru/grufault.c 2010-06-09 08:11:40.285085853 -0500
    +++ linux/drivers/misc/sgi-gru/grufault.c 2010-06-09 08:11:41.157110138 -0500
    @@ -306,7 +306,7 @@ upm:
    static void gru_flush_cache_cbe(struct gru_control_block_extended *cbe)
    {
    if (unlikely(cbe)) {
    - cbe->cbrexecstatus = 0; /* make CL dirty */
    + cbe->reserved6 = 0; /* make CL dirty */
    gru_flush_cache(cbe);
    }
    }


    \
     
     \ /
      Last update: 2010-07-19 23:43    [W:0.019 / U:0.104 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site