Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4155855ybi; Mon, 27 May 2019 12:16:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqzJmbAzMjy1eD/CLEtwaAs53300UBp/dcDRjyRo5MSoMU8u/orWeUwyz5MYLlG8LDVDaMdg X-Received: by 2002:a63:2355:: with SMTP id u21mr17847915pgm.205.1558984594734; Mon, 27 May 2019 12:16:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558984594; cv=none; d=google.com; s=arc-20160816; b=GfxXih00DMZ7C5eVlWIN+cg6wO6Ckrg6IAdvE1ZyJDVgo7WRJWquePSf3jJSS+VmQU pNVrkgs/IQ47PlX31nfTUFX+nN1O+iqOPzcc5q+WHvMMVAVvnokkwNCrWZclfcytD+Uc QO62erY+chx0sqg05RsRu+ZryezP274PJwHpOC1PcPg/Ng1QIq6yEH2Bd3T/ahhOtRTW kAqLyYLZ4Gl6lGbt6mYKYSe+3Y8IziSaOEfPXw+1cngOjcQ0sd3FwRZQ1LsNSfHWYlo4 lsz675gydbvR+PI5pg6YhigHd3YKOhAokTeNB1/FU5EDHI9YvUCCNiljBFT/TNLshog/ SeVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=lQh5iMIK6tHDUIF/9F0izv09YkPpLetazpRY2IbhT9Y=; b=RmIIeS5sQfuL89QcjOzeWW2Si2ydhWFhfl6FA7Z4XrPNteFitdOAqC1RFHj+eJtOVY L5vLDjaa1lYCQgktX2+YyOTZT+8k4m6cfH+2dBm0XPvmWVVrYqbgOooTs7lh2hpieGmz x7MYYHC2xB4deVuVXWvSK9dTAdkyBdbIH+TWE97gQD83u9Krp086YKSU4HTQs6igJ3T/ /EYE4ibJJ+cpUoqhYCYYJEkeoECQSYzDK6YvlcfznUWFxbdF0Bcdc/Z7aeUOJ7Aoetfn Rib6NbgwnB2nMx4VCt4Au/jENnpOUiK1150rBXxtbUpBPMwZudRddHOT2drZo0i78XsH 6RRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=lW9ZEB5d; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c17si18628093pgd.368.2019.05.27.12.16.19; Mon, 27 May 2019 12:16:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=lW9ZEB5d; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727176AbfE0TPF (ORCPT + 99 others); Mon, 27 May 2019 15:15:05 -0400 Received: from merlin.infradead.org ([205.233.59.134]:42752 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726801AbfE0TPF (ORCPT ); Mon, 27 May 2019 15:15:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=lQh5iMIK6tHDUIF/9F0izv09YkPpLetazpRY2IbhT9Y=; b=lW9ZEB5dRAprOlMWHMTROQS3WE WGUYgFwik+pP4/KSVn5JWoMd3OWFs0jpVzbvRchCh6sjIOEa1SqiRXJxKMJ/jzd5Z7c5LNEC+oMbw DiIVaaSrngYkEXqrg/+OQBCf3RpJ6/lcG4kP+sZwLOziXWcfDvbOMtJP0W1+ytP82yZB+xIhiEvG/ i4BmXprMS0AjSTxDbLf9RwbMZq6x+3ALhXkYeZBuyjYFhCXgZqK5jlM7/ASTo2VQUcNisvckOCe7I HPsiP7CEVx7dkPKo4EjVZZBnp+TBAEFImsb2iTswUYN6ygjexZAq/d6oGyyQw7kzVyZJkkZk7CGXF HqF4DJJA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVL5D-0005rB-OS; Mon, 27 May 2019 19:14:55 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 840A420301225; Mon, 27 May 2019 21:14:54 +0200 (CEST) Date: Mon, 27 May 2019 21:14:54 +0200 From: Peter Zijlstra To: Nadav Amit Cc: Ingo Molnar , Andy Lutomirski , Borislav Petkov , "linux-kernel@vger.kernel.org" , Dave Hansen , Thomas Gleixner , "H. Peter Anvin" , "x86@kernel.org" Subject: Re: [RFC PATCH 4/6] x86/mm/tlb: Refactor common code into flush_tlb_on_cpus() Message-ID: <20190527191454.GI2623@hirez.programming.kicks-ass.net> References: <20190525082203.6531-1-namit@vmware.com> <20190525082203.6531-5-namit@vmware.com> <20190527092434.GT2623@hirez.programming.kicks-ass.net> <9BE478F9-C700-46C5-80BC-B905FD0AAB17@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9BE478F9-C700-46C5-80BC-B905FD0AAB17@vmware.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 27, 2019 at 06:59:01PM +0000, Nadav Amit wrote: > > On May 27, 2019, at 2:24 AM, Peter Zijlstra wrote: > > > > On Sat, May 25, 2019 at 01:22:01AM -0700, Nadav Amit wrote: > > > >> There is one functional change, which should not affect correctness: > >> flush_tlb_mm_range compared loaded_mm and the mm to figure out if local > >> flush is needed. Instead, the common code would look at the mm_cpumask() > >> which should give the same result. > > > >> @@ -786,18 +804,9 @@ void flush_tlb_mm_range(struct mm_struct *mm, unsigned long start, > >> info = get_flush_tlb_info(mm, start, end, stride_shift, freed_tables, > >> new_tlb_gen); > >> > >> - if (mm == this_cpu_read(cpu_tlbstate.loaded_mm)) { > >> - lockdep_assert_irqs_enabled(); > >> - local_irq_disable(); > >> - flush_tlb_func_local(info, TLB_LOCAL_MM_SHOOTDOWN); > >> - local_irq_enable(); > >> - } > >> - > >> - if (cpumask_any_but(mm_cpumask(mm), cpu) < nr_cpu_ids) > >> - flush_tlb_others(mm_cpumask(mm), info); > > > > So if we want to double check that; we'd add: > > > > WARN_ON_ONCE(cpumask_test_cpu(smp_processor_id(), mm_cpumask(mm)) == > > (mm == this_cpu_read(cpu_tlbstate.loaded_mm))); > > > > right? > > Yes, except the condition should be inverted (“!=“ instead of “==“), and I > would prefer to use VM_WARN_ON_ONCE(). > > Unfortunately, this condition does fire when copy_init_mm() calls dup_mm(). > I don’t think there is a correctness issue, and I am tempted just check, > before warning, that (mm != init_mm) . > > What do you say? Works for me.