From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.alien8.de (mail.alien8.de [65.109.113.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C77797B3C7 for ; Tue, 12 Mar 2024 16:35:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=65.109.113.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710261330; cv=none; b=cem4PoSLifAQE4QPjC0T7iukkEDMzx88+5yTG9GKPOeugATjhdbNO2vZ/qYXYNqV20/V9buRl9udWhV13Clyqsd6kKpSsf/PEJ16/0xLJwFqepFR8iwJFYozTTGzE3ej3ii9zvmt9MUmPRW1S1f2Rn1a35vOw699plZdcixhrc8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710261330; c=relaxed/simple; bh=S8Gs69JN4BRkAeykLxUkio2jGlDuEezvviIDYxcsAWg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=kYTzJGIl0y6XM0pO4RIMBe3A7oDmQsvHxxa3UXJTOXCBQY+JvdXW2GuzVRdzmEt3cDLP3aVcV5zmzjEqO5bLTbc/JWU25I2iLTiwVFSIJO2i2zjTVZdbAd0tc0CVpo2FDNAnTPE4YYwaTxS7yqCx2LKk5FdP/AeL5OB58RXx4no= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=alien8.de; spf=pass smtp.mailfrom=alien8.de; dkim=pass (4096-bit key) header.d=alien8.de header.i=@alien8.de header.b=AZVdRiHX; arc=none smtp.client-ip=65.109.113.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=alien8.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=alien8.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (4096-bit key) header.d=alien8.de header.i=@alien8.de header.b="AZVdRiHX" Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.alien8.de (SuperMail on ZX Spectrum 128k) with ESMTP id 4B7E140E01A0; Tue, 12 Mar 2024 16:35:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.alien8.de Authentication-Results: mail.alien8.de (amavisd-new); dkim=pass (4096-bit key) header.d=alien8.de Received: from mail.alien8.de ([127.0.0.1]) by localhost (mail.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id C7Fj07iVaBQ2; Tue, 12 Mar 2024 16:35:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=alien8; t=1710261323; bh=P6Nl44Mmk5e+Il2mmTMKgMSHn/Wtfj20yZkZYWVB8Gs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AZVdRiHXZef7l0OGlxlbI6SoxrveedSFzf03ZcUuRzJXZtM794XB2slSMvi0l3P4H myLYJheI1jT6lDWHIcabRHGOKvVTvzBvjJ8DnMe1EylB1iLVf/RBTN0lTf02U3lxpI bO0VcO4Z9oG0onMeephMq7Lre6CRv0U0m7hIYfByQjE/W6Uy6p9lt8COWXDLe58lID W+3ZDUnsRg+wlK98R/jv5Az6j4oGLrZL52kxhLgsqx5bwR1KLkrTyqggiTNe6VAidJ iK4suK3AuqGiGN0RZcksQrv5RXSU/xek9gq5Da+pIvftgpxN7pSusWpX4twi5vWcYu CA4OJZy+lCqDdRxTCExCBwNJ8uNED3R7LB6V/qIGzrkokuib/M4KnibwpZcOQJnSDk lJnVbDF2O+WBuJTEX1ulc09wCi1c8zfZ7uSr+vJixzzk3VDihLanhL9IlTUo9p+zr+ dY/ALOvvHLYBb/UQK8yAe4ZocdifI2dNnCa/BzRtzMeLtMNz+mSR1OvyuqD+T/hlrZ UsVcKVbHCQe6TYRx1+sfrAyIxSLpxI4qay6l1+z137D7IJ5bzu8u4Zs8xjNDhIwsBY Y5BMo/KPX0P4BqCxq6nG/UZIKf/5Fg8TOw9I9bCoAwPEtNMASwTnOlJFb6lBwhXFWc zEmyw1hYE3OtSnFXQ0QzFgJE= Received: from zn.tnic (pd953021b.dip0.t-ipconnect.de [217.83.2.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail.alien8.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 0F86240E016B; Tue, 12 Mar 2024 16:35:08 +0000 (UTC) Date: Tue, 12 Mar 2024 17:35:02 +0100 From: Borislav Petkov To: Yosry Ahmed Cc: Dave Hansen , x86@kernel.org, Thomas Gleixner , Ingo Molnar , Dave Hansen , "H. Peter Anvin" , Andy Lutomirski , Peter Zijlstra , "Kirill A. Shutemov" , Rick Edgecombe , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [PATCH v2 1/3] x86/mm: Use IPIs to synchronize LAM enablement Message-ID: <20240312163502.GGZfCENkvNb41IJWPy@fat_crate.local> References: <20240312155641.4003683-1-yosryahmed@google.com> <20240312161337.GFZfB_MdSFtAUXjeLU@fat_crate.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On Tue, Mar 12, 2024 at 09:23:48AM -0700, Yosry Ahmed wrote: > Sure, although I am kinda familiar with that. It would be useful to > point out what part(s) I may be violating :) Are you kidding? Dave just told you. Lemme paste the whole text for you: "Don't get discouraged - or impatient After you have submitted your change, be patient and wait. Reviewers are busy people and may not get to your patch right away. Once upon a time, patches used to disappear into the void without comment, but the development process works more smoothly than that now. You should receive comments within a few weeks (typically 2-3); if that does not happen, make sure that you have sent your patches to the right place. Wait for a minimum of one week before resubmitting or pinging reviewers - possibly longer during busy times like merge windows." https://kernel.org/doc/html/latest/process/submitting-patches.html > Right, I am aware of that part. According to the tip tree handbook I > shouldn't expect them to be handled during the merge window, but do > x86 folks prefer I hold off on sending them until after the merge > window? I believe I speak for all of tip folks when I say that they prefer not to be spammed with the same set too regularly. As to when you send: there's never a good moment because our mailboxes are constantly overflowing. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette