Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751752AbdILPua (ORCPT ); Tue, 12 Sep 2017 11:50:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:45094 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750999AbdILPu3 (ORCPT ); Tue, 12 Sep 2017 11:50:29 -0400 Subject: Re: [PATCH 2/4] xen: limit grant v2 interface to the v1 functionality To: Boris Ostrovsky , linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org References: <20170908144849.2958-1-jgross@suse.com> <20170908144849.2958-3-jgross@suse.com> From: Juergen Gross Message-ID: <8c87dc06-bbc8-5279-d135-d3351032913d@suse.com> Date: Tue, 12 Sep 2017 17:50:27 +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=windows-1252 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: 745 Lines: 20 On 12/09/17 17:44, Boris Ostrovsky wrote: > On 09/08/2017 10:48 AM, Juergen Gross wrote: >> As there is currently no user for sub-page grants or transient grants >> remove that functionality. This at once makes it possible to switch >> from grant v2 to grant v1 without restrictions, as there is no loss of >> functionality other than the limited frame number width related to >> the switch. > > But isn't that ABI violation? v2 is expected to support this (XSAs > notwithstanding) No, I don't think so. The hypervisor still supports it, but the domU (or dom0) isn't required to make use of all the features IMHO. Or are you aware of any backend querying the grant version of a frontend and acting in another way if v2 is detected? Juergen