linux-kernel - Re: [PATCH] powernv: Add OCC driver to mmap sensor area

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: <87bmlqutq5.fsf@linux.vnet.ibm.com>
Date:   Mon, 02 Oct 2017 14:14:10 +1100
From:   Stewart Smith <stewart@...ux.vnet.ibm.com>
To:     Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
        mpe@...erman.id.au
Cc:     ego@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
        paulus@...ba.org,
        Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
        linuxppc-dev@...ts.ozlabs.org, akshay.adiga@...ux.vnet.ibm.com
Subject: Re: [PATCH] powernv: Add OCC driver to mmap sensor area

Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com> writes:
> This driver provides interface to mmap the OCC sensor area
> to userspace to parse and read OCC inband sensors.

Why?

Is this for debug? If so, the existing exports interface should be used.

If there's actual sensors, we already have two ways of exposing sensors
to Linux: the OPAL_SENSOR API and the IMC API.

Why this method and not use the existing ones?

-- 
Stewart Smith
OPAL Architect, IBM.