linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions
Date: Fri, 16 Dec 2011 15:43:57 +0000	[thread overview]
Message-ID: <4EEB673D.3040608@citrix.com> (raw)
In-Reply-To: <CAHkRjk48jHO19H04rf8252+v04hk9qSdKBrfYCqJsZyamVhMEw@mail.gmail.com>

On 30/11/11 14:11, Catalin Marinas wrote:
> On 30 November 2011 11:39, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>> 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.
> 
> Indeed, you don't really need LPAE. What you may need though is
> generic timers support for A15, it would allow less Hypervisor traps.
> For up-to-date architecture patches (well, development tree, not
> guaranteed to be stable), I would recommend this (they get into
> mainline at some point):
> 
> http://git.kernel.org/?p=linux/kernel/git/cmarinas/linux-arm-arch.git;a=summary
> 
> Either use master or just cherry-pick the branches that you are interested in.

Hi Catalin,

Which branches are required for the Versatile Express with the
Cortex-A15? I merged linux-arm-arch/arm-arch/vexpress in but I get a
instruction fault immediately after branching to __mmap_switched.

Is it not setting up the MMU correctly?

David

  parent reply	other threads:[~2011-12-16 15:43 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
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       ` David Vrabel [this message]
2011-12-16 16:54         ` [Xen-devel] " 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=4EEB673D.3040608@citrix.com \
    --to=david.vrabel@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;
as well as URLs for NNTP newsgroup(s).