From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/4] xen: limit grant v2 interface to the v1 functionality
Date: Tue, 12 Sep 2017 12:21:30 -0400 [thread overview]
Message-ID: <46a17191-916a-e039-7e2f-a197e6783fe4@oracle.com> (raw)
In-Reply-To: <7dd99241-f771-9fa2-8a6a-ce019dbe08b6@suse.com>
On 09/12/2017 12:09 PM, Juergen Gross wrote:
> On 12/09/17 18:05, Boris Ostrovsky wrote:
>> On 09/12/2017 11:50 AM, Juergen Gross wrote:
>>> 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?
>> I am not aware of any but that doesn't mean that they don't (or won't)
>> exist.
> But isn't the frontend the one which is defining what is granted in
> which way? How should there be an ABI breakage when the frontend just
> isn't using sub-page or transitive grants?
People may provide both front and backend drivers and frontends, knowing
that v2 is available, could decide to use those features.
-boris
next prev parent reply other threads:[~2017-09-12 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:48 [PATCH 0/4] xen: grant table interface v2 support Juergen Gross
2017-09-08 14:48 ` [PATCH 1/4] xen: re-introduce support for grant v2 interface Juergen Gross
2017-09-12 15:41 ` [Xen-devel] " Boris Ostrovsky
2017-09-12 15:45 ` Juergen Gross
2017-09-08 14:48 ` [PATCH 2/4] xen: limit grant v2 interface to the v1 functionality Juergen Gross
2017-09-12 15:44 ` Boris Ostrovsky
2017-09-12 15:50 ` Juergen Gross
2017-09-12 16:05 ` Boris Ostrovsky
2017-09-12 16:09 ` Juergen Gross
2017-09-12 16:21 ` Boris Ostrovsky [this message]
2017-09-12 18:18 ` Juergen Gross
2017-09-13 13:22 ` Boris Ostrovsky
2017-09-13 13:38 ` Juergen Gross
2017-09-13 13:50 ` Boris Ostrovsky
2017-09-13 14:45 ` Juergen Gross
2017-09-13 16:20 ` Boris Ostrovsky
2017-09-14 8:13 ` Juergen Gross
2017-09-08 14:48 ` [PATCH 3/4] xen: add grant interface version dependent constants to gnttab_ops Juergen Gross
2017-09-12 16:02 ` Boris Ostrovsky
2017-09-08 14:48 ` [PATCH 4/4] xen: select grant interface version Juergen Gross
2017-09-12 16:21 ` [Xen-devel] " Boris Ostrovsky
2017-09-12 18:54 ` Andrew Cooper
2017-09-13 9:23 ` Juergen Gross
2017-09-15 13:00 ` Juergen Gross
2017-09-15 13:21 ` Jan Beulich
[not found] ` <59BBEFFC020000780017B8EF@suse.com>
2017-09-15 13:27 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a17191-916a-e039-7e2f-a197e6783fe4@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome