From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brijesh Singh Subject: Re: [RFC PATCH v2 00/32] x86: Secure Encrypted Virtualization (AMD) Date: Fri, 3 Mar 2017 15:15:30 -0600 Message-ID: References: <148846752022.2349.13667498174822419498.stgit@brijesh-build-machine> <20170303203323.GA5305@bhelgaas-glaptop.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Return-path: In-Reply-To: <20170303203323.GA5305@bhelgaas-glaptop.roam.corp.google.com> Sender: owner-linux-mm@kvack.org List-Id: linux-crypto.vger.kernel.org Hi Bjorn, On 03/03/2017 02:33 PM, Bjorn Helgaas wrote: > On Thu, Mar 02, 2017 at 10:12:01AM -0500, Brijesh Singh wrote: >> This RFC series provides support for AMD's new Secure Encrypted Virtualization >> (SEV) feature. This RFC is build upon Secure Memory Encryption (SME) RFCv4 [1]. > > What kernel version is this series based on? > This patch series is based off of the master branch of tip. Commit a27cb9e1b2b4 ("Merge branch 'WIP.sched/core'") Tom's RFC v4 patches (http://marc.info/?l=linux-mm&m=148725973013686&w=2) Accidentally, I ended up rebasing SEV RFCv2 patches from updated SME v4 instead of original SME v4. So you may need to apply patch [1] [1] http://marc.info/?l=linux-mm&m=148857523132253&w=2 Optionally, I have posted the full git tree here [2] [2] https://github.com/codomania/tip/branches -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org