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:	Wed, 6 Jun 2007 18:26:55 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Jesse Barnes <jesse.barnes@...el.com>
cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs



On Wed, 6 Jun 2007, Jesse Barnes wrote:

> On Wednesday, June 6, 2007 3:13 pm Justin Piszcz wrote:
>> On Wed, 6 Jun 2007, Jesse Barnes wrote:
>>> On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
>>>> Mem:   8039620k total,  7936472k used,   103148k free,      708k
>>>> buffers Mem:   8039608k total,   969380k used,  7070228k free,
>>>> 1232k buffers
>>>>
>>>> I am curious, why does the patch != the mem=8832M?
>>>
>>> I'm not sure... can you post your e820 map from boot and the
>>> contents of /proc/mtrr?  Maybe my patch is trimming off a few too
>>> many pages, or maybe 8832M isn't quite right and actually ends up
>>> leaving you with a few uncached pages.
>>>
>>> Jesse
>>
>> Unless you know of some other way I can capture the output, it only
>> starts showing the dmesg from [50..] onward.
>
> Did you boot the kernel with the 'debug' option?  Maybe your dmesg
> buffer is too small (there's a config option for that iirc).
>
> Jesse
>

Nope, I booted with only netconsole= options.  I have a lot of HW in the 
box and I guess the buffer is too small.  Not sure where to change it in 
the kernel.  Looking..
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ