From: Jui-Hao Chiang <juihaochiang@gmail.com>
To: Lakshitha Harshan <harshan.dll@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Memory Sharing
Date: Sun, 19 Jun 2011 19:34:59 -0400 [thread overview]
Message-ID: <BANLkTikCRN1cnwMYRb=jYjzmq5_e__OSMg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin7Oef+ByF1but4HaQGWm0EZhN6+g@mail.gmail.com>
Hi, Harshan;
The share() in mem_sharing.c doesn't check if the content two pages
(handles) are the same. The function simply drop the 2nd one (client
handle), and that's why you got all VMs crash except the domU which is
used for getting the handles (shandles).
You have to use memcmp or some other way in share() function to make
sure they are actually the same.
Bests,
Jui-Hao
On Thu, Jun 16, 2011 at 10:15 AM, Lakshitha Harshan
<harshan.dll@gmail.com> wrote:
> Hi,er
>
> I am playing with memory sharing functions (nominate & share), for my
> research project. In my project, i get the GFNs of starting & ending
> pages of kernel code segment using xc_translate_foreign_address and
> then using a loop i nominate the memory pages of kernel code segment &
> share them.
>
> Both nominate & share() functions returns 0, on most sharing requests
> (almost 99%).
> My problem is that after sharing the memory, all of the other domUs
> except the domU which is used for getting the handles (shandles) for
> sharing memory pages are frozen, if i start one VM after another and
> try to share code pages after VMs have logged in. If i try to run the
> same procedure on already started set of guest domains, the VMs will
> be restarted (except the shandle domU).
>
> So what could be the reason for this?
> I'm using Xen -4.1.1-rc3-pre.
>
> Thanks,
> Harshan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2011-06-19 23:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 14:15 Memory Sharing Lakshitha Harshan
2011-06-19 23:34 ` Jui-Hao Chiang [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-18 16:19 memory sharing sepanta s
2016-02-04 21:04 Memory Sharing hanji unit
2016-02-05 0:29 ` Tamas K Lengyel
2016-02-05 10:40 ` David Vrabel
2011-07-26 7:33 Lakshitha Harshan
2011-07-26 9:51 ` Tim Deegan
2011-06-14 5:04 Lakshitha Harshan
2011-06-14 8:10 ` Tim Deegan
2011-06-01 3:45 Lakshitha Harshan
2011-06-01 9:46 ` Tim Deegan
2011-05-24 7:17 Lakshitha Harshan
2011-05-24 9:19 ` Tim Deegan
2011-05-03 4:49 Lakshitha Harshan
2011-05-03 12:05 ` Tim Deegan
2011-04-26 9:52 Lakshitha Harshan
2011-04-09 6:37 Lakshitha Harshan
2011-04-09 8:36 ` Keir Fraser
2011-04-03 8:28 Memory sharing Lakshitha Harshan
2011-04-03 8:58 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTikCRN1cnwMYRb=jYjzmq5_e__OSMg@mail.gmail.com' \
--to=juihaochiang@gmail.com \
--cc=harshan.dll@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).