From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759131Ab3EGIzr (ORCPT ); Tue, 7 May 2013 04:55:47 -0400 Received: from service87.mimecast.com ([91.220.42.44]:58505 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758940Ab3EGIzp convert rfc822-to-8bit (ORCPT ); Tue, 7 May 2013 04:55:45 -0400 Message-ID: <5188C18D.10103@arm.com> Date: Tue, 07 May 2013 09:55:41 +0100 From: Marc Zyngier User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: Giridhar Maruthy CC: "kgene.kim@samsung.com" , Russell King - ARM Linux , "linux-arm-kernel@lists.infradead.org" , "linux-samsung-soc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "kvmarm@lists.cs.columbia.edu" , Christoffer Dall Subject: Re: [RFC PATCH V2] ARM: EXYNOS: Fix hotplug when CPUs boot in HYP mode References: <1367905910-30913-1-git-send-email-giridhar.m@samsung.com> In-Reply-To: X-Enigmail-Version: 1.4.6 X-OriginalArrivalTime: 07 May 2013 08:55:42.0389 (UTC) FILETIME=[A793D650:01CE4B00] X-MC-Unique: 113050709554302601 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/05/13 06:54, Giridhar Maruthy wrote: > This patch is a modification from the Christoffer Dall's u-boot > patch. This is required to put the secondary processors in hyp > mode during cpu hotplug when u-boot is no longer alive. > > Marc Zyngier suggested this logic to go into firmware or, u-boot > putting a trampoline code into a page /memreserve/d by DT. But > this seemed to have a problem. Once the cpu is hotplugged in > runtime, the control is in ROM code and waits for event. > Kernel provides a return address in kernel to which the processor > jumps once it gets an event. If the control branches to the > trampoline code here, this trampoline code has no kernel return > address. > > Someone with better logic or better placement of this logic > elsewhere is welcome. What prevents you from writing the kernel address in the memreserved page? Some obvious location, like the last word of the page? You only have to do it once (from the boot CPU, for example). Or did I miss something else? M. -- Jazz is not dead. It just smells funny...