Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp286577ybi; Mon, 15 Jul 2019 20:56:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqy9Fgy1duczUv2n3OkzZCmLBK8mSJW4T/iU6MwRpG5Q3KKS1ae+lRGJU90m+Ymyx8HsRdYr X-Received: by 2002:a17:90a:1ae1:: with SMTP id p88mr31998325pjp.26.1563249375922; Mon, 15 Jul 2019 20:56:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563249375; cv=none; d=google.com; s=arc-20160816; b=z0JxVksHkTwTHmwsHaxdCFG1mM2yc/he2dtNwU0wrL/DyqcdnXqY7SqwGbUZxcngDY x8MlQ6nurUOen7Fxi/eubC9Mx4vWQDZx9vfupw2GafuzYNTiJUy6NVRg909V7K2ibjeb 9398Xlw62wUejWn474QU3iVA64oU9VtchSC/SJtiCk1SAcycpgC3SGCip28eGSVEQ6sq FEWPlCk6jqkCJpjk9JELr6DzqSFk8HfcK6m8Qgrq38q80B2zoUHYBpkj9fvbvvegp+sk w1ayi1b9rByhjHA1zoKCm56dhVohm4C0bffdTPuW3OiB8MKGZ2uAu1J2DDCH6/by42Xv YQfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=57Dkdtg5rrp2c59xmrxa9YiFgeeTrHEnYg1slkMvlGA=; b=dlX+yqbTv9WITdI1IoROKJ0Jt6TnNsLVZYof1PVv+2E4PZeyTQ68b6wHygeQk/5M3l vbCNDP41iiDA+Z3gYYeNYJKL9mPYnW1+Nnt0Y+rZiKuWj0FFm2SyUvMSvnwM69O2a5pF 4xpzXyAEgHFG15TN6SOXijXTrtTab/ODFL29FXE4LLwLKppb6uFG1abm8z3NV2Nz9stZ LUPDKHnVXr3fMldCP6JqqThoHHm1RG+VpUKUq0NlAD7ESc4M2oyu9Oo0LMAUTi7rLqgr PTox428vpBZnzXkGVUj78lQ6BR68cVtohrC4NshEHh5dmn2mkbTkzcBE3IXGbg7068Is HmSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y3si17664884pjv.50.2019.07.15.20.55.59; Mon, 15 Jul 2019 20:56:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730972AbfGPDzW (ORCPT + 99 others); Mon, 15 Jul 2019 23:55:22 -0400 Received: from mx2.suse.de ([195.135.220.15]:49506 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730275AbfGPDzW (ORCPT ); Mon, 15 Jul 2019 23:55:22 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 3C1C7AB9D; Tue, 16 Jul 2019 03:55:21 +0000 (UTC) Subject: Re: [Xen-devel] [PATCH 0/2] Remove 32-bit Xen PV guest support To: Andrew Cooper , Andy Lutomirski , Andi Kleen Cc: Borislav Petkov , Stefano Stabellini , X86 ML , Thomas Gleixner , LinuxVirtualization , xen-devel , Boris Ostrovsky , Ingo Molnar , LKML , Alok Kataria , "H. Peter Anvin" References: <20190715113739.17694-1-jgross@suse.com> <87y30zfe9z.fsf@linux.intel.com> From: Juergen Gross Message-ID: Date: Tue, 16 Jul 2019 05:55:20 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15.07.19 19:39, Andrew Cooper wrote: > On 15/07/2019 18:28, Andy Lutomirski wrote: >> On Mon, Jul 15, 2019 at 9:34 AM Andi Kleen wrote: >>> Juergen Gross writes: >>> >>>> The long term plan has been to replace Xen PV guests by PVH. The first >>>> victim of that plan are now 32-bit PV guests, as those are used only >>>> rather seldom these days. Xen on x86 requires 64-bit support and with >>>> Grub2 now supporting PVH officially since version 2.04 there is no >>>> need to keep 32-bit PV guest support alive in the Linux kernel. >>>> Additionally Meltdown mitigation is not available in the kernel running >>>> as 32-bit PV guest, so dropping this mode makes sense from security >>>> point of view, too. >>> Normally we have a deprecation period for feature removals like this. >>> You would make the kernel print a warning for some releases, and when >>> no user complains you can then remove. If a user complains you can't. >>> >> As I understand it, the kernel rules do allow changes like this even >> if there's a complaint: this is a patch that removes what is >> effectively hardware support. If the maintenance cost exceeds the >> value, then removal is fair game. (Obviously we weight the value to >> preserving compatibility quite highly, but in this case, Xen dropped >> 32-bit hardware support a long time ago. If the Xen hypervisor says >> that 32-bit PV guest support is deprecated, it's deprecated.) >> >> That being said, a warning might not be a bad idea. What's the >> current status of this in upstream Xen? > > So personally, I'd prefer to see support stay, but at the end of the day > it is Juergen's choice as the maintainer of the code. Especially on the security front we are unsafe with 32-bit PV Linux. And making it safe will make it so slow that the needed effort is not spent very well. Juergen