From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] xen/arm: Support kick cpus and switch to hypervisor for the OMAP5 Date: Thu, 15 Aug 2013 13:10:49 +0100 Message-ID: <1376568649.9273.157.camel@hastur.hellion.org.uk> References: <1376558212-4783-1-git-send-email-baozich@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Chen Baozi , Andrii Anisov , Xen Developer List List-Id: xen-devel@lists.xenproject.org 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.