Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2042008imm; Thu, 23 Aug 2018 13:07:28 -0700 (PDT) X-Google-Smtp-Source: AA+uWPyQwiAreYBJI54dsDxvJIXTIqhIeMpxE/5utG+dqD5kcfbN3tjIgUxqXmHWcvZvc3NYDevh X-Received: by 2002:a65:4384:: with SMTP id m4-v6mr57120696pgp.265.1535054848069; Thu, 23 Aug 2018 13:07:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535054848; cv=none; d=google.com; s=arc-20160816; b=fAsR8jnLFswqChY2pScHhEmNvJ1ATRQfhIRsqd3708+vjsxt2JW2zPM4eOj2PJCBpN RJEseXSa9vmjv7lBnCIxoGgJUR8zIPdPE8IbY81XUVn4QSoPcjXtC+l/89td/3+AicHe 6YbM6n/4KqG60Ee6AZQdrNY+IX/4OBhZEkJwLxJ6kXEg4+v3ZidxhkTdZMVnhTgA/4nw 9hTxtD8FowmDj/txQZvIt5oYGu2CSnfxWoyoWz+ZZHm0i6yZk+MZhmg4ZjLjvE4YECj3 /GdBN/F9TfWP3qVs1if8gpkDoXOSIII7VgidvSEB5sgMMilX6V+khBqmEpCHOAqd/7Aq c58g== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=aeXpZ+m00ocDUfiNeDZ0T4J2ECp23t8w3+BTJsqyERI=; b=j0BhECKB36UwiwYoh7Xtzud11z4UwAv7QfR4SogDlBKiArmNIIKU/CwPyYRkfd6z6b EfLW7C9r7BYo4EYzeBNzwb1RPiKjFXIzfRe4omFjX0XKJVRZWjv8OEfrLOQMHMltsoFN t8OztMPbqkgXGllADlkHByvXa450iE+9mgEhTy6w23/TMLCbYwSVVhUIQ5q+XPlhf+/i +K/0l2h3wMVeEnjueYjCs8KV/OM1hA9f7RuSGRsEjfR7bv5Af2fbjPzI3aY5AMCYmGoa ++40iExaJk+kRBDln0ceCRZwdC6VaYJ46/jyWzrQsmipRZrA0PZnb0riZ9zfBFOW70UJ fWEA== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 136-v6si5557940pfc.187.2018.08.23.13.07.12; Thu, 23 Aug 2018 13:07:28 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727049AbeHWXgi (ORCPT + 99 others); Thu, 23 Aug 2018 19:36:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:35640 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726459AbeHWXgi (ORCPT ); Thu, 23 Aug 2018 19:36:38 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id A95C2AE10; Thu, 23 Aug 2018 20:05:21 +0000 (UTC) Date: Thu, 23 Aug 2018 22:05:20 +0200 From: Michal Hocko To: Andi Kleen Cc: Vlastimil Babka , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Dave Hansen , stable@vger.kernel.org Subject: Re: [PATCH] x86/speculation/l1tf: suggest what to do on systems with too much RAM Message-ID: <20180823200520.GW29735@dhcp22.suse.cz> References: <20180823134418.17008-1-vbabka@suse.cz> <20180823142812.7363-1-vbabka@suse.cz> <20180823154648.GD12066@tassilo.jf.intel.com> <20180823192547.GS29735@dhcp22.suse.cz> <20180823193833.GE12066@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180823193833.GE12066@tassilo.jf.intel.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 Thu 23-08-18 12:38:33, Andi Kleen wrote: > > There are people who care about L1TF mitigations. I am not going to > > question their motivation. In any case a hint how to make the mitigation > > active again sounds more useful than something that sounds as scary as > > "you are vulnerable". > > FWIW an early version of these patches automatically limited the available > memory, but Linus pointed out that people likely prefer their memory. Nobody is questioning that. The point is to give them a hint on how to make the mitigation active again without going to call for help. The message does tell them how to _enable_ it and point them to the documentation on how to _decide_. -- Michal Hocko SUSE Labs