From: "Michael S. Zick" <lkml@morethan.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [Bug Fix]: Do 32-bit table calculations in pre-processor
Date: Fri, 3 Jul 2009 14:41:01 -0500 [thread overview]
Message-ID: <200907031441.04604.lkml@morethan.org> (raw)
In-Reply-To: <4A4E58AC.7010905@zytor.com>
On Fri July 3 2009, H. Peter Anvin wrote:
> Michael S. Zick wrote:
> >>
> >> The PGTABLE reservation seems much too big. I think 1 page should be
> >> sufficient for a system with large pages. Even if not, 0x6d000 is way
> >> too large. And they symptoms of failing to reserve the initial
> >> pagetable are pretty non-subtle.
> >>
> >
> > Random system halts, deadlocks with interrupts disabled?
> > Yup, that sounds familiar.
> >
> > If I ever get more than a stopped machine with a glowing power light;
> > I will be certain to share.
> >
>
> Let's see... on a non-PSE system we may need one PDE and one PTE page
> per 4 MB, up to 1 GB, for a total of 256 pages or 1 MB of memory, so in
> that sense 0x6d000 (109 pages) doesn't sound at all unreasonable
> (non-PSE system with 512 MB of RAM?)
>
> However, we shouldn't have to do this kind of hacks with
> MAPPING_BEYOND_END, and we *certainly* shouldn't do it by implicitly
> hard-coding the value of PAGE_SHIFT.
>
Good point: (1<<(32-PAGE_SIFT)) would handle other than 4k pages.
I just hardcoded it as a working example of the change from setting
the page table size by design rather than numeric error.
And yes, it has 512Mbyte of ram, so 1/2Mbyte page table sounds right to me.
Mike
> -hpa
>
next prev parent reply other threads:[~2009-07-03 19:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 18:14 [Bug Fix]: Do 32-bit table calculations in pre-processor Michael S. Zick
2009-07-03 18:27 ` Andi Kleen
2009-07-03 18:38 ` Michael S. Zick
2009-07-03 19:08 ` Jeremy Fitzhardinge
2009-07-03 19:13 ` Michael S. Zick
2009-07-03 19:30 ` Jeremy Fitzhardinge
2009-07-03 20:03 ` Michael S. Zick
2009-07-03 18:56 ` Jeremy Fitzhardinge
2009-07-03 18:57 ` Jeremy Fitzhardinge
2009-07-03 19:03 ` Michael S. Zick
2009-07-03 19:11 ` Jeremy Fitzhardinge
2009-07-03 19:18 ` H. Peter Anvin
2009-07-03 19:46 ` Michael S. Zick
2009-07-03 20:00 ` H. Peter Anvin
2009-07-03 19:14 ` H. Peter Anvin
2009-07-03 19:41 ` Michael S. Zick [this message]
2009-07-03 19:48 ` H. Peter Anvin
2009-07-03 20:38 ` Michael S. Zick
2009-07-03 20:40 ` H. Peter Anvin
2009-07-03 21:02 ` Michael S. Zick
2009-07-03 22:33 ` H. Peter Anvin
2009-07-04 0:05 ` Michael S. Zick
2009-07-04 0:11 ` H. Peter Anvin
2009-07-03 22:01 ` Michael S. Zick
2009-07-04 13:23 ` Michael S. Zick
2009-07-03 19:33 ` Jeremy Fitzhardinge
2009-07-03 20:07 ` Yinghai Lu
2009-07-03 20:08 ` Yinghai Lu
2009-07-03 20:48 ` Michael S. Zick
2009-07-03 20:45 ` Michael S. Zick
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=200907031441.04604.lkml@morethan.org \
--to=lkml@morethan.org \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.