From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: sepanta s <sapanta992@gmail.com>,
"xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>,
Tamas K Lengyel <tamas.lengyel@zentific.com>
Subject: Re: An issue in sharing the pages again in xen-memshare
Date: Mon, 23 Jul 2018 10:22:23 +0300 [thread overview]
Message-ID: <b1a73c07-3e50-38ad-7ef5-851df86bac7b@bitdefender.com> (raw)
In-Reply-To: <CABaiLQ959qf8fDZSV5-G1utG3mZUB2WMmw+HaMjfXC0PXtkzhw@mail.gmail.com>
On 07/23/2018 05:37 AM, sepanta s wrote:
> I have written a program that can share memory pages of two VMs every x
> milliseconds. To do so, I modified xen and added an unshare event to be
> able to capture it. However, for some pages, when I receive the unshare
> event that contains the information about the pages which was about to
> be written on and put it on a buffer for sharing them again after x
> milliseconds, I cannot nominate them again and an error occurs. So, the
> sharing mechanism I have built can partially share pages. I guess the
> problem might be because of internal structure of sharing mechanism in
> the Xen but can't figure out the problem.
> Do you have any idea what can cause this problem? Or what should I
> check to get closer to any solution?
I've never used this feature, but Tamas might have some insight into
this (added to Cc).
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-23 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 2:37 An issue in sharing the pages again in xen-memshare sepanta s
2018-07-23 7:22 ` Razvan Cojocaru [this message]
2018-07-28 6:43 ` sepanta s
2018-08-24 5:07 ` sepanta s
2018-08-24 9:49 ` Razvan Cojocaru
[not found] ` <CABaiLQ-y7JjRiNz2+kBVfmkcSFbevRgZCpuHo=pWY9B77OV4pA@mail.gmail.com>
[not found] ` <ef7f95fe-bbc0-bdd9-d9ae-f0324d6e87b0@bitdefender.com>
[not found] ` <CABaiLQ9D-g4WziFbE-3kecLae539qvAeMW2u7kz1hDo0u7YNbA@mail.gmail.com>
[not found] ` <CABaiLQ-hkSzjFRv-SRh=Tt6z01ynFT-RKWPGtuSDFPHghtFFWg@mail.gmail.com>
[not found] ` <990b64a3-d797-09d1-6f91-2c87bb799223@bitdefender.com>
[not found] ` <CABaiLQ8SO7iXA6wMMbCaXEUZNC8rr=f8EkomWCXzQ+b1-qXDWw@mail.gmail.com>
[not found] ` <CABaiLQ9B00dsmSbCs28-2SRoZHudkQTjMbfdZ4Eha-WRVONu1Q@mail.gmail.com>
2018-10-06 14:24 ` Tamas Lengyel
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=b1a73c07-3e50-38ad-7ef5-851df86bac7b@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=Xen-devel@lists.xen.org \
--cc=sapanta992@gmail.com \
--cc=tamas.lengyel@zentific.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.