Frans Pop wrote:Frans, With or with out pat, in the recent kernels (like 2.6.26-rc4/rc5 etc), ioremap() uses UC- and PCI mmap of /sys/devices/pci.../resource (used by X) uses UC- And fb_mmap() also uses UC-. It's interesting that you don't see this artifact with "nopat". Essentially with or with out pat enabled, we use the same memory attributes. So depending on the MTRR setup (set by X server), effective memory attribute across different mappings should be same (which is UC- or WC with mtrr). Can you also check, if there is any impact with kernel boot param for vesafb "mtrr:3"? thanks, suresh --
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Christoph Hellwig | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scan... |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Emmanuel Dreyfus | fixing send(2) semantics (kern/29750) |
| Christos Zoulas | Re: Melting down your network [Subject changed] |
| Juan RP | Changing the I/O scheduler on-the-fly |
| Emmanuel Dreyfus | Re: fixing send(2) semantics (kern/29750) |
