linux-kernel - Re: [PATCH v2] PCI/DOE: Expose the DOE protocols via sysfs

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: <20230804160542.GA19120@wunner.de>
Date:   Fri, 4 Aug 2023 18:05:42 +0200
From:   Lukas Wunner <lukas@...ner.de>
To:     Alistair Francis <alistair23@...il.com>
Cc:     Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Greg KH <gregkh@...uxfoundation.org>, bhelgaas@...gle.com,
        linux-pci@...r.kernel.org, alex.williamson@...hat.com,
        christian.koenig@....com, kch@...dia.com, logang@...tatee.com,
        linux-kernel@...r.kernel.org,
        Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH v2] PCI/DOE: Expose the DOE protocols via sysfs

On Fri, Aug 04, 2023 at 11:17:59AM -0400, Alistair Francis wrote:
> On Wed, Aug 2, 2023 at 6:52???PM Lukas Wunner <lukas@...ner.de> wrote:
> > I kind of like the approach of exposing a list which can be grep'ed,
> > even though it may go against the rule of having just one datum per
> > attribute.  I'd prefer a representation that's human-readable though,
> > e.g. "0001:01" for CMA-SPDM.
> 
> Yeah, it's my preferred method as well, but it's not going to be
> accepted upstream

How about procfs instead of sysfs?

No "single datum per file" rule over there.
PCI content goes into /proc/bus/pci/.
Already used by lspci to access config space.

Thanks,

Lukas