linux-kernel - Re: [PATCH v5 1/4] uio: add ioctl support

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>] [day] [month] [year] [list]

Date:	Wed, 7 Oct 2015 22:00:58 +0300
From:	Vlad Zolotarov <vladz@...udius-systems.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	bruce.richardson@...el.com, linux-kernel@...r.kernel.org,
	hjk@...sjkoch.de, avi@...udius-systems.com, corbet@....net,
	alexander.duyck@...il.com, gleb@...udius-systems.com,
	mst@...hat.com
Subject: Re: [PATCH v5 1/4] uio: add ioctl support

On 10/07/15 21:05, Stephen Hemminger wrote:
>
> Thinking more of a custom filesystem like configfs
>

Why would configfs be better?
I imagine the final files layout as follows: uioY device that would have 
enabled MSI-X would have a separate uio/uioY/msix/irqZ for each IRQ[Z] 
MSI-X vector.
And this under the same roof with uio/uioY/maps/mapK files.

We then need to implement the write() method for irqZ files so that it 
would accept the eventfd and bind it (or unbind if the value is negative).
We may also make read() return not only the currently bond eventfd 
descriptor but also the corresponding MSI-X IRQ number.

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