linux-kernel - Re: [PATCH] x86: mtrr cleanup for converting continuous to discrete

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: <86802c440805011420g78a6abberaae6b765663ed33b@mail.gmail.com>
Date:	Thu, 1 May 2008 14:20:04 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Gabriel C" <nix.or.die@...glemail.com>,
	"Mika Fischer" <mika.fischer@...pnet.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: mtrr cleanup for converting continuous to discrete - auto detect v2

On Thu, May 1, 2008 at 2:10 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> Yinghai Lu wrote:
>
> > On Thu, May 1, 2008 at 12:42 PM, H. Peter Anvin <hpa@...or.com> wrote:
> >
> > > Yinghai Lu wrote:
> > >
> > >
> > > > loop mtrr chunk_size and gran_size from 1M to 2G to find out optimal
> > > >
> > > value.
> > >  Why stopping at 2 GB?
> > >
> >
> > if you select 4g for chunk size, we don't need to convert that from
> > continuous to discrete to make X server driver happen.
> >
> > actually the code could support any chunk_size...
> >
> > for example: 16 g system
> > orginal:
> > 0-4g WB
> > 3.5g-4g UC
> > 4g-8g WB
> > 8g-16g WB
> > 16g-16.5g WB
> >
> > if you set chunk size to 16g, and gran size <= 512M
> > you will get
> > 0-16g WB
> > 3.5g-4g UC
> > 16g-16.5g WB
> >
> >
>
>  Yes, 16 GB systems are already mainstream; 32 GB is common, so I don't see
> any reason to stop at 2 GB.  Instead, it should loop up to the physical
> address size.

but our objective is that has 0xd0000000-0xe0000000 (WC) not to be
overlapping with other MTRR entries (UC)..

YH
--
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/