From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756858AbcHWMgW (ORCPT ); Tue, 23 Aug 2016 08:36:22 -0400 Received: from mail-oi0-f51.google.com ([209.85.218.51]:34782 "EHLO mail-oi0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754667AbcHWMgU (ORCPT ); Tue, 23 Aug 2016 08:36:20 -0400 Date: Tue, 23 Aug 2016 07:36:17 -0500 From: Andy Gross To: Lorenzo Pieralisi Cc: Stephen Boyd , Will Deacon , linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, Catalin Marinas , Srinivas Kandagatla , stanimir.varbanov@linaro.org, linux-kernel@vger.kernel.org, patches@linaro.org, Bjorn Andersson , sudeep.holla@arm.com Subject: Re: [PATCH 1/2] arm64: kernel: Add SMC Session ID to results Message-ID: <20160823123617.GD30923@hector.attlocal.net> References: <1471672274-19317-1-git-send-email-andy.gross@linaro.org> <1471672274-19317-2-git-send-email-andy.gross@linaro.org> <20160822134313.GJ14680@arm.com> <20160822140246.GA30923@hector.attlocal.net> <20160822145326.GK14680@arm.com> <20160823003831.GN6502@codeaurora.org> <20160823103841.GD8724@red-moon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160823103841.GD8724@red-moon> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 23, 2016 at 11:38:41AM +0100, Lorenzo Pieralisi wrote: > On Mon, Aug 22, 2016 at 05:38:31PM -0700, Stephen Boyd wrote: > > [...] > > > This all comes about because the firmware generates a session id > > for the SMC call and jams it in x6. The assembly on the > > non-secure side is written with a tight loop around the smc > > instruction so that when the return value indicates > > "interrupted", x6 is kept intact and the non-secure OS can jump > > back to the secure OS without register reloading. Perhaps > > referring to x6 as result value is not correct because it's > > really a session id that's irrelevant once the smc call > > completes. > > Sorry I missed this bit. The session id is _generated_ by secure > firmware (probably only when the value passed in x6 == 0 (?)) > and actually returned to the caller so that subsequent (interrupted) > calls can re-issue the same value, is that correct ? Yes, that is exactly what is going on. You always pass in 0 for the first call. If the call is interrupted and needs to be re-executed, you will get a specific result in a0 that tells you to redo the call using x6 as your session ID. > > If that's the case the value in x6 is a result value from an SMCCC > perspective and your current FW is not SMCCC compliant. Should we then write our own ASM snippet to do exactly what we want? It'd be the same as the arm_smccc except with the extra str. I'm ok with that, I was just hoping to leverage the existing smccc code. The quirk also works well, except it costs everyone else 1 load and compare. Regards, Andy