From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2 of 6] arm: Move hyp-mode entry code out of line
Date: Fri, 1 Jun 2012 07:29:39 +0100 [thread overview]
Message-ID: <1338532179.14877.39.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <4FC7A24B.3010506@citrix.com>
On Thu, 2012-05-31 at 17:54 +0100, David Vrabel wrote:
> On 31/05/12 17:40, Tim Deegan wrote:
> > # HG changeset patch
> > # User Tim Deegan <tim@xen.org>
> > # Date 1338482127 -3600
> > # Node ID 05447f395c91029fb732142e36788cfa92374045
> > # Parent 25d389d891c5a2a3009258ef7261379a9ad97746
> > arm: Move hyp-mode entry code out of line.
> >
> > This code is grottier than the rest of the start-of-day code and
> > very specific to the software model we're developing on.
> > Segregate it accordingly, by putting it in its own file.
>
> I've been vaguely thinking about writing a stub-bootloader to do this
> and provide the DTB (instead of having to link it with Xen). Is this
> something that would be useful?
Rather than a new stub-bootloader we should switch over to using the
same boot-wrapper.git as Linaro and KVM are using[0], and perhaps
enhancing it to meet our needs.
One benefit of that is that when they come to do stuff on real hardware
we will already be somewhat aligned with something which looks a bit
like a bootloader so it should be easier for us to transition too.
It also has other benefits like enabling us to use semi-hosting to pull
the files off the host filesystem.
Ian.
[0] http://git.linaro.org/gitweb?p=arm/models/boot-wrapper.git;a=summary
next prev parent reply other threads:[~2012-06-01 6:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 16:39 [PATCH 0 of 6] ARM: various boot-time tidying Tim Deegan
2012-05-31 16:39 ` [PATCH 1 of 6] arm: More interrupt setup at start-of-day for secondary CPUs Tim Deegan
2012-05-31 16:40 ` [PATCH 2 of 6] arm: Move hyp-mode entry code out of line Tim Deegan
2012-05-31 16:54 ` David Vrabel
2012-06-01 6:29 ` Ian Campbell [this message]
2012-05-31 16:40 ` [PATCH 3 of 6] arm: avoid memory write in switch to Hyp mode Tim Deegan
2012-06-01 9:07 ` Ian Campbell
2012-06-01 9:18 ` Tim Deegan
2012-05-31 16:40 ` [PATCH 4 of 6] arm: missing __init annotation Tim Deegan
2012-05-31 16:40 ` [PATCH 5 of 6] arm: allow ourselves access to all coprocessors in non-secure mode Tim Deegan
2012-05-31 16:40 ` [PATCH 6 of 6] arm: Enable VFP at boot Tim Deegan
2012-06-01 9:20 ` Ian Campbell
2012-06-01 9:29 ` Tim Deegan
2012-06-01 9:37 ` Ian Campbell
2012-06-01 9:31 ` [PATCH 0 of 6] ARM: various boot-time tidying Ian Campbell
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=1338532179.14877.39.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=david.vrabel@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).