From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: Ian.Pratt@cl.cam.ac.uk, Steven.Hand@cl.cam.ac.uk,
Christian.Limpach@cl.cam.ac.uk, Keir.Fraser@cl.cam.ac.uk,
akpm@osdl.org
Subject: Xen VMM patch set - take 4
Date: Wed, 08 Dec 2004 07:28:16 +0000 [thread overview]
Message-ID: <E1CbwFE-0006PZ-00@mta1.cl.cam.ac.uk> (raw)
We've sync'ed up with the head of the Xen repository, and also brought
the patch up to 2.6.10-rc3
The patches are pretty much identical to the take 3 set, which people
seemed to be pretty happy with.
To get a working arch xen system you need the following set of
patches:
1. add ptep_establish_new to make va available
2. return code for arch_free_page
3. runtime disable of VT console
4. HAS_ARCH_DEV_MEM enables Xen to use own /dev/mem definition
5. split free_irq into teardown_irq
6. alloc_skb_from_cache (already accepted by Dave Miller)
The actual new architecture, arch xen, is too big to post to the list,
so here's a link:
http://www.cl.cam.ac.uk/netos/xen/downloads/arch-xen.patch
Likewise for the virtual block, network, and console drivers:
http://www.cl.cam.ac.uk/netos/xen/downloads/drivers-xen.patch
Arch xen will be maintained by myself, Keir Fraser, Christian Limpach
and Steve hand.
Cheers,
Ian
next reply other threads:[~2004-12-08 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 7:28 Ian Pratt [this message]
2004-12-08 7:29 ` [1/6] Xen VMM #4: add ptep_establish_new to make va available Ian Pratt
2004-12-08 10:42 ` Christoph Hellwig
2004-12-08 7:29 ` [2/6] Xen VMM #4: return code for arch_free_page Ian Pratt
2004-12-08 7:30 ` [3/6] Xen VMM #4: runtime disable of VT console Ian Pratt
2004-12-08 12:41 ` David Woodhouse
2004-12-08 7:30 ` [4/6] Xen VMM #4: HAS_ARCH_DEV_MEM Ian Pratt
2004-12-08 10:44 ` Christoph Hellwig
2004-12-08 7:31 ` [5/6] Xen VMM #4: split free_irq into teardown_irq Ian Pratt
2004-12-08 7:31 ` [6/6] Xen VMM #4: alloc_skb_from_cache 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=E1CbwFE-0006PZ-00@mta1.cl.cam.ac.uk \
--to=ian.pratt@cl.cam.ac.uk \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®