linux-kernel - Re: Intel-Quad on GA-P35-S3 motherboard with 4*2GB

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:	Tue, 18 Sep 2007 10:50:09 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Wojciech Kromer <wojciech.kromer@....com.pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Intel-Quad on GA-P35-S3 motherboard with 4*2GB

On Tue, Sep 18, 2007 at 04:35:43PM +0200, Wojciech Kromer wrote:
> Yes, it's a bit strange, but there should be a way to configure it in linux.
> I found only memmap option which does selection of regions, but not 
> remapping.

No it is entirely the BIOS's job to do that.  It would be very hard for
linux to safely change that.

> I have 64 bit compilation of course.

So in your case it would have been just fine with a simpler mapping.

> It's Intel-quad, so there are 4 CPUs.

Weird.  The message about the MTRR on all the CPUs not maching sound
like a strange bios bug.  Are you running the latest bios version?

> It's in prevoius mail:
> 
> # dmesg|grep BIOS-e820
> >BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> >BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> >BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> >BIOS-e820: 0000000000100000 - 000000009fee0000 (usable)
> >BIOS-e820: 000000009fee0000 - 000000009fee3000 (ACPI NVS)
> >BIOS-e820: 000000009fee3000 - 000000009fef0000 (ACPI data)
> >BIOS-e820: 000000009fef0000 - 000000009ff00000 (reserved)
> >BIOS-e820: 00000000c0000000 - 00000000c4000000 (reserved)
> >BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> >BIOS-e820: 0000000100000000 - 0000000260000000 (usable)

Looks to match the MTRR setup at least.  So how much ram does the kernel
actually want to use?

--
Len Sorensen
-
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/