Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3549871imu; Mon, 14 Jan 2019 05:07:46 -0800 (PST) X-Google-Smtp-Source: ALg8bN5gDlcMKIB8/DGlv9Guiw5d44Yc1MfDRwVXDj/q5CRa5DDxzIkfD6tOZTJdEwB84wb0ofp8 X-Received: by 2002:a62:99dd:: with SMTP id t90mr25042176pfk.179.1547471266591; Mon, 14 Jan 2019 05:07:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547471266; cv=none; d=google.com; s=arc-20160816; b=Tdk/mG1KBddmbmI/pndDAxIEGuBMIomiyrOBo+KJw5Hvzs0+IvlZvJvZGhb67OnYQZ OVUc8ebpGl7UJIR+h4LBSxYNBGs2+XBBKQngxqg0sstuo0EznOfWmVY093EX0kEFAdh0 rSTMqR/aubZjyClzUvlE0mLoMOlapTmcnDdb3zW0eUhV6lhorY5RqtW+M8CpVJG0Pv1Y ac6P6d66wnh4l7sV2YGtIV87zZtw0SwDzDpwiauALxAh7u2znBmzzhlCmD9ON2HpSQmL ZFz+jLIa/EJyfEtDfN2S1qUMxJe7gF+6fCO//r/OCN8rKwbcQi/xsGBpf980sY8TC2T8 ktCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=d/MayZnYEj9j71Q6em5cwLufviUht8SjEnula+fQB/E=; b=Tn+bvNon27y6+AxVmcqFGP1JUD57SoRrYgliilKpIF6K+NoLjSWRrG60pndkNusvn2 PFz8SMRaaDqvfTiQ5JpfgtlS8cfwByCZEUyobECSK/KIQFZNhOQCRJ1fuTPCuBw8zgQy ajlkmo5mn7QoJ6yD7Mpo51+A2H7K+mQKhUF0SmM2nnymsNKnAqb0MRvMhrjHwgKKX9tS MxmILoX8WaVzQBtokPJd1gr3apUQai7D9hr95miPCrdgYwomZSsGr/WV4UYigC9jLMAn r5fQdwBxUesw/Lo+4S/uKSdkYxNqr2eloAUi71FBiUHQtsdupvijO+K0R5YavNfxVbM5 qVng== 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 m65si310103pfg.282.2019.01.14.05.07.31; Mon, 14 Jan 2019 05:07:46 -0800 (PST) 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 S1726554AbfANNGW (ORCPT + 99 others); Mon, 14 Jan 2019 08:06:22 -0500 Received: from mx2.suse.de ([195.135.220.15]:38958 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726449AbfANNGW (ORCPT ); Mon, 14 Jan 2019 08:06:22 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 899DFAD6B; Mon, 14 Jan 2019 13:06:20 +0000 (UTC) Date: Mon, 14 Jan 2019 14:06:19 +0100 (CET) From: Jiri Kosina To: Pavel Machek cc: Tim Chen , Jonathan Corbet , Thomas Gleixner , Linus Torvalds , Tom Lendacky , Ingo Molnar , Peter Zijlstra , Josh Poimboeuf , Andrea Arcangeli , David Woodhouse , Andi Kleen , Dave Hansen , Asit Mallick , Arjan van de Ven , Jon Masters , Waiman Long , Greg KH , Borislav Petkov , linux-kernel@vger.kernel.org, x86@kernel.org, stable@vger.kernel.org Subject: Re: [PATCH] x86/speculation: Add document to describe Spectre and its mitigations In-Reply-To: <20190114130153.GC21544@amd> Message-ID: References: <64efec3fda40c0758601bf9b1480a35d76d3c487.1545413988.git.tim.c.chen@linux.intel.com> <20181228103437.4c03c181@lwn.net> <20190113231001.GB18710@amd> <20190114120157.GB21544@amd> <20190114130153.GC21544@amd> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Jan 2019, Pavel Machek wrote: > Frankly I'd not call it Meltdown, as it works only on data in the cache, > so the defense is completely different. Seems more like a l1tf > :-). Meltdown on x86 also seems to work only for data in L1D, but the pipeline could be constructed in a way that data are actually fetched into L1D before speculation gives up, which is not the case on ppc (speculation aborts on L2->L1 propagation IIRC). That's why flushing L1D on ppc is sufficient, but on x86 it's not. -- Jiri Kosina SUSE Labs