From: "J.A. Magallón" <jamagallon@ono.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Intel driver vs MTRRs conflict
Date: Wed, 18 Feb 2009 23:50:22 +0100 [thread overview]
Message-ID: <20090218235022.1b5aba55@one.home> (raw)
In-Reply-To: <499B64DC.2060600@zytor.com>
On Tue, 17 Feb 2009 17:31:08 -0800, "H. Peter Anvin" <hpa@zytor.com> wrote:
> J.A. Magallón wrote:
> >
> > As I said, everything works. And even fast for the kind of machine, it's an
> > Aspire One and gears gives 740 fps, and video playback is pretty smooth.
> > But perhaps it would be faster if X could get that mtrr it claims ?
> >
>
Sorry for the delay...
> Which CPU?
>
Atom N270, 1.60GHz, hyperthreaded. 512Kb cache
I have realized that I boot with video=intelfb:mtrr,ywrap.
Could this be interferring ?
Things in syslog I think are relevant:
Feb 17 23:45:47 one klogd: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 17 23:45:47 one klogd: original variable MTRRs
Feb 17 23:45:47 one klogd: reg 0, base: 4194176KB, range: 128KB, type WP
Feb 17 23:45:47 one klogd: reg 1, base: 4194048KB, range: 128KB, type UC
Feb 17 23:45:47 one klogd: reg 2, base: 0GB, range: 256MB, type WB
Feb 17 23:45:47 one klogd: reg 3, base: 256MB, range: 256MB, type WB
Feb 17 23:45:47 one klogd: reg 4, base: 504MB, range: 8MB, type UC
Feb 17 23:45:47 one klogd: reg 5, base: 502MB, range: 2MB, type UC
Feb 17 23:45:47 one klogd: reg 6, base: 501MB, range: 1MB, type UC
Feb 17 23:45:47 one klogd: reg 7, base: 0GB, range: 128KB, type UC
Feb 17 23:45:47 one klogd: total RAM coverred: 501M
Feb 17 23:45:47 one klogd: Found optimal setting for mtrr clean up
Feb 17 23:45:47 one klogd: gran_size: 64K ^Ichunk_size: 16M ^Inum_reg: 4 ^Ilose cover RAM: 0G
Feb 17 23:45:47 one klogd: New variable MTRRs
Feb 17 23:45:47 one klogd: reg 0, base: 0GB, range: 512MB, type WB
Feb 17 23:45:47 one klogd: reg 1, base: 501MB, range: 1MB, type UC
Feb 17 23:45:47 one klogd: reg 2, base: 502MB, range: 2MB, type UC
Feb 17 23:45:47 one klogd: reg 3, base: 504MB, range: 8MB, type UC
Feb 17 23:45:47 one klogd: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 17 23:45:47 one klogd: kernel direct mapping tables up to 1f500000 @ 7000-c000
...
Feb 17 23:45:47 one klogd: vesafb: framebuffer at 0x20000000, mapped to 0xdfd80000, using 1875k, total 7872k
Feb 17 23:45:47 one klogd: vesafb: mode is 800x600x16, linelength=1600, pages=7
Feb 17 23:45:47 one klogd: vesafb: scrolling: redraw
Feb 17 23:45:47 one klogd: vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Feb 17 23:45:47 one klogd: Console: switching to colour frame buffer device 100x37
Feb 17 23:45:47 one klogd: fb0: VESA VGA frame buffer device
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2009.1 (Cooker) for x86_64
Linux 2.6.27.5-desktop-1mnb (gcc 4.3.2 (GCC) #1 Sun Nov
prev parent reply other threads:[~2009-02-18 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 23:20 Intel driver vs MTRRs conflict J.A. Magallón
2009-02-18 1:31 ` H. Peter Anvin
2009-02-18 22:50 ` J.A. Magallón [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090218235022.1b5aba55@one.home \
--to=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox