From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brijesh Singh Subject: Re: [Part2 PATCH v4 02/29] x86/CPU/AMD: Add the Secure Encrypted Virtualization CPU feature Date: Fri, 29 Sep 2017 17:44:24 -0500 Message-ID: References: <20170919204627.3875-1-brijesh.singh@amd.com> <20170919204627.3875-3-brijesh.singh@amd.com> <20170929121900.3wc5axlkanfggpdr@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: brijesh.singh@amd.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Tom Lendacky , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , x86@kernel.org To: Borislav Petkov Return-path: In-Reply-To: <20170929121900.3wc5axlkanfggpdr@pd.tnic> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 09/29/2017 07:19 AM, Borislav Petkov wrote: ... > > This one was in the Part1 set, right? It landed here for whatever > reason... > Part1 is based on tip/master and Part2 is based on kvm/master. With the current division, we should be able to compile and run part1 and part2 independently. This patch defines X86_FEATURE_SEV which is currently been used by svm.c hence I kept the patch in Part2. If we move it in Part1 then Part2 build will fail -- I am okay with including it as a pre-cursor to Part2 series. Is this something acceptable? -Brijesh