From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: Xen-devel@lists.sourceforge.net
Subject: Re: Fw: Xen on /. again
Date: Thu, 20 Jan 2005 15:30:32 -0800 [thread overview]
Message-ID: <41F03F18.4060204@diku.dk> (raw)
In-Reply-To: <200501202241.06631.maw48@cl.cam.ac.uk>
Mark Williamson wrote:
> Well domains are not aware of each other's memory usage, so I wouldn't have
> thought that allocation / exposing real page tables would matter. (Except
> dom0 can of course see everything if it wants).
Microkernel people like to make the argument that you could create a
low-bandwidth covert channel by systematically allocating and freeing a
set of pages, and because domains see real page frame numbers they can
learn the state of the other guy by looking at what pages they get in
return from an alloc call. I suppose you could randomize the
page-allocator, but then you will have to leave a certain amount of
pages unused at all times, to have enough random pages to choose from.
(For myself, I would much rather have the real page tables and find a
way to live with the covert channels, but I am not building
military-grade systems).
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-20 23:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 19:57 Fw: Xen on /. again Trent Jaeger
2005-01-20 22:11 ` Jacob Gorm Hansen
2005-01-20 22:41 ` Mark Williamson
2005-01-20 23:30 ` Jacob Gorm Hansen [this message]
2005-01-21 0:14 ` Mark Williamson
2005-01-21 0:48 ` David Hopwood
2005-01-21 0:55 ` Mark Williamson
2005-01-21 1:32 ` David Hopwood
2005-01-21 1:38 ` Mark Williamson
2005-01-21 1:09 ` Reiner Sailer
2005-01-21 7:53 ` Steven Hand
2005-01-21 8:08 ` Steven Hand
2005-01-21 2:35 ` Jody Belka
2005-01-21 11:06 ` Mark A. Williamson
2005-01-21 11:22 ` Mark A. Williamson
2005-01-21 23:37 ` Jody Belka
2005-01-22 17:20 ` Mark Williamson
2005-01-22 18:16 ` Jody Belka
2005-01-23 17:52 ` Multiple netif device channels (was Fw: Xen on /. again) Mark Williamson
2005-01-25 0:32 ` Jody Belka
2005-01-25 13:52 ` Mark Williamson
2005-01-25 23:06 ` Multiple netif device channels Jody Belka
2005-01-26 20:36 ` Mark Williamson
2005-01-27 0:51 ` Jody Belka
2005-01-27 14:00 ` Jody Belka
2005-01-21 0:19 ` Fw: Xen on /. again Trent Jaeger
-- strict thread matches above, loose matches on Subject: below --
2005-01-21 1:25 Ian Pratt
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=41F03F18.4060204@diku.dk \
--to=jacobg@diku.dk \
--cc=Xen-devel@lists.sourceforge.net \
--cc=maw48@cl.cam.ac.uk \
/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.