linux-kernel - Re: [RFC 1/3] powernv/cpuidle : Support for pre-entry and post exit of stop state in firmware

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: <1588035100.usm3gb816q.astroid@bobo.none>
Date:   Tue, 28 Apr 2020 11:08:54 +1000
From:   Nicholas Piggin <npiggin@...il.com>
To:     Abhishek Goel <huntbag@...ux.vnet.ibm.com>,
        linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org
Cc:     ego@...ux.vnet.ibm.com, mikey@...ling.org, mpe@...erman.id.au,
        oohall@...il.com, psampat@...ux.ibm.com, svaidy@...ux.ibm.com,
        skiboot@...ts.ozlabs.org
Subject: Re: [RFC 1/3] powernv/cpuidle : Support for pre-entry and post exit
 of stop state in firmware

Thanks for picking this up and pushing it along. I do plan to come back 
and take another look at it all, but what we do need to do first is get 
a coherent approach to this proposed new calling convention and OS ops.

It's fine to work on this in the meantime, but to start merging things
my idea is:

- OPAL must leave r13-r15 untouched for the OS.
- OS ops are made available only for a "v4" OS that uses the new
  calling convention, including kernel stack.
- OS ops baseline (all OSes must provide) will be console / printk 
  facility, trap handling and crash/symbol decoding on behalf of OPAL,
  and runtime virtual memory.

Other OS ops features can be added in the versioned structure, including 
this.

I'm trying to get back to cleaning these things up and start getting 
them merged now. Any comments or review on those would be helpful.

Thanks,
Nick