[Xen-devel] [PATCH v10] x86/altp2m: support for setting restrictions for an array of pages

[Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>]

On 03/13/2018 07:44 PM, Wei Liu wrote:
> On Wed, Dec 13, 2017 at 04:22:20PM +0200, Petre Pircalabu wrote:
> [...]
> Tabs here.
> 
> With this fixed, libxc bits:
> 
> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

We seem to have (again) arrived at an impasse with this patch.

To summarize, the original designers of altp2m have not replied anything
to repeated requests for comments, we've briefly discussed the issue at
the Xen Developer Summit last year, and it was concluded that, since we
do have a valid use case, we carry on with whatever design most fit with
the single-page setting xc_altp2m_set_mem_access() (which is a HVMOP).

Previously, Andrew has argued for the operation to be a HVMOP (in
keeping with the original design), while Jan has pointed out that since
this is only currently useful as a DOMCTL it would perhaps better be
implemented as one (which I personally also prefer, as it gets rid of
the very ugly compat code).

In the process of negotiating this, concerns have been voiced about the
possibility of restricting altp2m operations from either dom0 or the
guest. This is addressed, IMHO, by Tamas' patches:

https://patchwork.kernel.org/patch/9661873/

The situation is now this: Wei's obviously acked it; Jan agrees to let
it in, pending acks from Andrew or George.

We're happy to address any clear objections. But it would be a shame to
lose all this work we've all been doing for the better part of an year,
as I'm sure we all agree.

Please let us know how to proceed.


Thanks,
Razvan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel