[lkml]   [2009]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH] x86: make text_poke() atomic
    Ingo Molnar wrote:
    >>> So perhaps another approach to (re-)consider would be to go back
    >>> to atomic fixmaps here. It spends 3 slots but that's no big
    >>> deal.
    >> Oh, it's a good idea! fixmaps must make it simpler.
    >>> In exchange it will be conceptually simpler, and will also scale
    >>> much better than a global spinlock. What do you think?
    >> I think even if I use fixmaps, we have to use a spinlock to protect
    >> the fixmap area from other threads...
    > that's why i suggested to use an atomic-kmap, not a fixmap.

    Even if the mapping is atomic, text_poke() has to protect pte
    from other text_poke()s while changing code.
    AFAIK, atomic-kmap itself doesn't ensure that, does it?

    Thank you,

    > Ingo
    > --
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to
    > More majordomo info at
    > Please read the FAQ at

    Masami Hiramatsu

    Software Engineer
    Hitachi Computer Products (America) Inc.
    Software Solutions Division


     \ /
      Last update: 2009-03-03 00:41    [W:0.020 / U:6.160 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site