linux-kernel - Re: [patch] x86, voyager: fix ioremap

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:	Sun, 27 Apr 2008 16:04:07 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Miller <davem@...emloft.net>
CC:	jeff@...zik.org, James.Bottomley@...senPartnership.com,
	mingo@...e.hu, tglx@...utronix.de, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

David Miller wrote:
> I think this is a reasonable course of action.
> 
> That leaves one of Jeff's concerns, what to do with pci_iomap().  That
> was designed to give mappings with caching enabled, and as a result we
> probably should make it behave that way.

Yes, it should.  Just be clear that *that* is a semantic change over 
what the code currently does; it would appear that that is what the code 
is *trying* to do.

I believe on x86 it will still get clamped by the MTRRs, at least 
initially (I don't think we have flipped the default MTRR type to WB 
yet) but that would immediately change the behaviour on non-x86 
architectures.

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