On Wed, Jun 16, 2021 at 04:35:32PM +0100, Luís Mendes wrote: > Hi Greg, > > Replies follow below. > > Thanks, > Luis > > On Wed, Jun 16, 2021 at 3:28 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Wed, Jun 16, 2021 at 02:40:13PM +0100, Luís Mendes wrote: > > > Dear Linux kernel maintainers/developers, > > > > > > > > > I would like to discuss a modern alternate to Sysctl syscall and its > > > feasibility for armhf and aarch64 for supporting ioperm, iopl, inb, > > > outb and their siblings APIs emulation in Glibc, or even on an > > > external library to provide such sys/io.h API compatibility with > > > x86_64. > > > > > > The advantage of having ioperm, iopl, inb and outb emulation for armhf > > > > What is "armhf"? > > armhf is a common acronym for arm 32-bits with an hardware floating point unit. > > > > > > and aarch64 is that they can provide cross-compilation ability of > > > x86_64 applications and constitutes an easy and practical API for > > > simple I/O. This was not only useful for old ISA cards as it is today > > > for PCIe cards with I/O space, like I/O cards, LPT Parallel interface > > > cards, as well as many other cards that may have PCIe I/O space > > > (network cards, etc). PCIe LPT interface cards as well as > > > multi-function cards are still widely available, just search ebay or > > > amazon, and many suggestions will pop up. > > > > > > I know for instance that LPT interface cards have their ppdev driver > > > which already provides an ioctl interface to access the card I/O > > > lines, but it is not performant for applications like bit-banging an > > > LPT card to load firmware into a micro-controller, for instance, > > > Microchip/ATMEL 8-bit micro-controllers. Plus the ioperm, iopl, inb, > > > outb has a simpler API for doing simple interactions with the I/O > > > space, like is the case with the IO lines of the LPT parallel > > > interface card. > > > > You should never use iopl, inb, and outb on modern systems, sorry. > > Please use the bus-specific ways to access the devices needed, or mmap > > the needed memory ranges into your program and directly access them that > > way if you know what you are doing for your specific hardware type (the > > UIO api provides this for you.) > > I understand that. It is just that since it is allowed and has been > allowed on x86_64 for a long time, and is in use by many > applications... Was it really in use by any arm systems in a way that worked? IO ports were semi-standardized in some places on x86, but NEVER on arm, so what programs used them that need to do so in a cross-platform way? > so that for simplicity and cross-compatibility that it > could be made available once again for armhf as it was up until kernel > 5.5 and the glibc version available at that time. But the backing hardware is so different, why does it need to be "compatible"? What programs are using this on arm that expect to do so in a way that would also work on x86? What hardware accesses are they wanting to do? > If the roadmap for user applications is towards UIO api, while > deprecating the inb, outb, I will have a look at that API for armhf. I > do know that mmap will not work for accessing PCIe IO spaces for > armhf, or at least not consistently across kernel versions, from my > experience. It only worked for PCIe memory regions. I will re-check > all that. mmap works with the UIO api, please look into that, it's what it is there for when you know _EXACTLY_ what hardware you have and want to access it directly from userspace. thanks, greg k-h
