On Wed, Dec 11, 2013 at 01:21:09PM +0000, Mel Gorman wrote:
> According to documentation on barriers, stores issued before a LOCK can
> complete after the lock implying that it's possible tlb_flush_pending can
> be visible after a page table update. As per revised documentation, this patch
> adds a smp_mb__before_spinlock to guarantee the correct ordering.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Mel Gorman <mgor...@suse.de>
Assuming that there is a lock acquisition after calls to
set_tlb_flush_pending():
Acked-by: Paul E. McKenney <paul...@linux.vnet.ibm.com>
(I don't see set_tlb_flush_pending() in mainline.)
> ---
> include/linux/mm_types.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index c122bb1..a12f2ab 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -482,7 +482,12 @@ static inline bool tlb_flush_pending(struct mm_struct
> *mm)
> static inline void set_tlb_flush_pending(struct mm_struct *mm)
> {
> mm->tlb_flush_pending = true;
> - barrier();
> +
> + /*
> + * Guarantee that the tlb_flush_pending store does not leak into the
> + * critical section updating the page tables
> + */
> + smp_mb__before_spinlock();
> }
> /* Clearing is done after a TLB flush, which also provides a barrier. */
> static inline void clear_tlb_flush_pending(struct mm_struct *mm)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
