linux-kernel - Re: PCI userland access non-mmap APIs, kernel access to legacy space

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

Date:	Tue, 19 Jun 2007 11:17:51 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Jesse Barnes <jesse.barnes@...el.com>
Cc:	linux-pci@...ey.karlin.mff.cuni.cz,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Matthew Wilcox <matthew@....cx>, Greg KH <greg@...ah.com>,
	Ian Romanick <idr@...ibm.com>, Jeff Garzik <jgarzik@...ox.com>,
	Kyle McMartin <kyle@...artin.ca>
Subject: Re: PCI userland access non-mmap APIs, kernel access to legacy
	space


> But adding read/write is fine with me.  In fact, having read/write hooks 
> for the memory backed resource files is also nice, since it makes 
> dealing with them on the command line a bit easier.

Plan is to use iomap so I get both IO and MMIO for (almost) free :-)

> > Also, while at it, I would like to introduce a pair of in-kernel
> > interfaces:
> 
> What's the other half of the pair?

Heh, indeed, there is none, I initially had a separate function for mem
and for io and at the last minute though "ugh, let's just use a struct
resource !" :-)

> Yeah, sounds like a good additional abstraction for that interface.  
> Should make porting it to other arches easier (I talked with kyle about 
> this last week, so maybe this'll give him motivation to do it for 
> parisc).

Ok, good. I'll do some code asap.

Ben.


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