Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966049Ab2JZSlk (ORCPT ); Fri, 26 Oct 2012 14:41:40 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:42678 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966020Ab2JZSlj (ORCPT ); Fri, 26 Oct 2012 14:41:39 -0400 MIME-Version: 1.0 In-Reply-To: <508AD2FF.5020306@redhat.com> References: <20121025121617.617683848@chello.nl> <20121025124832.840241082@chello.nl> <5089F5B5.1050206@redhat.com> <508A0A0D.4090001@redhat.com> <508ACE6E.8060303@redhat.com> <508AD2FF.5020306@redhat.com> From: Linus Torvalds Date: Fri, 26 Oct 2012 11:41:17 -0700 X-Google-Sender-Auth: PQ8SoJD-nIXSkHZnGbk81N2IOcg Message-ID: Subject: Re: [PATCH 05/31] x86/mm: Reduce tlb flushes from ptep_set_access_flags() To: Rik van Riel Cc: Michel Lespinasse , Peter Zijlstra , Andrea Arcangeli , Mel Gorman , Johannes Weiner , Thomas Gleixner , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Ingo Molnar Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 917 Lines: 22 On Fri, Oct 26, 2012 at 11:14 AM, Rik van Riel wrote: > > I suspect the next context switch would flush out the TLB, > making it a slowdown, not a lockup. Common case, yes. But the page fault might happen in kernel space (due to a "put_user()" call, say), and with CONFIG_PREEMPT=n. Sure, put_user() is always done in a context where blocking (and scheduling) is legal, but that doesn't necessarily equate scheduling actually happening. If we're returning to kernel space and don't have any IO, it might never happen. Anyway, I suspect such behavior it's almost impossible to trigger. Which would just make it rather hard to find. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/