From: David Vrabel <david.vrabel@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCHv1 0/2] xen/grant-table: fix PV guests and remove V2 support
Date: Fri, 4 Jul 2014 13:21:02 +0100 [thread overview]
Message-ID: <53B69C2E.2090903@citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD03CD12A@AMSPEX01CL01.citrite.net>
On 04/07/14 13:01, Paul Durrant wrote:
>> -----Original Message-----
>> From: David Vrabel
>> Sent: 04 July 2014 12:55
>> To: Paul Durrant; xen-devel@lists.xenproject.org
>> Cc: Boris Ostrovsky
>> Subject: Re: [Xen-devel] [PATCHv1 0/2] xen/grant-table: fix PV guests and
>> remove V2 support
>>
>> On 04/07/14 11:59, Paul Durrant wrote:
>>>> -----Original Message-----
>>>> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
>>>> bounces@lists.xen.org] On Behalf Of David Vrabel
>>>> Sent: 02 July 2014 11:25
>>>> To: xen-devel@lists.xenproject.org
>>>> Cc: Boris Ostrovsky; David Vrabel
>>>> Subject: [Xen-devel] [PATCHv1 0/2] xen/grant-table: fix PV guests and
>>>> remove V2 support
>>>>
>>>> The first patch fixes a logn standing issue where the map/unmap of
>>>> grant table frames by PV guests was unsafe and could BUG() or have
>>>> other bad behaviour. This was caused by calling function that were
>>>> not permitted from atomic contexts.
>>>>
>>>> The second patch removes all V2 table code since it is unused.
>>>>
>>>
>>> How confident are you of that assertion?
>>
>> This is removing the /Linux/ code which has been using V1 only for a
>> while now.
>>
>
> If you believe that the API is likely to wither then that seems
> reasonable. I would have thought the code was unlikely to see much
> change though and it seems a shame to remove an interface to something
> that it still there in Xen... I guess *someone* may want to use it in
> future; particularly the copy-only grants could be useful for something
> like IDC (if the backend was unprivileged).
It's already withering. For example PVH doesn't support V2 as it doesn't
handle mapping/populating the status frames. And fixing a long standing
bug (see patch 1/2) was made more complicated by having to fix up the
(unused) code for dealing with the status frames.
And as an aside, I'm not convinced that copy-only grants are what's
needed for IDC with untrusted backend. I think revocable grants are
required for efficient usage of shared rings.
David
next prev parent reply other threads:[~2014-07-04 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 10:25 [PATCHv1 0/2] xen/grant-table: fix PV guests and remove V2 support David Vrabel
2014-07-02 10:25 ` [PATCH 1/2] x86/xen: safely map and unmap grant frames when in atomic context David Vrabel
2014-07-11 16:28 ` Konrad Rzeszutek Wilk
2014-07-02 10:25 ` [PATCH 2/2] xen/grant-table: remove support for V2 tables David Vrabel
2014-07-08 17:10 ` Konrad Rzeszutek Wilk
2014-07-08 17:51 ` David Vrabel
2014-07-11 15:52 ` Boris Ostrovsky
2014-07-11 16:28 ` Konrad Rzeszutek Wilk
2014-07-04 10:59 ` [PATCHv1 0/2] xen/grant-table: fix PV guests and remove V2 support Paul Durrant
2014-07-04 11:55 ` David Vrabel
2014-07-04 12:01 ` Paul Durrant
2014-07-04 12:21 ` David Vrabel [this message]
2014-07-04 12:32 ` Paul Durrant
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=53B69C2E.2090903@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.