>>> On 20.07.16 at 20:01, wrote:
> +static int range_share(struct domain *d, struct domain *cd,
> + struct mem_sharing_op_range *range)
> +{
> +int rc = 0;
> +shr_handle_t sh, ch;
> +unsigned long start = range->_scratchspace ?: range->start;
> +
> +while( ran
On 27/07/16 10:01, George Dunlap wrote:
> On 26/07/16 23:43, Andrew Cooper wrote:
>> On 26/07/2016 16:49, George Dunlap wrote:
>>> On Tue, Jul 26, 2016 at 4:22 PM, Tamas K Lengyel
>>> wrote:
On Tue, Jul 26, 2016 at 3:12 AM, George Dunlap
wrote:
> On Wed, Jul 20, 2016 at 7:01 PM, Ta
On 26/07/16 23:43, Andrew Cooper wrote:
> On 26/07/2016 16:49, George Dunlap wrote:
>> On Tue, Jul 26, 2016 at 4:22 PM, Tamas K Lengyel
>> wrote:
>>> On Tue, Jul 26, 2016 at 3:12 AM, George Dunlap
>>> wrote:
On Wed, Jul 20, 2016 at 7:01 PM, Tamas K Lengyel
wrote:
> Currently mem-s
On 26/07/2016 16:49, George Dunlap wrote:
> On Tue, Jul 26, 2016 at 4:22 PM, Tamas K Lengyel
> wrote:
>> On Tue, Jul 26, 2016 at 3:12 AM, George Dunlap
>> wrote:
>>> On Wed, Jul 20, 2016 at 7:01 PM, Tamas K Lengyel
>>> wrote:
Currently mem-sharing can be performed on a page-by-page basis f
On Tue, Jul 26, 2016 at 4:22 PM, Tamas K Lengyel
wrote:
> On Tue, Jul 26, 2016 at 3:12 AM, George Dunlap
> wrote:
>> On Wed, Jul 20, 2016 at 7:01 PM, Tamas K Lengyel
>> wrote:
>>> Currently mem-sharing can be performed on a page-by-page basis from the
>>> control
>>> domain. However, this proc
On Tue, Jul 26, 2016 at 3:12 AM, George Dunlap wrote:
> On Wed, Jul 20, 2016 at 7:01 PM, Tamas K Lengyel
> wrote:
>> Currently mem-sharing can be performed on a page-by-page basis from the
>> control
>> domain. However, this process is quite wasteful when a range of pages have to
>> be deduplica
On Wed, Jul 20, 2016 at 7:01 PM, Tamas K Lengyel
wrote:
> Currently mem-sharing can be performed on a page-by-page basis from the
> control
> domain. However, this process is quite wasteful when a range of pages have to
> be deduplicated.
>
> This patch introduces a new mem_sharing memop for rang
