From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Chen Baozi <baozich@gmail.com>,
Andrii Anisov <andrii.anisov@globallogic.com>,
Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen/arm: Support kick cpus and switch to hypervisor for the OMAP5
Date: Thu, 15 Aug 2013 13:10:49 +0100 [thread overview]
Message-ID: <1376568649.9273.157.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <CAPnVf8wpNVJ3M2sO01vcNv+Rt1C6S5xjZT7xf9Zf_biANrvcxg@mail.gmail.com>
On Thu, 2013-08-15 at 11:03 +0100, Julien Grall wrote:
> I'm not in favor to extend this assembly file (see full explanation on
> Ian's mail http://lists.xen.org/archives/html/xen-devel/2013-06/msg01231.html).
>
> Some ideas to remove this file:
> - Move kick cpus code later (ie in C code) and per platform
> - Use U-boot or a bootwrapper to switch CPUs to HYP mode
Strangely enough I was just working on this bootwrapper stuff earlier in
the week (I just sent another mail about it). It's not there for the
kick cpu stuff yet but I have some ideas...
I expect we will actually want to do both of the things you suggest. If
the firmware does not leave secondary CPUs in a state where they can be
kicked from NS HYP mode or cause them to start in NS HYP then we will
need boot-wrapper to paper over this and make it look that way to Xen.
Then the kick cpus code in Xen can be moved later, hopefully as late as
the existing cpu_up code, although this might need some rejigging of how
we do the pagetable bootstrapping.
Ian.
prev parent reply other threads:[~2013-08-15 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:16 [PATCH] xen/arm: Support kick cpus and switch to hypervisor for the OMAP5 Chen Baozi
2013-08-15 9:33 ` Tim Deegan
2013-08-15 9:34 ` Andrii Anisov
2013-08-15 9:48 ` Chen Baozi
2013-08-15 11:10 ` Andrii Anisov
2013-08-15 11:23 ` Chen Baozi
2013-08-15 11:27 ` Andrii Anisov
2013-08-15 11:23 ` Andrii Anisov
2013-08-15 11:28 ` Chen Baozi
[not found] ` <CAGQvs6jN8a7j8J5=+PNA_8Cc2jx22Gom86EXc9KdD=xf3NFiLA@mail.gmail.com>
[not found] ` <AFEC4CA5-C8E7-4D08-97DC-1C4C95AD03F9@gmail.com>
2013-08-15 12:01 ` Andrii Anisov
2013-08-15 10:03 ` Julien Grall
2013-08-15 11:19 ` Chen Baozi
2013-08-15 11:40 ` Julien Grall
2013-08-15 11:48 ` Chen Baozi
2013-08-15 12:10 ` Ian Campbell [this message]
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=1376568649.9273.157.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=baozich@gmail.com \
--cc=julien.grall@linaro.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).