From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Katz <katzj@redhat.com>,
Xen Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: Proposal for init/kexec/hotplug format for Xen
Date: Sun, 27 Feb 2005 11:59:08 -0600 [thread overview]
Message-ID: <42220A6C.5040903@us.ibm.com> (raw)
In-Reply-To: <1ad6b47f0eb08a9a0218b83fb5f43865@cl.cam.ac.uk>
Keir Fraser wrote:
> A reasonable interface to user-space, but what about when one endpoint
> is inside the kernel? I'm also concerned that SysV IPC is usually used
> between mutually trusting parties -- this is *not* necessarily the
> case between management services and managed domains. We need e.g.,
> control over event-channel masking to be able to limit management
> resources consumed by overzealous or malicious guests.
I'm not suggesting we use the SysV interfaces, just the mechanisms
(named shared memory, message queues, semaphores). As primatives, this
seems like a good place to start. As interfaces, I agree that SysV is
not the way to go :-)
The persistent store protocol could be implemented on top of these
mechanisms. Any primatives would also have to be shared between kernel
and userspace (either through common header files or perhaps a kernel
interface to userspace for these mechanisms).
It's really just about generalizing what's already being used.
Regards,
Anthony Liguori
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-27 17:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 20:57 Proposal for init/kexec/hotplug format for Xen Rusty Russell
2005-02-27 10:53 ` Keir Fraser
2005-02-27 11:46 ` Rusty Russell
2005-02-27 15:25 ` Anthony Liguori
2005-02-27 15:48 ` Keir Fraser
2005-02-27 15:54 ` Anthony Liguori
2005-02-27 16:09 ` Keir Fraser
2005-02-27 16:16 ` Anthony Liguori
2005-02-27 16:31 ` Harry Butterworth
2005-02-27 16:42 ` Anthony Liguori
2005-02-27 17:32 ` Keir Fraser
2005-02-27 17:59 ` Anthony Liguori [this message]
2005-02-27 18:12 ` Harry Butterworth
2005-02-27 18:24 ` Anthony Liguori
2005-02-27 18:55 ` Harry Butterworth
2005-02-27 18:57 ` Keir Fraser
2005-02-27 19:10 ` Anthony Liguori
2005-02-27 21:49 ` Keir Fraser
2005-02-27 22:39 ` Anthony Liguori
2005-02-27 23:29 ` Harry Butterworth
2005-02-28 8:59 ` Keir Fraser
2005-02-27 19:38 ` Harry Butterworth
2005-02-27 16:05 ` Harry Butterworth
2005-02-28 12:06 ` Rusty Russell
2005-02-28 15:46 ` Anthony Liguori
2005-02-28 20:28 ` Jeremy Katz
2005-02-28 22:24 ` Harry Butterworth
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 13:08 Re: " harry
2005-02-28 13:32 ` Rusty Russell
2005-02-28 13:40 ` Harry Butterworth
2005-02-28 14:33 ` Keir Fraser
2005-02-28 16:46 ` Re: " Rusty Russell
2005-03-01 13:15 ` Harry Butterworth
2005-03-01 15:08 ` 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=42220A6C.5040903@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=katzj@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.sourceforge.net \
/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.