On 24/06/16 15:25, Jan Beulich wrote:
>
> And then - what's your expectation? Any parts of this new
> interface can subsequently be marked stable if we so wish. I
> don't see why this needs to happen right away.
Ok.
David
___
Xen-devel mailing list
Xe
On 24/06/16 15:25, Jan Beulich wrote:
On 24.06.16 at 15:51, wrote:
>> On 24/06/16 14:37, Jan Beulich wrote:
>> On 24.06.16 at 15:27, wrote:
On 24/06/16 11:35, Jan Beulich wrote:
On 24.06.16 at 12:29, wrote:
>> On 24/06/16 11:21, Jan Beulich wrote:
>>> A long while
>>> On 24.06.16 at 15:51, wrote:
> On 24/06/16 14:37, Jan Beulich wrote:
> On 24.06.16 at 15:27, wrote:
>>> On 24/06/16 11:35, Jan Beulich wrote:
>>> On 24.06.16 at 12:29, wrote:
> On 24/06/16 11:21, Jan Beulich wrote:
>> A long while back separating out all control kind operatio
On 24/06/16 14:37, Jan Beulich wrote:
On 24.06.16 at 15:27, wrote:
>> On 24/06/16 11:35, Jan Beulich wrote:
>> On 24.06.16 at 12:29, wrote:
On 24/06/16 11:21, Jan Beulich wrote:
> A long while back separating out all control kind operations (intended
> for use by only the co
>>> On 24.06.16 at 15:27, wrote:
> On 24/06/16 11:35, Jan Beulich wrote:
> On 24.06.16 at 12:29, wrote:
>>> On 24/06/16 11:21, Jan Beulich wrote:
A long while back separating out all control kind operations (intended
for use by only the control domain or device model) from the curre
On 24/06/16 11:35, Jan Beulich wrote:
On 24.06.16 at 12:29, wrote:
>> On 24/06/16 11:21, Jan Beulich wrote:
>>> A long while back separating out all control kind operations (intended
>>> for use by only the control domain or device model) from the currect
>>> hvmop hypercall has been discusse
>>> On 24.06.16 at 12:29, wrote:
> On 24/06/16 11:21, Jan Beulich wrote:
>> A long while back separating out all control kind operations (intended
>> for use by only the control domain or device model) from the currect
>> hvmop hypercall has been discussed. This series aims at finally making
>> th
On 24/06/16 11:21, Jan Beulich wrote:
> A long while back separating out all control kind operations (intended
> for use by only the control domain or device model) from the currect
> hvmop hypercall has been discussed. This series aims at finally making
> this reality (at once allowing to streamli
A long while back separating out all control kind operations (intended
for use by only the control domain or device model) from the currect
hvmop hypercall has been discussed. This series aims at finally making
this reality (at once allowing to streamline the associated XSM checking).
01: public /
