linux-kernel - Re: uninline check

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 17 Jul 2007 18:46:54 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Jeff Dike <jdike@...toit.com>
cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	zippel@...ux-m68k.org, jdike@...aya.com, alan@...rguk.ukuu.org.uk,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: uninline check_signature()

On Tue, 17 Jul 2007, Jeff Dike wrote:
> On Tue, Jul 17, 2007 at 03:22:16PM +0200, Geert Uytterhoeven wrote:
> > I saw this patch went in.
> > 
> > iomap_copy.o ues the raw I/O memory accessors, so it truly depends on
> > CONFIG_HAS_IOMEM.
> 
> This works for UML.

Of course. UML (and s390) doesn't have (a need for) I/O memory because it uses
paravirtualization for all drivers.

M68k uses I/O memory for all I/O (hence it sets CONFIG_HAS_IOMEM), but
many m68k machines don't have PCI or ISA (hence it doesn't set
CONFIG_PCI resp. CONFIG_ISA).

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
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/