Xen devel - Jul 2011 - Memory Sharing

Hi,

I''m doing a research project related to memory sharing. In my project
I''m
trying to share the memory pages in kernel code segments. These kernels are
identical.
I have carried out some experiments to analyze these memory pages. Results
concluded that no modifications occurs on these memory pages at runtime.

But after sharing these pages using nominate and share functions, 5 memory
pages calls unshare() operation just after sharing the code pages.

So my question is, if no modifications occurs at runtime, how could be
possible to call "unshare()"?

Thanks,

Harshan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi, 

At 13:03 +0530 on 26 Jul (1311685428), Lakshitha Harshan
wrote:
> I''m doing a research project related to memory sharing. In my
project I''m
> trying to share the memory pages in kernel code segments. These kernels are
> identical.
> I have carried out some experiments to analyze these memory pages. Results
> concluded that no modifications occurs on these memory pages at runtime.
> 
> But after sharing these pages using nominate and share functions, 5 memory
> pages calls unshare() operation just after sharing the code pages.
> 
> So my question is, if no modifications occurs at runtime, how could be
> possible to call "unshare()"?
Have you tried tracing the callers of the function to find out what they
are?  The WARN() macro is handy for that - it prints a complete
backtrace of the hypervisor call chain. 

Tim.

-- 
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel