xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: MAYAP christine <christine.mayapkamga@enseeiht.fr>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Fwd: Fwd: [Xen-users] Shared memory between Dom0 and DomU
Date: Thu, 10 Mar 2011 11:03:25 +0100	[thread overview]
Message-ID: <4D78A1ED.8040403@enseeiht.fr> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1849 bytes --]

Hello,

I'm still reading document about inter-VM communication via shared memory.
I found many reference about IVC.
Is it already present in Xen? How can i use them?

I really need some explanations .
Thanks!



-------- Message original --------
Sujet: 	Fwd: [Xen-users] Shared memory between Dom0 and DomU
Date : 	Wed, 09 Mar 2011 15:12:06 +0100
De : 	MAYAP christine <christine.mayapkamga@enseeiht.fr>
Pour : 	xen-devel@lists.xensource.com, xen-users@lists.xensource.com



Hello

While waiting for some help, i continued to google about this topic.
In fact, i want two distinct process (one on the Dom0 and the second one 
on the DomU) to be able the read or write in a share memory.

Many post are talking about granting permissions or grant table.

I'm sorry if my question is a bit stupid. Where would i start to be able 
the test those grant permission?
Should i need to write an external program or should i modify some Xen 
source codes?

I really have no idea about where to start.
I'll sincerely appreciate any idea. Even one stating where to start.

Thanks in advance!

-------- Message original --------
Sujet: 	[Xen-users] Shared memory between Dom0 and DomU
Date : 	Wed, 09 Mar 2011 13:07:19 +0100
De : 	MAYAP christine <christine.mayapkamga@enseeiht.fr>
Pour : 	xen-devel@lists.xensource.com, xen-users@lists.xensource.com



HI,

I'm a newbie in using shared memory with Xen. I was usually unsing it
between process on a same Computer.

Please, can i have some usefull links abour sharing memoru betwen Dom0
and DomU first and between DomU.

I'm able to give more informations if needed!

Cheers!

-- 
MAYAP Christine
IRIT/ENSEEIHT
2 rue Charles Camichel - BP 7122
31071 Toulouse cedex  7


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


[-- Attachment #1.2: Type: text/html, Size: 4110 bytes --]

[-- Attachment #2: Portion de message jointe --]
[-- Type: text/plain, Size: 138 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

             reply	other threads:[~2011-03-10 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 10:03 MAYAP christine [this message]
2011-03-16  3:17 ` Fwd: Fwd: [Xen-users] Shared memory between Dom0 and DomU Konrad Rzeszutek Wilk
2011-03-16  7:58   ` Pasi Kärkkäinen
2011-03-16  8:03     ` Ian Campbell
2011-03-16 13:49       ` Konrad Rzeszutek Wilk

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=4D78A1ED.8040403@enseeiht.fr \
    --to=christine.mayapkamga@enseeiht.fr \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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).