This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Memory Sharing

To: Lakshitha Harshan <harshan.dll@xxxxxxxxx>
Subject: Re: [Xen-devel] Memory Sharing
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Tue, 26 Jul 2011 10:51:48 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 26 Jul 2011 02:52:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAH-yA4TdWn6dFf=CSpXe16r5PW+otbqBph6_um_NWHGv4_LLDw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAH-yA4TdWn6dFf=CSpXe16r5PW+otbqBph6_um_NWHGv4_LLDw@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)

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 Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>