From: stefano.stabellini@eu.citrix.com (Stefano Stabellini)
To: linux-arm-kernel@lists.infradead.org
Subject: [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions
Date: Wed, 30 Nov 2011 11:39:11 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1111301053300.31179@kaball-desktop> (raw)
In-Reply-To: <201111292129.20444.arnd@arndb.de>
On Tue, 29 Nov 2011, Arnd Bergmann wrote:
> On Tuesday 29 November 2011, Stefano Stabellini wrote:
> > Hi all,
> > a few weeks ago I (and a few others) started hacking on a
> > proof-of-concept hypervisor port to Cortex-A15 which uses and requires
> > ARMv7 virtualization extensions. The intention of this work was to find
> > out how to best support ARM v7+ on Xen. See
> > http://old-list-archives.xen.org/archives/html/xen-arm/2011-09/msg00013.html
> > for more details.
> >
> > I am pleased to announce that significant progress has been made, and
> > that we now have a nascent Xen port for Cortex-A15. The port is based on
> > xen-unstable (HG CS 8d6edc3d26d2) and written from scratch exploiting
> > the latest virtualization, LPAE, GIC and generic timer support in
> > hardware.
>
> Very nice!
>
> Do you have a pointer to the kernel sources for the Linux guest?
We have very few changes to the Linux kernel at the moment (only 3
commits!), just enough to be able to issue hypercalls and start a PV
console.
A git branch is available here (not ready for submission):
git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git arm
the branch above is based on git://linux-arm.org/linux-2.6.git arm-lpae,
even though guests don't really need lpae support to run on Xen.
> Since Xen and KVM are both in an early working state right now,
> it would be very nice if we could agree on the guest model to make
> sure that it's always possible to run the same kernel in both
> (and potentially other future) hypervisors without modifications.
Yes, that would be ideal.
We don't plan on making many changes other than enabling PV frontends
and backends.
next prev parent reply other threads:[~2011-11-30 11:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:53 [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions Stefano Stabellini
2011-11-29 21:29 ` Arnd Bergmann
2011-11-30 11:39 ` Stefano Stabellini [this message]
2011-11-30 13:03 ` Arnd Bergmann
2011-11-30 13:25 ` [Xen-devel] " Ian Campbell
2011-11-30 14:32 ` Arnd Bergmann
2011-11-30 14:51 ` Pawel Moll
2011-11-30 16:27 ` Ian Campbell
2011-11-30 18:15 ` Arnd Bergmann
2011-11-30 18:32 ` [Embeddedxen-devel] " Stefano Stabellini
2011-12-01 10:26 ` Ian Campbell
2011-12-01 15:10 ` [Android-virt] " Catalin Marinas
2011-12-01 15:42 ` Arnd Bergmann
2011-12-01 16:02 ` Catalin Marinas
2011-12-01 16:44 ` Arnd Bergmann
2011-12-01 16:57 ` Catalin Marinas
2011-12-01 15:52 ` Ian Campbell
2011-12-01 15:12 ` Stefano Stabellini
2011-12-01 10:34 ` Ian Campbell
2011-11-30 14:11 ` Catalin Marinas
2011-11-30 14:20 ` Stefano Stabellini
2011-12-16 15:43 ` [Xen-devel] " David Vrabel
2011-12-16 16:54 ` Catalin Marinas
2011-12-16 17:38 ` David Vrabel
2011-12-16 17:47 ` Catalin Marinas
[not found] ` <CAAhSdy3F1oUQP=f_Tig4_MnufwPRpNooZYW8_cSTAse7aOaDoA@mail.gmail.com>
2011-11-30 11:41 ` Stefano Stabellini
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=alpine.DEB.2.00.1111301053300.31179@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=linux-arm-kernel@lists.infradead.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