Received: by 10.192.165.156 with SMTP id m28csp933399imm; Mon, 16 Apr 2018 11:02:02 -0700 (PDT) X-Google-Smtp-Source: AIpwx48pg94fCaEvz0CAua5ijBVskLTb4ZwiYko/9k/FaKGAD8yvzyFGh0sOLRRiz7XuzoTRJev2 X-Received: by 2002:a17:902:988b:: with SMTP id s11-v6mr4509571plp.306.1523901722223; Mon, 16 Apr 2018 11:02:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523901722; cv=none; d=google.com; s=arc-20160816; b=SLeq2OiN7Tty/b/SI7YX7v42kbnauaQ2a6edIejel5OjLTGhsKOREeF+YnfekhgEiq QYcN1mRgKd6KLqJ+WkuA7AqcrH+BP8LXhTgEhYrBjFgmUzH1cYNc3y4vXnHpn96jv1FS GE7vxgi6/g7aI0Fx41WtUZlm4v2JsuQ7V6ceKYdcltH99ZjPfg9ZVuGqm81m9MiLk4QO FwewccFpN0XCQdb7BnUlKNtv3IKZn24MvNvSB0jUWb5vHG8/ojtoviKAH1gKeKXrB6Oo mSyzvpX+gi5Z3skeY88w9f7QlkHo0/FMhKC+dEmXRToV046+3gIyTc6vt/YiNUULX9gp craw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=UzT3jw/ok+v1sp6XmMSlHc5AObceOaK/CjiD+1oE7XQ=; b=0yHg62UPKI6Jo2G4gDA8gI2zhW3LZGCFP++bJX0eGDyjloKv8ZjCdb/SkGRIerTxgu xsq2Io7D3MEIyv5nOWb4WyFln8k3eAPbiD8UjMCY5EK9GrX08nP5tXk12Oy0aL2Ps4y7 cemNrIbGy2+33VqUfvTaB00Reo+UsqcxV8nZ5L6Q92ITUE2Qjk3ZGB42B95/2TgcC7Lj rXySDsXmLkOK+/Wuokz/+aCCe6KLWrY+8Beb8sUsBCx9rymGRWqe/2PbLulFkycUed97 1a0rPav+bCgkadGsqr4wja69QNhvNAFbOhT1wAsOmfTStSOqZDiRiPWyKqG5jtIrEXRu oQ3A== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64-v6si1506303plb.574.2018.04.16.11.01.42; Mon, 16 Apr 2018 11:02:02 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753337AbeDPR7w (ORCPT + 99 others); Mon, 16 Apr 2018 13:59:52 -0400 Received: from terminus.zytor.com ([198.137.202.136]:35147 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752308AbeDPR7v (ORCPT ); Mon, 16 Apr 2018 13:59:51 -0400 Received: from carbon-x1.hos.anvin.org (c-24-5-245-234.hsd1.ca.comcast.net [24.5.245.234] (may be forged)) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id w3GHvsOF603039 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 16 Apr 2018 10:57:55 -0700 Subject: Re: [PATCH 00/35 v5] PTI support for x32 To: Joerg Roedel , Thomas Gleixner , Ingo Molnar Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds , Andy Lutomirski , Dave Hansen , Josh Poimboeuf , Juergen Gross , Peter Zijlstra , Borislav Petkov , Jiri Kosina , Boris Ostrovsky , Brian Gerst , David Laight , Denys Vlasenko , Eduardo Valentin , Greg KH , Will Deacon , aliguori@amazon.com, daniel.gruss@iaik.tugraz.at, hughd@google.com, keescook@google.com, Andrea Arcangeli , Waiman Long , Pavel Machek , "David H . Gutteridge" , jroedel@suse.de References: <1523892323-14741-1-git-send-email-joro@8bytes.org> From: "H. Peter Anvin" Message-ID: Date: Mon, 16 Apr 2018 10:57:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1523892323-14741-1-git-send-email-joro@8bytes.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/16/18 08:24, Joerg Roedel wrote: > Hi, > > here is the 5th iteration of my PTI enablement patches for > x86-32. There are no real changes between v4 and v5 besides > that I rebased the whole patch-set to v4.17-rc1 and resolved > the numerous conflicts that this caused. > Please don't use the term "x32" for i386/x86-32. "x32" generally refers to the x32 ABI for x86-64. "x64" in Microsoft terminology for x86-64 corresponds to "x86" for x86-32. -hpa