From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 7/7] libvchan: do not use xc_gntshr_share_page_notify in Mini-OS
Date: Mon, 29 Apr 2013 01:00:56 +0200 [thread overview]
Message-ID: <517DAA28.9090603@invisiblethingslab.com> (raw)
In-Reply-To: <20130428224842.GM4962@type.youpi.perso.aquilenet.fr>
[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]
On 29.04.2013 00:48, Samuel Thibault wrote:
> Marek Marczykowski, le Tue 23 Apr 2013 05:25:00 +0200, a écrit :
>> It isn't implemented there yet.
>
> Doesn't libvchan need it? It should probably be at least documented
> somewhere what does not work in the mini-os case, e.g. stubdom/README.
It can be simulated by manual event channel fire in libxenvchan_close, which I
should do. Will be in the next patch version.
IIUC there is no case in which (properly written) vchan server application
will terminate without ability to libxenvchan_close(), but mini-os will still
be alive and can notify the client.
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-28 23:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:45 [PATCH 0/7] Optionally add libvchan to stubdom Marek Marczykowski
2013-04-21 1:46 ` [PATCH 2/7] libvchan: create xenstore entries in one transaction Marek Marczykowski
2013-04-26 18:04 ` David Vrabel
2013-04-28 22:43 ` Marek Marczykowski
2013-04-22 1:44 ` [PATCH 1/7] minios: enhance xenstore available for stubdoms Marek Marczykowski
2013-04-28 22:34 ` Samuel Thibault
2013-04-22 1:50 ` [PATCH 3/7] libvchan: remove unnecessary includes Marek Marczykowski
2013-04-22 2:10 ` [PATCH 6/7] stubdom: make libvchan available in stubdom Marek Marczykowski
2013-04-28 22:46 ` Samuel Thibault
2013-04-23 3:16 ` [PATCH 4/7] minios: add gnttab_find_grant_of_page Marek Marczykowski
2013-04-28 22:41 ` Samuel Thibault
2013-04-28 22:51 ` Marek Marczykowski
2013-04-23 3:17 ` [PATCH 5/7] libxc: implement gntshr for minios Marek Marczykowski
2013-04-28 22:44 ` Samuel Thibault
2013-04-28 23:17 ` Marek Marczykowski
2013-04-28 23:22 ` Samuel Thibault
2013-04-23 3:25 ` [PATCH 7/7] libvchan: do not use xc_gntshr_share_page_notify in Mini-OS Marek Marczykowski
2013-04-28 22:48 ` Samuel Thibault
2013-04-28 23:00 ` Marek Marczykowski [this message]
2013-04-26 14:55 ` [PATCH 0/7] Optionally add libvchan to stubdom George Dunlap
2013-04-26 14:56 ` Marek Marczykowski
2013-04-26 14:57 ` George Dunlap
2013-04-26 15:02 ` Marek Marczykowski
2013-04-26 15:03 ` Ian Campbell
2013-04-26 16:41 ` Daniel De Graaf
2013-04-28 22:52 ` Samuel Thibault
2013-04-28 23:08 ` Marek Marczykowski
2013-04-30 21:22 ` Samuel Thibault
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=517DAA28.9090603@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.