From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751415AbbCSUIa (ORCPT ); Thu, 19 Mar 2015 16:08:30 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:34019 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751310AbbCSUIY (ORCPT ); Thu, 19 Mar 2015 16:08:24 -0400 Message-ID: <550B2CB1.4060901@redhat.com> Date: Thu, 19 Mar 2015 21:08:17 +0100 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Stefan Bader , kvm@vger.kernel.org, Linux Kernel Mailing List , Ben Hutchings Subject: Re: regression: nested: L1 3.15+ fails to load kvm-intel on L0 <3.10 References: <55093B52.5090904@canonical.com> <550942ED.4040809@redhat.com> <550B2A57.4090406@canonical.com> In-Reply-To: <550B2A57.4090406@canonical.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/03/2015 20:58, Stefan Bader wrote: > This was added in 3.10. So the range of kernels affected <3.10 back > to when nested vmx became somewhat usable. For 3.2 Ben (and > obviously us) would be affected. Apart from that, I believe, it is > only 3.4 which has an active longterm. At least that change looks > safer for stable as it sounds like correcting things and not adding > a feature. I was able to cherry-pick that into a 3.2 kernel and > then a 3.16 guest successfully can load the kvm-intel module again, > of course with the same shortcomings as before. Feel free to backport whatever you want to distro kernels. But I'm going to NACK for stable@ anything that is related to nested virt. The code has changed so much that I simply cannot do a meaningful review of most patches when applied to old codebases. Paolo