From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 26 Jul 2018 10:05:07 -0000 Received: from mail.linuxfoundation.org ([140.211.169.12]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fid8r-0004HV-Uh for speck@linutronix.de; Thu, 26 Jul 2018 12:05:06 +0200 Date: Thu, 26 Jul 2018 12:04:53 +0200 From: Greg KH Subject: [MODERATED] Re: [PATCH v2 0/4] L1TF KVM ARCH_CAPABILITIES #0 Message-ID: <20180726100453.GD7872@kroah.com> References: <20180725143100.16309-1-pbonzini@redhat.com> <20180725155216.GC14692@kroah.com> 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 Thu, Jul 26, 2018 at 10:12:58AM +0200, speck for Paolo Bonzini wrote: > On 25/07/2018 17:52, speck for Greg KH wrote: > > On Wed, Jul 25, 2018 at 04:30:56PM +0200, speck for Paolo Bonzini wrote: > >> Support for ARCH_CAPABILITIES bit 3, which can already be used to disable > >> the mitigations on a nested hypervisor. Patch 1 is already in Linus's > >> tree. > > Should I be taking patch 1 into a stable tree now, or wait until the > > rest of these land? > > Yes, you can do that if you prefer. It's commit > cd28325249a1ca0d771557ce823e0308ad629f98. It seems only applicable to 4.17.y, older kernels (like 4.14 and 4.9) don't seem to need it, right? Or will they be needed for this "mess"? thanks, greg k-h