From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 29 Oct 2019 15:42:55 -0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iPTe2-0002F3-6v for speck@linutronix.de; Tue, 29 Oct 2019 16:42:54 +0100 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 876EBB412 for ; Tue, 29 Oct 2019 15:42:46 +0000 (UTC) Date: Tue, 29 Oct 2019 16:42:45 +0100 From: Joerg Roedel Subject: [MODERATED] Re: ***UNCHECKED*** Re: Re: Re: Re: [PATCH v7 0/5] NX 0 Message-ID: <20191029154245.GL838@suse.de> References: <1571902455-22638-1-git-send-email-pbonzini@redhat.com> <20191028160203.GB838@suse.de> <20191029093900.GF838@suse.de> <20191029123157.GG838@suse.de> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Tue, Oct 29, 2019 at 04:35:56PM +0100, speck for Thomas Gleixner wrote: > So the fix is independent of the NX pile, right? But OTOH, for testing the > NX stuff with all the various knobs and options the patch is needed I > assume. The fix is independent in a sense that its pure existence doesn't reveal anything under the embargo, but the issue that is fixed by it only happens with the NX pile applied. So yes, it is needed to test the NX patches with EPT disabled (or NPT disabled on AMD). Joerg