linux-kernel - Re: [PATCH] trim memory not covered by WB 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: <Pine.LNX.4.64.0706150634320.26433@p34.internal.lan>
Date:	Fri, 15 Jun 2007 06:34:54 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Pim Zandbergen <P.Zandbergen@...roscoop.nl>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trim memory not covered by WB MTRRs



On Fri, 15 Jun 2007, Pim Zandbergen wrote:

> Justin Piszcz wrote:
>> That's strange, I guess different chipsets 'chew' up different amounts of 
>> memory OR you have your DVT(?) (video-card memory/aperature) set to 256MB? 
>> I have mine set to 128MB, in top:
>> 
>> Mem:   8039576k total,  6187304k used,  1852272k free,      696k buffers
> Me:
> Mem:   7416672k total,   378988k used,  7037684k free,    13592k buffers
>
>> What type of memory are you using 
> 2x Kingston KVR667D2N5K2/4G
>> and what is your DVT set to?
> GigaByte's BIOS config options of the onboard graphics controller are
> very limited compared to those on your Intel motherboard.
>
> I can only choose the graphics buffer size, between
> "1MB+1~2MB for GTT" or "8MB+1~2MB for GTT".
> I chose the latter. The POST says 9MB are taken for video.
>
> Not that it matters much, as the current i810/intel xorg driver does
> not yet support the GMA3100, so I'm using the vesa driver.
>
> Thanks,
> Pim
>

I use the exact same memory model.  So it must be the difference in BIOS 
MTRR/E820 memory mappings.

Justin.
-
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/