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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53DB6A18.5050904@arm.com>
Date:	Fri, 01 Aug 2014 11:21:12 +0100
From:	Sudeep Holla <sudeep.holla@....com>
To:	Jisheng Zhang <jszhang@...vell.com>,
	Catalin Marinas <Catalin.Marinas@....com>,
	Will Deacon <Will.Deacon@....com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Sudeep Holla <sudeep.holla@....com>
Subject: Re: [Query] How to pass reboot arguments to secure firmware with
 PSCI spec



On 01/08/14 11:06, Jisheng Zhang wrote:
> 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?
>

What reboot arguments do you want to handle ?

>
>> 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?
>

What cmd do you want to pass ? The function id is already handled. What
else do you want to pass ?

If you see PSCI v0.2 spec, the SYSTEM_RESET and SYSTEM_SHUTDOWN takes no
parameters.

Regards,
Sudeep

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ