From: "Dimitrie O. Paun" <dpaun@rogers.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: "Dimitrie O. Paun" <dpaun@rogers.com>, xen-devel@lists.sourceforge.net
Subject: Re: Xen and Linux
Date: Sat, 6 Nov 2004 00:15:36 -0500 [thread overview]
Message-ID: <20041106051536.GB10101@rogers.com> (raw)
In-Reply-To: <E1CQDVL-0003zp-00@mta1.cl.cam.ac.uk>
On Fri, Nov 05, 2004 at 11:28:25PM +0000, Ian Pratt wrote:
> It would be very cool ;-) We might even get distros to ship it on
> their install CD...
Exactly where I was going ... :)
> There's one simple src change in arch Xen that has some quite far
> reaching consequences: we change FIXADDR_TOP which effectively
> gives us a 64MB whole at the top of the guest's VM space where
> Xen lives. This constant gets compiled into a bunch of different
> functions (though I believe it doesn't make it into modules
> --phew!).
Oh. Is there any way that the kernel can reuse that space
if it figures that it's not running under Xen. I haven't
looked too closely at the kernel's memory management, but
I seem to remember the zone allocators...
> I suspect it would be unpopular to make FIXADDR_TOP a variable,
> and it turns out to be a tricky thing to runtime patch. I think
> we just have to have arch-xen specific versions of all of the
> functions that use it.
Yes, in which case we could maybe turn it *there* into a variable.
> The simplest way to do this would be to have a tool that builds
> an x86 and xen kernel then merges the two together. Sounds a bit
> gross, but I think it would work quite well.
Maybe, but it would be bigger, and this maybe a problem for small
devices. Anyhow, not very satisfying :)
> Probably the cleanest solution of all would be to make all the
> other architectures adopt Xen's nice clean interfaces and then
> have stub routines for talking to the grotty realty of real
> hardware. Might be a hard one to sell to Linus et al though ;-)
Yeah, I'd think this would be the preferable route. How large
would such a patch be?. It may be worth it to float it on LKML
to see the reaction :)
--
Dimi.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-06 5:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 20:54 Xen and Linux Dimitrie O. Paun
2004-11-05 23:28 ` Ian Pratt
2004-11-06 5:15 ` Dimitrie O. Paun [this message]
2004-11-07 15:25 ` Xen and Openbsd Dave Feustel
2004-11-07 20:11 ` Janne Johansson
2004-11-07 21:25 ` Dave Feustel
2004-11-07 21:55 ` Mark A. Williamson
2004-11-08 11:27 ` Janne Johansson
2004-11-08 11:45 ` Keir Fraser
2004-11-08 13:12 ` Dave Feustel
2004-11-08 13:39 ` Keir Fraser
2004-11-08 13:43 ` Dave Feustel
2004-11-08 14:22 ` Mark A. Williamson
2004-11-07 21:55 ` Keir Fraser
2004-11-08 14:34 ` Xen and Linux Ronald G. Minnich
2004-11-09 3:44 ` David Hopwood
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=20041106051536.GB10101@rogers.com \
--to=dpaun@rogers.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--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.