linux-kernel - [Query] How to pass reboot arguments to secure firmware with PSCI spec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140801180652.72e722be@xhacker>
Date:	Fri, 1 Aug 2014 18:06:52 +0800
From:	Jisheng Zhang <jszhang@...vell.com>
To:	<catalin.marinas@....com>, <will.deacon@....com>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: [Query] How to pass reboot arguments to secure firmware with PSCI
 spec

Hi Catalin and Will,

I noticed that the following commit implement reboot via. PSCI SYSTEM_RESET
function. So my question is how to handle the reboot arguments? 


> static void psci_sys_reset(enum reboot_mode reboot_mode, const char *cmd)
> {
>       invoke_psci_fn(PSCI_0_2_FN_SYSTEM_RESET, 0, 0, 0);

How to pass cmd to secure firmware?

> }

Thanks in advance,
Jisheng

commit e71246a23acbc89e9cb4ebf1558d60e65733479f
Author: Ashwin Chaugule <ashwin.chaugule@...aro.org>
Date:   Thu Apr 17 14:38:41 2014 -0400

    PSCI: Add initial support for PSCIv0.2 functions
    
    The PSCIv0.2 spec defines standard values of function IDs
    and introduces a few new functions. Detect version of PSCI
    and appropriately select the right PSCI functions.
    
    Signed-off-by: Ashwin Chaugule <ashwin.chaugule@...aro.org>
    Reviewed-by: Rob Herring <robh@...nel.org>
    Acked-by: Catalin Marinas <catalin.marinas@....com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/