Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752234AbdIHE0u (ORCPT ); Fri, 8 Sep 2017 00:26:50 -0400 Received: from mx2.suse.de ([195.135.220.15]:46900 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750937AbdIHE0t (ORCPT ); Fri, 8 Sep 2017 00:26:49 -0400 Subject: Re: [RFC 08/17] x86/asm/64: De-Xen-ify our NMI code To: Andy Lutomirski Cc: X86 ML , "linux-kernel@vger.kernel.org" , Borislav Petkov , Brian Gerst , Andrew Cooper , Boris Ostrovsky , Kees Cook References: From: Juergen Gross Message-ID: Date: Fri, 8 Sep 2017 06:26:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 656 Lines: 21 On 07/09/17 20:38, Andy Lutomirski wrote: > On Thu, Sep 7, 2017 at 2:34 AM, Juergen Gross wrote: >> On 06/09/17 23:36, Andy Lutomirski wrote: >>> Xen PV is fundamentally incompatible with our fancy NMI code: it >>> doesn't use IST at all, and Xen entries clobber two stack slots >>> below the hardware frame. >>> >>> Drop Xen PV support from our NMI code entirely. >>> >>> XXX: Juergen: could you write and test the tiny patch needed to >>> make Xen PV have a xen_nmi entry that handles NMIs? I don't know >>> how to test it. >> >> You mean something like the attached one? > > Yes. Mind if I add it to my series? Go ahead! Juergen