linux-kernel - Re: [RFC 7/8] fpga-region: add sysfs interface

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]

Date:   Wed, 15 Feb 2017 10:21:57 -0700
From:   Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:     Alan Tull <atull@...nel.org>
Cc:     Moritz Fischer <moritz.fischer@...us.com>,
        linux-kernel@...r.kernel.org, linux-fpga@...r.kernel.org
Subject: Re: [RFC 7/8] fpga-region: add sysfs interface

On Wed, Feb 15, 2017 at 10:14:20AM -0600, Alan Tull wrote:
> Add a sysfs interface to control programming FPGA.
> 
> Each fpga-region will get the following files which set values
> in the fpga_image_info struct for that region.  More files will
> need to be added as fpga_image_info expands.
> 
> firmware_name
> * writing a name of a FPGA image file to firmware_name causes the
>   FPGA region to write the FPGA
> 
> partial_config
> * 0 : full reconfiguration
> * 1 : partial reconfiguration

This is really a property of the bitfile. It would be really nice to
have a saner system for describing the bitfiles that doesn't rely on
so much out of band stuff.

Eg when doing partial reconfiguration it would be really sane to have
some checks that the full bitfile is the correct basis for the partial
bitfile.

It also seems link Zynq needs an encrypted/not encrypted flag..

I wonder if we should require a Linux specific header on the bitfile
instead? That would make the bitfile self describing at least.

Jason