linux-kernel - RE: Out of mtrrs

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]

Message-ID: <7E82351C108FA840AB1866AC776AEC460B7FC128@orsmsx505.amr.corp.intel.com>
Date:	Fri, 29 Aug 2008 15:55:43 -0700
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"\"J.A. Magallón\"" <jamagallon@....com>,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: RE: Out of mtrrs



>-----Original Message-----
>From: linux-kernel-owner@...r.kernel.org
>[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of "J.A.
>Magallón"
>Sent: Friday, August 29, 2008 8:33 AM
>To: Linux-Kernel
>Subject: Out of mtrrs
>
>Hi all...
>
>I'm using the xorg intel driver, and drm/X report it has no free mtrrs
>in kernel to set up:
>
>one:~# cat /proc/mtrr
>reg00: base=0xfffe0000 (4095MB), size= 128KB: write-protect, count=1
>reg01: base=0xfffc0000 (4095MB), size= 128KB: uncachable, count=1
>reg02: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
>reg03: base=0x10000000 ( 256MB), size= 256MB: write-back, count=1
>reg04: base=0x1f800000 ( 504MB), size=   8MB: uncachable, count=1
>reg05: base=0x1f600000 ( 502MB), size=   2MB: uncachable, count=1
>reg06: base=0x1f500000 ( 501MB), size=   1MB: uncachable, count=1
>reg07: base=0x00000000 (   0MB), size= 128KB: uncachable, count=1
>
>dmesg:
>
>[drm] Initialized i915 1.6.0 20060119 on minor 0
>mtrr: no more MTRRs available
>
>one:/var/log# grep Linear x.log
>(--) intel(0): Linear framebuffer at 0x20000000
>
>I think X tries to get a mtrr at 0x20000000, but kernel has no free one
>to offer.
>
>Does this have any solution ?
>

One of the main motivations to add PAT support was this kind of errors.
With PAT aware X, this will no longer be a problem as X will map this
using PAT APIs.

Thanks,
Venki
--
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/