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;
Date:   Mon, 20 May 2019 15:48:55 -0700 (PDT)
Message-Id: <20190520.154855.2207738976381931092.davem@davemloft.net>
To:     rick.p.edgecombe@intel.com
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        peterz@infradead.org, mroos@linux.ee, netdev@vger.kernel.org,
        sparclinux@vger.kernel.org, bp@alien8.de, luto@kernel.org,
        mingo@redhat.com, namit@vmware.com, dave.hansen@intel.com
Subject: Re: [PATCH v2] vmalloc: Fix issues with flush flag
From:   David Miller <davem@davemloft.net>
In-Reply-To: <c6020a01e81d08342e1a2b3ae7e03d55858480ba.camel@intel.com>
References: <20190520200703.15997-1-rick.p.edgecombe@intel.com>
        <90f8a4e1-aa71-0c10-1a91-495ba0cb329b@linux.ee>
        <c6020a01e81d08342e1a2b3ae7e03d55858480ba.camel@intel.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Date: Mon, 20 May 2019 22:17:49 +0000

> Thanks for testing. So I guess that suggests it's the TLB flush causing
> the problem on sparc and not any lazy purge deadlock. I had sent Meelis
> another test patch that just flushed the entire 0 to ULONG_MAX range to
> try to always the get the "flush all" logic and apprently it didn't
> boot mostly either. It also showed that it's not getting stuck anywhere
> in the vm_remove_alias() function. Something just hangs later.

I wonder if an address is making it to the TLB flush routines which is
not page aligned.  Or a TLB flush is being done before the callsites
are patched properly for the given cpu type.