From: Ian Jackson <iwj@xenproject.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Jan Beulich <jbeulich@suse.com>, <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony PERARD <anthony.perard@citrix.com>,
"Juergen Gross" <jgross@suse.com>,
Christian Lindig <christian.lindig@citrix.com>,
David Scott <dave@recoil.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH for-4.16 v6] gnttab: allow setting max version per-domain
Date: Mon, 8 Nov 2021 14:46:39 +0000 [thread overview]
Message-ID: <24969.14415.979563.323346@mariner.uk.xensource.com> (raw)
In-Reply-To: <YYPkx7148Ive/352@Air-de-Roger>
Roger Pau Monné writes ("Re: [PATCH for-4.16 v6] gnttab: allow setting max version per-domain"):
> Overall I think it's best to
> express supported grant versions independently, and we might wish to
> also allow to select a discrete set of grant versions that a domain
> supports. IMO it might be sensible in the future if a new grant
> version appears (v3), to select to expose grant v1 and v3 only to the
> domain, and avoid v2. This would require some changes here, but we can
> see about those when the time comes.
I'm not sure what layer we're talking about here. The patch
introduces a max version into the libxl api. Is there any significant
chance of a v3 (and hence, wanting to change the api) any time soon ?
Ian.
next prev parent reply other threads:[~2021-11-08 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 10:48 [PATCH for-4.16 v6] gnttab: allow setting max version per-domain Roger Pau Monne
2021-11-04 11:00 ` Christian Lindig
2021-11-04 12:05 ` Ian Jackson
2021-11-08 15:11 ` Ian Jackson
2021-11-04 12:09 ` Ian Jackson
2021-11-04 12:25 ` Jan Beulich
2021-11-04 13:48 ` Roger Pau Monné
2021-11-08 14:46 ` Ian Jackson [this message]
2021-11-08 14:54 ` Roger Pau Monné
2021-11-04 12:56 ` Andrew Cooper
2021-11-08 15:00 ` Ian Jackson
2021-11-08 15:07 ` Roger Pau Monné
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=24969.14415.979563.323346@mariner.uk.xensource.com \
--to=iwj@xenproject.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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;
as well as URLs for NNTP newsgroup(s).