Re: [PATCH RFC 9/9] mm: mark pages that have their permissions controlled by a domain

[Razvan Cojocaru <rcojocaru@bitdefender.com>]

On 07/03/2014 01:19 PM, Jan Beulich wrote:
>>>> On 02.07.14 at 15:34, <rcojocaru@bitdefender.com> wrote:
>> This goes together with the mem-event API changes and marks certain
>> pages as being controlled from outside the HV (a user domain in our
>> case). This prevents Xen from resetting the permissions in certain
>> cases, enforcing the previously expressed intention of receiving a
>> memory event everytime the owning domain triggers a fault.
> 
> These "certain cases" would clearly benefit from being named in a
> more precise fashion - it's not been that long ago that for some of
> the cases where the access permissions got reset as a side effect
> we decided to remove that side effect, and it was discussed to also
> be done for at least one more case. I.e. perhaps you would not
> need extensive changes like the ones here if that was done?

Could you please point us to these discussions? It would definitely be
very nice if the problem has been fixed in the meantime.

We're not entirely sure what the trigger for the resets was in our case.
We've so far ruled out live migration and ballooning, by disabling them
in the .conf files for the guests.

We hook into the guest fairly early, almost immediately after it starts
running, and occasionally (quite rarely, actually), we lost the
permissions set on some pages, apparently during the boot process (or
very shortly after).


Thanks,
Razvan Cojocaru